net.ihe.gazelle.assets.SearchCriteria : 113 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
CH-XCPDCH-XCPD-001reviewedTestable 1 1 For the EPR only the Shared/National Patient Identifier Query mode MUST be used. Other modes as defined in this transaction (see also IHE ITI TF-2b, chapter 3.55.1) MUST NOT be used (see Section 1.10.1 Modes and Options)38Section 1.10.16/6/19 9:11:58 AM by aberge
CH-XCPDCH-XCPD-002reviewedTestable 0 1 The Health Data Locator and Revoke Option of the Patient Location Query transaction [ITI-56] MUST NOT be used (see Section 1.10.1 Modes and Options)38Section 1.10.18/26/19 5:25:26 PM by mbesnier
CH-XCPDCH-XCPD-010reviewedTestable 1 1 In the "Person" parameter, either "Person.name" or "Patient.id" must be non-null (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.18/26/19 5:25:26 PM by mbesnier
CH-XCPDCH-XCPD-011reviewedTestable 1 1 In the "Person" parameter, the "telecom" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.18/26/19 5:25:26 PM by mbesnier
CH-XCPDCH-XCPD-014reviewedTestable 1 1 In the "Person" parameter, the "deceasedInd" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.18/26/19 5:25:26 PM by mbesnier
CH-XCPDCH-XCPD-015reviewedTestable 1 1 In the "Person" parameter, the "deceasedTime" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.18/26/19 5:25:26 PM by mbesnier
CH-XCPDCH-XCPD-016reviewedTestable 1 1 In the "Person" parameter, the "multipleBirthInd" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.18/26/19 5:25:26 PM by mbesnier
CH-XCPDCH-XCPD-017reviewedTestable 1 1 In the "Person" parameter, the "multipleBirthOrderNumber" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.18/26/19 5:25:26 PM by mbesnier
CH-XCPDCH-XCPD-018reviewedTestable 1 1 In the "Person" parameter, the "addr" field MUST NOT be used MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.18/26/19 5:25:26 PM by mbesnier
CH-XCPDCH-XCPD-019reviewedTestable 1 1 In the "Person" parameter, the "maritalStatusCodeCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.18/26/19 5:25:26 PM by mbesnier
CH-XCPDCH-XCPD-020reviewedTestable 1 1 In the "Person" parameter, the "religiousAffiliationCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.18/26/19 5:25:26 PM by mbesnier
CH-XCPDCH-XCPD-021reviewedTestable 1 1 In the "Person" parameter, the "raceCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.18/26/19 5:25:26 PM by mbesnier
CH-XCPDCH-XCPD-022reviewedTestable 1 1 In the "Person" parameter, the "ethnicGroupCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.18/26/19 5:25:26 PM by mbesnier
CH-XCPDCH-XCPD-023to be reviewedTestable 1 1 rephrase to forbid the use of OtherIDs insteadIn the "OtherIDs" parameter, the "classCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.18/26/19 5:25:26 PM by mbesnier
CH-XCPDCH-XCPD-025to be reviewedTestable 1 1 rephrase to forbid the use of the PersonalRelationship insteadIn the "PersonalRelationship" parameter, the "classCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)42Section 1.10.3.18/26/19 5:25:26 PM by mbesnier
ITI55ITI55-001reviewedTestable 0 1 The Responding Gateway Actor SHALL indicates in its response to the initiating gateway whether the community has knowledge of a patient matching the set of demographic data and, if a match is found, returns the demographics known by the responding community.326Section 3.55.15/2/19 5:27:50 PM by wbars
ITI55ITI55-002reviewedTestable 0 0 If more than one match is found related to an ITI-55 request from Initiating Gateway the Responding Gateway has the option of providing a list of matching patients or returning nothing326Section 3.55.15/2/19 5:27:55 PM by wbars
ITI55ITI55-003reviewedTestable 0 1 The Cross Gateway Patient Discovery Request is implemented using the HL7 Patient Registry Query by Demographics (PRPA_MT201306UV02) message329Section 3.55.4.1.15/2/19 5:28:02 PM by wbars
ITI55ITI55-004reviewedTestable 0 0 For each element which is required in the request query, the element shall be specified by the Initiating Gateway in the request and shall be used by the Responding Gateway as part of its demographic matching algorithm.329Section 3.55.4.1.25/2/19 5:28:31 PM by wbars
ITI55ITI55-005reviewedTestable 0 0 For each element which is optional in the request query,, the element does not need to be specified by the Initiating Gateway in the request but, if specified, shall be used by the Responding Gateway as part of its demographic matching algorithm.329Section 3.55.4.1.25/2/19 5:28:36 PM by wbars