Stream: implementers
Topic: FHIRPath in HL7v2
Aaron (Sep 06 2018 at 16:29):
I noticed that there is an Appendix on on the FHIR specification about using FHIRPath to against HL7v2 messages. (http://hl7.org/fhirpath/#hl7v2)
At a glance, it doesn't appear that the FHIR .NET API implemented any specific support for HL7v2. (I may have just missed it.)
Out of curiosity, does anybody here have any practical experience with FHIRPath and HL7v2? Any thoughts on the experience that you can share? It seems like everybody will still have to create their own models.
Grahame Grieve (Sep 06 2018 at 21:49):
It seems like everybody will still have to create their own models.
Grahame Grieve (Sep 06 2018 at 21:49):
not sure what that means
Grahame Grieve (Sep 06 2018 at 21:49):
I intended to implement against v2, but the opportunity hasn't come up yet
Ewout Kramer (Sep 14 2018 at 12:23):
Hi Aaron - in the .NET API the FhirPath engine is not written against the FHIR model, but against an abstract interface called IElementNavigator. This interface represents the data according to the abstract model sketched in the intro of the FHIRPath specification. I have not implemented this interface for V2, but anyone should be able to do so.
nicola (RIO/SS) (Sep 14 2018 at 12:49):
Try new fhirpath.js - it's dynamic and model agnostic :) - https://lhncbc.github.io/fhirpath.js/
Last updated: Apr 12 2022 at 19:14 UTC
