net.ihe.gazelle.assets.SearchCriteria : 42 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
ITI8ITI8-1to be reviewedTestable 0 1 The following events from a Patient Identity Source Actor will trigger one of the Admit/Register or Update messages: A01 Admission of an in-patient into a facility A04 Registration of an outpatient for a visit of the facility A05 Pre-admission of an in-patient (i.e., registration of patient information ahead of actual admission) 39Section 3.8.4.1.19/3/18 6:11:00 PM by aboufahj
ITI8ITI8-10to be reviewedTestable 0 0 The MSH segment shall be constructed as defined in ITI TF-2x: C.2.2 Message Control.40Section 3.8.4.1.2.11/29/19 2:23:47 PM by
ITI8ITI8-11to be reviewedTestable 0 0 Field MSH-9 Message Type shall have at least two components. The first component shall have a value of ADT; the second component shall have one of the values of A01, A04, A05 or A08 as appropriate. The third component is optional; however, if present, it shall have the following value for each corresponding message type: ADT_A01 for A01 message type ADT_A01 for A04 message type ADT_A05 for A05 message type ADT_A01 for A08 message type40Section 3.8.4.1.2.11/29/19 2:23:58 PM by
ITI8ITI8-12to be reviewedTestable 0 0 The Patient Identity Source Actor is not required to send any attributes within the EVN segment beyond what is specified in the HL7 standard. See Table C.1-4 in ITI TF-2x: C.2.4 Common Segment Definitions for the specification of this segment.40Section 3.8.4.1.2.21/29/19 2:23:47 PM by
ITI8ITI8-13to be reviewedTestable 0 0 The Patient Identity Source Actor is not required to send any attributes within the PID segment beyond what is specified in the HL7 standard.40Section 3.8.4.1.2.31/29/19 2:23:47 PM by
ITI8ITI8-14to be reviewedTestable 0 0 When sending ADT messages A01, A04, and A05, the Patient Identity Source Actor shall populate appropriate values in the fields as listed in Table 3.8-243Table 3.8-22/1/16 1:02:18 PM by
ITI8ITI8-15to be reviewedTestable 0 0 The ADT message shall use the field PID-3 Patient Identifier List to convey the Patient ID uniquely identifying the patient within a given Patient Identification Domain.40Section 3.8.4.1.2.31/29/19 2:23:47 PM by
ITI8ITI8-16to be reviewedTestable 0 0 The Patient Identity Source Actor shall provide the patient identifier in the ID component (first component) of the PID-3 field (PID-3.1). The Patient Identity Source Actor shall use component PID-3.4 to convey the assigning authority (Patient Identification Domain) of the patient identifier. Either the first subcomponent (namespace ID) or the second and third subcomponents (universal ID and universal ID type) shall be populated. If all three subcomponents are populated, the first subcomponent shall reference the same entity as is referenced by the second and third components.40Section 3.8.4.1.2.31/29/19 2:23:47 PM by
ITI8ITI8-17to be reviewedTestable 0 0 The Admit/ Register or Update Patient message is not required to include any attributes within the PV1 segment beyond what is specified in the HL7 standard.42Section 3.8.4.1.2.41/29/19 2:23:47 PM by
ITI8ITI8-18to be reviewedTestable 0 0 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.42Section 3.8.4.1.31/29/19 2:23:58 PM by
ITI8ITI8-19to be reviewedTestable 0 0 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. The information filled by the Patient Identifier Cross-reference Manager is based on the configuration associating each of the Patient Identity Source Actors with the subcomponents of the correct assigning authority (namespace ID, UID and UID type).42Section 3.8.4.1.31/29/19 2:23:47 PM by
ITI8ITI8-2to be reviewedTestable 0 1 Changes to patient demographics (e.g., change in patient name, patient address, etc.) shall trigger the following Admit/Register or Update message: A08 Update Patient Information 39Section 3.8.4.1.19/3/18 6:11:01 PM by aboufahj
ITI8ITI8-20to be reviewedTestable 0 0 A single Patient Identity Source Actor can serve multiple Patient Identification domains. The Patient Identifier Cross-reference Manager Actor shall only recognize (by configuration) a single Patient Identity Source Actor per domain.42Section 3.8.4.1.31/29/19 2:23:47 PM by
ITI8ITI8-21to be reviewedTestable 0 0 Once the Patient Identifier Cross-reference Manager has completed its cross-referencing function, it shall make the newly cross-referenced identifiers available to PIX queries and send out notification to any Patient Identifier Cross-reference Consumers that have been configured (as being interested in receiving such notifications) using the PIX Update Notification transaction (see Section 3.10 for the details of that transaction).42Section 3.8.4.1.31/29/19 2:23:47 PM by
ITI8ITI8-22to be reviewedTestable 0 0 The identifier of the domain shall specify all 3 components of the HL7 1150 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.42Section 3.8.4.1.3.11/29/19 2:23:58 PM by
ITI8ITI8-23to be reviewedTestable 0 0 The Patient Identity Source Actor is expected to be the MSH-3 Sending Application and the corresponding MSH-4 Sending Facility fields in the HL7 ADT message. (Alternative identification schemes might include IP address of the Patient Identity Source Actor or Node Authentication if the Audit Trail and Node Authentication Integration Profile is used.)42Section 3.8.4.1.3.11/29/19 2:23:47 PM by
ITI8ITI8-24to be reviewedTestable 0 0 The identifier of the Patient Identification Domain of the XDS Affinity Domain shall be specified with 3 components of the HL7 assigning authority (data type 1185 HD): namespaceID, universal ID and universal ID type. The universal ID shall be an ISO OID (Object Identifier), and therefore the universal ID Type must be ISO.43Section 3.8.4.1.4.11/29/19 2:23:58 PM by
ITI8ITI8-25to be reviewedTestable 0 0 When two patients records are found to identify the same patient by a Patient Identity Source Actor in a Patient Identifier Domain and are merged, the Patient Identity Source shall trigger the following message: A40 Merge Patient Internal ID An A40 message indicates that the Patient Identity Source Actor has done a merge within a specific Patient Identification Domain. That is, MRG-1 (patient ID) has been merged into PID-3 (Patient ID).44Section 3.8.4.2.11/29/19 2:23:58 PM by
ITI8ITI8-26to be reviewedTestable 0 0 The Patient Identity Feed transaction is an HL7 ADT message. The message shall be generated by the system (Patient Identity Source Actor) that performs the update whenever two patient records are found to reference the same person.44Section 3.8.4.2.21/29/19 2:23:47 PM by
ITI8ITI8-27to be reviewedTestable 0 0 The segments of the HL7 Merge Patient message listed below are required, and the detailed description of the message is provided in Section 3.8.4.2.2.13.8.4.2.2.6. The PV1 segment is optional.44Section 3.8.4.2.21/29/19 2:23:47 PM by