net.ihe.gazelle.assets.SearchCriteria : 14 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-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-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-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-3to be reviewedTestable 0 2 Patient Registry Record Revised (PRPA_TE201302UV02) event from a Patient Identity Source shall trigger the Revise Patient Record message.193Section 3.44.4.1.15/2/19 4:38:23 PM by wbars
ITI44ITI44-46to be reviewedTestable 1 2 When grouped with ATNA Secure Node or Secure Application actors, this transaction is to be audited as Patient Record event, as defined in ITI TF-2a: Table 3.20.6-1. Audit messages produced by the Patient Identity Source actor shall comply with the definitin given in table 3.44.5.1.1 214Section 3.44.5.1.18/26/19 3:28:19 PM by aberge
ITI44ITI44-6to be reviewedTestable 0 2 A given Patient Identity Source Actor may serve more than one Patient Identifier Domain. 193Section 3.44.4.1.15/2/19 4:38:31 PM by wbars
ITI44ITI44-7to be reviewedTestable 0 2 The components of the PRPA_MT201301UV02 and PRPA_MT201302UV02 messages listed in section 3.44.4.1.2 are required.194Section 3.44.4.1.25/2/19 4:38:34 PM by wbars
ITI44ITI44-8to be reviewedTestable 0 2 The Patient Identity Feed transaction is carried out by the HL7 v3 Patient Activate (PRPA_MT201301UV02) and Patient Revise (PRPA_MT201302UV02) messages, as defined in the subsequent sections. The Patient Identity Source shall generate the message whenever a patient is registered or when some piece of patient demographic data changes.194Section 3.44.4.1.25/2/19 4:38:38 PM by wbars
PIXV3PIXV3-1reviewedTestable 1 4 All the actors involved in the Patient Identity Cross-Referencing HL7 V3 (PIXV3) integration profile shall be grouped with the Time Client Actor.235Table 23.68/26/19 5:25:26 PM by wbars
PIXV3PIXV3-15to be reviewedTestable 0 4 The patient identifier SHALL be represented as a root and an extension, where the root is an appropriately assigned OID. 234Section 23.55/2/19 11:31:35 AM by wbars
PIXV3PIXV3-2to be reviewedTestable 0 2 Patient Identity Source actor which claims support of the Patient Identity Cross-Referencing HL7 V3 (PIXV3) integration profile shall perform the Patient Identity Feed HL7V3 [ITI-44] transaction232Table 23.1-15/2/19 11:22:37 AM by wbars