net.ihe.gazelle.assets.SearchCriteria : 91 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-1to be reviewedTestable 0 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). 195Section 3.44.39/3/18 6:10:52 PM by jlabbe
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. 202Section 3.44.4.1.2.49/3/18 6:10:53 PM by jlabbe
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" 202Section 3.44.4.1.2.49/3/18 6:10:53 PM by jlabbe
ITI44ITI44-12to be reviewedTestable 0 2 The Patient Identifier Cross-reference Manager shall be capable of accepting attributes specified in Table 3.44.4.1.2-1 203Section 3.44.4.1.39/3/18 6:10:53 PM by jlabbe
ITI44ITI44-13to be reviewedTestable 0 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). 203Section 3.44.4.1.39/3/18 6:10:53 PM by jlabbe
ITI44ITI44-14to be reviewedTestable 0 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" 204Section 3.44.4.1.3.19/3/18 6:10:53 PM by jlabbe
ITI44ITI44-19to be reviewedTestable 0 2 The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. 210Section 3.44.4.2.2.49/3/18 6:10:54 PM by jlabbe
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.195Section 3.44.4.1.19/3/18 6:10:54 PM by jlabbe
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) 207Section 3.44.4.2.19/3/18 6:10:55 PM by jlabbe
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. 207Section 3.44.4.2.29/3/18 6:10:55 PM by jlabbe
ITI44ITI44-23to be reviewedTestable 0 2 The Patient Registry Duplicates Resolved interaction is carried out by the HL7 v3 Patient Demographics message (PRPA_MT201303UV02) . 207Section 3.44.4.2.29/3/18 6:10:55 PM by jlabbe
ITI44ITI44-24to be reviewedTestable 0 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 O207Section 3.44.4.2.29/3/18 6:10:55 PM by jlabbe
ITI44ITI44-25to be reviewedTestable 0 3 The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. 210Section 3.44.4.2.2.49/3/18 6:10:56 PM by jlabbe
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" 210Section 3.44.4.2.2.49/3/18 6:10:56 PM by jlabbe
ITI44ITI44-27to be reviewedTestable 0 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. 211Section 3.44.4.2.39/3/18 6:10:56 PM by jlabbe
ITI44ITI44-28to be reviewedTestable 0 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 Transactions211Section 3.44.4.2.39/3/18 6:10:56 PM by jlabbe
ITI44ITI44-29to be reviewedTestable 0 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.2/24/15 5:36:05 PM by jlabbe
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.195Section 3.44.4.1.19/3/18 6:10:57 PM by jlabbe
ITI44ITI44-31to be reviewedTestable 0 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"211Section 3.44.4.2.3.12/24/15 5:36:05 PM by jlabbe
ITI44ITI44-46to be reviewedTestable 0 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 216Section 3.44.5.1.19/3/18 6:10:59 PM by jlabbe