IHE is requested to add the appropriate FHIR resource to its implementation mechanism. Now I have published a complete set of FHIR compliance resources for PDQm and MHD profiles. MCSD is also available from Luke.
A little background. Common FHIR resources are available on account for planned restrictions incorporated by IHE in the IHE file in the past. The profile of IHE is a standard that considers the use of the case and creates an interoperability solution. This is done using IHE’s long-term management through the standard selection process, the usual developmental process, public comment review, the test execution stage, and the Connectathon review.
The IHE profile is similar to the HL7 implementation directory. Each organization has differences, but each one can make a similar effort. IHE is stereotyping since 1998.
As an independent organization, IHE can use very simple and clean situations that require contact with many different criteria. Profiles that need to call HL7 v2, DICOM and eb-Registry at the same time are the biggest strengths of IHE. Where HL7 is more limited than writing implementation guides to some HL7 standards such as FHIR (US Core) or CDA (C-CDA). Most likely it will be said about this in the future. HL7 and IHE work to find a great way to collaborate and integrate.
Demographic consultation for patients with mobile phones (PDQm)
I understand why IHE’s profile exists because there are multiple profiles for both use cases that show how the HL7 v2 messaging and HL7 v3 messages are restricted. So you’re history of the IHE of 2003 (14 years ago). Since IHE publishes PDQ and PDQv3, the IHE audience wants to see the taste of FHIR. Therefore, there is PDQm. The truth is, this profile has no restrictions and can have a profile. However, since they exist, we need to implement appropriate FHIR resources.
The best place is the PDQm IQ wiki page, which will update all future updates on this page. There is a section on the PDIR resources on this wiki page. On this page, all matching FHIR resources refer to the “Implementation Guide” description.
Formally, the PDQm profile is also published in the Simplifier. See https://simplifier.net/IHEPDQmimplementatio
These resource matches are also listed at https://registry.fhir.org
The following links are the current version in Simplifier. The main URI is also known as a permanent URI. The main URI can not be used in the browser, but it can be used in the FHIR registry
PDQM Implementation Guide
kind of canonical http://ihe.net/fhir/ImplementationGuide/IHE.PDQm
IHE PDQm Consumer Capability Statement
General URL http://ihe.net/fhir/CapabilityStatement/IHE.PDQm.consumer
Capacity IHE PDQm supplier capacity
General URL http://ihe.net/fhir/CapabilityStatement/IHE.PDQm.supplier
Note that we have published the definition of the structure of the patient’s origin of PDQm. It has been removed because PDQm-IHQ does not restrict the patient’s source and thus is called STU3 patient definition structure.
Competitive resources are also available on the FTP site. Ftp://ftp.ihe.net/TF_Implementation_Material/fhir/
Mobile health documents (MHD)
profile is an IHE profile due to the history of IHD XDS / XCA / XDR / XDM etc.
Family Share documents. Therefore, IHE demonstrates how the FHIR standard is
used as the API interface for these XD environments.
The best place is the IHE Wiki for MHD page, where all the future
updates on this page will be updated. There is a section on the wiki page
dedicated to FHIR MHD resources. On this page, all matching FHIR resources refer
to the “Implementation Guide” description.
The MHD profile is informally published in the Simplifier as a set of matching FHIR resources, which are also collected at https://registry.fhir.org