net.ihe.gazelle.assets.SearchCriteria : 7 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
PIXPIX-001to be reviewedTestable 0 0 A Patient Identifier Cross-reference Domain consists of a set of Patient Identifier Domains known and managed by a Patient Identifier Cross-reference Manager Actor. The Patient Identifier Cross-reference Manager Actor is responsible for creating, maintaining and providing lists of identifiers that are aliases of one another across different Patient Identifier Domains.49Section 52/1/16 1:02:18 PM by
PIXPIX-002to be reviewedTestable 0 0 The Patient Identifier Cross-reference Domain embodies the following assumptions about agreement within the group of individual Identifier Domains: They have agreed to a set of policies that describe how patient identities will be cross-referenced across participating domains; They have agreed to a set of processes for administering these policies; They have agreed to an administration authority for managing these processes and policies. All these assumptions are critical to the successful implementation of this profile. This integration profile imposes minimal constraints on the participating Patient Identifier Domains and centralizes most of the operational constraints for the overall Patient Identification Cross-reference Domain in the Patient Identifier Cross-reference Manager Actor. If the individual Identifier Domains cannot agree to the items outlined above, implementation of this profile may not provide the expected results.49Section 51/29/19 2:23:47 PM by
PIXPIX-003to be reviewedTestable 0 0 The Patient Identifier Cross-reference Consumer may use either a query for sets of cross-reference patient identifiers or use both a notification about cross-reference changes and a query transaction. In the case of using a notification, the Patient Identifier Cross-reference Consumer may also use the PIX Query Transaction to address situations where the Patient Identifier Cross-reference Consumer may be out of synch with the Patient Identifier Cross-reference Manager. This Integration Profile does not specify the consumer policies in using the PIX Query Transaction (ITI TF-2a: 3.9).49Section 51/29/19 2:23:58 PM by
PIXPIX-004to be reviewedTestable 0 0 In order to claim support of this Integration Profile, an implementation must perform the required transactions (labeled R). Transactions labeled O are optional.51Section 5.12/1/16 1:02:18 PM by
PIXPIX-005to be reviewedTestable 0 0 Options that may be selected for this Integration Profile are listed in the Table 5.2-1 along with the Actors to which they apply. Dependencies between options when applicable are specified in notes. The options are the following : Pediatric demographics for both Patient identity source and patient identifier cross-reference manager and PIX update nootfiication for patient identifier cross-reference consumer52Table 5.2-11/29/19 2:23:58 PM by
PIXPIX-006to be reviewedTestable 0 0 Patient Identity Source actors which support the Pediatric Demographics Option are required to support the Patient Identity Management [ITI-30] transaction and shall provide values, when available, for the fields identified as Pediatric Demographics fields.52Section 5.2.12/1/16 1:02:18 PM by
PIXPIX-007to be reviewedTestable 0 0 Patient Identifier Cross-reference Manager Actors which support the Pediatric Demographics Option are required to support the Patient Identity Management [ITI-30] transaction, and if values for one or more of the Pediatric Demographics fields are specified in the Patient Identity Management [ITI-30], they shall be considered as part of the matching algorithm of the PIX Manager.52Section 5.2.12/1/16 1:02:18 PM by