Search Criteria : 32 assertions found for this search Review filtered assertions


Applies to

Applied to
Not applied to


Covered by
Not covered by
Id scheme
Assertion id
#Applies to
Last changed
ITI38ITI38-002reviewedTestable 0 1 For stored queries that rely on concepts that a community may not support, namely associations, folders and submission sets, a Responding Gateway is allowed to respond with zero entries125Section 3.38.18/2/19 4:27:33 PM by mtoudic
ITI38ITI38-004reviewedTestable 1 2 homeCommunityId is structured as an OID limited to 64 characters and specified in URI syntax127Section 11:53:44 AM by aeschlimann
ITI38ITI38-008reviewedTestable 2 1 If the patient identifier is unknown by the Responding Gateway’s community, the Responding Gateway shall return either a successful response with no elements or an error with errorCode XDSUnknownPatientId, depending on local policy.128Section 11:54:29 AM by aeschlimann
ITI38ITI38-009reviewedTestable 1 1 FindDocuments Stored Query is required for Responding Gateway128Section 11:54:18 AM by aeschlimann
ITI38ITI38-010reviewedTestable 1 1 GetDocuments Stored Query is required for Responding Gateway128Section 11:54:20 AM by aeschlimann
ITI38ITI38-011reviewedTestable 1 1 The Responding Gateway Actor shall Return an XDSUnknownCommunity error code if the value of homeCommunityId is specified and is not known by the Responding Gateway129Section 11:54:32 AM by aeschlimann
ITI38ITI38-012reviewedTestable 1 1 The Responding Gateway Actor shall verify the homeCommunityId is specified on relevant queries and return an XDSMissingHomeCommunityId error code if missing129Section 11:54:41 AM by aeschlimann
ITI38ITI38-013reviewedTestable 1 1 The Responding Gateway Actor shall pass all parameters into the Registry Stored Query [ITI-18] transaction, when routing to a local XDS Document Registry129Section 11:54:52 AM by aeschlimann
ITI38ITI38-014reviewedTestable 1 1 In the response generated by the Respnding Gateway, If returntype=”LeafClass”, the ExtrinsicObject and RegistryPackage elements shall contain the home attribute129Section 11:54:59 AM by aeschlimann
ITI38ITI38-015reviewedTestable 1 1 In the response generated by the Respnding Gateway, If returnType=”ObjectRef”, the ObjectRef element shall contain the home attribute129Section 11:55:04 AM by aeschlimann
ITI38ITI38-016reviewedTestable 1 1 The Responding Gateway SHALL ensure that every RegistryError element returned in the response shall have the location attribute set to the homeCommunityId of the Responding Gateway129Section 11:55:21 AM by aeschlimann
ITI38ITI38-017reviewedTestable 0 2 The Initiating Gateway Actor shall On receiving the response from the Responding Gateway, verify the homeCommunityId is present where appropriate129Section 4:28:02 PM by mtoudic
ITI38ITI38-019reviewedTestable 0 1 All XDSMissingHomeCommunityId errors generated by the Initiating Gateway to the document consumer of the internal actor SHALL include, in the context of the message, identification of the Responding Gateway that returned the invalid response and the element or elements that were in error.129Section 5:32:51 PM by NicolasBailliet
ITI38ITI38-020reviewedTestable 0 1 If both successes and failures are received from Responding Gateways, the Initiating Gateway shall return both RegistryObjectList and RegistryErrorList in one response and specify PartialSuccess status.129Section 5:32:51 PM by NicolasBailliet
ITI38ITI38-027reviewedTestable 1 3 The Responding Gateway Shall audit the Cross Gateway Query as if it were a Document Registry except that for EventTypeCode the Responding Gateway shall specify EV(“ITI-38”, “IHE Transactions”, “Cross Gateway Query”)130Section 11:53:10 AM by aeschlimann
ITI38ITI38-028reviewedTestable 1 2 The Responding Gateway interacting with a local Document Registry SHALL audit as if it were a Document Consumer130Section 11:53:13 AM by aeschlimann
ITI39ITI39-001reviewedTestable 2 2 The ‘homeCommunityId’ parameter is required134Section 3.39.19/17/19 11:57:43 AM by aeschlimann
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 2 2 The Cross Gateway Retrieve uses the same syntax and standards as the Retrieve Document Set transaction specified in XDS135Section 11:57:46 AM by aeschlimann
ITI39ITI39-004reviewedTestable 2 2 The message semantics for Cross Gateway Retrieve are the same as Retrieve Document Set138Section 11:57:50 AM by aeschlimann