US Core

fhir technical technical fhirinteroperabilityhealthcare
Source: HL7 System: http://hl7.org/fhir/us/core Code: US Core Reviewed: 11/02/2026 License: CC-BY-4.0

US Core

One-sentence definition: US Core is the HL7 FHIR Implementation Guide that defines the minimum FHIR profiles, terminology bindings, and Must Support requirements for health data exchange in the United States — forming the technical baseline for ONC certification and most US FHIR interoperability programs.

Full Definition

FHIR provides a global, general-purpose framework. US Core narrows it to a specific context: US healthcare, US regulatory requirements, and US clinical data standards. It is the FHIR expression of USCDI — translating the policy-level data classes that ONC mandates into concrete FHIR profiles that systems can implement and validate against.

US Core publishes profiles for the FHIR resources most commonly needed in US interoperability: Patient, Practitioner, Organization, Condition, Observation (vital signs, lab results, social history), MedicationRequest, AllergyIntolerance, Immunization, Procedure, DocumentReference, and others. Each profile specifies which fields are Must Support (implementers must be able to populate and process them), which are required, and which terminology bindings apply.

The IG also defines the Must Support semantics specifically: a Must Support element means a sending system must populate it if the data is available, and a receiving system must be able to store and display it. This bi-directional obligation is what makes Must Support a conformance requirement rather than a hint.

US Core versions track USCDI versions: US Core 3.x aligned with USCDI v1, US Core 6.x aligned with USCDI v3. Each new USCDI version adds data classes, and a corresponding US Core release adds the profiles and extensions needed to carry that data in FHIR.

Context and Usage

Where This Term Appears

  • ONC certification: 2015 Edition certification criteria require EHRs to support US Core as part of the standardized patient access API
  • Da Vinci IGs: Most Da Vinci IGs build on US Core profiles as their base
  • Payer API documentation: CMS requires impacted payers to publish Patient Access and Provider Directory APIs conformant with US Core
  • FHIR validators: Validation tools use the US Core IG package to check that FHIR resources meet US requirements

Common Usage Examples

In conversation: “Does your server support US Core 6.1? We need USCDI v3 data classes, and the older profiles won’t cover social determinants.”

In documentation: “The Patient resource must conform to the US Core Patient Profile, which requires at least one identifier, name, and gender.”

Relationship to Other Terms

  • FHIR — the standard US Core profiles and extends for US-specific use
  • USCDI — the policy-level data standard that US Core technically implements in FHIR
  • ONC — the regulatory body whose certification criteria mandate US Core conformance
  • Profile — the primary conformance artifact US Core publishes for each resource type
  • Implementation Guide — US Core is one of the most widely referenced FHIR IGs in the US

Common Misconceptions

Misconception: US Core and USCDI Are the Same Thing

  • Incorrect belief: US Core and USCDI are two names for the same standard.
  • Reality: USCDI is a policy standard maintained by ONC that defines what clinical data categories must be supported. US Core is a FHIR IG maintained by HL7 that defines how to represent those data categories in FHIR resources. USCDI is technology-agnostic; US Core is the FHIR-specific implementation.
  • Why it matters: Policy teams reference USCDI data classes; engineering teams implement US Core profiles. Conflating them causes misalignment between policy requirements and technical implementation.

Misconception: US Core Is Optional for US FHIR Implementations

  • Incorrect belief: US Core is a useful reference but not a hard requirement — systems can choose their own FHIR profiling approach.
  • Reality: ONC certification criteria, CMS payer API requirements, and most US interoperability programs specify US Core conformance explicitly. Systems that don’t support US Core profiles cannot claim ONC certification and cannot interoperate with systems that expect US Core-conformant data.
  • Why it matters: US Core is the de facto floor for US FHIR implementations. Building without it means building to a private standard that won’t interoperate with the broader ecosystem.

Why US Core Matters

US Core is the common language of US FHIR interoperability. Without it, every organization would define its own FHIR profiles for the same clinical resources — resulting in data that is syntactically FHIR-compliant but semantically incompatible. US Core establishes a single set of profiles that any US FHIR system can target, enabling patient data to flow between providers, payers, and applications without custom mapping.

For US Core profile details, Must Support semantics, and version differences, see the canonical reference → FHIR Profiling

Cross-References

  • FHIR — the standard US Core profiles and extends
  • USCDI — the policy standard US Core technically implements
  • ONC — the regulatory body whose certification criteria mandate US Core conformance
  • Profile — the primary conformance artifact US Core publishes

Last reviewed: February 11, 2026 Definition authority: HL7 International Content status: Canonical reference