Patient Access and Provider Directory APIs
As part of The Interoperability and Patient Access final rule (CMS-9115-F), The Centers for Medicare & Medicaid Services (CMS) along with the Office of the National Coordinator for Health Information Technology (ONC) have mandated that payers must make patient health care claims and clinical information available through standards-based Patient Access and Provider Directory Application Programming Interfaces (APIs) for many government insurance plans beginning on July 1, 2021.
MVP’s Code of Conduct
At MVP, we believe that our members’ data belongs to them, and that they have a right to safe, secure data sharing in the applications they choose.
As such, application developers who would like to work with our APIs are expected to adhere to the CARIN Alliance code of conduct.
The CARIN Alliance code of conduct is meant to provide consumers with transparency into how their information is being used and disclosed by their chosen consumer-facing application.
Key points from the CARIN Alliance code of conduct include:
- Avoiding default personal data sharing by obtaining informed, proactive consent from users in advance of personal data disclosure.
- Compliance with the Children’s Online Privacy Protection Act (COPPA)
- Limiting the collection of personal data to only what the user has expressly consented to
In addition to adhering to the CARIN Alliance Code of Conduct, developers are expected to share the following resources with MVP for all applications that use MVP’s APIs. To share these resources, please contact MVP eSupport by phone at 1-888-656-5695, option 3 or email at firstname.lastname@example.org.
- User guides
- App store listings for every app store in which an app is listed
- Detailed use cases for member data
Working With MVP’s APIs
To begin working with MVP’s Patient Access or Provider Directory APIs, please register for a developer account.
Once registered, you may begin working with our API endpoints.
To update any information, (e.g. Contact Name, Redirect URL, etc.) associated with a developer account that is currently registered to work with MVPs Interoperability APIs, please go here.