Stream: v2 to FHIR
Topic: R4 to v2 converter
Akshay (Mar 03 2022 at 18:57):
Is there a R4 to hl7v2 converter?
Lloyd McKenzie (Mar 03 2022 at 19:11):
I've moved your post to a different topic. (Always change your topic name to reflect your question - or search for an existing related thread.)
Lloyd McKenzie (Mar 03 2022 at 19:27):
Short answer - no.
- There's no 'standard' HL7 FHIR Bundle. A bundle might contain any kind of resource and there be no indication of what 'kind' of message should result from it.
- The same resources might map different ways depending on what message you're mapping to
- Expectations for the content of a message vary from v2 system to v2 system
- FHIR is extensible and those would need to be individually mapped
There are a standard set of mappings available in the v2-to-FHIR implementation guide that you could use as a starting point.
John Moehrke (Mar 03 2022 at 19:28):
I very much expect that for specific data-flows that the commercial HL7 interface engines have solutions. These would come with the constraints that Lloyd mentions.
René Spronk (Mar 04 2022 at 15:36):
However, one of the main problems is going from a non-event based environment (REST) to a fully business-event-based messaging environment. Sure, the mapping of data elements from FHIR resources to v2 segments has its challenges, but bridging the gap between messaging and REST turns out to be rather tricky as well. At the very least you'd have to have some fancy event-detection mechanism based on the (ultimate) source of the data. Most 'mapping solutions' (whether commercial or not) don't offer anything when it comes to mapping the fundamental differences in exchange paradigms.
Last updated: Apr 12 2022 at 19:14 UTC
