What this domain asks
Risk that data move successfully but lose or distort meaning because codes, units, value sets, local terms, context, negation, status, and version provenance are incomplete or transformed incorrectly.
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
- Which code systems and versions are supported and licensed?
- How are local concepts mapped, reviewed, and changed?
- Are source code, normalized code, method, confidence, and history retained?
- How are units, reference ranges, status, and negation preserved?
- Who resolves ambiguous mappings and downstream safety issues?
- How are value-set updates tested before release?
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.
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.
Conformance Testing And Validation
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for conformance testing and validation 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.
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
- 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.