View scope

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

63 Assertions in Scope

net.ihe.gazelle.assets.SearchCriteria

Id scheme
Assertion id
Predicate
CH-PIXCH-PIX-001In the "Person" parameter at least "Person.name" or "Patient.id" must be non-null (see Table Table 9: Patient Active and Revise Model Attributes)
CH-PIXCH-PIX-002In the "Person" parameter, in the "name" field the birth name is passed with the qualifier BR (see Table 9: Patient Active and Revise Model Attributes)
CH-PIXCH-PIX-003In the "Person" parameter, the "religiousAffiliationCode" MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes)
CH-PIXCH-PIX-004In the "Person" parameter the "raceCode" field MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes)
CH-PIXCH-PIX-005In the "Person" parameter, the "ethnicGroupCode" MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes)
CH-PIXCH-PIX-006In the "OtherIDs" parameter, if patient is already registered in a community, the MPI-PID MUST be provided here (see Table 9: Patient Active and Revise Model Attributes)
CH-PIXCH-PIX-007In the "PersonalRelationship" parameter, the code MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes)
CH-PIXCH-PIX-008The "DataSource" Parameter MUST be specified to the assigning authority/authorities of the MPI-PID in the affinity domain. See also ITI TF-2b, chapter 3.45.4.1.2.1 (see Section 1.8.1.1 Major Components of the Patient Registry Query by Identifier)
CH-PIXCH-PIX-009The "otherId" MUST contain the EPR-PID. See also ITI TF-2b, chapter 3.45.4.2.2.1 (see Section 1.8.2.1 Major Components of the Get Corresponding Identifiers Query Response)
ITI44ITI44-1Patient Identity Feed HL7 V3 references the following standard HL7 Version 3 Edition 2008 Patient Administration DSTU, Patient Topic (found at http://www.hl7.org/memonly/downloads/v3edition.cfm#V32008).
ITI44ITI44-12The Patient Identifier Cross-reference Manager shall be capable of accepting attributes specified in Table 3.44.4.1.2-1
ITI44ITI44-13Once the Patient Identifier Cross-reference Manager has completed its cross-referencing function, it shall make the newly cross-referenced identifiers available to PIX queries and send out notification to any Patient Identifier Cross-reference Consumers that have been configured as being interested in receiving such notifications using the PIX Update Notification HL7 V3 transaction (see ITI TF-2b: 3.46 for the details of that transaction).
ITI44ITI44-14The following WSDL naming conventions SHALL apply: wsdl:definitions/@name="PIXManager": add message -> "PRPA_IN201301UV02_Message" revise message -> "PRPA_IN201302UV02_Message" acknowledgement ->"MCCI_IN000002UV01_Message" portType -> "PIXManager_PortType" add operation -> "PIXManager_PRPA_IN201301UV02" revise operation -> "PIXManager_PRPA_IN201302UV02" SOAP 1.2 binding -> "PIXManager_Binding_Soap12" SOAP 1.2 port -> "PIXManager_Port_Soap12"
ITI44ITI44-19The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.
ITI44ITI44-24Each HL7 Merge Patient message shall be acknowledged by the HL7 v3 Accept Acknowledgement (MCCI_MT000200UV01), which is described in ITI TF-2x: Appendix O
ITI44ITI44-25The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.
ITI44ITI44-27The Patient Identifier Cross-reference Manager shall be capable of accepting attributes in the Resolve Duplicates message as specified in Table 3.44.4.2.2-1.
ITI44ITI44-28After the identifier references are replaced, the Patient Identifier Cross-reference Manager shall reapply its internal cross-referencing logic/ policies before providing the updated information via either the PIX Query or PIX Notification Transactions
ITI44ITI44-29When the Patient Identifier Cross-reference Manager receives the Resolve Duplicates message type of the Patient Identity Feed transaction, it shall cross-reference the patient identifiers provided in the wrapper and the payload of the message by replacing any references it is maintaining internally to the patient ID provided in the wrapper by the patient ID included in the payload.
ITI44ITI44-31The following WSDL naming conventions SHALL apply: wsdl:definitions/@name="PIXManager": merge message -> "PRPA_IN201304UV02_Message" acknowledgement ->"MCCI_IN000002UV01_Message" portType -> "PIXManager_PortType" merge operation -> "PIXManager_PRPA_IN201304UV02" SOAP 1.2 binding -> "PIXManager_Binding_Soap12" SOAP 1.2 port -> "PIXManager_Port_Soap12"