| XCAI | XCAI-001 | reviewed | Testable |
1
|
1
| Covered by XDS-I | Imaging Document Consumer must support Retrieve Imaging Document Set [RAD-69] transaction. | 238 | Table 29.1- 1 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-002 | reviewed | Testable |
1
|
1
| Covered by XDS-I | Image document source must support Retrieve Imaging Document Set [RAD-69] transaction. | 238 | Table 29.1- 1 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-003 | reviewed | Testable |
1
|
1
| | Initiating Imaging Gateway must support Retrieve Imaging Document Set [RAD-69] transaction. | 238 | Table 29.1- 1 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-004 | reviewed | Testable |
1
|
1
| | Initiating Imaging Gateway must support Cross Gateway Retrieve Imaging Document Set [RAD-75] transaction. | 238 | Table 29.1- 1 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-005 | reviewed | Testable |
1
|
1
| | Responding Imaging Gateway must support Retrieve Imaging Document Set [RAD-69] transaction. | 238 | Table 29.1- 1 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-006 | reviewed | Testable |
1
|
1
| | Responding Imaging Gateway must support Cross Gateway Retrieve Imaging Document Set [RAD-75] transaction. | 238 | Table 29.1- 1 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-007 | reviewed | Testable |
0
|
1
| RAD TF-1 does not show an option for RIG support of Async on RAD-69, but I (Ralph) think that is because it is not optional. RAD TF-3 4.69.4.3 states: A Responding Imaging Gateway shall use the Asynchronous Web Services Exchange method if the Image Document Source supports the Asynchronous Web Services Option. | The Responding Imaging Gateway shall support the use of Asynchronous Web Services Methods (ITI TF-2: Appendix V.5) for the [RAD-75] transaction. | 239 | Section 29.1.1.1 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-008 | reviewed | Testable |
0
|
1
| | Initiating Imaging Gateway must support Asynchronous Web Services Exchange for RAD-69. Async support for RAD-75 is optional. | 239 | Section 29.1.1.2 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-010 | reviewed | Testable |
0
|
1
| Covered in XDS | Identify which Responding Imaging Gateways and homeCommunityIds. Identify which PID for each Responding Imaging Gateway. (method not specified) Initiate a Cross Gateway Query transaction [ITI-38] to each Responding Gateway | 239 | Section 29.3.2 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-012 | reviewed | Testable |
0
|
1
| Covered in XDS | Collect the response from all Responding Gateways. Verify that the homeCommunityId is present in each appropriate element | 240 | Section 29.3.2 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-013 | reviewed | Testable |
1
|
1
| Covered in XDS | Consolidate all updated response data into one response to the Document Consumer. The Initiating Gateway returns to the Document Consumer the same homeCommunityId attribute values that it received from Responding Gateway(s). | 240 | Section 29.3.2 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-016 | reviewed | Testable |
0
|
1
| Covered in XDS | Determines which Responding Imaging Gateways to contact by using the homeCommunityId to obtain the Web Services endpoint of the Responding Imaging Gateway. Initiate one or more Cross Gateway Retrieve Document Set transactions [ITI-39].If the homeCommunityId represents the local community the Initiating Gateway will initiate a Retrieve Document Set to a local Document Repository. | 240 | Section 29.3.2 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-018 | reviewed | Testable |
0
|
1
| Covered in XDS | Consolidate ITI-39 responses and respond to ITI-43. Response provides manifest and includes a) the Retrieve Location UID identifying the Imaging Document Source, b) the document unique Ids identifying the imaging documents within the Imaging Document Source c) list of one or more DICOM transfer syntax UIDs, d) Study Instance UID, e) Series Instance UID f) the homeCommunityId attribute. | 240 | Section 29.3.2 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-019 | | Testable |
0
|
1
| Covered in XDS | Displays list of images and reports to user | 240 | Section 29.3.2 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-021 | | Testable |
0
|
1
| | Determines which Responding Imaging Gateways to contact by using the homeCommunityId to obtain the Web Services endpoint of the Responding Imaging Gateway. Initiate one or more Cross Gateway Retrieve Imaging Document Set transactions [RAD-75]. Consolidate the results. | 240 | Section 29.3.2 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-022 | | Testable |
0
|
1
| | Initiate one or more Retrieve Document Set transaction [RAD-69] to the Imaging Document Source identified by the Retrieve Location UID(s) within the request and consolidate the responses in repsonse to RAD-75 | 240 | Section 29.3.2 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-023 | | Testable |
1
|
1
| | Must initiate a RAD-69 directly to any IDSs in the IC. | 240 | Section 29.3.2 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-024 | | Testable |
0
|
1
| Covered in XDS-I.b | shall include a SHA1 hash of the image document content in the Document metadata | 245 | Section 29.4.2 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-025 | | Testable |
0
|
1
| We don't have anything covering this. | Shall have the ability to verify the SHA 1 hash of the image document with the hash in the Document metadata. | 245 | Section 29.4.2 | 2/1/24 10:11:39 AM by alegrand |
|
| XCAI | XCAI-026 | | Testable |
1
|
1
| | Responding Imaging Gateway shall return either zero documents with no further information or XDSUnknownPatientId in response to queries of unknown patient identifiers, depending on local policy. This applies to patient identifiers that are properly formatted or improperly formatted. | 245 | Section 29.4.2 | 2/1/24 10:11:39 AM by alegrand |
|