Search Criteria : 213 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
ITI1ITI1-1reviewedTestable 0 0 The Time Server shall support NTP define in Network Time Protocol Version 3. RFC1305.132Section 3.1.4.12/5/16 12:27:23 PM by aboufahj
ITI1ITI1-10reviewedTestable 0 0 The Time Client may also support for automated discovering of the Time Server address.132Section 3.1.4.12/5/16 12:27:23 PM by aboufahj
ITI1ITI1-11reviewedTestable 1 0 Implementations must support a time synchronization accuracy with a median error of less than one second.132Section 3.1.4.1.22/5/16 12:27:23 PM by aboufahj
ITI1ITI1-2reviewedTestable 0 0 The Time Server shall support SNTP define in Simple Network Time Protocol RFC4330.132Section 3.1.4.12/5/16 12:27:23 PM by aboufahj
ITI1ITI1-3reviewedTestable 0 0 The Time Server may support Secure NTP.132Section 3.1.4.12/5/16 12:27:23 PM by aboufahj
ITI1ITI1-4reviewedTestable 1 0 The Time Client shall support at least SNTP (RFC4330) or NTP v3 (RFC1305).132Section 3.1.4.12/5/16 12:27:23 PM by aboufahj
ITI1ITI1-5reviewedTestable 0 0 The Time Client may support Secure NTP.132Section 3.1.4.12/5/16 12:27:23 PM by aboufahj
ITI1ITI1-6reviewedTestable 0 0 The Time Client grouped with a Time Server shall support NTP and NOT implement SNTP.132Section 3.1.4.12/5/16 12:27:23 PM by aboufahj
ITI1ITI1-7reviewedTestable 0 0 The "High accuracy" Time Client shall support NTP and NOT implement SNTP.132Section 3.1.4.12/5/16 12:27:23 PM by aboufahj
ITI1ITI1-8reviewedTestable 0 0 The Time Client shall at least support a manual configuration of Time Server IP address.132Section 3.1.4.12/5/16 12:27:23 PM by aboufahj
ITI1ITI1-9reviewedTestable 0 0 The Time Client may also support for automated retreiving of the Time Server address from DHCP.132Section 3.1.4.12/5/16 12:27:23 PM by aboufahj
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-011validatedTestable 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.71Section 3.10.4.1.24/4/16 4:14:20 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