What this domain asks
Risk that exchanged information lacks source, time, status, authorship, context, completeness, or transformation history, preventing the receiving organization from evaluating whether and how to use it.
The domain should retain its own evidence, decision owner, materiality criteria, exception path, and consequence even when it shares organization identity, workflow, or technology with adjacent domains. Aggregation can support oversight; it should not erase the evidence behind different risks or operating outcomes.
Buyer questions
- Can every element be traced to source, time, status, and transformation?
- How are missing, duplicate, stale, and conflicting values represented?
- Which data are never requested, not returned, filtered, or unsupported?
- How do corrections propagate to downstream consumers?
- What receiving workflow reconciles exchanged data?
- How are quality metrics defined and monitored by source?
Mapped workflows
FHIR Profile And Implementation-Guide Support
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for FHIR profile and implementation-guide support within this domain.
C-CDA Document Exchange
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for C-CDA document exchange within this domain.
Query-Based Document Exchange
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for query-based document exchange within this domain.
Patient Identity And Record Matching
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for patient identity and record matching within this domain.
Terminology Normalization And Value-Set Management
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for terminology normalization and value-set management within this domain.
Data Quality, Lineage, And Provenance
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for data quality, lineage, and provenance within this domain.
Operational Monitoring And Exception Management
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for operational monitoring and exception management within this domain.
Authority context
US Core 9.0.0
US Core defines U.S. FHIR profiles, interactions, search expectations, and guidance for exchanging common clinical data. Version 9.0.0 remains based on FHIR R4 and incorporates current USCDI-oriented development.
USCDI v6
USCDI v6 defines an expanded national set of health-data classes and elements intended to support interoperable exchange. Publication, regulatory adoption, and voluntary certification advancement are distinct status records.
PDex 2.1.0
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.
C-CDA 5.0.0
C-CDA 5.0.0 consolidates U.S. clinical document templates and current guidance while remaining based on the underlying CDA R2 document standard. It uses FHIR tooling to represent templates but does not turn CDA documents into FHIR resources.
Relevant operating models
- Enterprise Interoperability And Integration Platform
- FHIR Server, API, And Compliance Platform
- Clinical Data Network And Record-Retrieval Platform
- Terminology And Semantic-Interoperability Platform
- Cloud Health-Data Platform
Evidence boundary
Health Interoperability Review provides market, standards, policy, and operating research. It does not provide patient-specific medical advice, determine an individual's rights or coverage, certify product conformity, authorize a disclosure, or replace legal, privacy, security, clinical, or implementation review. A provider's documented capability can identify a research candidate but cannot establish buyer-specific adequacy for this domain.