Base FHIR leaves many choices to implementers, and US Core narrows them for US use. HL7 says it defines the minimum constraints on FHIR resources to create the US Core Profiles, and the minimum RESTful interactions for accessing patient data. Each profile, for resources such as Patient, Condition, Observation, AllergyIntolerance and Procedure, states which elements, extensions, vocabularies and value sets must be present.
Must Support
Profiles flag elements as mandatory or Must Support, and the guide has a dedicated page on what each means for senders and receivers. For an app developer, Must Support is the practical contract: these are the fields a conformant server should be able to return when it has the data.
Versions and certification
US Core is based on FHIR R4, and the current published version is 9.0.0 (STU 9). Each US Core version lines up with a USCDI version; HL7's mapping pairs US Core 6.1.0 with USCDI v3.1 and 9.0.0 with USCDI v6. For ONC certification, the standardized API criterion uses US Core 6.1.0 as its baseline, with 7.0.0 and 8.0.1 approved as newer options. Certified developers must also publish API documentation through a public link with no preconditions.
Why it matters
When an EHR vendor says it supports FHIR, the useful follow-up is which US Core version. Two servers can both be valid FHIR R4 and still disagree on what a blood pressure observation looks like, unless both conform to the same US Core version.
Example: an analytics product that pulls vital signs from several health systems writes its parser against the US Core vital signs profiles. If every source is certified to the same US Core version, one parser covers all of them, and testing focuses on optional fields and local codes.