ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

— May 16, 2026 · 9 min read

FHIR R6 preview: what the next version changes

HL7 is preparing the sixth major revision of FHIR. After R4 (2019) and R5 (published in March 2023), R6 targets a 2026 ballot and consolidates the maturity of pivotal clinical resources. This article frames the expected evolutions without extrapolating beyond what is publicly announced on the HL7 tracker and build.fhir.org.

R4, R5, R6: the stabilisation trajectory

To situate R6, recall the status of its predecessors. FHIR R4 (released October 2018, version 4.0.1 in November 2019) remains the most broadly deployed version in national ecosystems (US Core, IPA, IPS, France SI-DMP). Its key characteristic: the most-used resources (Patient, Observation, Encounter, Medication*, AllergyIntolerance) are marked Normative, meaning stable and backward-compatible in all future versions of FHIR. FHIR R5 (released March 2023) expanded the normative perimeter, reworked some clinical resources and pinned the 5.0.0 spec for Quantity, terminology services and FHIRPath.

R6, still in development at the time of this article, mainly aims to capitalise on R5 experience and to finalise normative marking for a broader set of resources, particularly in diagnostic / pharmacy / imaging domains. HL7 has indicated on its tracker a 2026 ballot target, with official publication likely spread across 2026-2027.

Expected evolutions

Normative perimeter extension

Several pivotal clinical resources currently marked Trial Use in R5 are in discussion to become Normative in R6: notably in diagnostic-orientation, care-path (Care*) and pharmacy (Medication*, MedicationRequest, MedicationDispense) domains. The practical consequence: once normative, a resource cannot introduce breaking changes in later versions, finally stabilising semantics for clinical vendors.

SMART App Launch and SMART on FHIR alignment

The SMART specification family (notably SMART App Launch 2.0.0 and SMART on FHIR 2.0.0) has progressed independently of FHIR. R6 aims to better integrate references to these specs, clarify OAuth 2.0 / OpenID Connect authentication patterns and harmonise capability statements with SMART scopes.

Terminology services and validators

Terminology services saw significant evolution between R4 and R5 (notably clarification on $translate, $expand, and composed value-set handling). R6 aims to finalise these operations, clarify $validate-code semantics in multi-system cases, and better align with SNOMED CT, LOINC and ICD-11 terminology requirements.

Anticipated breaking changes vs R5

FHIR limits breaking changes by discipline, but some are expected in R6: cardinality adjustments on Trial Use resources, strengthening of invariant constraints (FHIRPath invariants), and consolidation of some complex datatypes. Exact changes will be published at ballot time in 2026. Clinical vendors in production on R5 should plan a targeted audit on the Trial Use resources they use, as those carry the highest breaking-change risk.

Migration path from R4 or R5

For a vendor whose installed base is on R4, the recommended migration goes first through R5 (which already covers most semantic novelties), then through R6 once the version is stable. R4→R5 compatibility is managed by rules documented in the FHIR Cross-Version Extensions spec and by FHIR StructureMap transformations published by HL7. The same logic will apply for R5→R6.

For implementations connected to national ecosystems (US Core version 6 on R4, IPA, IPS, etc.), the R6 switch will mainly depend on the evolution of corresponding implementation guides, which in practice freeze the FHIR version used for years. Count 18 to 24 months between R6 publication and the first national R6 IGs appearing.

Conclusion: a consolidation version

R6 will probably be the most mature FHIR version, with an expanded normative perimeter, stabilised terminology services and reinforced SMART alignment. For vendors in production on R4 or R5, the reasonable horizon is 2027-2028 for first R6 pilot projects, and 2029-2030 for mass migrations aligned on national IG publication. The right 2026 reflex is to monitor the HL7 tracker and build.fhir.org without entering a premature migration.

To dig further, the article FHIR R5 vs HL7 v2.5.1 compares the current state of both families, and the Introduction to FHIR page gives the core concepts needed to understand the impact of a major version.