...
It is possible (likely?) that this development would occur in parallel to the current MoveSCU implementation.
List of desired operations functionality from a web user interface:
- View move SCU items in their various states (pending, completed, failed, canceled, etc.)
- View transmission time for completed move SCU items
- Cancel a pending move SCU item
- Time to live for an item in the queue after it has been completed/failed/canceled.
- Trigger a pending item to be sent immediately
List of desired functionality of the forward service:
- The ability to specify a distinct C-STORE SCU AET attribute (different than the retrieve AET or Move SCP AET) without having to configure additional DICOM server services
- The ability to only forward if the content has changed, e.g. the MD5 of newly stored images is different than previously stored images. This is to eliminate duplicate forwarding operations when a misbehaved DICOM device sends in the same data multiple times.