FHIR Chat · IPS Mapping (CDA/FHIR)

Stream: IPS

Topic: IPS Mapping (CDA/FHIR)

Alexander Dimitrov (Nov 29 2020 at 16:34):

Hey everybody.

I would like to do a transformation from an International Patient Summary (IPS) FHIR document / set of ressources to a IPS CDA. Both implementation guides are available:

Is there any existing script which can do such a transformation (in one direction, or in both directions)? If there is not any, it would be really great if someone could give me some hints how this can be done (guides, etc.). Would it be an option to work with the FHIR Mapping Language to do such a transformation?

Thanks in advance!

Rob Hausam (Nov 30 2020 at 02:27):

@Alexander Dimitrov Hi. As far as I am aware, there isn't anything specific to IPS that we have to offer for transforming a FHIR IPS instance to CDA IPS. There is the more general work on C-CDA on FHIR - but that (as far as I am aware) is only about transforming in the other direction. In the IPS specifications, we have stated the intention to provide and to maintain substantial alignment between the two specifications to the degree that is possible, but we explicitly did not promise that a means would be provided to directly transform between instances of the CDA and FHIR specifications (in either direction) - although that clearly could be very useful if resources are available and someone develops it.

Alexander Dimitrov (Nov 30 2020 at 16:26):

@Rob Hausam Thanks for the reply! Such a transformation might end being part of my master thesis, this is why I was curious. Since I'm still pretty new to FHIR and CDA, what do you think would be the most easy/elegant way to do such a transformation (IPS FHIR to IPS FHIR and vice versa)? Could this be done with the FHIR Mapping Language (write mapping instructions, which then can be run onto the FHIR Server), or would I run into some expected troubles? Any suggestions are very welcome :)

David Hay (Nov 30 2020 at 17:37):

Hi Alexander - I wrote a couple of blog posts on using the mapping language that may be of use to you. I don't think that the app works properly ATM (the back end operations got moved around) but could be fixed if needed. In particular, note that the mapping engine is a specific bit of functionality and not generally implemented by FHIR servers...

Alexander Zautke (Nov 30 2020 at 18:52):

@Frank Olthuijsen

Oliver Egger (Nov 30 2020 at 18:59):

@Alexander Dimitrov we worked on maps transforming IHE Pharmacy Content Profiles to FHIR and back with the FHIR mapping language, see here if interested: https://github.com/hl7ch/cda-fhir-maps .

Rob Hausam (Nov 30 2020 at 20:05):

@Alexander Dimitrov It looks like the suggestions from @David Hay and @Oliver Egger would be good to investigate. As I said before, if you (or anyone) does produce something like this for IPS, I think that would be very useful. And even if it's only an initial (partial) attempt, it would be good to test at a Connectathon.

Alexander Dimitrov (Dec 01 2020 at 15:06):

Thanks for the responses!
@David Hay Ah I understand, thank you. So the mapping engine is responsible to create the StructureMap resource, which then has to be uploaded onto the FHIR server.

David Hay (Dec 01 2020 at 17:47):

Not quite - the mapping engine needs the StructureMap/s as part of the input (as well as other resources like structure definitions). Have you seen this page in the spec?

Alexander Zautke (Dec 01 2020 at 17:54):

Over the last few Connectathons we also tried to come up with a short explanation on how the mapping language works. It can be found here: https://confluence.hl7.org/display/FHIR/Using+the+FHIR+Mapping+Language

David Hay (Dec 01 2020 at 17:54):

Also - the firely implementation has lots of info, and I'm sure that @Vadim Peretokin would be happy to help out...

David Hay (Dec 01 2020 at 17:56):

@Alexander Zautke - I guess I better go fix my tool as there's a link there!

David Hay (Dec 01 2020 at 17:59):

Also : in that page, the transformation of the instructions into the StructureMap is shown as being done by the mapping engine - could that be confusing? Would it be better labelled as 'transformer' or some such?

Alexander Zautke (Dec 01 2020 at 18:09):

The word "mapping engine" is now used everywhere, that's why we chose to leave it.

Last updated: Apr 12 2022 at 19:14 UTC

Main menu

FHIR Chat · IPS Mapping (CDA/FHIR) · IPS