| ITI44 | ITI44-1 | reviewed | Testable |
3
|
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). | 201 | Section 3.44.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-10 | to be reviewed | Testable |
0
|
2
| | The Patient Registry Record Added/Revised messages will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. | 209 | Section 3.44.4.1.2.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-11 | to be reviewed | Testable |
0
|
2
| | 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"
| 209 | Section 3.44.4.1.2.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-12 | reviewed | Testable |
1
|
2
| | The Patient Identifier Cross-reference Manager shall be capable of accepting attributes specified in Table 3.44.4.1.2-1 | 210 | Section 3.44.4.1.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-13 | validated | Testable |
1
|
2
| | 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). | 210 | Section 3.44.4.1.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-14 | reviewed | Testable |
1
|
2
| | 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"
| 211 | Section 3.44.4.1.3.1 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-16 | to be reviewed | Testable |
0
|
2
| | 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 . | 212 | Section 3.44.4.1.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-17 | to be reviewed | Testable |
0
|
2
| | 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 | 212 | Section 3.44.4.1.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-18 | to be reviewed | Testable |
0
|
2
| | Patient identifiers of other patient identification domains, if present in a received message, shall be ignored by the Document Registry. | 212 | Section 3.44.4.1.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-19 | reviewed | Testable |
2
|
2
| | The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. | 217 | Section 3.44.4.2.2.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-2 | to be reviewed | Testable |
0
|
1
| | Patient Registry Record Added (PRPA_TE201301UV02) event from a Patient Identity Source shall trigger the Add Patient Record message. | 201 | Section 3.44.4.1.1 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-20 | to be reviewed | Testable |
0
|
2
| | 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" | 212 | Section 3.44.4.1.4.1 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-21 | to be reviewed | Testable |
0
|
1
| | 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) | 214 | Section 3.44.4.2.1 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-22 | to be reviewed | Testable |
0
|
2
| | 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. | 214 | Section 3.44.4.2.2 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-23 | to be reviewed | Testable |
0
|
2
| | The Patient Registry Duplicates Resolved interaction is carried out by the HL7 v3 Patient Demographics message (PRPA_MT201303UV02) . | 214 | Section 3.44.4.2.2 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-24 | reviewed | Testable |
1
|
3
| | 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 | 214 | Section 3.44.4.2.2 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-25 | reviewed | Testable |
1
|
3
| | The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. | 217 | Section 3.44.4.2.2.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-26 | to be reviewed | Testable |
0
|
2
| | 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"
| 217 | Section 3.44.4.2.2.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-27 | reviewed | Testable |
1
|
2
| | 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. | 218 | Section 3.44.4.2.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-28 | reviewed | Testable |
1
|
2
| | 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 | 218 | Section 3.44.4.2.3 | 2/5/16 12:27:23 PM by aboufahj |
|