I have been pushing IHE to add FHIR conformance resources to their publication mechanism. I now have published the full set of FHIR conformance resources for PDQm and MHD profiles. Also available is mCSD by Luke.
A bit of background. FHIR conformance resources are available to carry programatically the constraints that historically IHE has written narratively into an IHE Profile. An IHE Profile is a standard that takes a Use-Case and creates an Interoperability solution. This is done using long standing IHE Governance through a standards selection process, standards development process, public comment review, trial-implementation phase, and connectathon testing.
An IHE Profile is very similar to an HL7 Implementation Guide. Each organization has variances, but both can do similar effort. IHE has been doing Profiling since 1998
IHE as an standalone organization can very easily and cleanly Profile large use-cases that require the interaction with many different standards. Profiling that needs to simultaneously invoke HL7 v2, DICOM, and eb-Registry are the biggest strengths of IHE. Where as HL7 is more limited to writing focused Implementation Guides around the HL7 specific standards like FHIR (US-Core) or CDA (C-CDA). Much more is likely going to be said about this in the future. HL7 and IHE are working to find a good way to cooperate and complement.
The best place to go is to the IHE wiki page for PDQm, as any updates that happen in the future will be updated on that page. There is a section on this wiki page dedicated to PDQm FHIR resources. That page is also what all of the FHIR conformance resources point to as the narrative 'implementation guide'.
Informatively the PDQm profile is also published on Simplifier. See https://simplifier.net/IHEPDQmimplementatio
These conformance resources are also registered at https://registry.fhir.org
The following links are to current copy in Simplifier. The canonical URI is also given as the permanent URI. The canonical URI is not usable in a browser, but may be used at the FHIR registry
Note that previously we did publish a StructureDefinition for the PDQm Patient Resource. This has been removed as IHE PDQm does not constrain the Patient Resource at all, and therefore the STU3 Patient StructureDefintion is now referenced.
The conformance resources are also available on the FTP site ftp://ftp.ihe.net/TF_Implementation_Material/fhir/
The MHD profile is also an IHE profile due to the history of IHE XDS/XCA/XDR/XDM etc. The Document Sharing family. Thus IHE shows how to use the FHIR standard as an API to these XD* environments.
Informatively MHD profile is also published on Simplifier as a set of FHIR conformance resources, that are also registered at https://registry.fhir.org
Note the following links are to current instances maintained in Simplifier. This URL may change over time, which is why the canonical URI is provided. The canonical URI can not be used for browser navigation, but can be used for lookup at registry or simplifier as search capability allows.
A bit of background. FHIR conformance resources are available to carry programatically the constraints that historically IHE has written narratively into an IHE Profile. An IHE Profile is a standard that takes a Use-Case and creates an Interoperability solution. This is done using long standing IHE Governance through a standards selection process, standards development process, public comment review, trial-implementation phase, and connectathon testing.
An IHE Profile is very similar to an HL7 Implementation Guide. Each organization has variances, but both can do similar effort. IHE has been doing Profiling since 1998
IHE as an standalone organization can very easily and cleanly Profile large use-cases that require the interaction with many different standards. Profiling that needs to simultaneously invoke HL7 v2, DICOM, and eb-Registry are the biggest strengths of IHE. Where as HL7 is more limited to writing focused Implementation Guides around the HL7 specific standards like FHIR (US-Core) or CDA (C-CDA). Much more is likely going to be said about this in the future. HL7 and IHE are working to find a good way to cooperate and complement.
Patient Demographics Query for Mobile (PDQm)
I will be clear the reason this is an IHE profile is because of long standing set of Profiles of the exact same use-cases that show how to constrain HL7 v2 messaging, and HL7 v3 messaging. Thus, they are historically in IHE from 2003 (14 years ago). Given that IHE had PDQ and PDQv3 published, the IHE audience wanted to see the FHIR flavor. Thus PDQm exists. The reality is that this profile is about as unconstrained as a profile can be. But because it exists, we need to publish FHIR conformance resources.
Informatively the PDQm profile is also published on Simplifier. See https://simplifier.net/IHEPDQmimplementatio
These conformance resources are also registered at https://registry.fhir.org
The following links are to current copy in Simplifier. The canonical URI is also given as the permanent URI. The canonical URI is not usable in a browser, but may be used at the FHIR registry
- PDQm ImplementationGuide
- canonical URI http://ihe.net/fhir/ImplementationGuide/IHE.PDQm
- IHE PDQm Consumer Actor CapabilityStatement
- IHE PDQm Supplier Actor CapabilityStatement
Note that previously we did publish a StructureDefinition for the PDQm Patient Resource. This has been removed as IHE PDQm does not constrain the Patient Resource at all, and therefore the STU3 Patient StructureDefintion is now referenced.
The conformance resources are also available on the FTP site ftp://ftp.ihe.net/TF_Implementation_Material/fhir/
Mobile Healthcare Documents (MHD)
The best place to go is to the IHE wiki page for MHD, as any updates that happen in the future will be updated on that page. There is a section on this wiki page dedicated to MHD FHIR resources. That page is also what all of the FHIR conformance resources point to as the narrative 'implementation guide'.
Informatively MHD profile is also published on Simplifier as a set of FHIR conformance resources, that are also registered at https://registry.fhir.org
Note the following links are to current instances maintained in Simplifier. This URL may change over time, which is why the canonical URI is provided. The canonical URI can not be used for browser navigation, but can be used for lookup at registry or simplifier as search capability allows.
- IHE MHD Implementation Guide
- canonical URI http://ihe.net/fhir/ImplementationGuide/IHE.MHD
- FormatCode CodeSystem
- canonical URI http://ihe.net/fhir/ValueSet/IHE.FormatCode.codesystem
- Identifier urn:oid:1.3.6.1.4.1.19376.1.2.3
- FormatCode ValueSet
- canonical URI http://ihe.net/fhir/ValueSet/IHE.formatcode.vs
- Identifier urn:oid:1.3.6.1.4.1.19376.1.2.7.1
- Actor Capability Statements
- MHD Document Source Actor CapabilityStatement
- MHD Document Recipient Actor CapabilityStatement
- MHD Document Responder Actor CapabilityStatement
- MHD Document Consumer Actor CapabilityStatement
- Structure Definitions
- Document Manifest
- List (Folder)
- canonical URI http://ihe.net/fhir/StructureDefinition/IHE.MHD.List
- DocumentReference from Query with Comprehensive Metadata
- DocumentReference from Query with Minimal Metadata
- DocumentReference in Provide with Comprehensive Metadata
- canonical URI http://ihe.net/fhir/StructureDefinition/IHE.MHD.Provide.Comprehensive.DocumentReference
- DocumentReference in Provide with Minimal Metadata
- MHD Provide Document Bundle with Minimal Metadata (ITI-65)
- MHD Provide Document Bundle with Comprehensive Metadata (ITI-65)
Conclusion
I likely have made mistakes... Please point them out to me so I can fix them. I am very open to opportunities for improvement.
This comment has been removed by a blog administrator.
ReplyDelete