Terminology mapping and translation – ConceptMap updates in FHIR R5
summary
FHIR R5 changes make ConceptMap usable rather than just descriptive: the relationship codes are simplified and now explicitly indicate mapping direction, unmapped cases are handled at the source side, and dependsOn/product entries accept polymorphic values instead of plain strings. ConceptMap can now map to or from entire value sets and the $translate operation is updated to accept an explicit ConceptMap reference. Early edits land in the CI build with recent commits in the last 48 hours and a consolidated ConceptMap2 is planned to replace the existing resource in the September R5 build.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:43Need for mapping and translation
- 7:57Concept Map and translate
- 12:33Practical mapping examples
- 21:11Rationale for R5 changes
- 25:22Versioning and future plans
- 31:22Specific technical improvements
