| 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 |
|
| ITI8 | ITI8-003 | validated | Testable |
0
|
1
| | Each message shall be acknowledged by the HL7 ACK message (see ITI TF-2x C.2.3) sent by the receiver of ADT message to its sender | 39 | Section 3.8.4.1.2 | 4/4/16 4:53:07 PM by aberge |
|
| ITI8 | ITI8-018 | validated | Testable |
0
|
1
| | The Patient Identifier Cross-reference Manager shall be capable of accepting attributes in the PID segment as specified in HL7 standard as well as their extended field length as defined in Table 3.8-2. This is to ensure that the Patient Identifier Cross-reference Manager can handle a sufficient set of corroborating information in order to perform its cross-referencing function. | 44 | Section 3.8.4.1.3 | 4/4/16 4:50:37 PM by aberge |
|
| ITI8 | ITI8-019 | validated | Testable |
0
|
1
| | If the PID-3.4 (assigning authority) component is not included in the message (as described in Section 3.8.4.1.2.3) the Patient Identifier Cross-reference Manager shall fill PID-3.4 prior to storing the ID information and performing its cross-referencing activities. | 45 | Section 3.8.4.1.3 | 4/4/16 4:50:40 PM by aberge |
|
| ITI8 | ITI8-020 | validated | Testable |
0
|
1
| | The Patient Identifier Cross-reference Manager Actor shall only recognize (by configuration) a single Patient Identity Source Actor per domain. | 45 | Section 3.8.4.1.3 | 4/4/16 5:01:40 PM by aberge |
|
| ITI8 | ITI8-021 | validated | Testable |
0
|
1
| | Once the Patient Identifier Cross-reference Manager has completed its cross-referencing function, it shall send out notification to any Patient Identifier Cross-reference Consumers that have been configured using the PIX Update Notification transaction (see Section 3.10 for the details of that transaction). | 45 | Section 3.8.4.1.3 | 4/4/16 4:42:44 PM by aberge |
|
| ITI8 | ITI8-022 | validated | Testable |
0
|
1
| | The identifier of the domain shall specify all 3 components of the HL7 assigning authority (including the namespace ID and/or both the universal ID and universal ID type subcomponents) of the PID-3 field for the identification of the domain. | 45 | Section 3.8.4.1.3.1 | 4/4/16 4:51:01 PM by aberge |
|
| ITI8 | ITI8-037 | validated | Testable |
0
|
1
| | When the Patient Identifier Cross-reference Manager receives the ADT^A40 message type of the Patient Identity Feed transaction, it shall cross-reference the patient identifiers provided in the PID-3 and MRG-1 fields of the message by replacing any references it is maintaining internally to the patient ID provided in the MRG-1 field by the patient ID included in the PID-3 field. | 48 | Section 3.8.4.2.3 | 4/4/16 4:44:19 PM by aberge |
|
| ITI9 | ITI9-001 | validated | Testable |
0
|
1
| | A Patient Identifier Cross-reference Consumers which needs to get the patient identifier associated with a domain for which it needs patient related information shall trigger the request for corresponding patient identifiers message based on the following HL7 trigger event:
Q23 Get Corresponding Identifiers | 57 | Section 3.9.4.1.1 | 4/4/16 4:54:53 PM by aberge |
|
| ITI9 | ITI9-005 | validated | Testable |
0
|
1
| | The Patient Identifier Cross-reference Consumer Actor shall provide component QPD-3.4, Assigning Authority, by including either the first subcomponent (namespace ID) or the second and third subcomponents (universal ID and universal ID type) If all three subcomponents are populated, the first subcomponent shall reference the same entity as is referenced by the second and third components. | 58 | Section 3.9.4.1.2.2 | 4/4/16 4:55:21 PM by aberge |
|