Please use a compatible browser :Google Chrome or Mozilla Firefox
Page expired. Any change will be lost. Try to refresh the page.
Gazelle update scheduled, unsaved changes will be lost :
Your session will timeout :
Redeployed...
Logged out...
The server is restarting. Any change will be lost.
 

View Transaction

View Transaction Information

Id: 139

Keyword: ITI-44

Name: Patient Identity Feed HL7 V3

Description: Patient Identity Feed HL7 V3

TF Reference:

Status: Final Text

Document Section :

None

Id
Keyword
Name
Description
Action
39 XDS.b Cross-Enterprise Document Sharing The Cross-Enterprise Document Sharing (XDS.b) IHE Integration Profile facilitates the registration, distribution and access across health enterprises of patient electronic health records. Cross-Enterprise Document Sharing is focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility.
44 PIXV3 Patient Identifier Cross-Reference HL7 V3 The PIX profile supports the Cross-referencing of patient identifiers from multiple Patient Identification Domains. These Cross-referenced patient identifiers can then be used by "identity consumer" systems to correlate information about a single patient from sources that "know" the patient by different identifiers. This allows a Clinician to have more complete view of the patient information.
90 CH:XDS-I.b Cross-Enterprise Document Sharing for Imaging
356 CH:PIXV3 Patient Identifier Cross-Referencing HL7 V3 Swiss Extension
386 CH:XDS.b Cross-Enterprise Document Sharing Swiss Extension
Id
Keyword
Name
Description
Action
27PAT_ID_X_REF_MGRPatient Identity Cross-reference ManagerServes a well-defined set of Patient Identification Domains. Based on information provided by in each Patient Identification Domain by a Patient Identification Source Actor, it manages the cross-referencing of patient identifiers across Patient Identification Domains.
43DOC_REGISTRYDocument RegistryThe Document Registry Actor maintains metadata about each registered document in a document entry. This includes a link to the Document in the Repository where it is stored. The Document Registry responds to queries from Document Consumer actors about documents meeting specific criteria. It also enforces some healthcare specific technical policies at the time of document registration.
45PAT_ID_SRCPatient Identity SourceEach Patient Identification Domain requires this Actor to assign patient identities and to notify a Patient Identity Cross-reference Manager Actor of all events related to patient identification (creation, update, merge, etc.). For example, the Registration (ADT) Actor defined by the radiology Scheduled Workflow Profile would likely be a Patient Identity Source.
Assertion Id
Description
ITI44-1 Patient Identity Feed HL7 V3 references the following standard HL7 Version 3 Edition 2008 Patient Administration DSTU, Patient Topic (found at http://www.hl7.org/memonly/downloads/v3edition.cfm#V32008).
ITI44-10 The Patient Registry Record Added/Revised messages will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.
ITI44-11 The following WSDL naming conventions SHALL apply for transmission of the Patient Registry Record Added/Revised messages : add message -> "PRPA_IN201301UV02_Message" revise message -> "PRPA_IN201302UV02_Message" acknowledgement -> "MCCI_IN000002UV01_Message"
ITI44-12 The Patient Identifier Cross-reference Manager shall be capable of accepting attributes specified in Table 3.44.4.1.2-1
ITI44-13 Once the Patient Identifier Cross-reference Manager has completed its cross-referencing function, it shall make the newly cross-referenced identifiers available to PIX queries and send out notification to any Patient Identifier Cross-reference Consumers that have been configured as being interested in receiving such notifications using the PIX Update Notification HL7 V3 transaction (see ITI TF-2b: 3.46 for the details of that transaction).
ITI44-14 The following WSDL naming conventions SHALL apply: wsdl:definitions/@name="PIXManager": add message -> "PRPA_IN201301UV02_Message" revise message -> "PRPA_IN201302UV02_Message" acknowledgement ->"MCCI_IN000002UV01_Message" portType -> "PIXManager_PortType" add operation -> "PIXManager_PRPA_IN201301UV02" revise operation -> "PIXManager_PRPA_IN201302UV02" SOAP 1.2 binding -> "PIXManager_Binding_Soap12" SOAP 1.2 port -> "PIXManager_Port_Soap12"
ITI44-16 The Document Registry shall be capable of accepting attributes in the Patient Registry Record Added or Patient Registry Record Revised messages as specified in Table 3.44.4.1.2-1 .
ITI44-17 The Document Registry shall store only the patient identifiers of the patient identification domain designated by the Affinity Domain for document sharing in the registry
ITI44-18 Patient identifiers of other patient identification domains, if present in a received message, shall be ignored by the Document Registry.
ITI44-19 The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.
ITI44-2 Patient Registry Record Added (PRPA_TE201301UV02) event from a Patient Identity Source shall trigger the Add Patient Record message.
ITI44-20 The following WSDL naming conventions SHALL apply for the Document Registry: wsdl:definitions/@name="DocumentRegistry": "add" message -> "PRPA_IN201301UV02_Message" "revise" message -> "PRPA_IN201302UV02_Message" acknowledgement ->"MCCI_IN000002UV01_Message" portType -> "DocumentRegistry_PortType" add operation -> "DocumentRegistry_PRPA_IN201301UV02" revise operation -> "DocumentRegistry_PRPA_IN201302UV02" SOAP 1.2 binding -> "DocumentRegistry_Binding_Soap12" SOAP 1.2 port -> "DocumentRegistry_Port_Soap12"
ITI44-21 When two patients™ records are found to identify the same patient by a Patient Identity Source in a Patient Identifier Domain, the Patient Identity Source shall indicate this information using the following trigger: Patient Registry Duplicates Resolved (PRPA_TE201304UV02)
ITI44-22 The message shall be generated by the system (Patient Identity Source) that performs the update whenever two patient records are found to reference the same person.
ITI44-23 The Patient Registry Duplicates Resolved interaction is carried out by the HL7 v3 Patient Demographics message (PRPA_MT201303UV02) .
ITI44-24 Each HL7 Merge Patient message shall be acknowledged by the HL7 v3 Accept Acknowledgement (MCCI_MT000200UV01), which is described in ITI TF-2x: Appendix O
ITI44-25 The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.
ITI44-26 The following WSDL naming conventions SHALL apply for transmitting the Patient Registry Resolve Duplicates message: "resolve duplicates" message -> "PRPA_IN201304UV02_Message" Acknowledgement -> "MCCI_IN000002UV01_Message"
ITI44-27 The Patient Identifier Cross-reference Manager shall be capable of accepting attributes in the Resolve Duplicates message as specified in Table 3.44.4.2.2-1.
ITI44-28 After the identifier references are replaced, the Patient Identifier Cross-reference Manager shall reapply its internal cross-referencing logic/ policies before providing the updated information via either the PIX Query or PIX Notification Transactions

Tool index

  • Simulators

    Copyright IHE 2024
  • Gazelle 7.1.7
Back to top