net.ihe.gazelle.assets.SearchCriteria : 21 assertions found for this search Review filtered assertions

Assertion

Applies to

Applied to
Not applied to

Coverage

Covered by
Not covered by
Id scheme
Assertion id
Status
Testable?
#Coverage
#Applies to
Comment
Predicate
Page
Tags
Last changed
Actions
ITI10ITI10-001validatedTestable 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.69Section 3.9.4.1.14/4/16 4:12:59 PM by aberge
ITI10ITI10-003validatedTestable 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.70Section 3.10.4.1.24/4/16 4:13:12 PM by aberge
ITI10ITI10-008validatedTestable 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.70Section 3.10.4.1.24/4/16 4:13:37 PM by aberge
ITI10ITI10-012validatedTestable 0 1 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.71Section 3.10.4.1.2.14/4/16 4:58:17 PM by aberge
ITI10ITI10-013validatedTestable 0 1 The EVN segment shall be constructed regarding the rules in ITI TF-2x: C.2.4.71Section 3.10.4.1.2.24/4/16 4:58:20 PM by aberge
ITI10ITI10-014validatedTestable 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.71Section 3.10.4.1.2.34/4/16 4:15:25 PM by aberge
ITI10ITI10-015validatedTestable 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).71Section 3.10.4.1.2.34/4/16 4:16:11 PM by aberge
ITI10ITI10-016validatedTestable 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.71Section 3.10.4.1.2.34/4/16 4:16:23 PM by aberge
ITI10ITI10-017validatedTestable 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.72Section 3.10.4.1.2.34/4/16 4:16:30 PM by aberge
ITI10ITI10-018validatedTestable 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.72Table 3.10-24/4/16 4:58:24 PM by aberge
ITI8ITI8-018validatedTestable 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.44Section 3.8.4.1.34/4/16 4:50:37 PM by aberge
ITI8ITI8-019validatedTestable 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. 45Section 3.8.4.1.34/4/16 4:50:40 PM by aberge
ITI8ITI8-020validatedTestable 0 1 The Patient Identifier Cross-reference Manager Actor shall only recognize (by configuration) a single Patient Identity Source Actor per domain.45Section 3.8.4.1.34/4/16 5:01:40 PM by aberge
ITI8ITI8-021validatedTestable 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).45Section 3.8.4.1.34/4/16 4:42:44 PM by aberge
ITI8ITI8-037validatedTestable 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. 48Section 3.8.4.2.34/4/16 4:44:19 PM by aberge
ITI9ITI9-008validatedTestable 0 1 The Patient Identifier Cross-reference Manager Actor shall 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).59Section 3.9.4.1.34/4/16 4:55:36 PM by aberge
ITI9ITI9-009validatedTestable 0 1 testable ?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.59Section 3.9.4.1.34/4/16 4:55:43 PM by aberge
ITI9ITI9-011validatedTestable 0 1 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 from the Patient Identifier Cross-reference Consumer.60Section 3.9.4.2.24/4/16 4:55:50 PM by aberge
ITI9ITI9-015validatedTestable 0 1 The Patient Identifier Cross-reference Manager Actor shall echo the QPD Segment value that was sent in the QBP^Q23 message.61Section 3.9.4.2.2.44/4/16 4:55:57 PM by aberge
ITI9ITI9-016validatedTestable 0 1 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. 61Section 3.9.4.2.2.54/4/16 4:56:04 PM by aberge