View scope

keyword
PIXV3
Description
This scope gathers all the assertions which applies in the context of the Patient Identity Cross-referencing HL7V3 (PIXV3) integration profile.
Back

91 Assertions in Scope

Search Criteria

Id scheme
Assertion id
Predicate
ITI44ITI44-1Patient 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).
ITI44ITI44-10The Patient Registry Record Added/Revised messages will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.
ITI44ITI44-11The 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"
ITI44ITI44-12The Patient Identifier Cross-reference Manager shall be capable of accepting attributes specified in Table 3.44.4.1.2-1
ITI44ITI44-13Once 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).
ITI44ITI44-14The 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"
ITI44ITI44-19The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.
ITI44ITI44-2Patient Registry Record Added (PRPA_TE201301UV02) event from a Patient Identity Source shall trigger the Add Patient Record message.
ITI44ITI44-21When 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)
ITI44ITI44-22The 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.
ITI44ITI44-23The Patient Registry Duplicates Resolved interaction is carried out by the HL7 v3 Patient Demographics message (PRPA_MT201303UV02) .
ITI44ITI44-24Each HL7 Merge Patient message shall be acknowledged by the HL7 v3 Accept Acknowledgement (MCCI_MT000200UV01), which is described in ITI TF-2x: Appendix O
ITI44ITI44-25The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.
ITI44ITI44-26The following WSDL naming conventions SHALL apply for transmitting the Patient Registry Resolve Duplicates message: "resolve duplicates" message -> "PRPA_IN201304UV02_Message" Acknowledgement -> "MCCI_IN000002UV01_Message"
ITI44ITI44-27The 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.
ITI44ITI44-28After 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
ITI44ITI44-29When the Patient Identifier Cross-reference Manager receives the Resolve Duplicates message type of the Patient Identity Feed transaction, it shall cross-reference the patient identifiers provided in the wrapper and the payload of the message by replacing any references it is maintaining internally to the patient ID provided in the wrapper by the patient ID included in the payload.
ITI44ITI44-3Patient Registry Record Revised (PRPA_TE201302UV02) event from a Patient Identity Source shall trigger the Revise Patient Record message.
ITI44ITI44-31The following WSDL naming conventions SHALL apply: wsdl:definitions/@name="PIXManager": merge message -> "PRPA_IN201304UV02_Message" acknowledgement ->"MCCI_IN000002UV01_Message" portType -> "PIXManager_PortType" merge operation -> "PIXManager_PRPA_IN201304UV02" SOAP 1.2 binding -> "PIXManager_Binding_Soap12" SOAP 1.2 port -> "PIXManager_Port_Soap12"
ITI44ITI44-46When grouped with ATNA Secure Node or Secure Application actors, this transaction is to be audited as Patient Record event, as defined in ITI TF-2a: Table 3.20.6-1. Audit messages produced by the Patient Identity Source actor shall comply with the definitin given in table 3.44.5.1.1