| ITI10 | ITI10-001 | to be reviewed | Testable |
0
|
0
| | 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. The configuration of the domains of interest to a Patient Cross-reference Consumer is maintained by the Patient Cross-reference Manager. | 69 | Section 3.10.4.1.1 | 1/29/19 2:23:58 PM by null |
|
| ITI10 | ITI10-002 | to be reviewed | Testable |
0
|
0
| | Several notifications may have to be issued to communicate a single update to a set of cross-reference patient identifiers as required to reflect all the changes on the resulting sets of cross-reference patient Identifiers belonging to Patient Identifier Domains of interest to the Patient Identifier Cross-referencing Consumer. | 66 | Section 3.10.4.1.1 | 1/29/19 2:23:47 PM by null |
|
| ITI10 | ITI10-003 | to be reviewed | Testable |
0
|
0
| | It is wholly the responsibility of the Patient Identifier Cross-reference Manager to perform the matching of patient identifiers based on the patient traits it receives. 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. | 67 | Section 3.10.4.1.2 | 1/29/19 2:23:47 PM by null |
|
| ITI10 | ITI10-004 | to be reviewed | Testable |
0
|
0
| | A PIX A01 feed is sent for a patient for DOM_A. The update notification shall contain the patient identifier and assigning authority for DOM_A. | 67 | Section 3.10.4.1.2 | 1/29/19 2:23:47 PM by null |
|
| ITI10 | ITI10-005 | to be reviewed | Testable |
0
|
0
| | A PIX A01 feed is processed for DOM_AD. The Patient Identifier Cross-reference Manager cross references this patient with DOM_A. The update notification shall contain the patient identifier and assigning authority for DOM_A and DOM_AD. | 67 | Section 3.10.4.1.2 | 1/29/19 2:23:58 PM by null |
|
| ITI10 | ITI10-006 | to be reviewed | Testable |
0
|
0
| | A PIX A08 feed is processed for DOM_AD changing the patient address. The Patient Identifier Cross-reference Manager cross references determines this patient is no longer the same patient as DOM_A. Two update notifications shall be sent. One containing the patient identifier and assigning authority for DOM_A. The other one containing the patient identifier and assigning authority for DOM_AD. | 67 | Section 3.10.4.1.2 | 1/29/19 2:23:58 PM by null |
|
| ITI10 | ITI10-007 | to be reviewed | Testable |
0
|
0
| | The list of cross-references is not made available until the set of policies and processes for managing the cross-reference function have been completed. The policies of administering identities adopted by the cooperating domains are completely internal to the Patient Identifier Cross-reference Manager and are outside of the scope of this standard. Possible matches should not be communicated until the healthcare institution policies and processes embodied in the Patient Identifier Cross-reference Manager reach a positive matching decision. | 67 | Section 3.10.4.1.2 | 1/29/19 2:23:58 PM by null |
|
| ITI10 | ITI10-008 | to be reviewed | Testable |
0
|
0
| | 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. | 67 | Section 3.10.4.1.2 | 1/29/19 2:23:47 PM by null |
|
| ITI10 | ITI10-009 | to be reviewed | Testable |
0
|
0
| | The Patient Identifier Cross-reference Manager should account for consumers interested in all domains. | 67 | Section 3.10.4.1.2 | 1/29/19 2:23:58 PM by null |
|
| ITI10 | ITI10-010 | to be reviewed | Testable |
0
|
0
| | The MSH, EVN, PID and PV1 segments are required. Others are optionals. | 68 | Table 3.10-1 | 1/29/19 2:23:58 PM by null |
|
| ITI10 | ITI10-011 | to be reviewed | Testable |
0
|
0
| | Each ITI-10 message shall be acknowledged by the HL7 ACK message sent by the receiver of ADT message to its sender. See ITI TF-2x: C.2.3, Acknowledgement Modes for the definition and discussion of the ACK message. | 67 | Section 3.10.4.1.2 | 1/29/19 2:23:47 PM by null |
|
| ITI10 | ITI10-012 | to be reviewed | Testable |
0
|
0
| | The MSH segment shall be constructed as defined in ITI TF-2x: C.2.2, Message Control.
Field MSH-9 Message Type shall have all three components populated with a value. The first component shall have a value of ADT; the second component shall have the value of A31. The third component shall have a value of ADT_A05. | 68 | Section 3.10.4.1.2.1 | 1/29/19 2:23:58 PM by null |
|
| ITI10 | ITI10-013 | to be reviewed | Testable |
0
|
0
| | See ITI TF-2x: C.2.4 for the list of all required and optional fields within the EVN segment. | 68 | Section 3.10.4.1.2.2 | 1/29/19 2:23:47 PM by null |
|
| ITI10 | ITI10-014 | to be reviewed | Testable |
0
|
0
| | 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. | 68 | Section 3.10.4.1.2.3 | 1/29/19 2:23:58 PM by null |
|
| ITI10 | ITI10-015 | to be reviewed | Testable |
0
|
0
| | 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). | 68 | Section 3.10.4.1.2.3 | 1/29/19 2:23:58 PM by null |
|
| ITI10 | ITI10-016 | to be reviewed | Testable |
0
|
0
| | 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. | 68 | Section 3.10.4.1.2.3 | 1/29/19 2:23:47 PM by null |
|
| ITI10 | ITI10-017 | to be reviewed | Testable |
0
|
0
| | 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. | 68 | Section 3.10.4.1.2.3 | 1/29/19 2:23:58 PM by null |
|
| ITI10 | ITI10-018 | to be reviewed | Testable |
0
|
0
| | 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. | 69 | Table 3.10-2 | 1/29/19 2:23:47 PM by null |
|
| ITI10 | ITI10-019 | to be reviewed | Testable |
0
|
0
| | 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. | 69 | Section 3.10.4.1.3 | 1/29/19 2:23:58 PM by null |
|
| ITI10 | ITI10-020 | to be reviewed | Testable |
0
|
0
| | 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. | 69 | Section 3.10.4.1.3 | 1/29/19 2:23:58 PM by null |
|