Difference between revisions of "Patient Identifier Cross-Reference for Mobile (PIXm)"

Latest revision as of 10:10, 12 January 2022

defines a lightweight RESTful interface to a Patient Identifier Cross-reference Manager, leveraging technologies readily available to mobile applications and lightweight browser based applications.

Formal Specification

PIXm (html/IG) specification

Trial Implementation

@@ Line 1: / Line 1: @@
-The Patient Identifier Cross-reference for Mobile (PIXm) Profile defines a lightweight RESTful interface to a Patient Identifier Cross-reference Manager, leveraging technologies readily available to mobile applications and lightweight browser based applications.
+defines a lightweight RESTful interface to a Patient Identifier Cross-reference Manager, leveraging technologies readily available to mobile applications and lightweight browser based applications.
 __TOC__
-==Summary==
+==Formal Specification==
-The Patient Identifier Cross-reference for Mobile Integration Profile provides a transaction for mobile and lightweight browser based applications to query a Patient Identifier Cross- reference Manager for a list of patient identifiers based on the patient identifier in a different domain and retrieve a patient’s cross-domain identifiers information into the application.
-This profile provides a lightweight alternative to PIX Query [ITI-9] or PIXv3 Query [ITI-45], using a HTTP RESTful Query. This profile depends upon the implementation of the PIX or PIXV3 Profile or equivalent for the patient identity feed and update notifications. Two example groupings are shown in TF-1: 41.5.
+===[https://profiles.ihe.net/ITI/TF/Volume1/ch-41.html PIXm (html/IG) specification]===
+* [https://profiles.ihe.net/ITI/TF/Volume1/ch-41.html Trial Implementation]
-This profile does not assume Patient Identifier Cross-reference Manager has the ability to act as a full-fledged FHIR server, other than for the profiled transaction. The profile can be used to provide a RESTful interface to a PIX or PIXv3 Patient Identifier Cross-reference Manager without providing other FHIR services.
-[[Image:PIXm.jpg]]
+[[Category:ITI Profile]]
+[[Category:Profiles]]
-==Benefits==
+[[Category:FHIR]]
-The Patient Identifier Cross-reference for Mobile Profile is intended to be used by lightweight  applications and mobile devices present in healthcare enterprises of a broad range of sizes (hospital, a clinic, a physician office, etc.). It supports the cross-reference query of patient
+[[Category:PatientId]]
-identifiers from multiple Patient Identifier Domains via the following interaction:
-• The ability to access the list(s) of cross-referenced patient identifiers via a query/response.
-The following use case and descriptions assume familiarity with the profiles in ITI TF-1:5 and ITI TF-1:23, and only describe the RESTful actors and transaction alternatives.
-[[File:Process-Flow-with-PIXm.png]]
-This diagram shows how PIXm actors (in solid outlined, white boxes) can integrate into a PIX environment (gray boxes; described in ITI TF-1: 5.2). For a discussion of the relationship between this Integration Profile and an enterprise master patient index (eMPI) see ITI TF-1: 5.4
-==Details==
-The Patient Identifier Cross-reference Consumer fits into the combination of actors and transactions defined for PIX, see ITI TF-1:5. It adds the alternative of using the Mobile Patient Identifier Cross-reference Query [ITI-83] instead of the PIX Query [ITI-9], or PIXV3 Query [ITI-45] transactions. The PIXm Patient Identifier Cross-reference Consumer uses a query for sets of cross-referenced
-patient identifiers.
-'''Multiple Identifier Domains with a Single Facility/Enterprise Use Case Description'''
-A patient is in an ambulance on his way to the hospital after an accident. The mobile Care system in the ambulance wants to get allergy information (e.g., using the MHD Profile) for the patient. The mobile Care system uses the patient’s driver’s license number ‘E-123’ as their patient ID. Before requesting the allergy information from the hospital, it must translate the known patient identity (driver’s license) to the patient’s identity known by the hospital (MRN). To achieve this correlation, the mobile Care system issues a Mobile Patient Identifier Crossreference Query to the Patient Identifier Cross-reference Manager and retrieves the corresponding patient identity. It requests a list of patient ID aliases corresponding to patient ID = ‘E-123’ (within the “mobile Care domain”) from the Patient Identifier Cross-reference Manager. Having linked this patient with a patient known by medical record number = ‘007’ in the ‘ADT Domain’, the Patient Identifier Cross-reference Manager returns this list to the mobile Care system so that it may retrieve the allergies information for the desired patient. The mobile Care system can now request the allergy information from the hospital allergy system using the allergy system’s own patient ID (MRN-007) including the domain identifier/assigning authority. In this scenario, the hospital’s main ADT system (acting as a Patient Identity Source) would provide a Patient Identity Feed (using the patient’s MRN as the identifier) to the Patient Identifier Cross-reference Manager. Similarly, the mobile Care system or the external assigning authority would also provide a Patient Identity Feed to the Patient Identifier Cross-reference Manager using the patient driver’s license as the patient identifier and providing its own unique identifier domain identifier.
-'''Multiple Identifier Domains with a Single Facility/Enterprise Process Flow'''
-The PIXm Profile is intended to provide a different transport mechanism for the cross-identifier Query functionality described in the PIX Profile. Hence, the Mobile Patient Identifier Crossreference Query [ITI-83] transaction can be used where the PIX Query [ITI-9] (or equivalent) transaction is used. The following diagram describes only Patient Cross-Identity for Mobile Process Flow.
-[[File:Basic_Process_Single_Facility_Process_Flow_PIXm.png]]
-''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short.  E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
-==Systems Affected==
-''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>''
-* ''PACS systems may store, manage, and/or display Evidence Documents.''
-* ''Display systems may query, retrieve and display Evidence Documents.''
-* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
-'''Actors & Transactions:'''
-''<Insert an actor-transaction diagram, and or list of Content Definitions>''
-==Specification==
-'''Profile Status:''' [[Comments| Final Text]]
-''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
-'''Documents:'''
-''<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile.  This is a simple inventory of official normative and informative text.  If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below.  If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>''
-[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
-'''Underlying Standards:'''
-''<list all the standards on which the profile is based; if possible with links to sources>''
-:* [http://dicom.nema.org DICOM]
-:* [http://www.hl7.org HL7]
-:* ...
-==See Also==
-''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''
-'''Related Profiles'''
-''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one.  Start with the name of the other profile as a link and then explain the relationship.>''
-* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
-* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
-* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
-* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
-* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
-'''Consumer Information'''
-The [[Profile FAQ Template]] answers typical questions about what the Profile does.  ''<Replace the link with a link to the actual FAQ page for the Profile>''
-The [[Profile Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile.  ''<Replace the link with a link to the actual Purchasing page for the Profile>''
-'''Implementer Information'''
-The [[Profile Implementation Template]] provides additional information about implementing this Profile in software.  ''<Replace the link with a link to the actual Implementation page for the Profile>''
-'''Reference Articles'''
-''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis).  Go ahead, Google: IHE <Profile Name> abstract   or Google: IHE <Profile Name> and under the "more" select "Scholar".  You might be surprised. >''
-This page is based on the [[Profile Overview Template]]
-[[Category:Template]]
-<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>

Difference between revisions of "Patient Identifier Cross-Reference for Mobile (PIXm)"

Latest revision as of 10:10, 12 January 2022

Contents

Formal Specification

PIXm (html/IG) specification

Navigation menu

Search