CARIN Consumer Directed Payer Data Exchange Implementation Guide
CARIN Blue Button defines FHIR profiles for consumer-directed exchange of claims and encounter information using the Common Payer Consumer Data Set.
What the authority record establishes
CARIN Blue Button defines FHIR profiles for consumer-directed exchange of claims and encounter information using the Common Payer Consumer Data Set.
Implementation guide referenced in payer API policy and guidance; controlling obligations remain in applicable rules
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
The 2026 release creates a current version-control question for payer and app implementations; support must be stated by version rather than as a generic Blue Button claim.
Affected operating stages
- Claims Mapping
- Consumer Authorization
- API Access
- Application Display
- Version Transition
- 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.
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
- consumer application developers
- payer API vendors
- members and patient-access teams
- conformance teams
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
The guide does not determine which claims a payer maintains, whether an app is trustworthy, or whether displayed information is complete.