
manage the API connection process with 3rd party
developers in a highly secure, compliant, and
organized setting.


connections among
Transformation across Healthcare


ingestion of data from multiple EMRs for storage
in FHIR server


Member Data with Centaur
API Platform

Experience
members to securely access claims, clinical,
rand encounter information through
any validated third-party
application of their choice.

CentaurTM API Platform

Payer Data Connectivity
government regulations, enabling seamless
payer-to-payer, provider-to-payer and
payer-to-provider data
exchangeusing FHIR APIs.

by sending and receiving clinical data


sharing between Payers at a Member's request


connect with each other efficiently


data through APIs

The CMS Mandates that Payers:
Patient Access API
Implement and maintain an open FHIR-based API with appropriate authentication and authorization to share data with members
Provider Directory API
Make provider and pharmacy directory data available via the Provider Directory API.
Register Applications
Support 3rd party developers in accessing security tokens and development sandboxes for registering applications
Supporting Documents
Provide appropriate supporting documents to quickly and securely connect with Payers’ environment
Payers can effortlessly expand their network of technology partners
Enable a dynamic microservices strategy with an agile developer portal


Reduce the development burden associated with meeting the CMS Mandates
Empower members with access to your network of application partnerss

One platform to manage communication and registration process with 3rd party developers
- Customizable application registration form
- Giving third party developers access to API documentation
- 3rd parties can test in Sandbox and ‘apply’ for promotion to production
- Customizable production application form with terms & Conditions
- Everything happens on one platform
Reduce the development burden associated with meeting the CMS Mandates
- 3rd party developers provide resources for members on the Payer’s behalf
- ‘Low-touch’ interactions with third party developers
- Admins can promote 3rd party applications to production at the click of a button
Empower members with access to your network of application partners
- Seamlessly Provide members with access to their clinical and claims data
- Members can choose where to access and manage their historical medical records
- More personalized experience for members
- Close the gap in communication between Members, Providers and Payers
HC Developer Portal is Designed to Help Payers Meet CMS-9115-F
Work with a user-friendly UI to provide API documentation by accepting Swagger Json Files
Provide developer registration forms to create developer profiles within the portal
Customizable application registration form to register applications with the platform and get the credentials
Ability to promote the registered application to production via the production application form and accepting Terms & Conditions
Administrator view to manage production applications and pending production application requests
Editing application shows both Sandbox and Production application details such as name, redirect URL, Scope, Environment and Credentials
Who Interacts With a Developer Portal
Developer portals are not only for developers. In fact, portals create an ecosystem where multiple stakeholders interact.
Let’s take a closer look at who uses the dev portal:
Developers
The team of developers who built the portal and the APIs.
API consumers
The end-consumer and those who get value from your APIs.
Product Owners
Product owners gather new ideas for products or features.
Salespeople
A portal can help with business development and partner recruitment.
Developer advocates
They bridge the gap between developers and the company
Technical writers
They produce content about APIs and onboarding initiatives