| XCAI | XCAI-001 | reviewed | Testable |
0
|
1
| | Must support Retrieve Imaging Document Set [RAD-69] transaction. | 268 | Section 29.1 | 1/18/17 4:55:56 PM by jdramou |
|
| XCAI | XCAI-002 | reviewed | Testable |
0
|
1
| | Must support Retrieve Imaging Document Set [RAD-69] transaction. | 269 | Section 29.1 | 1/18/17 4:56:04 PM by jdramou |
|
| XCAI | XCAI-003 | reviewed | Testable |
11
|
1
| | Must support Retrieve Imaging Document Set [RAD-69] transaction. | 269 | Section 29.1 | 2/9/17 4:29:23 PM by gthomazon |
|
| XCAI | XCAI-004 | reviewed | Testable |
10
|
1
| | Must support Cross Gateway Retrieve Imaging Document Set [RAD-75] transaction. | 269 | Section 29.1 | 2/9/17 4:30:28 PM by gthomazon |
|
| XCAI | XCAI-005 | reviewed | Testable |
10
|
1
| | Must support Retrieve Imaging Document Set [RAD-69] transaction. | 269 | Section 29.1 | 2/9/17 4:34:01 PM by gthomazon |
|
| XCAI | XCAI-006 | reviewed | Testable |
11
|
1
| | Must support Cross Gateway Retrieve Imaging Document Set [RAD-75] transaction. | 269 | Section 29.1 | 2/9/17 4:35:27 PM by gthomazon |
|
| 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. | Must support the use of Asynchronous Web Services Methods for RAD-75. The documentation does not show an option for async support for RAD-69. | 269 | Section 29.1.1 | 1/18/17 4:52:56 PM by jdramou |
|
| XCAI | XCAI-008 | reviewed | Testable |
0
|
1
| | Must support Asynchronous Web Services Exchange for RAD-69. Async support for RAD-75 is optional. | 269 | Section 29.1.1 | 2/14/17 9:36:03 AM by |
|
| XCAI | XCAI-009 | reviewed | Testable |
0
|
1
| Covered in XDS | Initiate Registry Stored Query [ITI-18] to Initiating Gateway | 272 | Section 29.3.2 | 1/18/17 4:41:45 PM by jdramou |
|
| 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 | 272 | Section 29.3.2 | 1/18/17 4:50:01 PM by jdramou |
|
| XCAI | XCAI-011 | reviewed | Testable |
0
|
1
| Covered in XDS | Initiate a Registry Stored Query [ITI-18] to the local Document Registry. Update the response from the Document Registry to ensure that the homeCommunityId is specified on every applicable element. This updated response is sent as the response. | 272 | Section 29.3.2 | 1/18/17 4:53:08 PM by jdramou |
|
| 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 | 272 | Section 29.3.2 | 1/18/17 4:50:13 PM by jdramou |
|
| XCAI | XCAI-013 | reviewed | Testable |
0
|
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). | 272 | Section 29.3.2 | 1/18/17 4:50:24 PM by jdramou |
|
| XCAI | XCAI-014 | reviewed | Testable |
0
|
1
| Covered in XDS | DC must account for two unique aspects of the response; a) the homeCommunityId attribute will be specified and b) the Document Consumer may not be able to map the Retrieve Location UID value directly to a Document Repository located in a remote community. DC retains the values of the homeCommunityId attribute. | 272 | Section 29.3.2 | 1/18/17 4:42:27 PM by jdramou |
|
| XCAI | XCAI-015 | reviewed | Testable |
0
|
1
| Covered in XDS | Initiates a Retrieve Document Set [ITI-43] to IG. Includes a) the document unique ID b) the Retrieve Location unique ID c) the homeCommunityId attribute. | 272 | Section 29.3.2 | 1/18/17 4:42:38 PM by jdramou |
|
| 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. | 273 | Section 29.3.2 | 1/18/17 4:50:59 PM by jdramou |
|
| XCAI | XCAI-017 | reviewed | Testable |
0
|
1
| Covered in XDS | Initiate Retrieve Document Set [ITI-43] to Document Repositories. Response to these are bundled in response to ITI-39 | 273 | Section 29.3.2 | 1/18/17 4:53:19 PM by jdramou |
|
| 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. | 273 | Section 29.3.2 | 1/18/17 4:51:13 PM by jdramou |
|
| XCAI | XCAI-019 | reviewed | Testable |
0
|
1
| Covered in XDS | Displays list of images and reports to user | 273 | Section 29.3.2 | 1/18/17 4:42:51 PM by jdramou |
|
| XCAI | XCAI-020 | reviewed | Testable |
0
|
1
| | User chooses content, initiates Retrieve Imaging Document Set [RAD-69] to Initiating Imaging Gateway, including 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. | 273 | Section 29.3.2 | 1/18/17 5:01:42 PM by jdramou |
|