search

IHE / IT-Infrastructure

Online repository for information assets supporting the profiles (implementation specifications) in the IHE IT Infrastructure Technical Framework.
Creative Commons Attribution 4.0 International
33 stars 13 forks source link

Mobile Patient Identity Feed #147

Closed JohnMoehrke closed 3 years ago

JohnMoehrke commented 3 years ago
  1. Proposed Work Item: Mobile Patient Identity Feed Proposal Editor: Oliver Egger, ahdis ag and Martin Smock eHealth Suisse Work item Editor: Oliver Egger, ahdis ag and Martin Smock eHealth Suisse Date: 4/2/21 Version: 1.1 Domain: IHE ITI
  2. The Problem To facilitate integration for mobile applications for feeding patient identifiers and patient demographics there exists no mobile IHE Profile. Patient identifiers can be queried with the PIXm profile, but there is no corresponding feed as in PIX or PIX V3. This limits that lightweight applications and mobile devices present in a broad range of healthcare enterprises can query identifiers but are not able to transmit patient identity information from an identity source to a Patient Identifier Cross-reference Manager as defined in the IHE ITI Framework.
  3. Key Use Case A mobile application wants to register a patient in a community where a PIX Manager handles the correlation of the different patient identifiers and demographics according to the rules defined by the affinity domain. The mobile application feeds its local identifier of the patient and queries afterwards patient identifier valid for the affinity domain based on its local identifier.
  4. Standards & Systems IHE PIX, IHE PIX V3 IHE PMIR Mobile Patient Identity Feed [ITI-93] transaction.
  5. Discussion IHE has defined a solution for the transmission of patient identity information for PIX and PIX V3, it would be a valuable addition to have a mobile RESTFul version of it, as we see in Switzerland that SOAP based transactions are a barrier to integration to affinity domains for mobile applications. IHE could offer an additional blueprint which would be globally available. The PMIR Patient Identify Feed transaction covers already a part of the needed transmission however PMIR has a use-case that requires the creation of a centrally managed golden/master identification attributes which is not the same as for a Patient Identifier Cross-reference Manager.
JohnMoehrke commented 3 years ago

merged into #149