net.ihe.gazelle.assets.SearchCriteria : 19 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
ITI-92ITI-001to be reviewedTestable 2 4 Restricted Update Document Set [ITI-92] is used by the Update Initiator and Update Responder (See Section 3.92 Restricted Update Document Set) 24Section 3.927/1/19 4:10:57 PM by NicolasBailliet
ITI-92ITI-002to be reviewedTestable 2 4 The Restricted Update Document Set Request message shall use SOAP 1.2 and Simple SOAP (See Section 3.92.4.1.2 Message Semantics) 25Section 3.92.4.1.27/1/19 4:11:00 PM by NicolasBailliet
ITI-92ITI-003to be reviewedTestable 2 4 Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V.3: Synchronous and Asynchronous Web Services (see Section 3.92.4.1.2 Message Semantics) 25Section 3.92.4.1.27/1/19 4:11:02 PM by NicolasBailliet
ITI-92ITI-004to be reviewedTestable 1 3 The Update Initiator shall ensure that all metadata attributes are consistent with the requirements specified in ITI TF-3 (see Section 3.92.4.1.2.1 Content)27Section 3.92.4.1.2.17/1/19 4:09:02 PM by NicolasBailliet
ITI-92ITI-005to be reviewedTestable 1 3 The Update Responder shall use Metadata Annotations when processing the request for storage (see Section 3.92.4.1.2.2 Metadata Annotations) 27Section 3.92.4.1.2.27/1/19 4:11:06 PM by NicolasBailliet
ITI-92ITI-006to be reviewedTestable 1 3 The default value for Association Propagation is "yes" (See Section 3.92.4.1.2.2.2 Association Propagation) 28Section 3.92.4.1.2.2.27/1/19 4:11:08 PM by NicolasBailliet
ITI-92ITI-007to be reviewedTestable 1 3 The Update Responder shall return the status and any error codes incurred during the processing of the request in its response message (See Section 3.92.4.1.3 Expected Actions)29Section 3.92.4.1.37/1/19 4:11:10 PM by NicolasBailliet
ITI-92ITI-008to be reviewedTestable 1 3 If the value is not known, the Update Responder shall return the error code, XDSUnknownCommunity (See Section 3.92.4.1.3.1 Forward Update Option) 29Section 3.92.4.1.3.17/1/19 4:11:15 PM by NicolasBailliet
ITI-92ITI-009to be reviewedTestable 1 3 If the value is omitted, the Update Responder shall return the error code, XDSMissingHomeCommunityId (See Section 3.92.4.1.3.1 Forward Update Option)29Section 3.92.4.1.3.17/1/19 4:11:17 PM by NicolasBailliet
ITI-92ITI-010to be reviewedTestable 1 3 The current version of the stored logical metadata object shall always have an availabilityStatus equal to urn:oasis:names:tc:ebxml-regrep:StatusType:Approved and prior versions shall have their availabilityStatus attribute set tourn:oasis:names:tc:ebxml-regrep:StatusType:Deprecated (see Section 3.92.4.1.3.4.1 Storage Requirements)30Section 3.92.4.1.3.4.17/1/19 4:11:20 PM by NicolasBailliet
ITI-92ITI-011to be reviewedTestable 1 3 Unless a more specific code is provided within the validation, the Update Responder shall return the error code, XDSMetadataUpdateError, for any error returned during processing (See Section 3.92.4.1.3.4 Request Validation) 31Section 3.92.4.1.3.47/1/19 4:11:22 PM by NicolasBailliet
ITI-92ITI-012to be reviewedTestable 1 3 The system shall contain an existing DocumentEntry (Stable or On-Demand) metadata object instance with status of urn:oasis:names:tc:ebxml-regrep:StatusType:Approved (See Section 3.92.4.1.3.4 Request Validation) 32Section 3.92.4.1.3.47/1/19 4:11:27 PM by NicolasBailliet
ITI-92ITI-013to be reviewedTestable 1 3 The SS-DE HasMember Association shall be present and have a Slot with name PreviousVersion (See Section 3.92.4.1.3.4 Request Validation) 32Section 3.92.4.1.3.47/1/19 4:11:29 PM by NicolasBailliet
ITI-92ITI-014to be reviewedTestable 1 3 The submitted and existing DocumentEntry objects shall have the same values for both the logicalID ans uniqueID attribute (See Section 3.92.4.1.3.4 Request Validation) 32Section 3.92.4.1.3.47/1/19 4:11:31 PM by NicolasBailliet
ITI-92ITI-015to be reviewedTestable 1 3 The submitted and existing DocumentEntry objects shall have the same values for the patientID attributes (see Section 3.92.4.1.3.4 Request Validation) 32Section 3.92.4.1.3.47/1/19 4:11:34 PM by NicolasBailliet
ITI-92ITI-016to be reviewedTestable 1 3 All metadata objects must conform to the rules for content and format defined in ITI TF-3: 4.2 and 4.3. Stable Document Entry object metadata must confirm to the requirements defined in ITI TF-2b: 3.42 for the Register Document Set-b [ITI-42] transaction (see Section 3.92.4.1.3.4 Request Validation)32Section 3.92.4.1.3.47/1/19 4:11:36 PM by NicolasBailliet
ITI-92ITI-017to be reviewedTestable 1 3 On-Demand Document Entry objects must conform to the requirements defined in ITI TF-2b: 3.61 for the Register On-Demand Document Entry [ITI-61] transaction (see Section 3.92.4.1.3.4 Request Validation)32Section 3.92.4.1.3.47/1/19 4:11:39 PM by NicolasBailliet
ITI-92ITI-018to be reviewedTestable 1 3 The Restricted Update Document Set Response message shall use SOAP 1.2 and Simple SOAP (see Section 3.92.4.2.2 Message Semantics) 33Section 3.92.4.2.27/1/19 4:11:42 PM by NicolasBailliet
ITI-92ITI-019to be reviewedTestable 1 3 Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V.3: Synchronous and Asynchronous Web Services (see Section 3.92.4.2.2 Message Semantics) 33Section 3.92.4.2.27/1/19 4:11:44 PM by NicolasBailliet