The Centers for Medicare and Medicaid Services (CMS) Data at the Point of Care (DPC) API is currently in a pilot phase in which a limited number of users can access Medicare Fee-For-Service claims data through the API once their solution has been approved for production. This pilot program promotes the industry-standard HL7 Fast Healthcare Interoperability Resources (FHIR), specifically the Bulk FHIR specification.
Since the pilot is a learning experience for both CMS and users, participants in the pilot program may encounter breaking changes to code, iterations to regulations, and will be asked to participate in research sessions with CMS as the program continues to grow and evolve.
Connect with your Health IT team
Health IT Implementers:
If interested in implementing DPC on behalf of healthcare organizations, please begin by following the steps below.
1. Test the API
Health IT implementers are asked to test and develop a solution in the sandbox environment using synthetic data before applying for production credentials.
After testing and developing a DPC solution in the sandbox environment:
a. Join the Production Pilot Queue
When you're ready to request production access, please email the DPC team. You will receive a follow-up email from the DPC team when it is your turn to onboard. Depending on the backlog of organizations, this may mean that your organization will sit in the queue for a few weeks before it is your turn to onboard.
Please do not plan to fill out the application unless your organization has tested your solution in sandbox and is able to share security documentation with CMS.
b. Schedule a Demonstration with the DPC team
In the email following up on your application to the pilot program, you will receive a link to schedule a demonstration of your DPC solution with the DPC team.
Please be prepared to answer the following questions:
Walk us through the end-to-end workflow. How will practitioners see the data in your system?
How frequently will your organization make requests to the API? How quickly will you need the data returned?
What is your retry logic for requests that fail?
What will you do if you do not receive data back for some of the requested patients?
How will the data be used? For example, are you using the data for aggregate population reporting, or for insights into the needs of an individual patient? or both?
Where does the application live?
Would there be a separate instance if you bring on another practice during pilot or MVP?
During onboarding in the early phases of the pilot program, we'll be providing keys directly to the practitioner organization to grant access to production via secure email - we will not be using the same web portal as our sandbox environment. Please consider how to best communicate with the practitioner to securely transfer secrets if necessary.
Are you ready for breaking changes during the pilot program?
As we introduce new features into the pilot program, how will you incorporate those changes into your solution?
How did you test your DPC solution? What documentation did you use the most?
How much time do you anticipate needing for testing and QA between obtaining production access and putting data in front of your providers?
c. Provide Security Certification
Health IT implementers preparing to onboard the production environment must provide one of the accepted security certifications below:
Office of the National Coordinator for Health Information Technology (ONC) Health IT Certification
Active Health Information Trust Alliance (HITRUST) CSF Validated Assessment
Active HITRUST self-validation assessment (valid for one year from date of first implementation if currently pursuing the HITRUST validated assessment)
Trusted Network Accreditation Program - Participant/Participant Member (TNAP - Participant/Member)
Trusted Network Accreditation Program (TNAP - QHIN)
System and Organization Controls (SOC) 2 certified
Type 1 certified (valid for one year from date of first implementation if currently pursuing type 2)
Type 2 certified
International Organization for Standardization (ISO): 27001, 27017, or 27018 certified
3. Onboard with DPC
The onboarding session will test your DPC solution with production Medicare Fee-For-Service claims data.
Approximately 2-3 weeks after your successful DPC solution demonstration in the sandbox environment, you will receive an email with information and a link to schedule an onboarding session. In the same email, you will also receive further instructions on production requirements prior to the onboarding date.
After completing production requirements, you will receive production credentials for the healthcare organization for which you are implementing the DPC solution.
During the live onboarding session, you will receive real-time support from DPC engineers as you demonstrate the following:
Submit a request for data
Receive requested data from DPC
Share Your Feedback
The DPC team is always seeking feedback! Pilot partners will be requested to participate in research sessions where Health IT implementers and healthcare organizations will be asked, together or separately, to share their experiences, challenges, and recommendations regarding the design of the DPC API and its features.
Join the DPC Google Group community to ask questions, share your thoughts, and hear about updates and upcoming events related to DPC.