FHIR Mapping Language
summary
Defines a portable, purely declarative language plus a standard API that abstracts host storage/lookup so mappings run in any engine; provides a concrete syntax, structureMap resource interchange, Java CLI + validator tooling and a graphical editor for subsets. Teams convert every FHIR resource (month‑long sweep) and write R2↔R3 maps and CDA→FHIR transforms; engines run them but round‑trip testing showed gaps and some maps remain work in progress.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:10Why a FHIR Mapping Language
- 4:49Levels of Mapping
- 8:36Concept Map resource
- 10:35Concept Map Example
- 12:41Detailed Mapping: Requirements
- 13:44Architecture
- 15:46Language Decisions
- 19:56Resource StructureMap
- 20:23Tutorial: Simple Case
- 21:07Understanding content/class models
- 25:19Length Restriction
- 26:11Type Conversion
- 26:28Hierarchical Content #2
- 29:08Invoking Transforms
- 34:06Examples: CDA
related talks
21mTransitioning of Message Mapping Guide to FHIR Implementation Guide
38mFHIR Projects
29mFIDDLR: streamlining reuse with concern-specific modelling languages
39mOpen mHealth OmH and FHIR
45mMechanics of FHIR in Reporting and Referrals
16mThe Future of Healthcare and Clinical Research Under FHIR
21mPreparations and plans from the Austrian EHR towards FHIR
36mLeveraging FHIR Capabilities to Enable Patient Access and Provider Directory APIs