FHIR North 2023: Data Mapping

Slides are available here: https://docs.google.com/presentation/d/10AR4uxrt39WpK4PfP_bN6qYxpRMKf7AyM_TCX30eBbQ/edit#slide=id.p There is a lack of guidance from the FHIR community about data mapping. https://www.hl7.org/fhir/mapping-language.html and https://www.hl7.org/fhir/structuremap.html aim to cover this gap. But, there no implementations that you can easily start to use and there is no tooling for debugging and writing FHIR mappings. So developers keep building mapping engines or using some general solutions like jsonata, jmespath, etc. Some companies build DSL like FUME or JUTE. I faced the mapping issue while building the FHIR SDC IG implementation. As a big fan of data DSL, I decided to use JUTE. It worked pretty well. But then, I realized that I don’t even need the whole set of JUTE features. I only use its data DSL nature along with fhirpath calls via function. So I simplify the JUTE by replacing JUTE’s path syntax with FHIRPath. The result was so simple and obvious to read, so I decided to replace JUTE with this new DSL. Since it is FHIRPath powered I called it FHIRPath Mapping Language. I would like to demonstrate it and show how you can leverage this approach in building mappers.