net.ihe.gazelle.assets.SearchCriteria : 251 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.13Section 3.1.4.13/20/15 11:59:23 AM by aboufahj
ITI1ITI1-10reviewedTestable 0 0 The Time Client may also support for automated discovering of the Time Server address.13Section 3.1.4.13/20/15 11:59:23 AM by aboufahj
ITI1ITI1-11reviewedTestable 0 0 Implementations must support a time synchronization accuracy with a median error of less than one second.13Section 3.1.4.1.21/29/19 2:23:58 PM by aboufahj
ITI1ITI1-2reviewedTestable 0 0 The Time Server shall support SNTP define in Simple Network Time Protocol RFC4330.13Section 3.1.4.13/20/15 11:59:23 AM by aboufahj
ITI1ITI1-3reviewedTestable 0 0 The Time Server may support Secure NTP.13Section 3.1.4.13/20/15 11:59:23 AM by aboufahj
ITI1ITI1-4reviewedTestable 0 0 The Time Client shall support at least SNTP (RFC4330) or NTP v3 (RFC1305).13Section 3.1.4.13/20/15 11:59:23 AM by aboufahj
ITI1ITI1-5reviewedTestable 0 0 The Time Client may support Secure NTP.13Section 3.1.4.13/20/15 11:59:23 AM by aboufahj
ITI1ITI1-6reviewedTestable 0 0 The Time Client grouped with a Time Server shall support NTP and NOT implement SNTP.13Section 3.1.4.13/20/15 11:59:23 AM by aboufahj
ITI1ITI1-7reviewedTestable 0 0 The "High accuracy" Time Client shall support NTP and NOT implement SNTP.13Section 3.1.4.13/20/15 11:59:23 AM by aboufahj
ITI1ITI1-8reviewedTestable 0 0 The Time Client shall at least support a manual configuration of Time Server IP address.13Section 3.1.4.13/20/15 11:59:23 AM by aboufahj
ITI1ITI1-9reviewedTestable 0 0 The Time Client may also support for automated retreiving of the Time Server address from DHCP.13Section 3.1.4.13/20/15 11:59:23 AM by aboufahj
ITI10ITI10-001to be reviewedTestable 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.69Section 3.10.4.1.11/29/19 2:23:58 PM by
ITI10ITI10-002to be reviewedTestable 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.66Section 3.10.4.1.11/29/19 2:23:47 PM by
ITI10ITI10-003to be reviewedTestable 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.67Section 3.10.4.1.21/29/19 2:23:47 PM by
ITI10ITI10-004to be reviewedTestable 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.67Section 3.10.4.1.21/29/19 2:23:47 PM by
ITI10ITI10-005to be reviewedTestable 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.67Section 3.10.4.1.21/29/19 2:23:58 PM by
ITI10ITI10-006to be reviewedTestable 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.67Section 3.10.4.1.21/29/19 2:23:58 PM by
ITI10ITI10-007to be reviewedTestable 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.67Section 3.10.4.1.21/29/19 2:23:58 PM by
ITI10ITI10-008to be reviewedTestable 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.67Section 3.10.4.1.21/29/19 2:23:47 PM by
ITI10ITI10-009to be reviewedTestable 0 0 The Patient Identifier Cross-reference Manager should account for consumers interested in all domains.67Section 3.10.4.1.21/29/19 2:23:58 PM by