View scope

keyword
CH-PDQ
Description
Scope for the EPD Swiss CH:PDQ profile

38 Assertions in Scope

net.ihe.gazelle.assets.SearchCriteria

Id scheme
Assertion id
Predicate
CH-PDQCH-PDQ-001The PatientTelecom Query Parameter MUST NOT be used (see Table 12 : Message Information Model for The Patient Registry Query by Demographics Message)
CH-PDQCH-PDQ-006In 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)
CH-PDQCH-PDQ-007In the "Person" parameter either "Person.name" or "Patient.id" must be non-null (see Table 13: Message Information Model for Patient Regitry Find Candidates)
CH-PDQCH-PDQ-008In 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)
CH-PDQCH-PDQ-009In the "Person" parameter, the "religiousAffiliationCode" MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)
CH-PDQCH-PDQ-010In the "Person" parameter the "raceCode" field MUST NOT be used (see Table 13: Message Information Model for Patient Registry Find Candidates)
CH-PDQCH-PDQ-011In the "Person" parameter, the "ethnicGroupCode" MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes)
CH-PDQCH-PDQ-012In the "OtherIDs" parameter, the EPR-PID MAY be added here (see Table 10: Message Information Model for Patient Registry Find Candidates)
CH-PDQCH-PDQ-013In 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)
CH-PDQCH-PDQ-014If 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)
CH-PDQCH-PDQ-015The 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)
ITI47ITI47-1Implementers 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)
ITI47ITI47-10The 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.
ITI47ITI47-11The following WSDL naming conventions SHALL apply: query message -> "PRPA_IN201305UV02_Message"
ITI47ITI47-12The Patient Demographics Supplier shall be capable of accepting, searching on, and responding with attributes in the Query Person by Demographics message
ITI47ITI47-13The Supplier shall return at least all exact matches to the query parameters sent by the Consumer;
ITI47ITI47-18The Patient Demographics Suppliers response to the Find Candidates Query message is triggered by the following trigger: Find Candidates Response (PRPA_TE201306UV02)
ITI47ITI47-19An 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
ITI47ITI47-2Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V Web Services for IHE Transactions
ITI47ITI47-21The 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