Future of FHIR Conformance
summary
FHIR R5 introduces an obligation extension on ElementDefinition plus mustHaveValue and valueAlternatives to replace brittle mustSupport rules, and adds an ActorDefinition resource, requirements and test-plan support; obligations list concrete behaviors (store, display, edit, process), can target actors (form‑filler, form‑manager, slider support) and be context‑filtered (valueSet, usageContext, “current” binding for net‑new vs legacy data), enabling auto‑generated tests and back‑porting to earlier releases to make conformance computable and reusable.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 1:06Must support vs cardinality explained
- 3:56Problems with must support approach
- 7:51Introducing obligation in R5
- 12:53Obligation codes and actors
- 17:26Structured Data Capture use case
- 22:03Additional bindings for conformance
- 25:19Requirements resource in R5
- 27:10Capability statement improvements
- 33:00Testing with test plans and scripts
- 37:13Summary of new conformance resources
- 38:20Q&A session
