United States Core Data for Interoperability Version 6
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.
What the authority record establishes
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.
USCDI v6 is not the general mandatory certification baseline as of July 19, 2026; HTI-1 adopted USCDI v3 as the baseline beginning January 1, 2026, while SVAP permits voluntary advancement under stated conditions
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
USCDI version determines the content baseline around which profiles, certification, mapping, and exchange programs are designed. Buyers should demand a version-aware roadmap and evidence for missing or newly added elements.
Affected operating stages
- Data Inventory
- Element Mapping
- Profile Alignment
- Terminology
- Certification Planning
- Exchange Testing
- Version Transition
Capabilities to examine
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.
C-CDA Document 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 C-CDA document exchange.
Terminology Normalization And Value-Set Management
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 terminology normalization and value-set management.
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
- certified health IT developers
- health systems
- health plans
- public-health teams
- standards and data-governance leaders
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
USCDI identifies data classes and elements; it does not by itself specify one transport, guarantee data availability, or establish clinical completeness.