| ITI45 | ITI45-12 | reviewed | Testable |
0
|
2
| | The Patient Identifier Cross-reference Manager shall be capable of accepting attributes as specified in Table 3.45.4.1.2-1 | 223 | Section 3.45.4.1.3 | 5/2/19 5:01:49 PM by wbars |
|
| 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. | 223 | Section 3.45.4.1.3 | 5/2/19 5:01:54 PM by wbars |
|
| ITI45 | ITI45-14 | reviewed | Testable |
0
|
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" | 223 | Section 3.45.4.1.3.1 | 5/2/19 5:01:59 PM by wbars |
|
| ITI45 | ITI45-15 | reviewed | Testable |
0
|
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. | 224 | Section 3.45.4.2 | 5/2/19 5:02:04 PM by wbars |
|
| ITI45 | ITI45-17 | reviewed | Testable |
0
|
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. | 228 | Section 3.45.4.2.3 | 5/2/19 5:02:08 PM by wbars |
|
| 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). | 228 | Section 3.45.4.2.3 | 6/6/19 9:09:19 AM by aberge |
|
| ITI45 | ITI45-19 | reviewed | Testable |
0
|
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). | 228 | Section 3.45.4.2.3 | 5/2/19 5:02:19 PM by wbars |
|
| ITI45 | ITI45-2 | reviewed | Testable |
0
|
3
| | Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V Web Services for IHE Transactions | 217 | Section 3.45.3 | 5/2/19 5:00:52 PM by wbars |
|
| 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). | 228 | Section 3.45.4.2.3 | 6/6/19 9:09:49 AM by aberge |
|
| ITI45 | ITI45-21 | reviewed | Testable |
1
|
2
| | The Patient Identifier Cross-reference Manager does not recognize the Patient ID sent in the PatientIdentifier.value.AE (application error) is returned in Acknowledgement.typeCode (transmission wrapper) and 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).An AcknowledgmentDetail class is returned in which the attributes typeCode, code, and location are valued as follows:- typeCode : E- code: 204- location: XPath expression for the value element of the PatientIdentifier parameter | 228 | Section 3.45.4.2.3 | 6/6/19 9:10:12 AM by aberge |
|
| ITI45 | ITI45-22 | reviewed | Testable |
1
|
2
| | The Patient Identifier Cross-reference Manager does not recognize one or more of the Patient Identification Domains for which an identifier has been requested.AE (application error) is returned in Acknowledgement.typeCode (transmission wrapper) and in QueryAck.queryResponseCode (control act wrapper).No RegistrationEvent is returned.The queried-for patient identification domains are returned in the QueryByParameter parameter list (control act wrapper).For each domain that was not recognized, an AcknowledgmentDetail class is returned in which the attributes typeCode, code, and location are valued as follows:- typeCode: E- code: 204- Location: XPath expression for the value element of the DataSource parameter(which includes the repetition number of the parameter) | 228 | Section 3.45.4.2.3 | 6/6/19 9:10:48 AM by aberge |
|
| ITI45 | ITI45-23 | 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, and there are multiple identifiers within at least one of the requested domains.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). If the Patient Identifier Cross-reference Manager chooses to return multiple identifiers associated with the same domain, it shall return these identifiers either grouped in a single instance of the OtherIDs class, or all represented via repetitions of the Patient.id attribute. | 228 | Section 3.45.4.2.3 | 6/6/19 9:11:16 AM by aberge |
|
| ITI45 | ITI45-27 | reviewed | Testable |
1
|
3
| | When grouped with ATNA Secure Node or Secure Application actors, this transaction is to be audited as Query Information event. Audit message produced by the Patient Identifier Cross-reference Manager actor shall follow the rules defined in section 3.45.5.1.2 | 231 | Section 3.45.5.1 | 8/26/19 5:25:26 PM by aberge |
|
| ITI45 | ITI45-6 | reviewed | Testable |
0
|
2
| | The receiver shall respond to the query by sending the Patient Identifiers message (PRPA_MT201304UV02), no intermediate Accept Acknowledgement message is to be sent. | 218 | Section 3.45.4.1.2 | 5/2/19 5:01:21 PM by wbars |
|
| ITI45 | ITI45-7 | reviewed | Testable |
0
|
2
| | The receiver shall respond to the query by sending the Patient Identifiers message (PRPA_MT201304UV02), which uses the Application Level Acknowledgement transmission wrapper. This satisfies the requirements of original mode acknowledgment. | 218 | Section 3.45.4.1.2 | 5/2/19 5:01:14 PM by wbars |
|
| ITI45 | ITI45-8 | reviewed | Testable |
0
|
2
| | All appropriate identifiers shall be returned in a single response; therefore no continuation queries are allowed in this transaction. | 218 | Section 3.45.4.1.2 | 5/2/19 5:01:25 PM by wbars |
|
| ITI45 | ITI45-9 | reviewed | Testable |
0
|
2
| | If no DataSource parameter is supplied, the PIX Manager is required to return the identifiers from all known Patient Identity Domains | 219 | Section 3.45.4.1.2.1 | 5/2/19 5:01:29 PM by wbars |
|
| ITI46 | ITI46-12 | validated | Testable |
1
|
2
| | The Patient Identifier Cross-reference Manager shall have configuration indicating which Identity Consumers are interested in receiving the PIXV3 Update Notification Transactions. | 236 | Section 3.46.4.1.2 | 5/29/19 1:57:41 PM by aberge |
|
| ITI46 | ITI46-13 | validated | Testable |
1
|
2
| | This configuration information shall include identification of the identity consumer systems interested in receiving notifications and, for each of those systems, a list of the patient identifier domains of interest. | 236 | Section 3.46.4.1.2 | 5/29/19 1:57:49 PM by aberge |
|
| ITI46 | ITI46-14 | validated | Testable |
1
|
2
| | The Patient Registry Record Revised message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V | 240 | Section 3.46.4.1.2.4 | 5/29/19 1:51:43 PM by aberge |
|