Search Criteria : 8 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-12validatedTestable 0 2 The Patient Identifier Cross-reference Manager shall have configuration indicating which Identity Consumers are interested in receiving the PIXV3 Update Notification Transactions.246Section 3.46.4.1.22/5/16 12:27:23 PM by aboufahj
ITI46ITI46-13validatedTestable 0 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. 246Section 3.46.4.1.22/5/16 12:27:23 PM by aboufahj
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.251Section 3.46.4.1.32/5/16 12:27:23 PM by aboufahj
ITI46ITI46-17to be reviewedTestable 0 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 domain251Section 3.46.4.1.32/5/16 12:27:23 PM by aboufahj
ITI46ITI46-18to be reviewedTestable 0 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"252Section 3.46.4.1.3.12/5/16 12:27:23 PM by aboufahj
ITI46ITI46-20to 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. 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 transaction253Section 3.46.5.12/5/16 12:27:23 PM by aboufahj
ITI46ITI46-21to be reviewedTestable 0 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 interested251Section 3.46.4.1.32/5/16 12:27:23 PM by aboufahj
ITI46ITI46-7to be reviewedTestable 0 2 Each message shall be acknowledged by the HL7 V3 Accept Acknowledgement (MCCI_MT000200UV01), which is described in ITI TF-2x: Appendix O246Section 3.46.4.1.22/5/16 12:27:23 PM by aboufahj