dcm4chee
  1. dcm4chee
  2. DCMEE-1820

DCM4CHEE Management of the Move SCU Service

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: Wishlist
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Tracking Status:
      Risk Analysis - Todo, Test Spec - ToReview, Test State - Not tested

      Description

      In dcm4chee, DICOM objects that are transmitted out of the system (either as the result of a C-MOVE, or autoforwarding/routing) end up going through the Move SCU Service. Currently there is no easy way to manage the move process other than the ability to define a retry strategy and to remove all (move) messages from the underlying queue - individual messages cannot be identified and removed. Finally, failed (retries exhausted) messages are simply discarded.
      The main project goal is to create a management interface for the Move SCU Service. This includes a management console view of what has been sent, transfer times, delete queued transmissions, send immediately, etc.
      I have proposed a solution that utilizes the Unified Worklist and Procedure Step implementation - see:
      http://www.dcm4che.org/confluence/display/ee2/Move+SCU+Queue+Improvements

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Gunter Zeilinger
            Reporter:
            David Davies
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development