USCDI is a policy-level, format-agnostic data content standard from ONC defining which data classes and elements must be exchangeable, tied directly to Cures Act interoperability requirements, and released in versions that expand over time. US Core is the FHIR implementation guide that operationalizes those requirements technically — defining profiles that constrain base FHIR resources for US use, mapping USCDI data classes to specific resources, and specifying required/must-support/optional elements. Certified EHR FHIR APIs are built to US Core, and certification testing validates both the data scope (USCDI) and the technical representation (US Core) together.
Quick answer
US Core and USCDI get confused constantly because they address the same underlying goal from two different angles: USCDI, the United States Core Data for Interoperability, defines which specific data classes and elements must be exchangeable under federal interoperability rules, while US Core is the FHIR implementation guide that actually specifies how to represent that required USCDI data using FHIR resources and profiles. In plain terms, USCDI is the policy-level "what data" requirement, while US Core is the technical-level "how to represent it in FHIR" answer.
Below is what each standard actually defines, how they relate to each other in practice, and why both matter for meeting Cures Act compliance requirements. If you're building toward USCDI or US Core compliance, our free Mirth Health Check can review your specific implementation directly — part of the Mirth Connect support work we do for US healthcare teams.
What USCDI Actually Defines
USCDI is fundamentally a policy and data-content standard maintained by the Office of the National Coordinator for Health IT, defining required data classes rather than any specific technical exchange format.
Data Classes and Elements Required for Exchange
USCDI defines specific data classes, like patient demographics, medications, and lab results, along with the individual data elements within each class that must be supported for interoperable exchange under current federal requirements.
Versioned Releases Expanding Required Data Over Time
USCDI is released in versions, with each new version typically expanding the required data classes and elements, so confirm which specific USCDI version your compliance requirement actually references before scoping any implementation.
A Format-Agnostic Data Requirement, Not a Technical Standard
USCDI itself doesn't specify how data should be technically formatted or transmitted, focusing instead on what data must be exchangeable, leaving the actual technical implementation to standards like FHIR through guides like US Core.
Tied Directly to Cures Act Interoperability Requirements
USCDI compliance is directly tied to 21st Century Cures Act interoperability and information-blocking requirements, making it a genuine regulatory obligation rather than simply a voluntary best practice for certified health IT systems.
What US Core Actually Defines
US Core takes USCDI's data requirements and defines the specific FHIR profiles and technical constraints needed to represent that data consistently across different systems and implementations.
FHIR Profiles Constraining Base Resources for US Use
US Core defines profiles that constrain and extend base FHIR resources specifically for US healthcare use, adding required fields, specific value sets, and other constraints that the generic base FHIR specification alone doesn't mandate.
Mapping USCDI Data Classes to Specific FHIR Resources
Each USCDI data class maps to one or more specific FHIR resources under US Core, such as USCDI's medications data class mapping to the MedicationRequest and MedicationStatement resources with their US Core-specific profiles.
Defining Required, Must-Support, and Optional Elements
US Core profiles specify which resource elements are required, must-support, or optional, giving implementers clear guidance on exactly what needs to be populated versus what can be omitted while remaining conformant.
The Foundation Most Certified EHR FHIR APIs Build On
Most certified EHR FHIR APIs in the US are built to conform with US Core specifically, making it the practical technical standard developers actually encounter when integrating with a certified EHR's patient access API.
Why Both Standards Matter Together for Compliance
Understanding USCDI and US Core as two halves of the same compliance picture, rather than competing or redundant standards, clarifies what you actually need to implement for a genuinely compliant integration.
USCDI Tells You What Data Must Be Available
Start with USCDI to understand which data classes and elements your system needs to support for exchange, since this defines the actual regulatory scope of what data must be made interoperably accessible.
US Core Tells You How to Represent That Data in FHIR
Once you know what data USCDI requires, US Core tells you specifically how to structure that data using FHIR resources and profiles, giving you the concrete technical target to build your API implementation against.
Certification Testing Validates Against Both Standards
EHR certification testing validates that a system's FHIR API correctly implements US Core profiles covering the data USCDI requires, meaning genuine compliance requires satisfying both the data scope and the technical representation together.
Newer USCDI Versions May Require US Core Updates
As USCDI versions expand required data classes over time, US Core implementation guides are updated correspondingly, so staying current with both standards' latest versions matters for maintaining ongoing compliance rather than a one-time implementation.
When to call for help
Confirming which USCDI version and US Core profile version your specific compliance timeline actually requires is worth verifying before building anything. Our free Mirth Connect health check reviews your implementation as part of the standard diagnostic.
Troubleshooting something specific? Send us the log, or check pricing for our support plans.
Building toward USCDI or US Core compliance? Free Mirth health check — a written 12-point audit report in 48 hours, no cost.