Updated MHD, PDQm, and PIXm
Patient Identifier Cross-reference for Mobile (PIXm) -
Rev. 3.0.0. This revision was created using the Implementation Guide publisher. This is an update of PIXm that was previously published in PDF form. This new publication is published in HTML form with a full set of conformance resources and examples. New functionality has been added to support a patient identity feed to inform the Patient Identity Manager of changes to patient identities.
https://profiles.ihe.net/ITI/PIXm/index.html
Patient Demographics Query for Mobile (PDQm) - Rev. 2.3.0. This revision was created using the Implementation Guide publisher. This is an update of PDQm that was previously published in PDF form. This new publication is published in HTML form with a full set of conformance resources and examples. No new features were added.
https://profiles.ihe.net/ITI/PDQm/index.html
Mobile Access to Health Documents (MHD) - Rev. 4.0.2. This revision updated the publication to use the new Implementation Guide template. No new functionality was added.
https://profiles.ihe.net/ITI/MHD/index.html
Mobile Care Services Discovery (mCSD) Use Cases White Paper - Rev. 1.1 . This white paper presents multiple use cases that mCDS supports.
https://profiles.ihe.net/ITI/papers/mCSD/index.html
IHE Publications
These new publications are a part of the IHE family of Implementation Guide Profiles, and can be found at https://profiles.ihe.net
IHE is dedicated to the task of use-case driven Implementation Guide authoring, publication, maintenance, and testing. There is a long list of IHE Profiles (a form of Implementation Guide) supporting Healthcare IT workflows within and across the Healthcare space.
IHE Connectathon
These updated Implementation Guides will be available for formal product Interoperability testing at the upcoming IHE Connectathons https://www.ihe.net/participate/connectathon.
Hi John, do the changes to these profiles also propagate to IHE PMIR profile? PMIR defines ITI-93 for Pat. Identitify Feed versus ITI-104 in PIXm. thx. Andries
ReplyDeleteThe PMIR will still use the PIXm query, but not the PIXm feed. PIXm is about cross-referencing, PMIR is about a golden single unified Patient resource. The two would never be used in the same community. A community is either using cross-referencing, or is using a golden unified Patient resource.
DeleteThe feed in PIXm is different than the feed in PMIR. The reason is because PIXm is notifying the Pix Manager of identity changes, and the Pix Manager is expected only to update cross-references. The Pix Manager is not expected to harmonize or even preserve any of the other attributes in the Patient. It is a cross-reference of many domains.
Where as PMIR is about a golden unified single Patient instance about a patient. In PMIR the source is expected to fully update everything about the Patient in that golden Patient that it "Updates" in the Patient Registry. There is no cross-referencing, as there is only one Patient per human (that Patient resource might have many business identifiers (.identifier) that have been provided by the various sources).
Further the technical flow is very different. Eventually we do envision a more unified approach. We will likely take that up in the spring. A unified technical flow would not change the expected activity, as the Pix Manager is only about cross-referencing, and the PMIR Registry is only about a golden Patient. Thus they are very different environments, and would never be used together.
Great article & Keep it up.
ReplyDeleteVery nice post you have shared with us thank you so much for sharing this useful information.. There is clearly a great deal to think about this. I think you made some great focuses in Features too. Continue working, extraordinary job !