The future of FHIR: R4B and R5?

on YouTube ↗19m

" summary

R4B is a technical correction to R4 that fixes invariants, schematics and infrastructure; it includes a potentially breaking MedicationDefinition breaking change that few implementers used so impact is expected to be small. R4B backports subscription changes and adds DescriptionTopic and space-medicine resources, while content negotiation means servers must advertise 4.3. R5 opens for ballot with no new normative content (Patient/Observation edits are STU-only), new resources like ConditionDefinition and Transport, and transforms from R4 arrive after ballot; timelines target releases every ~2 years.

AI-written summary · about

" chapters (7)

1. 0:00Introduction to FHIR R4B
2. 1:15Key changes in R4B
3. 3:23Timeline for FHIR R5
4. 5:52Major changes in FHIR R5
5. 9:01Ballot process and transforms
6. 10:05Future of FHIR releases
7. 12:12Q&A session

" related talks

• 41mFHIR4: what's new?Grahame Grieve · HL7 FHIR DevDays Boston 2018
• 40mFHIR 5Grahame Grieve · HL7 FHIR DevDays 2019 Redmond
• 39mR5Grahame Grieve · DevDays 2023
• 46mSubscriptionsGino Canessa · DevDays 2023
• 45mIntroduction to FHIRSimone Heckmann · DevDays 2023
• 50mFuture roadmap of FHIRGrahame Grieve · DevDays 2023
• 46mFuture of FHIR ConformanceLloyd McKenzie · DevDays 2023
• 43mManaging multiple versionsGrahame Grieve · HL7 FHIR DevDays 2019 Redmond