Clinical Data Exchange (CDex) API
The Clinical Data Exchange (CDex) API is a FHIR®-based interoperability API that enables unsolicited data exchange flow, where a provider proactively sends relevant clinical data to the payer systems without a prior explicit request, based on a known business or clinical need. It enables the exchange of a wide range of clinical data formats, including FHIR® resources and Bundles, C-CDA documents, PDFs, and other file types.
Capability Statement
Developers can access the Acentra Health FHIR server capabilities for Clinical Data Exchange (CDex) API using the CapabilityStatement endpoint:
The capability statement describes the set of capabilities (behaviors) implemented by the FHIR Server to enable the Clinical Data Exchange (CDex) API. For example, it describes the enabled profiles, interactions, and provides information about the authorization and token endpoints.
API Access Setup
FHIR 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.
The FHIR Base URL will be provided upon successful App Registration approval.
Getting Access Token
| Section | Key | Value |
|---|---|---|
| HTTP Method | POST | https://sb.fhir.mhbapp.com/sof/oauth2/token |
| HTTP Headers | content-type | application/json |
| accept | application/json | |
| authorization | Basic base 64({client_id}:{client_secret}) | |
| HTTP Body | code | {oauth code} |
| grant_type | authorization_code | |
| redirect_uri | {your_redirect_uri} |
Operations
Acentra Health Interoperability Solution’s Clinical Data Exchange (CDex) API supports the following operations:
| Operation | Endpoint |
|---|---|
| $submit-attachment | https://sb.fhir.mhbapp.com/priorauth/$submit-attachment |
Profiles
Acentra Health Interoperability Solution’s Clinical Data Exchange (CDex) API supports the following profiles:
| Profile |
|---|
| CDex Parameters Submit Attachment |
| Document Reference |
Request Headers
All requests for Clinical Data Exchange (CDex) API profiles require the following headers
| Header | Value |
|---|---|
| content-type | application/json |
| accept | application/json |
| authorization | Bearer |
Sandbox Test Data Catalog
Synthetic test data is provided for PAS API. The identifiers provided to submit PAS requests can be used to obtain a PA tracking ID, which can then be used for CDex interactions. No separate test data is provided for CDex.
Important Information for EHR Systems
| Topic | Reference |
|---|---|
| Privacy, Security and HIPAA | https://www.healthit.gov/topic/privacy-security-and-hipaa |
| ONC Model Privacy Notice | https://www.healthit.gov/topic/privacy-security-and-hipaa/model-privacy-notice-mpn |