| RAD69 | RAD69-003 | reviewed | Testable |
1
|
2
| | The semantics of the Retrieve Imaging Document Set Response Message are identical to those inherited from the ITI-43 transaction and are specified in ITI TF-2b: 3.43.4.2.2. | 491 | Section 4.69.4.2.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD69 | RAD69-004 | to delete | Testable |
1
|
2
| | The Imaging Document Source or Initiating Imaging Gateway shall return the requested DICOM instances and a status code or an error code. The status codes, conditions of failure, and possible error messages are given in the ebRS standard and detailed in ITI TF-3: Table 4.2.4.2-4 [ITI-43] Retrieve Document Set and [ITI-39] Cross Gateway Retrieve Responses. | 492 | Section 4.69.4.2.3 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD69 | RAD69-005 | reviewed | Testable |
1
|
2
| | The Imaging Document Source shall encode the pixel data using one of the DICOM transfer 11590 syntaxes included in the Retrieve Imaging Document Set Request Message. If the Imaging Document Source cannot encode the pixel data using any of the requested transfer syntaxes then an error status shall be returned. | 492 | Section 4.69.4.2.3 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD69 | RAD69-006 | reviewed | Testable |
0
|
2
| | If the request contains a transfer syntax of 1.2.840.10008.1.2.4.94 (DICOM JPIP Referenced Transfer Syntax) or 1.2.840.10008.1.2.4.95 (DICOM JPIP Referenced Deflate Transfer Syntax), and the Imaging Document Source supports the requested transfer syntax, the following behavior is expected: If the DICOM Image Object(s) already have the same JPIP transfer syntax as the one indicated in the request, the Retrieve Imaging Document Set Response shall include the DICOM Image Objects unchanged. If the DICOM Image Object(s) have a transfer syntax that differs from that of the request, the Retrieve Imaging Document Set Response shall include the DICOM image with the transfer syntax changed to the requested transfer syntax. In addition, the pixel data Attribute (7Fe0,0010 tag) will have been removed and replaced with a Pixel Data Provider URL (0028,7FE0 tag). The URL represents the JPIP request and will include the specific target information.Upon receipt of this Retrieve Imaging Document Set Response, the Imaging Document Consumer may request the pixel data from the pixel data provider using the supplied URL. Additional parameters required by the application may be appended to the URL when accessing the pixel data provider. | 492 | Section 4.69.4.2.3 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD69 | RAD69-012 | reviewed | Testable |
2
|
2
| | The <iherad:RetrieveImagingDocumentSetRequest/> element for use with the Retrieve Imaging Document Set Request Message is defined by one or more <iherad:StudyRequest/> elements. This element contains one or more <iherad:StudyRequest/> elements. This element contains one or more <ihe:DocumentRequest/> elements. This element contains a required <ihe:RepositoryUniqueId/>, a required <ihe:DocumentUniqueId/> and a conditionally required <ihe:HomeCommunityId/>. | 494 | Section 4.69.5 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD69 | RAD69-013 | reviewed | Testable |
2
|
2
| | A required <iherad:TransferSyntaxUIDList/> element which contains a list of one or more <ihe:TransferSyntaxUID> elements. Each element represents one of the transfer syntax encodings that the Imaging Document Consumer is capable of processing. | 495 | Section 4.69.5 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD69 | RAD69-014 | reviewed | Testable |
1
|
2
| | The <ihe:RetrieveDocumentResponse/> element for use with the Retrieve Imaging Document Set Response Message is defined by a required /ihe:RetrieveDocumentSetResponse/rs:RegistryResponse element, a conditionally required sequence, if a matching document exists with <ihe:DocumentResponse/> elements containing a conditionally required <ihe:HomeCommunityId/> element, a required <ihe:RepositoryUniqueId/> that identifies , a required <ihe:Document/> element and a required <ihe:mimeType/> element that indicates the MIME type of the retrieved document. | 496 | Section 4.69.5 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD69 | RAD69-015 | reviewed | Testable |
1
|
2
| | The /RetrieveDocumentSetResponse/rs:RegistryResponse/@status attributes provides the overall status of the request: It shall contain one of the following values:urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success urn:ihe:iti:2007:ResponseStatusType:PartialSuccess urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure | 496 | Section 4.69.5 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD69 | RAD69-016 | reviewed | Testable |
1
|
2
| | For each document requested in a /RetrieveImagingDocumentSetRequest/StudyRequest/SeriesRequest/DocumentRequest element, if a warning is reported when retrieving the document, then a /RetrieveDocumentSetResponse/rs:RegistryResponse/rs:RegistryErrorList/ rs:RegistryError element shall be returned with the element @severity (urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Warning). | 496 | Section 4.69.5 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD75 | RAD75-001 | reviewed | Testable |
1
|
1
| | The message semantics for Cross Gateway Retrieve Imaging Document Set are the same as Retrieve Imaging Document Set [RAD-69] Request Message. See Section 4.69.4.1.2. | 506 | Section 4.75.4.1.2 | 2/1/24 10:11:39 AM by alegrand |
|
| RAD75 | RAD75-005 | reviewed | Testable |
0
|
1
| | The Responding Imaging Gateway shall return consolidated responses according to message semantics for the Retrieve Imaging Document Set Response message in Section 4.69.4.2.2. | 506 | Section 4.75.4.1.3 | 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-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-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 |
|