When Health Level Seven International (HL7) published FHIR Release 4 (R4), it marked a turning point for health-data exchange in the United States. R4 was the first version of FHIR to include normative content — portions of the specification that carry a backward-compatibility commitment. For implementers in Arizona, that distinction is more than a footnote: it means the core building blocks they invest in today are unlikely to break under their feet tomorrow.
Why “normative” matters
Earlier FHIR releases were published under a Standard for Trial Use (STU) designation. Trial-use content is valuable, but it can change between versions. Normative status signals that a resource or framework has been broadly tested and is considered stable. The RESTful API, the XML and JSON formats, and several foundational resources reached that bar in R4. Organizations building long-lived integrations — the kind that connect a hospital, a reference lab, and a statewide exchange — benefit from that predictability.
The US Core layer
R4 is the version that underpins the HL7 US Core Implementation Guide, the U.S. Realm profile set that constrains FHIR resources to a common, expectable shape. US Core is updated on an annual cadence to track the U.S. Core Data for Interoperability (USCDI), so Arizona implementers should treat “FHIR R4” and “the current US Core IG” as two layers of the same stack rather than competing choices.
What it means on the ground
For a clinic adding a patient-access app, or a health system exposing data to a query-based network, R4 plus US Core establishes a shared vocabulary: which fields must be present, which value sets apply, and which API interactions a server should support. That shared expectation is what lets a developer in Tucson write against a server in Flagstaff without a custom one-off integration each time.
AzHeC’s role here is not to certify products but to help Arizona stakeholders read the standards accurately. A plain-language primer on the difference between FHIR, US Core, and USCDI is available in our Standards work area, and newcomers can start with the glossary of Health IT terms.
The practical takeaway: R4’s normative status lowered the risk of building on FHIR. It did not finish the work. Conformance still depends on disciplined use of US Core profiles, careful terminology binding, and testing against real exchange partners — the unglamorous engineering that turns a published standard into records that actually move.