Search Criteria : 24 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
ITI38ITI38-001reviewedTestable 1 1 Initiating Gateway shall specify the homeCommunityId attribute in all Cross-Community Queries which do not contain a patient identifier.125Section 3.38.19/17/19 11:53:27 AM by aeschlimann
ITI38ITI38-003reviewedTestable 1 1 The homeCommunityId attribute is required on the Cross Gateway Query127Section 3.38.4.1.2.19/17/19 11:53:41 AM by aeschlimann
ITI38ITI38-004reviewedTestable 1 2 homeCommunityId is structured as an OID limited to 64 characters and specified in URI syntax127Section 3.38.4.1.2.19/17/19 11:53:44 AM by aeschlimann
ITI38ITI38-005reviewedTestable 1 1 The Initiating Gateway shall specify the homeCommunityId parameter within all queries which do not include a patient identifier parameter.127Section 3.38.4.1.2.19/17/19 11:53:47 AM by aeschlimann
ITI38ITI38-006reviewedTestable 1 1 Each Cross Gateway Query request can have at most one homeCommunityId value.127Section 3.38.4.1.2.19/17/19 11:53:51 AM by aeschlimann
ITI38ITI38-007reviewedTestable 1 1 If multiple entryUUID or uniqueID values are specified they must all be associated with the same homeCommunityId value127Section 3.38.4.1.2.19/17/19 11:53:58 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 3.38.4.1.38/2/19 4:28:02 PM by mtoudic
ITI38ITI38-021reviewedTestable 1 1 If an XDSUnknownPatientId error is returned from a Responding Gateway then the Initiating Gateway shall not include this error in the consolidated results sent to the Document Consumer.129Section 3.38.4.1.39/17/19 11:52:20 AM by aeschlimann
ITI38ITI38-022reviewedTestable 1 1 The Initiating Gateway shall pass all entities received in the Cross Gateway Query response into the response to the Registry Stored Query [ITI-18].129Section 3.38.4.1.39/17/19 11:52:27 AM by aeschlimann
ITI38ITI38-023reviewedTestable 1 1 If $XDSDocumentEntryType parameter is specified, and the Responding Gateway (or underlying XDS community) does support it, the proper information SHALL be returned130Section 3.38.4.1.3.19/17/19 11:52:38 AM by aeschlimann
ITI38ITI38-024reviewedTestable 1 2 The Initiating Gateway if receiving a Registry Stored Query transaction from a Document Consumer, shall audit as if it were a Document Registry130Section 3.38.4.1.49/17/19 11:52:55 AM by aeschlimann
ITI38ITI38-025reviewedTestable 1 2 The Initiating Gateway shall audit the Cross Gateway Query as if it were a Document Consumer except that for EventTypeCode the Initiating Gateway shall specify EV(“ITI-38”, “IHE Transactions”, and “Cross Gateway Query”)130Section 3.38.4.1.49/17/19 11:52:56 AM by aeschlimann
ITI38ITI38-026reviewedTestable 1 2 If Initiating Gateway interacting with a local Document Registry, shall audit as if it were a Document Consumer130Section 3.38.4.1.49/17/19 11:53:00 AM by aeschlimann
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 3.38.4.1.49/17/19 11:53:10 AM by aeschlimann
ITI39ITI39-001reviewedTestable 2 2 The ‘homeCommunityId’ parameter is required134Section 3.39.19/17/19 11:57:43 AM by aeschlimann
ITI39ITI39-004reviewedTestable 2 2 The message semantics for Cross Gateway Retrieve are the same as Retrieve Document Set138Section 3.39.4.1.29/17/19 11:57:50 AM by aeschlimann
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-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 2 4 Both the Initiating Gateway and Responding Gateway shall audit the Cross Gateway Retrieve140Section 3.39.69/17/19 11:58:30 AM by aeschlimann
ITI39ITI39-016reviewedTestable 2 2 The audit entries shall be equivalent to the entries required for the Retrieve Document Set140Section 3.39.69/17/19 11:58:38 AM by aeschlimann