Acentra Health · Interoperability SolutionSandbox Environment
Da Vinci · Attachments

Clinical Data Exchange (CDex)

Unsolicited exchange of clinical data - FHIR resources, C-CDA documents, PDFs and more - proactively sent from providers to payer systems.

Implementation GuideDa Vinci CDex
SecuritySMART on FHIR
Base Path/priorauth/api/v1
upload_file

Overview

The Clinical Data Exchange (CDex) API is a FHIR-based interoperability API that enables an unsolicited data-exchange flow, where a provider proactively sends relevant clinical data to 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.

To enable efficient exchange of large clinical documents, the CDex API supports a PreSigned URL-based attachment workflow. Clients obtain a secure, time-limited PreSigned URL to upload documents and then reference the uploaded content during CDex submission. This approach improves performance, reduces payload size, and provides a secure and scalable mechanism for exchanging large clinical attachments.

Clinical Data Exchange API
fact_check

Capability Statement

Developers can access the Acentra Health FHIR server capabilities for the CDex API using the CapabilityStatement endpoint:

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

The CapabilityStatement describes the supported profiles, interactions, 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.
terminal

Operations

The CDex API supports the following operations.

POST$submit-attachmenthttps://sb.fhir.mhbapp.com/priorauth/api/v1/$submit-attachment
POST$generate-presigned-urlshttps://sb.fhir.mhbapp.com/priorauth/api/v1/$generate-presigned-urls
POST$regenerate-presigned-urlshttps://sb.fhir.mhbapp.com/priorauth/api/v1/$regenerate-presigned-urls
dataset

Profiles

The CDex API supports the following profiles.

datasetCDex Parameters Submit AttachmentdatasetDocument Reference
http

Request Headers

All requests for CDex API profiles require the following headers:

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

Sample Responses & Data

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.

gpp_good

Important Information for EHR Systems

check