| ITI9 | ITI9-001 | to be reviewed | Testable |
0
|
0
| | A Patient Identifier Cross-reference Consumers need to get the patient identifier associated with a domain for which it needs patient related information will trigger the request for corresponding patient identifiers message based on the following HL7 trigger event:
Q23 Get Corresponding Identifiers | 55 | Section 3.9.4.1.1 | 1/29/19 2:23:47 PM by null |
|
| ITI9 | ITI9-002 | to be reviewed | Testable |
0
|
0
| | The Request for Corresponding Patient Identifiers transaction is conducted by the HL7 QBP^Q23 message. The Patient Identifier Cross-reference Consumer Actor shall generate the query message whenever it needs to obtain a corresponding patient identifier(s) from other Patient Identification Domain(s). The segments of the message listed below are required, and their detailed descriptions are provided in the following subsections. | 55 | Section 3.9.4.1.2 | 1/29/19 2:23:47 PM by null |
|
| ITI9 | ITI9-003 | to be reviewed | Testable |
0
|
0
| | The receiver shall respond to the query by sending the RSP^K23 response message. This satisfies the requirements of original mode acknowledgment; no intermediate ACK message is to be sent. | 55 | Section 3.9.4.1.2 | 1/29/19 2:23:47 PM by null |
|
| ITI9 | ITI9-004 | 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 QBP; the second component shall have the value of Q23. The third component shall have a value of QBP_Q21. | 55 | Section 3.9.4.1.2.1 | 1/29/19 2:23:47 PM by null |
|
| ITI9 | ITI9-005 | to be reviewed | Testable |
0
|
0
| | The Patient Identifier Cross-reference Consumer Actor is required to send attributes within the QPD segment as described in Table 3.9-2.
This message shall use the field QPD-3 Person Identifier to convey a single Patient ID uniquely identifying the patient within a given Patient Identification Domain.
The Patient Identifier Cross-reference Consumer Actor shall provide the patient identifier in the ID component (first component) of the QPD-3 field (QPD-3.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.
If the requesting system wishes to select the domains from which they wish to receive Patient IDs, it does so by populating QPD-4-What Domains Returned with as many repetitions as domains for which it wants to receive Patient IDs. Each repetition of QPD-4 shall contain an instance of data type CX in which only the fourth component (Assigning Authority) is populated; the remaining components shall be empty. The responding system shall return the Patient ID value for each requested domain if a value is known.
If QPD-4 is empty, the Patient Identifier Cross-reference Manager Actor shall return Patient IDs for all domains for which it possesses a corresponding Patient ID (subject to local publication restrictions).
The Consumer shall specify IHE PIX Query for QPD-1 Message Query Name. | 55 | Section 3.9.4.1.2.2 | 1/29/19 2:23:47 PM by null |
|
| ITI9 | ITI9-006 | to be reviewed | Testable |
0
|
0
| | Although HL7 requires that the RCP Segment be sent in all QBP messages, IHE does not require that the Patient Identifier Cross-reference Consumer Actor send any attributes within the RCP segment, as is specified in the HL7 standard. | 56 | Section 3.9.4.1.2.3 | 1/29/19 2:23:58 PM by null |
|
| ITI9 | ITI9-007 | to be reviewed | Testable |
0
|
0
| | Field RCP-1-Query Priority shall always contain I, signifying that the response to the query is to be returned in Immediate mode. | 56 | Section 3.9.4.1.2.3.1 | 1/29/19 2:23:58 PM by null |
|
| ITI9 | ITI9-008 | to be reviewed | Testable |
0
|
0
| | The Patient Identifier Cross-reference Manager Actor must be capable of receiving all valid combinations of subcomponents that make up the Assigning Authority component (i.e., all valid combinations of QPD-3.4). | 56 | Section 3.9.4.1.3 | 1/29/19 2:23:47 PM by null |
|
| ITI9 | ITI9-009 | to be reviewed | Testable |
0
|
0
| | The Patient Identifier Cross-reference Manager Actor shall be capable of accepting multiple concurrent PIX Query requests (Get Corresponding Identifiers messages) and responding correctly using the Return Corresponding Identifiers message. | 56 | Section 3.9.4.1.3 | 1/29/19 2:23:47 PM by null |
|
| ITI9 | ITI9-010 | to be reviewed | Testable |
0
|
0
| | The Patient Identifier Cross-reference Manager Actor shall be capable of accepting multiple concurrent PIX Query requests (Get Corresponding Identifiers messages) and responding correctly using the Return Corresponding Identifiers message. | 56 | Section 3.9.4.1.3 | 1/29/19 2:23:47 PM by null |
|
| ITI9 | ITI9-011 | to be reviewed | Testable |
0
|
0
| | The Return Corresponding Identifiers transaction is conducted by the HL7 RSP^K23 message. The Patient Identifier Cross-reference Manager Actor shall generate this message in direct response to the QBP^Q23 query message previously received. This message satisfies the Application Level, Original Mode Acknowledgement for the HL7 QBP^Q23 message. The segments of the message listed without enclosing square brackets in the table below are required. Detailed descriptions of all segments listed in the table below are provided in the following subsections. Other segments of the message are optional. | 57 | Section 3.9.4.2.2 | 1/29/19 2:23:47 PM by null |
|
| ITI9 | ITI9-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 RSP; the second component shall have the value of K23. The third component shall have a value of RSP_K23. | 57 | Section 3.9.4.2.2.1 | 1/29/19 2:23:47 PM by null |
|
| ITI9 | ITI9-013 | to be reviewed | Testable |
0
|
0
| | The Patient Identifier Cross-reference Manager Actor is not required to send any attributes within the MSA segment beyond what is specified in the HL7 standard. See ITI TF-2x: C.2.3 for the list of all required and optional fields within the MSA segment. | 58 | Section 3.9.4.2.2.2 | 1/29/19 2:23:58 PM by null |
|
| ITI9 | ITI9-014 | to be reviewed | Testable |
0
|
0
| | The Patient Identifier Cross-reference Manager Actor shall send attributes within the QAK segment as defined in Table 3.9-4. For the details on filling in QAK-2 (Query Response Status) refer to Section 3.9.4.2.2.6. | 58 | Table 3.9-4 | 1/29/19 2:23:58 PM by null |
|
| ITI9 | ITI9-015 | to be reviewed | Testable |
0
|
0
| | The Patient Identifier Cross-reference Manager Actor shall echo the QPD Segment value that was sent in the QBP^Q23 message. | 58 | Section 3.9.4.2.2.4 | 1/29/19 2:23:47 PM by null |
|
| ITI9 | ITI9-016 | to be reviewed | Testable |
0
|
0
| | The Patient Identifier Cross-reference Manager Actor shall return only those attributes within the PID segment that are required by the HL7 standard: PID-3-Patient IdentifierList and PID-5-Patient Name.
The PID segment is returned only when the Patient Identifier Cross-reference Manager Actor recognizes the specified Patient Identification Domain and Patient ID and an identifier exists for the specified patient in at least one other domain. See Section 3.9.4.2.2.6, Patient Identifier Cross-reference Manager Actor Query Response Behavior, for a detailed description of how the Patient Identifier Cross-reference Manager Actor responds to the query request under various circumstances.
The Patient Identifier Cross-reference Manager Actor shall use the field PID-3 Patient Identifier List to convey the Patient ID 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).
To eliminate the issue of conflicting name values between Patient Identifier Domains, the Patient Identifier Cross-reference Manager Actor shall return in an empty (not present) value in the first repetition of field PID-5-Patient Name, and shall return a second repetition of field PID-5-Patient Name in which the only populated component is Component 7 (Name Type Code). Component 7 of repetition 2 shall contain a value of S (Coded Pseudo-name to assure anonymity). All other components of repetition 2 shall be empty (not present). | 58 | Section 3.9.4.2.2.5 | 1/29/19 2:23:58 PM by null |
|
| ITI9 | ITI9-017 | to be reviewed | Testable |
0
|
0
| | The Patient Identifier Cross-reference Consumer will use the list of patient identifier aliases provided by the Patient Identifier Cross-reference Manager to perform the functions for which it requested the list.
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. | 61 | Section 3.9.4.2.3 | 1/29/19 2:23:47 PM by null |
|