The CMS Mandates that Payers:

One Integrated Platform for Third Party Developers and Healthcare Organizations to access Payer’s Healthcare Data

Patient Access API

Implement and Maintain Patient Access APIs that allow Third Party Developers to retrieve claims and clinical data, with the approval and at the direction of a member

Provider Directory API

Implement and Maintain Provider and Pharmacy Directory information via the Provider Directory APIs

Register Applications

Support Third Party Developers to test their connection to the APIs without requiring production access using sandbox environments.

Supporting Documents

Provide Third Party Developers with clear, standardized API documentation to quickly and securely connect to member data

Payers can effortlessly expand their network of technology partners

Enable a dynamic microservices strategy with an agile developer portal

Provide API Documentation and customizable application registration form within the tool to 3rd party developers

Agile Developer Portal

Payers can effortlessly expand their network of technology partners

CMS Mandate

Reduce the development burden associated with meeting the CMS Mandates

One platform to manage registration and communication with 3rd party applications to meet the patient access mandate

Payers can effortlessly expand their network of technology partners

Empower members with access to your network of application partners

Drive adoption of APIs and create robust API ecosystems for Third Party Developers and Healthcare organizations.

Application Partner

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