HL7 2.5.1 message -> HAPI FHIR

[Josh Hull]

My application is receiving an HL7 2.5.1 message, and I'd like to begin my FHIR implementation by using HAPI FHIR for internal messaging within our system. Can I take a HAPI 2.5.1 object, or a HL7 2.5.1 message and parse it into the FHIR object model?  

I haven't been able to find any documentation on getting a message from HL7 2.x into the HAPI FHIR object model, which makes me think I'm viewing the problem incorrectly.   

Does anyone have a suggestion on how to do that, documentation on doing that, or how to think about this process differently?  Thanks!

Josh

[Kevin Mayfield]

Hl7v2 to FHIR advice is on the main FHIR site. 

I've been leaving the v2 messaging alone and using FHIR for new interfaces.  

Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups "HAPI FHIR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hapi-fhir+...@googlegroups.com.
To post to this group, send email to hapi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hapi-fhir/41fe3572-48f0-4383-93e9-2b2bf2680b68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Josh]

I found an article through the main site's blog listings that talks through some of the issues. Thanks for the suggestion Kevin. It's not nearly as straight forward as I was imagining. 

http://fhirblog.com/2014/10/05/mapping-hl7-version-2-to-fhir-messages/

And also some information in the appendixes of the main FHIR page comparing the V2 model with the FHIR model: 

http://hl7.org/implement/standards/FHIR-Develop/comparison-v2.html

The section on mapping was particularly enlightening. 

"Mapping: One of the biggest challenges with HL7 V2 interoperability is the variation of implementation. Even when identical scenarios are being handled in similar business environments, the data elements supported can vary and even the place where a given data element is placed in an instance can vary. As a result, defining consistent mapping rules between V2 and FHIR at an international or even regional level is not terribly realistic. The FHIR mappings provided give a starting point for consideration, but mappings will generally need to be done on an implementation by implementation basis."

[Steve Lam]

I'm currently using HAPI HL7v2 (http://hl7api.sourceforge.net/) parse and map to HAPI FHIR. The HAPI HL7v2 API is pretty straightforward. You just have to base your mappings on your business requirements as HL7v2 is a wild west in terms of conformity and will be different depending what system the HL7v2 is coming from.