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
ITI38ITI38-008reviewedTestable 0 0 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.131Section 3.38.4.1.2.22/14/17 9:36:03 AM by
ITI38ITI38-013reviewedTestable 0 0 The Responding Gateway Actor shall pass all parameters into the Registry Stored Query [ITI-18] transaction, when routing to a local XDS Document Registry132Section 3.38.4.1.32/14/17 9:36:03 AM by
ITI38ITI38-019reviewedTestable 0 0 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.132Section 3.38.4.1.31/5/16 11:11:15 AM by aboufahj
ITI38ITI38-020reviewedTestable 0 0 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.133Section 3.38.4.1.31/5/16 11:11:15 AM by aboufahj
ITI38ITI38-021reviewedTestable 0 0 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.133Section 3.38.4.1.31/5/16 11:11:15 AM by aboufahj
ITI38ITI38-023reviewedTestable 0 0 If $XDSDocumentEntryType parameter is specified, and the Responding Gateway (or underlying XDS community) does support it, the proper information SHALL be returned133Section 3.38.4.1.3.11/5/16 11:11:15 AM by aboufahj
ITI38ITI38-024reviewedTestable 0 1 The Initiating Gateway if receiving a Registry Stored Query transaction from a Document Consumer, shall audit as if it were a Document Registry133Section 3.38.4.1.42/22/17 12:02:14 PM by aberge
ITI38ITI38-025reviewedTestable 0 1 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”)133Section 3.38.4.1.42/22/17 12:02:09 PM by aberge
ITI38ITI38-026reviewedTestable 0 1 If Initiating Gateway interacting with a local Document Registry, shall audit as if it were a Document Consumer133Section 3.38.4.1.42/22/17 12:02:06 PM by aberge
ITI38ITI38-027reviewedTestable 0 1 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”)134Section 3.38.4.1.42/22/17 12:02:31 PM by aberge
ITI38ITI38-028reviewedTestable 0 1 The Responding Gateway interacting with a local Document Registry SHALL audit as if it were a Document Consumer134Section 3.38.4.1.42/22/17 12:02:25 PM by aberge