Da Vinci Payer Data Exchange Implementation Guide

What the authority record establishes

PDex profiles FHIR-based exchange of clinical, claims, encounter, and prior-authorization information among payers, patients, and providers and introduces bulk APIs for provider and payer-to-payer access.

Technical guide used in CMS implementation context; exact regulatory requirements remain in controlling rules and guidance

The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.

Why it matters to this market

PDex is central to current payer data-exchange architecture, but buyers must track its US Core dependencies, API role, bulk behavior, member permission, and relationship to separate CARIN and Da Vinci guides.

Affected operating stages

• Data Mapping
• Member Matching
• Patient Access
• Provider Access
• Payer-To-Payer Exchange
• Bulk Export
• Testing

Capabilities to examine

FHIR API Gateway And Orchestration

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for FHIR API gateway and orchestration.

FHIR Profile And Implementation-Guide Support

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for FHIR profile and implementation-guide support.

SMART On FHIR Authorization

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for SMART on FHIR authorization.

Bulk Data Access And Export

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for bulk data access and export.

Provider Directory And Endpoint Discovery

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for provider directory and endpoint discovery.

Consent, Authorization, And Data Segmentation

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for consent, authorization, and data segmentation.

Payer And Claims Data Exchange

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for payer and claims data exchange.

Data Quality, Lineage, And Provenance

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for data quality, lineage, and provenance.

Conformance Testing And Validation

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for conformance testing and validation.

Affected buyer audiences

• health plans
• payer API platforms
• provider organizations
• consumer applications
• interoperability vendors

Implementation questions

• Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
• What is binding, what is guidance, and what is a technical or consensus standard?
• Which publication, adoption, effective, application, transition, and enforcement dates differ?
• Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
• How will a source revision affect open work and historical decisions?

Interpretation boundary

Use of PDex does not by itself establish compliance, production readiness, complete payer data, or authorized disclosure.