net.ihe.gazelle.assets.SearchCriteria : 34 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
ITI46ITI46-1validatedTestable 0 1 PIXV3 Update Notification [ITI-46] transaction 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) 235Section 3.46.35/2/19 5:10:21 PM by wbars
ITI46ITI46-12validatedTestable 1 2 The Patient Identifier Cross-reference Manager shall have configuration indicating which Identity Consumers are interested in receiving the PIXV3 Update Notification Transactions.236Section 3.46.4.1.25/29/19 1:57:41 PM by aberge
ITI46ITI46-13validatedTestable 1 2 This configuration information shall include identification of the identity consumer systems interested in receiving notifications and, for each of those systems, a list of the patient identifier domains of interest. 236Section 3.46.4.1.25/29/19 1:57:49 PM by aberge
ITI46ITI46-14validatedTestable 1 2 The Patient Registry Record Revised message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V240Section 3.46.4.1.2.45/29/19 1:51:43 PM by aberge
ITI46ITI46-15validatedTestable 2 2 The following WSDL naming conventions SHALL apply: revise message -> "PRPA_IN201302UV02_Message" acknowledgement -> "MCCI_IN000002UV01_Message"240Section 3.46.4.1.2.46/6/19 9:05:06 AM by aberge
ITI46ITI46-16to be reviewedTestable 0 2 The identifiers found in both Patient.id and OtherIDs.id attributes shall be considered together to form a complete list of patient identifiers from the different Patient Identity domains in which this actor is interested.241Section 3.46.4.1.35/2/19 5:11:38 PM by wbars
ITI46ITI46-17to be reviewedTestable 1 2 In the case where the returned list of identifiers contains multiple identifiers for a single domain, the Patient Identifier Cross-reference Consumer shall either use ALL of the multiple identifiers from the given domain or it shall ignore ALL of the multiple identifiers from the given domain241Section 3.46.4.1.36/6/19 9:05:20 AM by aberge
ITI46ITI46-18to be reviewedTestable 1 2 The following WSDL naming conventions SHALL apply: wsdl:definitions/@name="PIXConsumer": PIX update message -> "PRPA_IN201302UV02_Message" acknowledgement ->"MCCI_IN000002UV01_Message" portType -> "PIXConsumer_PortType" get identifiers operation -> "PIXConsumer_PRPA_IN201302UV02" SOAP 1.2 binding -> "PIXConsumer_Binding_Soap12" SOAP 1.2 port -> "PIXConsumer_Port_Soap12"241Section 3.46.4.1.3.16/6/19 9:05:23 AM by aberge
ITI46ITI46-19reviewedTestable 1 3 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. Tables 3.46.5.1.1 show items that are required to be part of the audit record produced by the Patient Identifier Cross-reference manager actor for this transaction243Section 3.46.5.18/26/19 5:25:26 PM by aberge
ITI46ITI46-2to be reviewedTestable 1 3 Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V Web Services for IHE Transactions.235Section 3.46.36/6/19 9:05:36 AM by aberge
ITI46ITI46-20to 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. Tables 3.46.5.1.2 show items that are required to be part of the audit record produced by the Patient Identifier Cross-reference consumer actor for this transaction243Section 3.46.5.18/26/19 3:29:41 PM by aberge
ITI46ITI46-21to be reviewedTestable 1 2 Whenever the Patient Identifier Cross-reference Consumer receives updated identifier information in a Patient Revise message that results in a change to the cross-referencing of a patient, the actor shall update its internal identifier information for the affected patient(s) in all domains in which it is interested241Section 3.46.4.1.36/6/19 9:05:45 AM by aberge
ITI46ITI46-3validatedTestable 1 2 The Patient Identifier Cross-reference Manager shall notify a Patient Identifier Cross-reference Consumer when there is a change in a set of cross-referenced patient identifiers for any of the patient identifiers belonging to Patient Identifier Domains of interest to the consumer236Section 3.46.4.1.15/29/19 1:51:52 PM by aberge
ITI46ITI46-4validatedTestable 1 2 Several notifications may have to be issued to communicate a single update to a set of cross-reference patient identifiers as required to reflect all the changes on the resulting sets of cross-reference patient Identifiers belonging to Patient Identifier Domains of interest to the Patient Identifier Cross-referencing Consumer236Section 3.46.4.1.15/29/19 1:52:12 PM by aberge
ITI46ITI46-5validatedTestable 1 2 The following HL7 trigger event will be used to update to the list of patient identifiers: Patient Registry Record Revised (PRPA_TE201302UV02). This trigger event signals that patient information was revised in a patient registry. 236Section 3.46.4.1.15/29/19 1:52:21 PM by aberge
ITI46ITI46-6validatedTestable 1 2 The PIX Update Notification transaction is conducted by the Patient Revise (PRPA_MT201302UV02) message236Section 3.46.4.1.25/29/19 1:52:25 PM by aberge
ITI46ITI46-7to be reviewedTestable 1 2 Each message shall be acknowledged by the HL7 V3 Accept Acknowledgement (MCCI_MT000200UV01), which is described in ITI TF-2x: Appendix O236Section 3.46.4.1.26/6/19 9:05:54 AM by aberge
ITI46ITI46VAL-001validatedTestable 1 0 OtherIDs.id.root SHALL be identical to scopingOrganization.id.root237Section 3.46.4.1.2.15/2/19 5:12:22 PM by wbars
ITI46ITI46VAL-002validatedTestable 1 0 scopingOrganization.id.extension SHALL NOT have any value237Section 3.46.4.1.2.15/2/19 5:12:35 PM by wbars
ITI46ITI46VAL-003validatedTestable 1 0 The provider organization needs to be identified by an id attribute, and at least one of address, telecommunications address, or contact person to be present.237Section 3.46.4.1.2.15/2/19 5:12:40 PM by wbars