| ITI38 | ITI38-019 | reviewed | Testable |
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. | 129 | Section 3.38.4.1.3 | 5/2/19 5:32:51 PM by NicolasBailliet |
|
| ITI38 | ITI38-020 | reviewed | Testable |
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. | 129 | Section 3.38.4.1.3 | 5/2/19 5:32:51 PM by NicolasBailliet |
|
| ITI39 | ITI39-002 | reviewed | Testable |
0
|
1
| | Responding Gateways shall support the Asynchronous Web Services Exchange Option on the Cross Gateway Retrieve. | 134 | Section 3.39.1 | 5/3/19 8:39:49 AM by NicolasBailliet |
|
| ITI39 | ITI39-006 | reviewed | Testable |
0
|
1
| | Initiating Gateways which support the On-Demand Documents Option shall be capable of retrieving an On-Demand Document Entry | 135 | Section 3.39.4.1.2 | 5/3/19 8:58:05 AM by NicolasBailliet |
|
| ITI39 | ITI39-008 | reviewed | Testable |
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 NewDocumentUniqueId | 139 | Section 3.39.4.1.2 | 5/3/19 8:59:18 AM by NicolasBailliet |
|
| ITI39 | ITI39-010 | reviewed | Testable |
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 Gateway | 136 | Section 3.39.4.1.3 | 5/3/19 9:01:55 AM by NicolasBailliet |
|
| ITI39 | ITI39-011 | reviewed | Testable |
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. | 136 | Section 3.39.4.1.3 | 5/3/19 9:09:52 AM by NicolasBailliet |
|
| ITI39 | ITI39-014 | reviewed | Testable |
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. | 136 | Section 3.39.4.1.3 | 5/3/19 9:09:25 AM by NicolasBailliet |
|
| XCA | XCA-005 | reviewed | Testable |
0
|
1
| | Initiating Gateway which support XDS Affinity Domain Option SHALL receive Registry Stored Query [ITI-18] transactions from a local Document Consumer Actor and act on those requests on behalf of the Document Consumer | 181 | Section 18.2.1 | 8/2/19 4:47:31 PM by mtoudic |
|
| XCA | XCA-006 | reviewed | Testable |
0
|
1
| | Initiating Gateway which support XDS Affinity Domain Option SHALL require the homeCommunityId as an input parameter on relevant queries, and shall specify the homeCommunityId attribute within its Registry Stored Query responses | 181 | Section 18.2.1 | 8/26/19 5:25:26 PM by NicolasBailliet |
|
| XCA | XCA-007 | reviewed | Testable |
0
|
1
| | Initiating Gateway which support XDS Affinity Domain Option SHALL receive Retrieve Document Set [ITI-43] transactions from a local Document Consumer Actor and act on those requests on behalf of the Document Consumer | 182 | Section 18.2.1 | 8/26/19 5:25:26 PM by NicolasBailliet |
|
| XCA | XCA-008 | reviewed | Testable |
0
|
1
| | Initiating Gateway which support XDS Affinity Domain Option SHALL require the homeCommunityId as an input parameter for Retrieve Document Set [ITI-43] transactions | 181 | Section 18.2.1 | 8/26/19 5:25:26 PM by NicolasBailliet |
|
| XCA | XCA-009 | reviewed | Testable |
0
|
1
| Agreed to do not cover this assertion | An Initiating Gateway that supports the On-Demand Documents Option SHALL be able to specify, in a Cross Gateway Query, a request for On-Demand Document Entries | 185 | Section 18.2.4 | 8/26/19 5:25:26 PM by NicolasBailliet |
|
| XCA | XCA-010 | reviewed | Testable |
0
|
1
| Agreed to do not cover this assertion | An Initiating Gateway that supports the On-Demand Documents Option SHALL be able to retrieve On-Demand Document Entries from one or more Responding Gateways | 185 | Section 18.2.4 | 8/26/19 5:25:26 PM by NicolasBailliet |
|
| XCA | XCA-011 | reviewed | Testable |
0
|
1
| | An Responding Gateway that supports the On-Demand Documents Option SHALL be able to respond with On-Demand Document Entries to a Cross Gateway Query requesting On-Demand Document Entries. | 185 | Section 18.2.4 | 8/26/19 5:25:26 PM by NicolasBailliet |
|
| XCA | XCA-012 | reviewed | Testable |
0
|
1
| | An Responding Gateway that supports the On-Demand Documents Option SHALL be able to respond to a Cross Gateway Retrieve requesting On-Demand Document Entries | 185 | Section 18.2.4 | 8/26/19 5:25:26 PM by NicolasBailliet |
|
| XCA | XCA-013 | reviewed | Testable |
0
|
2
| Agreed to do not cover this assertion | Responding Gateways which support the Persistence of Retrieved Documents Option shall support the On-Demand Documents Option | 185 | Section 18.2.5 | 8/26/19 5:25:26 PM by NicolasBailliet |
|
| XCA | XCA-014 | reviewed | Testable |
0
|
1
| Agreed to do not cover this assertion | Responding Gateways which support the Persistence of Retrieved Documents Option shall make available, as a Stable Document Entry in response to a Cross Gateway Query | 185 | Section 18.2.5 | 8/26/19 5:25:26 PM by NicolasBailliet |
|
| XCA | XCA-018 | reviewed | Testable |
0
|
1
| | Document Consumer shall either supply a patient identifier or a unique document entry identifier | 192 | Section 18.4.2 | 8/26/19 5:25:26 PM by NicolasBailliet |
|