How to configure forwarding of received instances

vrindanayak edited this page Oct 12, 2016 · 16 revisions
Clone this wiki locally

forward-series.puml

Configuration

To configure forwarding of received instances you have to add one or several Export Rules

  • on Device level - to forward instances received by any Application Entity of the Archive - or
  • on Application Entity level - to forward instances received by this Application Entity of the Archive -

and also add one Exporter for each destination.

You may adjusting following LDIF file:

version: 1
# Sample configuration for forwarding of received instances

# The Export Rule specifies on which entity level the export shall be triggered, how long the export shall be
# delayed after the receive of the last instance of the entity, and optionally additional conditions which
# have to be matched by the instance to trigger the export
dn: cn=Forward to STORESCP,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
objectClass: dcmExportRule
cn: Forward to STORESCP
dcmEntity: Series
dcmDuration: PT1M
dcmExporterID: STORESCP
# Only export CT and MR Series received by DCM4CHEE from FORWARD between Monday and Friday
#dcmProperty: ReceivingApplicationEntityTitle=DCM4CHEE
#dcmProperty: SendingApplicationEntityTitle=FORWARD
#dcmProperty: Modality=CT|MR
#dcmSchedule: dayOfWeek=1-5

# The Exporter object, referenced by the Export Rule via the Exporter ID, specifies the type and destination
# of the export, which local AE shall perform the forward, and which JMS Queue shall be used to queue Export
# Tasks ready to be performed, and optionally to defer the export to specified times
dn: dcmExporterID=STORESCP,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
objectClass: dcmExporter
dcmExporterID: STORESCP
dcmURI: dicom:STORESCP
dicomAETitle: DCM4CHEE
dcmQueueName: Export1
# defer export after business hours (between 6 pm and 6 am, or at any time on Saturday and Sunday)
#dcmSchedule: hour=18-6 dayOfWeek=*
#dcmSchedule: hour=* dayOfWeek=0,6

and import it to the LDAP Server by using the ldapadd command line utility or the LDIF Import... function of Apache Directory Studio - or directly use its New Entry... function to create corresponding Export Rule and Exporter entries.

One may refer to Export Rule and Exporter Descriptor to understand the description of attributes.

Verification

Required dcm4che Tools

  • storescu simulating the external object source (e.g. modality) STORESCU, from which objects are getting received
  • storescp simulating the external object destination (e.g. workstation) STORESCP, to which received objects are forwarded

Procedure

Remote application entity STORESCP needs to be configured, as it acts as a destination for instances that are forwarded by any Application Entity of Archive when the export rule is matched. Refer How to configure remote Application Entities

  1. Start storescp using STORESCP tool
    storescp -b STORESCP:port
    Below is a snippet of the same

         13:30:10,183 INFO  - Start TCP Listener on 0.0.0.0/0.0.0.0:5105
    
  2. Store images in archive using STORESCU tool
    storescu -c DCM4CHEE@hostname:port /image.dcm
    Below is a snippet of Request - Response log

         13:33:40,267 INFO  - STORESCU->MAS1TLN(1) << 227: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.2.485251.834849.68674954.2000021711442141 - ?
           tsuid=1.2.840.10008.1.2.4.80 - JPEG-LS Lossless Image Compression
    
         13:33:40,267 INFO  - STORESCU->MAS1TLN(1) >> 216: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.2.485251.834849.68674954.2000021711472219 - ?
           tsuid=1.2.840.10008.1.2.4.80 - JPEG-LS Lossless Image Compression
    
  3. After a delay of approximately 2 minutes, the image is being received on STORESCP side Below is a snippet of the Request - Response log

         13:35:24,780 INFO  - ARCPAS1TRT<-ARCACT1TLN(1) >> 228:C-STORE-RQ[pcid=5, prior=0
           cuid=1.2.840.10008.5.1.4.1.1.2 - CT Image Storage
           iuid=1.3.12.2.1107.5.8.2.485251.834849.68674954.2000021711414489 - ?
           tsuid=1.2.840.10008.1.2.4.80 - JPEG-LS Lossless Image Compression
    
         13:35:24,781 INFO  - ARCPAS1TRT<-ARCACT1TLN(1) << 228:C-STORE-RSP[pcid=5, status=0H
           cuid=1.2.840.10008.5.1.4.1.1.2 - CT Image Storage
           iuid=1.3.12.2.1107.5.8.2.485251.834849.68674954.2000021711414489 - ?
           tsuid=1.2.840.10008.1.2.4.80 - JPEG-LS Lossless Image Compression
    
  4. Once the export forwarding is complete, the status in the Export1 queue changes to Completed. Below is a snapshot of how it looks like below on the Archive UI page :

Export Triggered Features

  1. One may trigger an Instance Availability Notification to be sent to systems on successful export/forwarding of instances then one can follow the steps mentioned in Export Triggered IAN in How to configure Instance Availability Notification

  2. One may trigger a Storage Commitment to be sent to systems on successful export/forwarding of instances then one can follow the steps mentioned in Export Triggered in How to configure Storage Commitment