net.ihe.gazelle.assets.SearchCriteria : 79 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
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-10to be reviewedTestable 0 2 The Patient Registry Record Added/Revised messages will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. 200Section 3.44.4.1.2.45/2/19 4:37:58 PM by wbars
ITI44ITI44-11to be reviewedTestable 0 2 The following WSDL naming conventions SHALL apply for transmission of the Patient Registry Record Added/Revised messages : add message -> "PRPA_IN201301UV02_Message" revise message -> "PRPA_IN201302UV02_Message" acknowledgement -> "MCCI_IN000002UV01_Message" 200Section 3.44.4.1.2.45/2/19 4:38:01 PM by wbars
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-16to be reviewedTestable 0 2 The Document Registry shall be capable of accepting attributes in the Patient Registry Record Added or Patient Registry Record Revised messages as specified in Table 3.44.4.1.2-1 . 203Section 3.44.4.1.45/2/19 4:32:43 PM by wbars
ITI44ITI44-17to be reviewedTestable 0 2 The Document Registry shall store only the patient identifiers of the patient identification domain designated by the Affinity Domain for document sharing in the registry 203Section 3.44.4.1.45/2/19 4:32:45 PM by wbars
ITI44ITI44-18to be reviewedTestable 0 2 Patient identifiers of other patient identification domains, if present in a received message, shall be ignored by the Document Registry.203Section 3.44.4.1.45/2/19 4:32:47 PM by wbars
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-2to be reviewedTestable 0 1 Patient Registry Record Added (PRPA_TE201301UV02) event from a Patient Identity Source shall trigger the Add Patient Record message.193Section 3.44.4.1.15/2/19 4:32:52 PM by wbars
ITI44ITI44-20to be reviewedTestable 0 2 The following WSDL naming conventions SHALL apply for the Document Registry: wsdl:definitions/@name="DocumentRegistry": "add" message -> "PRPA_IN201301UV02_Message" "revise" message -> "PRPA_IN201302UV02_Message" acknowledgement ->"MCCI_IN000002UV01_Message" portType -> "DocumentRegistry_PortType" add operation -> "DocumentRegistry_PRPA_IN201301UV02" revise operation -> "DocumentRegistry_PRPA_IN201302UV02" SOAP 1.2 binding -> "DocumentRegistry_Binding_Soap12" SOAP 1.2 port -> "DocumentRegistry_Port_Soap12"203Section 3.44.4.1.4.15/2/19 4:32:53 PM by wbars
ITI44ITI44-21to be reviewedTestable 0 1 When two patients™ records are found to identify the same patient by a Patient Identity Source in a Patient Identifier Domain, the Patient Identity Source shall indicate this information using the following trigger: Patient Registry Duplicates Resolved (PRPA_TE201304UV02) 204Section 3.44.4.2.15/2/19 4:32:55 PM by wbars
ITI44ITI44-22to be reviewedTestable 0 2 The message shall be generated by the system (Patient Identity Source) that performs the update whenever two patient records are found to reference the same person. 205Section 3.44.4.2.25/2/19 4:38:06 PM by wbars
ITI44ITI44-23to be reviewedTestable 0 2 The Patient Registry Duplicates Resolved interaction is carried out by the HL7 v3 Patient Demographics message (PRPA_MT201303UV02) . 205Section 3.44.4.2.25/2/19 4:38:09 PM by wbars
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-26to be reviewedTestable 0 2 The following WSDL naming conventions SHALL apply for transmitting the Patient Registry Resolve Duplicates message: "resolve duplicates" message -> "PRPA_IN201304UV02_Message" Acknowledgement -> "MCCI_IN000002UV01_Message" 208Section 3.44.4.2.2.45/2/19 4:38:16 PM by wbars
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