Acentra Health · Interoperability Solution Sandbox Environment
Plan Transitions

Payer to Payer API

Secure exchange of member data between health plans to support continuity of care during member transitions, per CMS interoperability requirements.

Implementation GuideDa Vinci PDex
SecuritySMART Backend
Base Path/payer/api/v1
swap_horiz

Overview

The Payer-to-Payer API enables secure, standards-based exchange of member data between health plans to support continuity of care during member transitions. It allows receiving payer systems to retrieve claims, encounters, and prior authorization information from previous payer systems through authorized workflows.

It aligns with CMS-recommended implementation guides - CPCDS, HL7® Da Vinci PDex, and FHIR® Bulk Data - and leverages HL7® FHIR® with SMART Backend Services Authorization.

Payer to Payer API
fact_check

Capability Statement

Developers can access the Acentra Health FHIR server capabilities for the Payer-to-Payer API through the CapabilityStatement endpoint:

METAhttps://sb.fhir.mhbapp.com/payer/api/v1/metadata
View JSON

The CapabilityStatement describes the supported profiles, interactions, search parameters, and authorization and token endpoints.

login

API Access Setup

settings_suggestFHIR SMART Configuration

Clients can retrieve SMART configuration details by invoking the SMART configuration endpoint at /.well-known/smart-configuration, appended to the FHIR Base URL.

vpn_key
The FHIR Base URL is provided upon successful App Registration approval.
key

Getting an Access Token

The Payer to Payer API uses SMART Backend Services authorization. Request an access token from the token endpoint using the client_credentials grant.

POSTToken Endpointhttps://sb.fhir.mhbapp.com/sof/oauth2/token
HTTP Headers
HeaderValue
content-typeapplication/x-www-form-urlencoded
acceptapplication/json
HTTP Body
ParameterValue
scope{scopes}
grant_typeclient_credentials
client_id{client_id}
client_secret{client_secret}
terminal

Operations

The Payer to Payer API supports the following operations.

POST $member-matchhttps://sb.fhir.mhbapp.com/payer/api/v1/Patient/$member-match
POST $bulk-member-matchhttps://sb.fhir.mhbapp.com/payer/api/v1/Group/$bulk-member-match
POST $davinci-data-exporthttps://sb.fhir.mhbapp.com/payer/api/v1/Group/$davinci-data-export
dataset

Resources

info
All resources are returned via the $davinci-data-export bulk export operation - individual REST endpoints are not available for these profiles.
Identity Resolution
BULKParametersHRex Member Match RequestHRex
BULKParametersHRex Member Match ResponseHRex
BULKParametersPDex Multi-Member Match RequestPDex
BULKParametersPDex Multi-Member Match ResponsePDex
Member
BULKPatientPDex PatientPDex
BULKCoverageHRex CoverageHRex
BULKPractitionerCPCDS PractitionerCPCDS
BULKOrganizationCPCDS OrganizationCPCDS
BULKRelatedPersonCPCDS Related PersonCPCDS
Claims
BULKExplanationOfBenefitEOB Inpatient InstitutionalCARIN
BULKExplanationOfBenefitEOB Outpatient InstitutionalCARIN
BULKExplanationOfBenefitEOB Professional NonClinicianCARIN
BULKExplanationOfBenefitEOB OralCARIN
BULKExplanationOfBenefitEOB PharmacyCARIN
Authorization
BULKClaimPrior AuthorizationPDex
Audit
BULKProvenanceHRex ProvenanceHRex
http

Request Headers

All requests for Payer to Payer API profiles require the following headers:

HeaderValue
content-typeapplication/json
acceptapplication/json
authorizationBearer {access_token}
science

Sample Responses & Data

gpp_good

Important Information for Payer Systems

check