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
ITI39ITI39-001reviewedTestable 0 2 The ‘homeCommunityId’ parameter is required134Section 3.39.18/2/19 4:28:12 PM by mtoudic
ITI39ITI39-002reviewedTestable 0 1 Responding Gateways shall support the Asynchronous Web Services Exchange Option on the Cross Gateway Retrieve.134Section 3.39.15/3/19 8:39:49 AM by NicolasBailliet
ITI39ITI39-003reviewedTestable 0 2 The Cross Gateway Retrieve uses the same syntax and standards as the Retrieve Document Set transaction specified in XDS135Section 3.39.4.18/2/19 4:28:17 PM by mtoudic
ITI39ITI39-004reviewedTestable 0 2 The message semantics for Cross Gateway Retrieve are the same as Retrieve Document Set138Section 3.39.4.1.28/2/19 4:44:53 PM by mtoudic
ITI39ITI39-005reviewedTestable 0 1 The Initiating Gateway shall specify the homeCommunityId parameter within the Retrieve Document Set138Section 3.39.4.1.28/2/19 4:44:58 PM by mtoudic
ITI39ITI39-006reviewedTestable 0 1 Initiating Gateways which support the On-Demand Documents Option shall be capable of retrieving an On-Demand Document Entry135Section 3.39.4.1.25/3/19 8:58:05 AM by NicolasBailliet
ITI39ITI39-007reviewedTestable 0 1 Responding Gateways which support the On-Demand Documents Option shall be able to respond to retrieval of an On-Demand Document Entry135Section 3.39.4.1.25/3/19 8:58:46 AM by NicolasBailliet
ITI39ITI39-008reviewedTestable 0 1 Responding Gateways which support the Persistence of Retrieved Documents Option shall specify the NewRepositoryUniqueId element indicating the document is available for later retrieval and be able to return exactly the same document in all future retrieve requests for the document identified by NewDocumentUniqueId139Section 3.39.4.1.25/3/19 8:59:18 AM by NicolasBailliet
ITI39ITI39-009reviewedTestable 0 1 The Responding Gateway shall determine the local system or systems which hold the documents requested and interact with those systems.136Section 3.39.4.1.38/26/19 5:25:26 PM by NicolasBailliet
ITI39ITI39-010reviewedTestable 0 1 If more than one system is contacted the Responding Gateway shall consolidate the results from the multiple systems into one response to the Initiating Gateway136Section 3.39.4.1.35/3/19 9:01:55 AM by NicolasBailliet
ITI39ITI39-011reviewedTestable 0 2 If both successes and failures are received the Responding Gateway may choose to use PartialSuccess status to reflect both failure and success. The Responding Gateway may alternatively choose to suppress the failures and report only successes.136Section 3.39.4.1.35/3/19 9:09:52 AM by NicolasBailliet
ITI39ITI39-012reviewedTestable 0 1 Every RegistryError element returned in the response shall have the location attribute set to the homeCommunityId of the Responding Gateway.136Section 3.39.4.1.38/26/19 5:25:26 PM by NicolasBailliet
ITI39ITI39-013reviewedTestable 0 1 If the XDS Affinity Domain Option is supported, the Initiating Gateway Actor shall, if needed, consolidate results from multiple Responding Gateways136Section 3.39.4.1.38/26/19 5:25:26 PM by NicolasBailliet
ITI39ITI39-014reviewedTestable 0 2 If both successes and failures are received from Responding Gateways, the Initiating Gateway shall return both DocumentResponse and RegistryErrorList elements in one response and specify PartialSuccess status.136Section 3.39.4.1.35/3/19 9:09:25 AM by NicolasBailliet
ITI39ITI39-015reviewedTestable 0 4 Both the Initiating Gateway and Responding Gateway shall audit the Cross Gateway Retrieve140Section 3.39.65/3/19 9:15:27 AM by NicolasBailliet
ITI39ITI39-016reviewedTestable 0 2 The audit entries shall be equivalent to the entries required for the Retrieve Document Set140Section 3.39.65/3/19 9:51:10 AM by NicolasBailliet
ITI39ITI39-017reviewedTestable 0 2 The Initiating Gateway shall audit as if it were a Document Repository141Section 3.39.68/26/19 5:25:26 PM by NicolasBailliet
ITI39ITI39-018reviewedTestable 0 2 The Responding Gateway Shall audit the Cross Gateway Retrieve as if it were a Document Repository except that for EventTypeCode the Responding Gateway shall specify EV(“ITI-39”, “IHE Transactions”, “Cross Gateway Retrieve”)141Section 3.39.68/26/19 5:25:26 PM by NicolasBailliet
ITI39ITI39-019reviewedTestable 0 0 The Responding Gateway if interacting with a local Document Repository, shall audit as if it were a Document Consumer. One audit record shall be created for each Document Repository contacted.141Section 3.39.68/26/19 5:25:26 PM by NicolasBailliet