Stream: implementers
Topic: Mapping v3 to FHIR
Jan-Marc Verlinden (Apr 09 2019 at 11:39):
Hi there,
Maybe it is already asked, in that case sorry..;-). But we have implemented HAPI and it works perfect. Now we wish to integrate with HL7 v3, so we need some kind of mapping. Are there already tools available for this?
Lloyd McKenzie (Apr 09 2019 at 15:11):
v3 messaging or CDA? There's a lot of work happening on the latter, specifically with CCDA - check out #CCDA / FHIR mapping stream. If you're interested in mapping generic v3 messaging, the only guidance we have is here in the spec along with the RIM mappings. Each country that implemented v3 (or even that implemented CDA separate from CCDA) has typically encoded things differently, so there's no standard transformation that can occur. (v3 typically allows you to convey the same information 20+ different ways...) You might explore in your country-specific chat stream to see if there have been any conversion efforts of the country-specific v3 standards.
Jan-Marc Verlinden (Apr 09 2019 at 15:51):
Many thanks for your answer. It is about plain v3 messages for connecting to the Dutch LSP (National Contactpoint). Would be great if some Dutchie could help me out.. ;-)
Lloyd McKenzie (Apr 09 2019 at 16:01):
@Tom de Jong @René Spronk @Michael van der Zel
René Spronk (Apr 09 2019 at 17:14):
There are transformations from/to v3 and the Dutch ZIBs, and from FHIR to the Dutch ZIBs. There will be a centralized server on the LSP to transform between v3 and FHIR. If you need to do that client-side you could probably re-use the mappings, they'll probably be available for use by any party. @Alexander Henket
Alexander Henket (Apr 09 2019 at 17:33):
Integration with V3 is something that you do on a case by case basis. We have not found how you could magically infer semantics from a V3 model just because it inherits that from the RIM. Even with an RMIM like CDA there's still too much to be said for a general purpose mapping to work.
V3 as goes round on the LSP is defined by Nictiz specifications, for as far as it concerns health data that is. Wrappers and infrastructural support messages are defined by VZVZ, but I'm sure those do not have your focus (initially).
For transformation between information standards, or IGs as they would be called internationally, that Nictiz defines we have said that we would help projects establish that. As it is not a small endeavor we do this when demand is high enough and under proper governance.
For the LSP there's work in planning phase for a FHIR facade on the V3 inner world. This FHIR facade should be capable to offer a MedMij compliant interface for a growing number of standards. We tested in the Proves programme if this setup would work at all and turns out that you can design this to work.
The transformations are documented in wiki and executed in XSLT 2.0. The wiki allows you to build your own implementation while the XSLT 2.0 allow us to test if stuff works and if you want you can use them too. We hide nothing.
Now from your question I can't tell if transformation is what you mean with 'integration', but I'm assuming you do. The only transformation out in the open is currently for Medicatieproces 6.12 and 9.0.6 (soon to be updated to 9.0.7). The next ones will be for GP Data based on Ketenzorg. A known omission is support for errors (in the wrappers). This will soon be dealt with.
https://informatiestandaarden.nictiz.nl/wiki/Mappingarchitectuur
https://informatiestandaarden.nictiz.nl/wiki/Categorie:Mappings
https://github.com/Nictiz/Medicatieproces/tree/master/Publicaties
Hope that helps. @Arianne van de Wetering
Jan-Marc Verlinden (Apr 10 2019 at 06:33):
Hi @René Spronk and @Alexander Henket,
Yesterday I was at your offices and understood that there is no mapping from v3 to FHIR available, but as I understand right now there is. Great news..;-). Could we continue this discussion by email or make an appointment?
Many thanks, Jan-Marc
jan-marc@medrecord.io
Alexander Henket (Apr 10 2019 at 06:38):
Likely. You can find my and René's email address by clicking on the avatar. Mind you that can I tell you about what we have (planned). I'm not in the lead for additions to the set for a given need. For that I'll try to connect you with the right person(s), should the need arise
Arianne van de Wetering (Apr 10 2019 at 08:13):
For the use case of mapping the Dutch dispenses ('verstrekkingenlijst') as exchanged on LSP to FHIR, please take a look at the transaction MP-9 beschikbaarstellen verstrekkingenvertaling as can be found via https://informatiestandaarden.nictiz.nl/wiki/Mappingarchitectuur#Medicatieproces_.28MP.29 .
This has been designed with MedMij in mind, further functional/technical documentation can be found via: functional and technical documentation on MedMij.
Michael van der Zel (Apr 12 2019 at 11:50):
And what about @Tom de Jong ?
Last updated: Apr 12 2022 at 19:14 UTC
