net.ihe.gazelle.assets.SearchCriteria : 63 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-PIXCH-PIX-001reviewedTestable 1 1 In the "Person" parameter at least "Person.name" or "Patient.id" must be non-null (see Table Table 9: Patient Active and Revise Model Attributes)37Section 1.7.1.18/26/19 5:25:26 PM by mbesnier
CH-PIXCH-PIX-002reviewedTestable 1 1 In 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)38Section 1.7.1.18/26/19 5:25:26 PM by mbesnier
CH-PIXCH-PIX-003reviewedTestable 1 1 In the "Person" parameter, the "religiousAffiliationCode" MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes)38Section 1.7.1.18/26/19 5:25:26 PM by mbesnier
CH-PIXCH-PIX-004reviewedTestable 1 1 In the "Person" parameter the "raceCode" field MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes)39Section 1.7.1.18/26/19 5:25:26 PM by mbesnier
CH-PIXCH-PIX-005reviewedTestable 1 1 In the "Person" parameter, the "ethnicGroupCode" MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes)39Section 1.7.1.18/26/19 5:25:26 PM by mbesnier
CH-PIXCH-PIX-006reviewedTestable 1 1 In 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)39Section 1.7.1.18/26/19 5:25:26 PM by mbesnier
CH-PIXCH-PIX-007reviewedTestable 1 1 In the "PersonalRelationship" parameter, the code MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes)39Section 1.7.1.18/26/19 5:25:26 PM by mbesnier
CH-PIXCH-PIX-008reviewedTestable 2 1 The "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)42Section 1.8.1.18/26/19 5:25:26 PM by mbesnier
CH-PIXCH-PIX-009reviewedTestable 0 1 The "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)42Section 1.8.2.1 8/26/19 5:25:26 PM by mbesnier
ITI44ITI44-1reviewedTestable 2 1 Patient 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). 193Section 3.44.35/29/19 1:42:05 PM by aberge
ITI44ITI44-12reviewedTestable 1 2 The Patient Identifier Cross-reference Manager shall be capable of accepting attributes specified in Table 3.44.4.1.2-1 201Section 3.44.4.1.35/29/19 1:42:28 PM by aberge
ITI44ITI44-13validatedTestable 1 2 Once 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). 201Section 3.44.4.1.35/29/19 1:42:41 PM by aberge
ITI44ITI44-14reviewedTestable 1 2 The 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" 202Section 3.44.4.1.3.15/29/19 1:42:49 PM by aberge
ITI44ITI44-19reviewedTestable 1 2 The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. 208Section 3.44.4.2.2.45/29/19 1:43:02 PM by aberge
ITI44ITI44-24reviewedTestable 1 3 Each HL7 Merge Patient message shall be acknowledged by the HL7 v3 Accept Acknowledgement (MCCI_MT000200UV01), which is described in ITI TF-2x: Appendix O205Section 3.44.4.2.25/29/19 1:43:14 PM by aberge
ITI44ITI44-25reviewedTestable 1 3 The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. 208Section 3.44.4.2.2.45/29/19 1:43:24 PM by aberge
ITI44ITI44-27reviewedTestable 1 2 The 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. 209Section 3.44.4.2.35/29/19 1:43:49 PM by aberge
ITI44ITI44-28reviewedTestable 1 2 After 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 Transactions209Section 3.44.4.2.35/29/19 1:43:54 PM by aberge
ITI44ITI44-29reviewedTestable 1 2 When 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. 210Section 3.44.4.2.5/29/19 1:44:00 PM by aberge
ITI44ITI44-31reviewedTestable 1 2 The 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"209Section 3.44.4.2.3.15/29/19 1:44:34 PM by aberge