| CH-XCPD | CH-XCPD-001 | reviewed | Testable |
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) | 38 | Section 1.10.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-002 | reviewed | Testable |
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) | 38 | Section 1.10.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-010 | reviewed | Testable |
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) | 42 | Section 1.10.3.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-011 | reviewed | Testable |
1
|
1
| | In the "Person" parameter, the "telecom" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates) | 42 | Section 1.10.3.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-014 | reviewed | Testable |
1
|
1
| | In the "Person" parameter, the "deceasedInd" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates) | 42 | Section 1.10.3.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-015 | reviewed | Testable |
1
|
1
| | In the "Person" parameter, the "deceasedTime" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates) | 42 | Section 1.10.3.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-016 | reviewed | Testable |
1
|
1
| | In the "Person" parameter, the "multipleBirthInd" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates) | 42 | Section 1.10.3.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-017 | reviewed | Testable |
1
|
1
| | In the "Person" parameter, the "multipleBirthOrderNumber" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates) | 42 | Section 1.10.3.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-018 | reviewed | Testable |
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) | 42 | Section 1.10.3.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-019 | reviewed | Testable |
1
|
1
| | In the "Person" parameter, the "maritalStatusCodeCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates) | 42 | Section 1.10.3.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-020 | reviewed | Testable |
1
|
1
| | In the "Person" parameter, the "religiousAffiliationCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates) | 42 | Section 1.10.3.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-021 | reviewed | Testable |
1
|
1
| | In the "Person" parameter, the "raceCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates) | 42 | Section 1.10.3.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-022 | reviewed | Testable |
1
|
1
| | In the "Person" parameter, the "ethnicGroupCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates) | 42 | Section 1.10.3.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-023 | to be reviewed | Testable |
1
|
1
| rephrase to forbid the use of OtherIDs instead | In the "OtherIDs" parameter, the "classCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates) | 42 | Section 1.10.3.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XCPD | CH-XCPD-025 | to be reviewed | Testable |
1
|
1
| rephrase to forbid the use of the PersonalRelationship instead | In the "PersonalRelationship" parameter, the "classCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates) | 42 | Section 1.10.3.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| ITI55 | ITI55-001 | reviewed | Testable |
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. | 326 | Section 3.55.1 | 5/2/19 5:27:50 PM by wbars |
|
| ITI55 | ITI55-002 | reviewed | Testable |
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 nothing | 326 | Section 3.55.1 | 5/2/19 5:27:55 PM by wbars |
|
| ITI55 | ITI55-003 | reviewed | Testable |
0
|
1
| | The Cross Gateway Patient Discovery Request is implemented using the HL7 Patient Registry Query by Demographics (PRPA_MT201306UV02) message | 329 | Section 3.55.4.1.1 | 5/2/19 5:28:02 PM by wbars |
|
| ITI55 | ITI55-004 | reviewed | Testable |
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. | 329 | Section 3.55.4.1.2 | 5/2/19 5:28:31 PM by wbars |
|
| ITI55 | ITI55-005 | reviewed | Testable |
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. | 329 | Section 3.55.4.1.2 | 5/2/19 5:28:36 PM by wbars |
|