| RAD69 | RAD69-003 | reviewed | Testable |
16
|
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. | 194 | Section 4.69.4.2.2 | 2/13/17 11:30:04 AM by aberge |
|
| RAD69 | RAD69-004 | reviewed | Testable |
14
|
2
| | response: shall return the imaging document(s) or an error code in case the document could not be returned | 195 | Section 4.69.4.2.3 | 2/13/17 11:24:44 AM by aberge |
|
| RAD69 | RAD69-005 | reviewed | Testable |
6
|
2
| | response: The pixel data shall be encoded using one of the DICOM transfer syntaxes included in the request or an error status shall be returned | 195 | Section 4.69.4.2.3 | 2/13/17 11:24:46 AM by aberge |
|
| RAD69 | RAD69-006 | reviewed | Testable |
0
|
2
| | If the Imaging Document Consumer or Responding Imaging Gateway specifies a transfer syntax field 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. | 195 | Section 4.69.4.2.3 | 1/20/17 5:16:40 PM by jdramou |
|
| RAD69 | RAD69-012 | reviewed | Testable |
13
|
2
| | The <iherad:RetrieveImagingDocumentSetRequest/> element for use with the Retrieve Imaging Document Set Request Message is defined as:•One or more <iherad:StudyRequest/> elements each of which includes a “studyInstanceUID” attribute identifying the study associated with the DICOM images/ objects being retrieved. Each <iherad:StudyRequest/> element shall contain: •One or more <iherad:SeriesRequest/> elements each of which includes a “seriesInstanceUID” attribute identifying the series associated with the DICOM images/ objects being retrieved. Each <iherad:SeriesRequest/> element shall contain:•One or more <ihe:DocumentRequest/> elements, each one representing an individual document that the Imaging Document Consumer or Responding Imaging Gateway wants to retrieve from the Imaging Document Source. Each <ihe:DocumentRequest/> element contains:•A required <ihe:RepositoryUniqueId/> element that identifies the Imaging Document Source from which the document is to be retrieved. This value corresponds to XDSDocumentEntry.repositoryUniqueId.•A required <ihe:DocumentUniqueId/> element that identifies the document within the Imaging Document Source. This value corresponds to the SOP Instance UID referenced within the DICOM manifest.•A conditionally required <ihe:HomeCommunityId/> element that corresponds to the home attribute of the Identifiable class in ebRIM. The element shall be populated if the request is to an Initiating Imaging Gateway. Otherwise, it may be absent. | 197 | Section 4.69.5 | 2/13/17 11:24:55 AM by aberge |
|
| RAD69 | RAD69-013 | reviewed | Testable |
13
|
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 | 198 | Section 4.69.5 | 2/13/17 11:24:59 AM by aberge |
|
| RAD69 | RAD69-014 | reviewed | Testable |
14
|
2
| | The <ihe:RetrieveDocumentResponse/> element for use with the Retrieve Imaging Document Set Response Message is defined as:•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. The value of this element shall be the same as the value of the /RetrieveImagingDocumentSetRequest/StudyRequest/SeriesRequest/DocumentRequest/HomeCommunityId element in the Retrieve Document Set Request Message. If the <ihe:HomeCommunityId/> element is not present in the Retrieve Document Set Request Message, this value shall not be present.•A required <ihe:RepositoryUniqueId/> that identifies the Imaging Document Source from which the document is to be retrieved. The value of this element shall be the same as the value of the /RetrieveImagingDocumentSetRequest/StudyRequest/SeriesRequest/DocumentRequest/RepositoryUniqueId element in the original Retrieve Imaging Document Set Request Message. This value corresponds to RetrieveLocation UID in the DICOM manifest.•A required <ihe:DocumentUniqueId/> that identifies the document within the Imaging Document Source. The value of this element shall be the same as the value of the /RetrieveImagingDocumentSetRequest/StudyRequest/SeriesRequest/DocumentRequest/DocumentUniqueId element in the original Retrieve Imaging Document Set Request Message. This value corresponds to the SOP Instance UID referenced within the DICOM manifest.•A required <ihe:Document/> element that contains the retrieved document as an XOP Infoset.•A required <ihe:mimeType/> element that indicates the MIME type of the retrieved document | 199 | Section 4.69.5 | 2/13/17 11:25:00 AM by aberge |
|
| RAD69 | RAD69-015 | reviewed | Testable |
14
|
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 | 199 | Section 4.69.5 | 2/13/17 11:25:03 AM by aberge |
|
| RAD69 | RAD69-016 | reviewed | Testable |
14
|
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:•@severity is urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Warning•@errorCode is specified•@codeContext contains the warning message•@location contains the DocumentUniqueId of the document requested •The document shall be returned in an instance of /RetrieveDocumentSetResponse/DocumentResponse/Document as an XOP Infoset. The returned document and warning are correlated via the DocumentUniqueId. •If an error is reported when retrieving a document, then a /RetrieveDocumentSetResponse/rs:RegistryResponse/rs:RegistryErrorList/ rs:RegistryError element shall be returned with:•@severity is urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error•@errorCode is specified•@codeContext contains the error message•@location contains the DocumentUniqueId of the document requested•No corresponding RetrieveDocument SetResponse/DocumentResponse element shall be returned •If the document is successfully retrieved (without warning) then no /RetrieveDocumentSetResponse/rs:RegistryResponse/rs:RegistryErrorList/ rs:RegistryError element shall be present and a /RetrieveDocumentSetResponse/DocumentResponse/Document element shall be returned containing the document as an XOP Infoset. | 200 | Section 4.69.5 | 2/13/17 11:25:11 AM by aberge |
|
| RAD75 | RAD75-001 | reviewed | Testable |
11
|
1
| | The initiating gateway shall specify the 'homeCommunityId' parameter. The parameter shall contain the value that identifies the community associated with the Responding Imaging Gateway(s). | 210 | Section 4.75.4.1.2 | 2/9/17 5:45:18 PM by gthomazon |
|
| RAD75 | RAD75-005 | reviewed | Testable |
19
|
1
| | The Initiating Imaging Gateway Actor shall consolidate results from all Responding Imaging Gateways. This includes reflecting in the consolidated results returned to the originating Retrieve Imaging Document Set [RAD-69] all successes and failures received from Responding Imaging Gateways. If one of more responses with a status of failure or partial successes are received from Responding Imaging Gateways, the Initiating Imaging Gateway shall respond to the original RAD-69 request from the Imaging Document Consumer with both DocumentResponse and RegistryErrorList elements in one response and specify PartialSuccess status | 210 | Section 4.75.4.1.3 | 2/9/17 5:46:32 PM by gthomazon |
|
| 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-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-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-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-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-021 | reviewed | 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. | 273 | Section 29.3.2 | 1/18/17 5:01:50 PM by jdramou |
|