| CH-PDQ | CH-PDQ-001 | reviewed | Testable |
2
|
1
| | The PatientTelecom Query Parameter MUST NOT be used (see Table 12 : Message Information Model for The Patient Registry Query by Demographics Message) | 39 | Section 1.10.2.1 | 11/25/21 2:50:08 PM by vhofman |
|
| CH-PDQ | CH-PDQ-006 | reviewed | Testable |
3
|
1
| | In the "Patient" parameter, the "id" field should be valued with at least one Patient Identifier (see Table 13: Message Information Model for Patient Registry Find Candidates) | 42 | Section 1.10.3.1 | 11/25/21 2:50:08 PM by vhofman |
|
| CH-PDQ | CH-PDQ-007 | reviewed | Testable |
4
|
1
| | In the "Person" parameter either "Person.name" or "Patient.id" must be non-null (see Table 13: Message Information Model for Patient Regitry Find Candidates) | 42 | Section 1.10.3.1 | 11/25/21 2:50:08 PM by vhofman |
|
| CH-PDQ | CH-PDQ-008 | reviewed | Testable |
4
|
1
| | In the "Person" parameter, in the "name" field the birth name is passed with the qualifier BR (see Table 10: Message Information Model for Patient Registry Find Candidatess) | 33 | Section 1.9.2.1 | 11/25/21 2:50:08 PM by vhofman |
|
| CH-PDQ | CH-PDQ-009 | reviewed | Testable |
4
|
1
| | In the "Person" parameter, the "religiousAffiliationCode" MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates) | 42 | Section 1.10.3.1 | 11/25/21 2:50:09 PM by vhofman |
|
| CH-PDQ | CH-PDQ-010 | reviewed | Testable |
4
|
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 | 11/25/21 2:50:09 PM by vhofman |
|
| CH-PDQ | CH-PDQ-011 | reviewed | Testable |
4
|
1
| | In the "Person" parameter, the "ethnicGroupCode" MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes) | 29 | Section 1.7.1.1 | 11/25/21 2:50:09 PM by vhofman |
|
| CH-PDQ | CH-PDQ-012 | reviewed | Testable |
3
|
1
| | In the "OtherIDs" parameter, the EPR-PID MAY be added here (see Table 10: Message Information Model for Patient Registry Find Candidates) | 33 | Section 1.9.2.1 | 11/25/21 2:50:09 PM by vhofman |
|
| CH-PDQ | CH-PDQ-013 | reviewed | Testable |
2
|
1
| idem pix | In the "PersonalRelationship" parameter the code MUST be "FTH" for the Father and "MTH" for the Mother (see Table 10: Message Information Model for Patient Registry Find Candidates) | 33 | Section 1.9.2.1 | 11/25/21 2:50:09 PM by vhofman |
|
| CH-PDQ | CH-PDQ-014 | reviewed | Testable |
1
|
1
| | If there are more than 5 matches, there must be a special handling like in the XCPD transaction (see IHE ITI TF-2b, chapter 3.55.4.2.2.6) (see Section 1.9.2.1.1 Special handling for more attributes requested) | 37 | Section 1.9.2.1.1 | 11/25/21 2:50:09 PM by vhofman |
|
| CH-PDQ | CH-PDQ-015 | reviewed | Testable |
0
|
1
| | The different return cases should be handled equivalent to the XCPD cases in IHE ITI TF-2b, chapter 3.55.4.2.3 Expected Actions (see Section 1.9.2.1.1 Special handling for more attributes requested) | 37 | Section 1.9.2.1.1 | 11/25/21 2:50:09 PM by vhofman |
|
| ITI47 | ITI47-1 | reviewed | Testable |
0
|
0
| | Implementers of the Patient Demographics Query HL7 V3 [ITI-47] transaction shall comply with the requirements described in HL7 Version 3 Edition 2008, Patient Administration DSTU, Patient Topic (found at http://www.hl7.org/memonly/downloads/v3edition.cfm#V32008) | 246 | Section 3.47.3 | 5/2/19 4:16:29 PM by wbars |
|
| ITI47 | ITI47-10 | reviewed | Testable |
0
|
0
| | The messages exchanged in the context of the Patient Demographics Query HL7 V3 [ITI-47] transaction will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. | 253 | Section 3.47.4.1.2.4 | 5/2/19 4:16:32 PM by wbars |
|
| ITI47 | ITI47-11 | reviewed | Testable |
0
|
0
| | The following WSDL naming conventions SHALL apply:
query message -> "PRPA_IN201305UV02_Message" | 253 | Section 3.47.4.1.2.4 | 5/2/19 4:16:36 PM by wbars |
|
| ITI47 | ITI47-12 | reviewed | Testable |
0
|
0
| | The Patient Demographics Supplier shall be capable of accepting, searching on, and responding with attributes in the Query Person by Demographics message | 254 | Section 3.47.4.1.3.2 | 5/2/19 4:10:11 PM by wbars |
|
| ITI47 | ITI47-13 | reviewed | Testable |
0
|
0
| | The Supplier shall return at least all exact matches to the query parameters sent by the Consumer; | 254 | Section 3.47.4.1.3.2 | 5/2/19 4:10:17 PM by wbars |
|
| ITI47 | ITI47-18 | reviewed | Testable |
0
|
0
| | The Patient Demographics Suppliers response to the Find Candidates Query message is triggered by the following trigger:
Find Candidates Response (PRPA_TE201306UV02) | 254 | Section 3.47.4.2.1 | 5/2/19 4:10:23 PM by wbars |
|
| ITI47 | ITI47-19 | reviewed | Testable |
0
|
0
| | An application returns a Patient Registry Find Candidates Response message populated with information it holds for each person whose record matches the demographic information sent as parameters in a query-by-parameter message | 254 | Section 3.47.4.2.1 | 5/2/19 4:10:29 PM by wbars |
|
| ITI47 | ITI47-2 | reviewed | Testable |
0
|
0
| | Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V Web Services for IHE Transactions | 246 | Section 3.47.3 | 5/2/19 4:16:42 PM by wbars |
|
| ITI47 | ITI47-21 | reviewed | Testable |
0
|
0
| | The components of the Patient Registry Find Candidates Response message (PRPA_MT201310UV02) with cardinality greater than 0 (as shown in Figure 3.47.4.2.2-1) are required | 255 | Section 3.47.4.2.2 | 5/2/19 4:10:41 PM by wbars |
|