UI Triggered DICOM Export - dcm4che/dcm4chee-arc-light GitHub Wiki
DICOM objects can be exported to remote destinations either over web or using DICOM upper layer services. Archive's UI and RESTful services provides user with three ways to export objects to a destination :
- To export single study/series/object : Use Synchronised Export or Queued Export.
- To export multiple studies at a time : By default Queued Export is used.
- To export studies whose UIDs are specified in a CSV file : By default Queued Export is used.
Synchronised export means objects are directly synchronously sent to remote destinations without queueing them in Java Messaging Subsystem of archive's Wildfly application server. Queued export implies the studies are asynchronously sent to the remote destinations using Wildfly application server's JMS, eventually allowing the user to monitor these tasks and related queue messages using archive's UI.
Alternatively, choose rule based export to forward studies to a destination when they are stored to the archive instead of using Archive UI.