| 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-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-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 |
|
| ITI44 | ITI44-29 | reviewed | Testable |
1
|
2
| | When 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. | 210 | Section 3.44.4.2. | 3/23/15 2:42:06 PM by aberge |
|
| ITI44 | ITI44-31 | reviewed | Testable |
1
|
2
| | The 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" | 219 | Section 3.44.4.2.3.1 | 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-47 | reviewed | Testable |
1
|
3
| | When 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 Identifier Cross-reference Manageractor shall comply with the definitin given in table 3.44.5.1.2 | 225 | Section 3.44.5.1.2 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI44 | ITI44-9 | reviewed | Testable |
2
|
3
| | Each message (PRPA_MT201301UV02 and PRPA_MT201302UV02) shall be acknowledged by the HL7 v3 Accept Acknowledgement (MCCI_MT000200UV01), which is described in ITI TF-2x: Appendix O. | 202 | Section 3.44.4.1.2 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI45 | ITI45-12 | reviewed | Testable |
1
|
2
| | The Patient Identifier Cross-reference Manager shall be capable of accepting attributes as specified in Table 3.45.4.1.2-1 | 233 | Section 3.45.4.1.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI45 | ITI45-13 | validated | Testable |
0
|
2
| | The Patient Identifier Cross-reference Manager shall be capable of accepting multiple concurrent PIX Query requests (Get Corresponding Identifiers messages) and responding correctly using the Return Corresponding Identifiers message. | 233 | Section 3.45.4.1.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI45 | ITI45-14 | reviewed | Testable |
1
|
2
| | The following WSDL naming conventions SHALL apply:
wsdl:definitions/@name="PIXManager":
"get identifiers" query -> "PRPA_IN201309UV02_Message"
"get identifiers" response ->"PRPA_IN201310UV02_Message"
portType -> "PIXManager_PortType"
get identifiers operation -> "PIXManager_PRPA_IN201309UV02"
SOAP 1.2 binding -> "PIXManager_Binding_Soap12"
SOAP 1.2 port -> "PIXManager_Port_Soap12" | 233 | Section 3.45.4.1.3.1 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI45 | ITI45-15 | reviewed | Testable |
1
|
2
| | The Patient Identifier Cross-reference Managers response to the Get Corresponding Identifiers message will trigger the following message:
Patient Registry Get Identifiers Query Response (PRPA_TE201310UV02)
This query response returns all other identifiers associated with a particular person identifier. | 234 | Section 3.45.4.2 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI45 | ITI45-17 | reviewed | Testable |
1
|
2
| | The Patient Identifier Cross-reference Manager shall return the attributes within the HL7 Patient Identifiers message (PRPA_MT201304UV02) that are required by the HL7 standard, as shown in Figure 3.45.4.2.2-1. | 238 | Section 3.45.4.2.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI45 | ITI45-18 | reviewed | Testable |
1
|
2
| | The Patient Identifier Cross-reference Manager recognizes the specified Patient ID sent by the Patient Identifier Cross-reference Consumer in PatientIdentifier.value, and corresponding identifiers exist for the specified patient in at least one of the domains requested in DataSource.value (one identifier per domain). (See Case 6 below for the required behavior if there are multiple identifiers recognized within a given Identifier Domain by the Patient Identifier Cross-reference Manager.)
AA (application accept) is returned in Acknowledgement.typeCode (transmission wrapper).
OK (data found, no errors) is returned in QueryAck.queryResponseCode (control act wrapper).
A single RegistrationEvent class is returned, where at least one of the identifiers, which the Patient Identifier Cross-reference Manager did recognize as belonging to a requested domain, is returned in Patient.id. Subsequent such identifiers, if any, are returned in either Patient.id or OtherIDs.id, not including the queried-for patient identifier that is returned in the QueryByParameter parameter list (control act wrapper). | 238 | Section 3.45.4.2.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI45 | ITI45-19 | reviewed | Testable |
1
|
2
| | The Patient Identifier Cross-reference Manager recognizes the specified Patient ID sent by the Patient Identifier Cross-reference Consumer in PatientIdentifier.value, there are no specific domains requested in the query (no DataSource parameters are present), and corresponding identifiers exist for the specified patient in at least one other domain known to the Patient Identifier Cross-reference Manager (one identifier per domain).
AA (application accept) is returned in Acknowledgement.typeCode (transmission wrapper).
OK (data found, no errors) is returned in QueryAck.queryResponseCode (control act wrapper).
A single RegistrationEvent class is returned, where at least one of the identifiers, which the Patient Identifier Cross-reference Manager did recognize as belonging to a domain different from the domain of the queried-for patient identifier, is returned in Patient.id. Subsequent such identifiers, if any, are returned in either Patient.id or OtherIDs.id, not including the queried-for patient identifier, which is returned in the QueryByParameter parameter list (control act wrapper). | 238 | Section 3.45.4.2.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI45 | ITI45-2 | reviewed | Testable |
2
|
3
| | Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V Web Services for IHE Transactions | 227 | Section 3.45.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI45 | ITI45-20 | reviewed | Testable |
1
|
2
| | The Patient Identifier Cross-reference Manager recognizes the specified Patient ID sent in PatientIdentifier.value, but no identifier exists for that patient in any of the domains sent in DataSource.value.
AA (application accept) is returned in Acknowledgement.typeCode (transmission wrapper).
NF (no data found, no errors) is returned in QueryAck.queryResponseCode (control act wrapper).
No RegistrationEvent is returned.
The queried-for patient identifier is returned in the QueryByParameter parameter list (control act wrapper). | 238 | Section 3.45.4.2.3 | 2/5/16 12:27:23 PM by aboufahj |
|