| 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-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-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-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-3 | to be reviewed | Testable |
0
|
2
| | Patient Registry Record Revised (PRPA_TE201302UV02) event from a Patient Identity Source shall trigger the Revise Patient Record message. | 201 | Section 3.44.4.1.1 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-32 | to be reviewed | Testable |
0
|
2
| | The Document Registry shall be capable of accepting attributes in the Resolve Duplicates message as specified in Table 3.44.4.2.2.2-1 | 220 | Section 3.44.4.2.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-33 | to be reviewed | Testable |
0
|
2
| | Other attributes may exist, but the Document Registry shall ignore them. | 220 | Section 3.44.4.2.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-34 | to be reviewed | Testable |
0
|
2
| | When the Document Registry receives the Resolve Duplicates message of the Patient Identity Feed transaction, it shall merge the patient identity specified in the PriorRegistrationRole.id attribute of the Control-Act wrapper (subsumed patient identifier) into the patient identity specified in Patient.id attribute of the message payload (surviving patient identifier) in its registry. | 220 | Section 3.44.4.2.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-35 | to be reviewed | Testable |
0
|
2
| | After the merge, all Document Submission Sets (including all Documents and Folders beneath them) under the secondary patient identity before the merge shall point to the primary patient identity | 220 | Section 3.44.4.2.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-36 | to be reviewed | Testable |
0
|
2
| | The secondary patient identity shall no longer be referenced in the future services provided by the Document Registry | 220 | Section 3.44.4.2.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-37 | to be reviewed | Testable |
0
|
2
| | The following conditions shall be detected by the Document Registry. Messages containing these conditions shall not update the state of the Document Registry.
The subsumed patient identifier is not issued by the correct Assigning Authority according to the Affinity Domain configuration.
The surviving patient identifier is not issued by the correct Assigning Authority according to the Affinity Domain configuration.
The subsumed and surviving patient identifiers are the same.
The subsumed patient identifier has already been subsumed by an earlier message.
The surviving patient identifier has already been subsumed by and earlier message.
The subsumed patient identifier does not convey a currently active patient identifier known to the Document Registry. | 220 | Section 3.44.4.2.4 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-4 | to be reviewed | Testable |
0
|
2
| | The Patient Identifier Cross-reference Manager shall only perform cross-referencing logic on messages received from Patient Identity Source Actors | 201 | Section 3.44.4.1.1 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-43 | to be reviewed | Testable |
0
|
2
| | If none of the error conditions (see ITI44-37) occur then the Document Registry shall perform the following duties:
1. Records the merge. Only the subsumed and surviving patient identifiers need be remembered. A patient identifier merge affects the processing of future Register Document Set [ITI-14] transactions. See ITI TF-2a: 3.14.4.1.2.12 XDS Registry Adaptorfor details.
2. Multiple merge transactions can form a recorded merge chain, where the Subsumed identifier of the current merge is the Surviving identifier of a previous merge.
3. Register Document Set transactions referencing a subsumed identifier are rejected with an XDSUnknownPatientId error.
4. Stored Query transactions referencing a subsumed identifier return no content.
5. Stored Query transactions referencing a surviving identifier successfully match the entire recorded merge chain and return appropriate metadata.
6. No change in the Registry Query transaction. | 220 | Section 3.44.4.2.4 | 2/5/16 12:27:23 PM by aboufahj |
|