Two independent projects this week sent to the FHIR mailing list their diagrams of how they are using FHIR as an API to classic XDS environments. I thought both diagrams were fantastic illustrations of the power of the MHD, PIXm, and PDQm profiles. The power of using FHIR as a simplifying API to classic environments. These diagrams are not only technically wonderful, but also beautiful.
I have asked for permission to republish these diagrams. They are not my diagrams.
From the Jose Maria Olmo Millan working on the prevvy project, writes:
We are using a similar approach for our patient centric platform (prevvy.co). We have developed a FHIR/IHE server and we store CDA and FHIR documents in the same IHE infrastructure using IHE metadata capabilities.
..
FYI, this is our FHIR/IHE/DIRECT architecture
From Ioana Singureanu working on SAMHS BHITS project writes:
I'm supporting the SAMHS BHITS project to create a standard-based, open-source patient portal application (My Health Compass). Our project will use FHIR as an abstraction layer for the application. Our IExHub will expose FHIR services to the application while an HIE using standard-based SOAP services (IHE ITI) and/or HL7 Version 2 transactions.
We are not using FHIR for information exchange right now but when EHRs will support FHIR, the our users will be able to directly to one more EHRs to read and, in some cases, even create new resources (e.g. privacy consent).
Here is an overview of the component architecture:
Note that SAMHS will be at HIMSS next week, seek out Ken Salyards out at the FHA area of the HIMSS Interoperability Showcase.
Note they are also doing more than this, specifically there is also discussion on CDA<-->FHIR. Ill let Keith speak about that.
These are great examples. Well done!
I have asked for permission to republish these diagrams. They are not my diagrams.
From the Jose Maria Olmo Millan working on the prevvy project, writes:
We are using a similar approach for our patient centric platform (prevvy.co). We have developed a FHIR/IHE server and we store CDA and FHIR documents in the same IHE infrastructure using IHE metadata capabilities.
..
FYI, this is our FHIR/IHE/DIRECT architecture
From Ioana Singureanu working on SAMHS BHITS project writes:
I'm supporting the SAMHS BHITS project to create a standard-based, open-source patient portal application (My Health Compass). Our project will use FHIR as an abstraction layer for the application. Our IExHub will expose FHIR services to the application while an HIE using standard-based SOAP services (IHE ITI) and/or HL7 Version 2 transactions. We are not using FHIR for information exchange right now but when EHRs will support FHIR, the our users will be able to directly to one more EHRs to read and, in some cases, even create new resources (e.g. privacy consent).
Here is an overview of the component architecture:
Note that SAMHS will be at HIMSS next week, seek out Ken Salyards out at the FHA area of the HIMSS Interoperability Showcase.
Note they are also doing more than this, specifically there is also discussion on CDA<-->FHIR. Ill let Keith speak about that.
These are great examples. Well done!
No comments:
Post a Comment