Re: understanding DICOM workflow
On Thu, Jan 14, 2016 at 12:46:20PM +0100, Sébastien Jodogne wrote:
> > If so I was wondering whether the ModalityWorkList plugin
> > could be extended with one REST API call which would allow
> > external applications to add *.wl worklist item files over
> > the network rather than having to store them into the watched
> > path directly. All the ModalityWorkList plugin would do is to
> > accept such files and store them into the watched path.
> > Sound reasonable ?
> Yes. The only problem would be to remove the worklist once
> the device has uploaded its acquisition to Orthanc
How does that happen _now_ with the current ModalityWorkList
plugin ? (without regard to anything I said would be useful
from a GNUmed point of view)
I would have assumed there's two ways:
There's a standard DICOM way of saying "remove this
worklist entry" (regardless of whether it is completed).
Delete the corresponding *.wl from the worklist directory
being watched by Orthanc.
> (which will necessitate a custom "OnChange" callback watching DICOM
> files entering Orthanc), or if GNUmed invalidates some
I agree that there would be a need for a second REST API
call, namely to remove a give MWL entry.
Wait, does the ServeFolder plugin help any ? Does it support
put/delete of files in the served directory ?
> However, I currently have no time to work on this extension
> of the ModalityWorklists plugin.
Sure. Do you think I should open a card on Trello or is the
above a wontfix from the beginning ?
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346