| ITI10 | ITI10-001 | validated | Testable |
0
|
1
| | The Patient Identifier Cross-reference Manager shall notify a Patient Identifier Cross-reference Consumer when there is a change in a set of cross-referenced patient identifiers for any of the patient identifiers belonging to Patient Identifier Domains of interest to the consumer. | 69 | Section 3.9.4.1.1 | 4/4/16 4:12:59 PM by aberge |
|
| ITI10 | ITI10-003 | validated | Testable |
0
|
1
| | The information provided by the Patient Identifier Cross-reference Manager to Patient Identifier Cross-reference Consumers shall only contain a list of cross-referenced identifiers for the domains of interest as configured with the Patient Identifier Cross-reference Manager in two or more of the domains managed by the Patient Identifier Cross-reference Manager. | 70 | Section 3.10.4.1.2 | 4/4/16 4:13:12 PM by aberge |
|
| ITI10 | ITI10-008 | validated | Testable |
0
|
1
| | The Patient Identifier Cross-reference Manager configuration is expected to have configuration indicating which Consumers are interested in receiving the PIX Update Notification transactions. 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. | 70 | Section 3.10.4.1.2 | 4/4/16 4:13:37 PM by aberge |
|
| ITI10 | ITI10-011 | validated | Testable |
0
|
1
| | Each ITI-10 message shall be acknowledged by the HL7 ACK message sent by the receiver of ADT message to its sender. Acknowledgement shall respect ITI TF-2x C.2.3. | 71 | Section 3.10.4.1.2 | 4/4/16 4:14:20 PM by aberge |
|
| ITI10 | ITI10-014 | validated | Testable |
0
|
1
| | The Patient Identifier Cross-reference Manager Actor shall provide only those attributes within the PID segment that are required by the HL7 standard: PID-3-Patient Identifier List and PID-5-Patient Name. | 71 | Section 3.10.4.1.2.3 | 4/4/16 4:15:25 PM by aberge |
|
| ITI10 | ITI10-015 | validated | Testable |
0
|
1
| | The Patient Identifier Cross-reference Manager Actor shall use the field PID-3 Patient Identifier List to convey the Patient IDs uniquely identifying the patient within each Patient Identification Domain for which a Patient ID exists for the specified patient. Each resulting ID returned in PID-3 shall include a fully qualified Assigning Authority component. In other words, the Assigning Authority component returned shall include ALL subcomponents (namespace ID, Universal ID, and Universal ID type). | 71 | Section 3.10.4.1.2.3 | 4/4/16 4:16:11 PM by aberge |
|
| ITI10 | ITI10-016 | validated | Testable |
0
|
1
| | To eliminate the issue of multiple name values between Patient Identifier Domains, the Patient Identifier Cross-reference Manager Actor shall return a single space character in field PID-5-Patient Name. | 71 | Section 3.10.4.1.2.3 | 4/4/16 4:16:23 PM by aberge |
|
| ITI10 | ITI10-017 | validated | Testable |
0
|
1
| | A single PID segment is sent in which one repetition of PID-3-Patient Identifier List is populated for each of the identifiers in the notification. If the Patient Identifier Cross-reference Manager Actor chooses to send multiple identifiers associated with the same domain, it shall return these identifiers grouped in successive repetitions within the PID-3-Patient Identifier List. | 72 | Section 3.10.4.1.2.3 | 4/4/16 4:16:30 PM by aberge |
|
| ITI10 | ITI10-018 | validated | Testable |
0
|
1
| | As is specified by the HL7 Standard, Version 2.5, the PV1 Segment is required. The required field PV1-2-patient class shall contain N (not applicable) to indicate the transmission of patient information outside the context of a visit or encounter. Other fields shall be left blank. | 72 | Table 3.10-2 | 4/4/16 4:58:24 PM by aberge |
|
| ITI10 | ITI10-019 | validated | Testable |
0
|
1
| | The Patient Identifier Cross-reference Consumer, when it receives the ADT^A31 message, shall update its internal identifier information for the affected patient(s) in all domains in which it is interested whenever it receives updated identifier information that results in a change to the cross-referencing of a patient. | 72 | Section 3.10.4.1.3 | 4/4/16 4:17:16 PM by aberge |
|
| ITI10 | ITI10-020 | validated | Testable |
0
|
1
| | In the case where the returned list of identifiers contains multiple identifiers for a single domain, the Patient Identifier Cross-reference Consumer shall either use ALL of the multiple identifiers from the given domain or it shall ignore ALL of the multiple identifiers from the given domain. | 72 | Section 3.10.4.1.3 | 4/4/16 4:29:14 PM by aberge |
|
| ITI38 | ITI38-019 | reviewed | Testable |
0
|
1
| | All XDSMissingHomeCommunityId errors generated by the Initiating Gateway to the document consumer of the internal actor SHALL include, in the context of the message, identification of the Responding Gateway that returned the invalid response and the element or elements that were in error. | 129 | Section 3.38.4.1.3 | 5/2/19 5:32:51 PM by NicolasBailliet |
|
| ITI38 | ITI38-020 | reviewed | Testable |
0
|
1
| | If both successes and failures are received from Responding Gateways, the Initiating Gateway shall return both RegistryObjectList and RegistryErrorList in one response and specify PartialSuccess status. | 129 | Section 3.38.4.1.3 | 5/2/19 5:32:51 PM by NicolasBailliet |
|
| ITI39 | ITI39-002 | reviewed | Testable |
0
|
1
| | Responding Gateways shall support the Asynchronous Web Services Exchange Option on the Cross Gateway Retrieve. | 134 | Section 3.39.1 | 5/3/19 8:39:49 AM by NicolasBailliet |
|
| ITI39 | ITI39-006 | reviewed | Testable |
0
|
1
| | Initiating Gateways which support the On-Demand Documents Option shall be capable of retrieving an On-Demand Document Entry | 135 | Section 3.39.4.1.2 | 5/3/19 8:58:05 AM by NicolasBailliet |
|
| ITI39 | ITI39-008 | reviewed | Testable |
0
|
1
| | Responding Gateways which support the Persistence of Retrieved Documents Option shall specify the NewRepositoryUniqueId element indicating the document is available for later retrieval and be able to return exactly the same document in all future retrieve requests for the document identified by NewDocumentUniqueId | 139 | Section 3.39.4.1.2 | 5/3/19 8:59:18 AM by NicolasBailliet |
|
| ITI39 | ITI39-010 | reviewed | Testable |
0
|
1
| | If more than one system is contacted the Responding Gateway shall consolidate the results from the multiple systems into one response to the Initiating Gateway | 136 | Section 3.39.4.1.3 | 5/3/19 9:01:55 AM by NicolasBailliet |
|
| ITI39 | ITI39-011 | reviewed | Testable |
0
|
2
| | If both successes and failures are received the Responding Gateway may choose to use PartialSuccess status to reflect both failure and success. The Responding Gateway may alternatively choose to suppress the failures and report only successes. | 136 | Section 3.39.4.1.3 | 5/3/19 9:09:52 AM by NicolasBailliet |
|
| ITI39 | ITI39-014 | reviewed | Testable |
0
|
2
| | If both successes and failures are received from Responding Gateways, the Initiating Gateway shall return both DocumentResponse and RegistryErrorList elements in one response and specify PartialSuccess status. | 136 | Section 3.39.4.1.3 | 5/3/19 9:09:25 AM by NicolasBailliet |
|
| ITI55 | ITI55-006 | reviewed | Testable |
0
|
0
| | The Responding Gateway shall support Asynchronous Web Services Exchange as described in ITI TF-2x: V.5 | 329 | Section 3.55.4.1.2 | 5/2/19 5:28:40 PM by wbars |
|