| ITI38 | ITI38-008 | reviewed | Testable |
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. | 131 | Section 3.38.4.1.2.2 | 2/14/17 9:36:03 AM by |
|
| ITI38 | ITI38-013 | reviewed | Testable |
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 Registry | 132 | Section 3.38.4.1.3 | 2/14/17 9:36:03 AM by |
|
| ITI38 | ITI38-019 | reviewed | Testable |
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. | 132 | Section 3.38.4.1.3 | 1/5/16 11:11:15 AM by aboufahj |
|
| ITI38 | ITI38-020 | reviewed | Testable |
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. | 133 | Section 3.38.4.1.3 | 1/5/16 11:11:15 AM by aboufahj |
|
| ITI38 | ITI38-021 | reviewed | Testable |
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. | 133 | Section 3.38.4.1.3 | 1/5/16 11:11:15 AM by aboufahj |
|
| ITI38 | ITI38-023 | reviewed | Testable |
0
|
0
| | If $XDSDocumentEntryType parameter is specified, and the Responding Gateway (or underlying XDS community) does support it, the proper information SHALL be returned | 133 | Section 3.38.4.1.3.1 | 1/5/16 11:11:15 AM by aboufahj |
|
| ITI38 | ITI38-024 | reviewed | Testable |
0
|
1
| | The Initiating Gateway if receiving a Registry Stored Query transaction from a Document Consumer, shall audit as if it were a Document Registry | 133 | Section 3.38.4.1.4 | 2/22/17 12:02:14 PM by aberge |
|
| ITI38 | ITI38-025 | reviewed | Testable |
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”) | 133 | Section 3.38.4.1.4 | 2/22/17 12:02:09 PM by aberge |
|
| ITI38 | ITI38-026 | reviewed | Testable |
0
|
1
| | If Initiating Gateway interacting with a local Document Registry, shall audit as if it were a Document Consumer | 133 | Section 3.38.4.1.4 | 2/22/17 12:02:06 PM by aberge |
|
| ITI38 | ITI38-027 | reviewed | Testable |
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”) | 134 | Section 3.38.4.1.4 | 2/22/17 12:02:31 PM by aberge |
|
| ITI38 | ITI38-028 | reviewed | Testable |
0
|
1
| | The Responding Gateway interacting with a local Document Registry SHALL audit as if it were a Document Consumer | 134 | Section 3.38.4.1.4 | 2/22/17 12:02:25 PM by aberge |
|
| ITI39 | ITI39-002 | reviewed | Testable |
0
|
0
| | Responding Gateways shall support the Asynchronous Web Services Exchange Option on the Cross Gateway Retrieve. | 137 | Section 3.39.1 | 1/11/16 4:58:38 PM by aboufahj |
|
| ITI39 | ITI39-006 | reviewed | Testable |
0
|
0
| | Initiating Gateways which support the On-Demand Documents Option shall be capable of retrieving an On-Demand Document Entry | 139 | Section 3.39.4.1.2 | 1/5/16 11:19:22 AM by aboufahj |
|
| ITI39 | ITI39-008 | reviewed | Testable |
0
|
0
| | 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 NewDocumentUniqueId | 139 | Section 3.39.4.1.2 | 1/5/16 11:19:22 AM by aboufahj |
|
| ITI39 | ITI39-010 | reviewed | Testable |
0
|
0
| | If more than one system is contacted the Responding Gateway shall consolidate the results from the multiple systems into one response to the Initiating Gateway | 139 | Section 3.39.4.1.3 | 1/5/16 11:19:22 AM by aboufahj |
|
| ITI39 | ITI39-011 | reviewed | Testable |
0
|
0
| | 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. | 139 | Section 3.39.4.1.3 | 1/5/16 11:19:22 AM by aboufahj |
|
| ITI39 | ITI39-014 | reviewed | Testable |
0
|
0
| | 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. | 139 | Section 3.39.4.1.3 | 1/11/16 4:59:48 PM by aboufahj |
|
| ITI39 | ITI39-015 | reviewed | Testable |
0
|
2
| | Both the Initiating Gateway and Responding Gateway shall audit the Cross Gateway Retrieve | 140 | Section 3.39.4.1.4 | 2/22/17 12:01:39 PM by aberge |
|
| ITI39 | ITI39-016 | reviewed | Testable |
0
|
0
| | The audit entries shall be equivalent to the entries required for the Retrieve Document Set | 140 | Section 3.39.4.1.4 | 1/5/16 11:19:22 AM by aboufahj |
|
| ITI39 | ITI39-017 | reviewed | Testable |
0
|
1
| | The Initiating Gateway shall audit as if it were a Document Repository | 140 | Section 3.39.4.1.4 | 2/22/17 12:01:26 PM by aberge |
|