FHIR R4 vs R5 (and R6): Which Version Should You Build On?
FHIR R4 vs R5 (and R6): Which Version Should You Build On? - Ekipa AI
Summary
For US EHR integrations, the article advises building on FHIR R4. This is because the declared version governs the entire interaction—including MIME types and search behavior—and R4 maintains compatibility with existing certified APIs and payer contracts.
Details
This article compares FHIR R4, R5, and R6 to guide developers on version selection. From the perspective of US EHR integration, R4 is the baseline, referenced by US Core and ONC certification criteria, and remains the default for major EHR APIs. R5 is presented as an option for specific modeling, while R6 is still in ballot. Key technical changes include the renaming of `RequestGroup` to `RequestOrchestration` and the addition of the `CodeableReference` datatype in R5. However, the text warns that simply upgrading the payload is insufficient; developers must compare CapabilityStatements and regression-test every resource, as the declared version governs the entire interaction, not just the payload schema.
Original content copyright by respective publishers