DEV Community

Cover image for HL7 FHIR R4 vs R5: Why jumping to the latest version isn't always the best move
Svetlana Golubeva for Health Samurai

Posted on

HL7 FHIR R4 vs R5: Why jumping to the latest version isn't always the best move

When it comes to picking your FHIR version, the latest release might seem like the best choice — enter FHIR R5, packed with 4,000+ changes including shiny new resources and revamped real-time subscriptions. Sounds great, right?

But hold up. Most of the healthcare world still runs on FHIR R4, the stable workhorse backed by major EHR vendors like Epic and Oracle, and reinforced by government mandates. R5 introduces breaking changes and compatibility headaches, from patient record tweaks to allergy data shake-ups, forcing costly rewrites and complex migrations.

Plus, many partners and integrations are stuck on R4, limiting your real interoperability if you jump to R5 too soon.

The future? FHIR R6 promises stability and backward compatibility with official normative status, making it the smarter long-term upgrade. For now, most implementers (including us at Health Samurai) recommend sticking with R4, enjoying wide support and waiting for R6’s smooth rollout.

In short: Don't rush to upgrade. Choose stability, not just novelty. Your integrations (and your budget) will thank you.

What's your take? R5 now, wait for R6, or still loving R4? Drop your thoughts below!

Read the full article by our Customer Success Manager Vlad Zholnerchuk at health-samurai.io

Top comments (0)