Step 1
Step 2
Step 3
Step 4
Step 1
Attestation
Overview

In order to access Medicare Parts A and B claims data, a Prescription Drug Plan (PDP) Sponsor must first complete the attestation process for each of their participating Prescription Drug Plan (PDP) Sponsor contracts. During this process, a Prescription Drug Plan (PDP) Sponsor formally reviews and agrees to comply with the Claims Data Usage Protocols . These protocols regulate how their organization may or may not use the Medicare claims data provided by the AB2D API, including limitations associated with the reuse and disclosure of the data.

attestation
What type of organizations can attest?
expand_more
Stand-alone Medicare Part D Plan (PDP) sponsors (PACE and MAPD are not eligible).
Who can attest?
expand_more
  • Attestation must be performed by a Medicare Part D Plan (PDP) Sponsor CEO, CFO, or COO.
  • An Attestor must hold an active CEO, CFO, or COO role within their organization.
  • Part D Plan (PDP) sponsors can have multiple executives attest to each of their participating contracts. This is considered best practice and is strongly encouraged.
How does attestation affect claims data?
expand_more
  • Attested Part D Plan (PDP) sponsors are able to retrieve claims data for active plan enrollees from the date of attestation onwards. Claims data prior to the attestation date will not be provided.
  • Participating Part D Plan (PDP) sponsors must have an active Attestor at all times and will not receive data during periods where the (PDP) sponsor does not have an active Attestor. Data access will be restored once another active CEO, CFO, or COO attests. We highly recommend that Part D Plan (PDP) sponsors have multiple executives attest to contracts to reduce the risk of lapses in access to data based on attestation status.
How to initially attest
expand_more
  1. Log into HPMS
  2. Click on “Claims Data Attestation” (under Contract Management)
  3. Select the checkbox(es) next to one, multiple, or all contracts within the 'Contracts Without Attestation' window
  4. Click on the "Attest" button
  5. Review the Claims Data Usage Protocols
  6. Select the checkbox next to: "I hereby certify that I understand the attestation above"
  7. Click "Confirm"
How to add additional attesters
expand_more
  1. Log into HPMS
  2. Click on "Claims Data Attestation" (under Contract Management)
  3. Select the checkbox(es) next to one, multiple, or all contracts within the 'Attested Contract' window
  4. Click on the "Re-Attest" button
  5. Review the Claims Data Usage Protocols
  6. Select the checkbox next to: "I hereby certify that I understand the attestation above"
  7. Click "Confirm"
Step 2
Appoint an "AB2D Operations Specialist"
Overview
After attesting, Part D Plan (PDP) Sponsors will need to assign an "AB2D Data Operations Specialist" to act as their organization’s primary technical point of contact.
The "AB2D Data Operations Specialist"
check
Is a technical employee at the Part D Plan (PDP) sponsor that has the authority to access and view the data provided by the API.


check
Will be technically savvy enough to connect to the AB2D API and retrieve claims data from our Sandbox and Production environments.


check
Will need to provide static IP address(es) and or CIDR ranges for the network/system that is going to be accessing the AB2D API.
data-specialist
Step 3
Retrieve Synthetic Claims Data
Overview
The Sandbox is a test environment that enables anyone to interact with the AB2D API and retrieve synthetic Medicare Parts A and B claims data. A Part D Plan (PDP) sponsor “AB2D Data Operations Specialist” will need to verify they have retrieved synthetic claims data successfully in order to gain access to production data.
Connecting to the Sandbox
We are providing three different ways to retrieve synthetic claims data:
  1. Postman and Swagger User Guide
  2. Curl User Guide
  3. Advanced User Guide
Verifying Synthetic Data Retrieval
  • The "AB2D Data Operations Specialist" will need to record the Log ID from jobs that were executed successfully; retrieving synthetic claims data in our Sandbox environment.
  • The "AB2D Data Operations Specialist" will provide the Log ID from one of these jobs to the AB2D Team.
programmer
Step 4
Accessing Claims Data in Production
Overview
Once a connection to the sandbox environment has been verified, the AB2D team will work directly with the Part D Plan (PDP) sponsors to deliver production credentials. The Part D Plan (PDP) sponsor will use the production credentials to retrieve actual Medicare Parts A and B Claims Data from our production environment.
Delivering Production Credentials
  • After the "AB2D Data Operations Specialist" has provided their IP addresses and verified synthetic data retrieval, the AB2D team will work directly with the Attestor(s) to provide their organization’s production credentials.
production
Retrieving Actual Claims Data
  • Using the production credentials, the Part D Plan (PDP) sponsors will connect to the AB2D API in our production environment to download actual Medicare Parts A and B claims data.
  • The AB2D team will work closely with the organization and its "AB2D Data Operations Specialist" to answer any questions or troubleshoot any issues they have connecting to the AB2D API.