Retrieve Cache for RAD 69

Description

The test is to verify that Retrieve Cache is used for the IHE RAD-69 transaction. This means that object(s) are first copied to the retrieve cache from nearline storage and then will be used for RAD-69 transaction.

Steps

• Store object(s) to archive using storescu tool

   storescu -c DCM4CHEE@hostname:11112 /path-tostudy                                             
  

  Below is a snippet of Request - Response logs

   13:10:41,374 INFO  - STORESCU->DCM4CHEE(1) << 1:C-STORE-RQ[pcid=7, prior=0
     cuid=1.2.840.10008.5.1.4.1.1.2 - CT Image Storage
     iuid=1.3.12.2.1107.5.8.1.12345678.199508041417040742898 - ?
     tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian
  
   13:10:41,444 INFO  - STORESCU->DCM4CHEE(1) >> 1:C-STORE-RSP[pcid=7, status=0H
     cuid=1.2.840.10008.5.1.4.1.1.2 - CT Image Storage
     iuid=1.3.12.2.1107.5.8.1.12345678.199508041417040742898 - ?
     tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian
  

• Trigger RAD-69 transaction using XDS Exporter or use following curl command (Note : Replace the values of studyInstanceUID, seriesInstanceUID and DocumentUniqueId below with the values of the Study Instance UID, Series Instance UID and SOP Instance UID respectively of the object being used for this test) :

    curl -O http://localhost:8080/dcm4chee-arc/xdsi/ImagingDocumentSource \
    -H 'Content-Type: multipart/related; boundary="MIMEBoundary_4693e5ce87c3f1a8a06ebc9bbc9911b2e46e1863a7ac87ca"; type="application/xop+xml"; start="<0.5693e5ce87c3f1a8a06ebc9bbc9911b2e46e1863a7ac87ca@apache.org>"; start-info="application/soap+xml"; action="urn:ihe:rad:2009:RetrieveImagingDocumentSet"' \
    --data-binary '--MIMEBoundary_4693e5ce87c3f1a8a06ebc9bbc9911b2e46e1863a7ac87ca
    Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml"
    Content-Transfer-Encoding: binary
    Content-ID: <0.5693e5ce87c3f1a8a06ebc9bbc9911b2e46e1863a7ac87ca@apache.org>
    
    <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
    <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
    <wsa:To soapenv:mustUnderstand="true">http://localhost:8080/dcm4chee-arc/xdsi/ImagingDocumentSource</wsa:To>
    <wsa:MessageID soapenv:mustUnderstand="true">urn:uuid:3FC3AA9541DB19A2CA1509719154150</wsa:MessageID>
    <wsa:Action soapenv:mustUnderstand="true">urn:ihe:rad:2009:RetrieveImagingDocumentSet</wsa:Action></soapenv:Header>
    <soapenv:Body><xdsiB:RetrieveImagingDocumentSetRequest xmlns:xdsiB="urn:ihe:rad:xdsi-b:2009">
       <xdsiB:StudyRequest studyInstanceUID="1.2.392.200036.9125.0.199402091242.1">
          <xdsiB:SeriesRequest seriesInstanceUID="1.2.392.200036.9125.0.199402091242.1">
             <xdsb:DocumentRequest xmlns:xdsb="urn:ihe:iti:xds-b:2007">
                <xdsb:RepositoryUniqueId>1.3.6.1.4.1.21367.13.80.110</xdsb:RepositoryUniqueId>
                <xdsb:DocumentUniqueId>1.2.392.200036.9125.0.19950720105640</xdsb:DocumentUniqueId>
             </xdsb:DocumentRequest>
          </xdsiB:SeriesRequest>
       </xdsiB:StudyRequest>
       <xdsiB:TransferSyntaxUIDList>
          <xdsiB:TransferSyntaxUID>1.2.840.10008.1.2.1</xdsiB:TransferSyntaxUID>
       </xdsiB:TransferSyntaxUIDList>
    </xdsiB:RetrieveImagingDocumentSetRequest></soapenv:Body></soapenv:Envelope>
    --MIMEBoundary_4693e5ce87c3f1a8a06ebc9bbc9911b2e46e1863a7ac87ca--'
  

• One would see in the Wildfly server log that when the RAD-69 request is received by archive it first copies instance(s) from nearline storage to retrieve-cache storage and then uses it further from retrieve-cache for the RAD-69 transaction to complete.