Versioning

on YouTube ↗40m

" summary

Explains concrete rules and tooling: FHIR fragments never carry their release tag so version is a property of the channel, clients discover supported releases from the capability statement declares versions and servers can expose either separate endpoints per release or a single endpoint using the FHIR version MIME parameter; IG publisher and validator run everything through R5 so IG publisher uses R5 internally; conversion maps and Java libraries exist but transforms sometimes fail and package-level versioning is recommended because per-resource unversioned references are fragile.

AI-written summary · about

" chapters (10)

1. 0:00Introduction to versioning
2. 5:59Versioning in FHIR releases
3. 12:06Versioning strategy and SEMVER
4. 20:27API strategy for versioning
5. 26:50Challenges and costs of versioning
6. 28:22Q&A on adopting R5
7. 29:24Testing and version awareness
8. 34:04IG publisher and R5
9. 36:11Metadata API and capability statements
10. 37:14Single vs multiple endpoints

" related talks

• 43mManaging multiple versionsGrahame Grieve · HL7 FHIR DevDays 2019 Redmond
• 41mFHIR4: what's new?Grahame Grieve · HL7 FHIR DevDays Boston 2018
• 37mPackages and versioningMartijn Harthoorn · HL7 FHIR DevDays 2019 Redmond
• 19mThe future of FHIR: R4B and R5?Lloyd McKenzie · HL7 FHIR DevDays International 2022
• 40mFHIR 5Grahame Grieve · HL7 FHIR DevDays 2019 Redmond
• 50mAPI Versioning for REST: In Real Life, How Do We Do It?Alexandre Touret · DevFest Lille 2023
• 38mCustom Resource Definitions: Let's Talk About Versioning and ReleasesNick Young · CNCF Maintainer Summit Europe 2025
• 42mReferential IntegrityGrahame Grieve · FHIR DevDays Virtual Edition June 2021