Search Criteria : 11 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
ITI45ITI45-10reviewedTestable 2 2 The Patient Registry Query by Identifier message and response will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. 232Section 3.45.4.1.2.42/5/16 12:27:23 PM by aboufahj
ITI45ITI45-11reviewedTestable 1 2 The following WSDL naming conventions SHALL apply: Query by Identifier -> "PRPA_IN201309UV02_Message" Query Response -> "PRPA_IN201310UV02_Message"232Section 3.45.4.1.2.42/5/16 12:27:23 PM by aboufahj
ITI45ITI45-2reviewedTestable 2 3 Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V Web Services for IHE Transactions227Section 3.45.32/5/16 12:27:23 PM by aboufahj
ITI45ITI45-24reviewedTestable 1 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 (either requested or available).241Section 3.45.4.2.42/5/16 12:27:23 PM by aboufahj
ITI45ITI45-25reviewedTestable 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 domain.241Section 3.45.4.2.42/5/16 12:27:23 PM by aboufahj
ITI45ITI45-26reviewedTestable 1 3 When grouped with ATNA Secure Node or Secure Application actors, this transaction is to be audited as Query Information event. Audit message produced by the Patient Identifier Cross-reference Consumer actor shall follow the rules defined in section 3.45.5.1.1241Section 3.45.5.12/5/16 12:27:23 PM by aboufahj
ITI45ITI45-3reviewedTestable 1 2 A Patient Identifier Cross-reference Consumers need to get the patient identifier associated with a domain for which it needs patient related information shall trigger the request for corresponding patient identifiers message based on the following HL7 trigger event: Patient Registry Get Identifiers Query (PRPA_TE201309UV02) 228Section 3.45.4.1.12/5/16 12:27:23 PM by aboufahj
ITI45ITI45-4reviewedTestable 1 2 The Get Corresponding Identifiers transaction is initiated by the HL7 Patient Registry Query by Identifier (PRPA_MT201307UV02) message. The Patient Identifier Cross-reference Consumer shall generate the query message whenever it needs to obtain corresponding patient identifier(s) from other Patient Identification Domain(s). 228Section 3.45.4.1.22/5/16 12:27:23 PM by aboufahj
ITI45ITI45-5reviewedTestable 1 2 The components of the PRPA_MT201307UV02 message listed in section 3.45.4.1.2 are required.228Section 3.45.4.1.22/5/16 12:27:23 PM by aboufahj
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.217Table 2-12/5/16 12:27:23 PM by aboufahj
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. 250Section 23.52/5/16 12:27:23 PM by aboufahj