Overview
Da Vinci Payer Data Exchange (PDex) is the HL7 FHIR Implementation Guide specifying how US health plans expose member data via FHIR APIs. It is the technical foundation for the CMS Patient Access API (CMS-9115-F), the Payer-to-Payer API, and payer data elements of the Prior Authorization APIs. PDex extends US Core FHIR profiles with payer-specific elements capturing claims, coverage, prior-authorization, and clinical data as the plan holds it.
The Da Vinci Project is the broader HL7 accelerator that develops PDex and related payer-focused FHIR IGs. Da Vinci membership includes major payers (UnitedHealth, Humana, Cigna, Anthem/Elevance, Aetna/CVS), major EHR vendors (Epic, Oracle Health), large provider organizations, and HIT vendors. The collaborative model produces IGs that represent realistic implementation patterns rather than theoretical standards.
PDex includes several profile families. The PDex-USDF (US Drug Formulary) profiles describe formulary structure, drug-tier membership, and coverage rules. The PDex clinical profiles extend US Core to capture payer-held clinical data — payer-accessible labs, medications, conditions — with specific extensions for payer source systems. The PDex claims profiles describe how adjudicated claims and encounters are represented in FHIR. The PDex coverage profiles describe plan-coverage terms and member enrollment status.
PDex-PDA (Prior Authorization) profiles support prior-authorization exchange under CMS-0057-F — they represent PA submissions, decisions, and documentation. These profiles integrate with Da Vinci's CRD, DTR, and PAS IGs to complete the end-to-end PA workflow.
For payer operations, PDex is the implementation target for CMS Interoperability compliance. Payer FHIR platforms implement PDex profiles to serve Patient Access, Provider Directory, Payer-to-Payer, and Prior Authorization APIs. Many payers use vendor-supplied FHIR infrastructure (Optum Mulesoft, Salesforce Health Cloud, HealthLX, Smile Digital Health, and others) rather than building PDex-conformant infrastructure from scratch.
For app developers and health-tech vendors, PDex-conformant APIs enable consistent integration across payers. Rather than custom-integrating with each payer's data model, developers can build to PDex profiles and interoperate with essentially all CMS-regulated payers as they come into compliance.
Ongoing PDex evolution addresses gaps identified during production deployment. Data-freshness variations, US Core version alignment, and performance optimization for high-volume members are active work areas in the Da Vinci PDex working group.
From a board-reporting standpoint, Da Vinci Payer Data Exchange (PDex) belongs in the compliance committee's quarterly dashboard. The reporting line should include volume, exception rate, and any open remediation action; reviewers tie Da Vinci Payer Data Exchange (PDex) metrics to the broader compliance program KPIs so an emerging Da Vinci Payer Data Exchange (PDex) risk surfaces before it becomes a formal finding. Pairing the Da Vinci Payer Data Exchange (PDex) trend with fhir api gives the committee a single view of whether the control environment is strengthening or drifting.
Industry benchmark
Da Vinci PDex IG: current version 2.0 (2024). CMS-regulated payer adoption: nearly universal for Patient Access API compliance. Provider-side and app-developer adoption for integration: substantial and growing.
Worked example
An MA plan implements PDex-conformant FHIR endpoints for Patient Access API compliance. Member authenticates an aggregation app; app requests US Core and PDex-profiled resources including Coverage, Claim, ExplanationOfBenefit, and clinical data. The app receives structured FHIR responses and provides personalized benefit and clinical context.
Frequently asked questions — Da Vinci Payer Data Exchange (PDex)
Is PDex the same as US Core?
No — PDex extends US Core with payer-specific profiles and data elements (coverage, claims, formulary, prior-authorization). US Core provides the clinical-data baseline; PDex adds the payer layer.
Which CMS APIs use PDex?
Patient Access, Payer-to-Payer, Provider Directory, and Prior Authorization APIs all incorporate PDex profiles. PDex is the technical foundation across the CMS payer-interoperability API suite.
Do providers implement PDex?
No — PDex is a payer-side specification. Providers consume PDex-conformant APIs via EHR integrations, patient-app partnerships, or direct integration work.
Disclaimer
This glossary entry is operational reference for revenue-cycle and medical-billing professionals. It is not legal, clinical, or contractual advice. Industry benchmarks cite named public sources where available; always verify against the current guidance from the authority body before relying on a number in a contract, policy, or compliance filing.