> > does any of the existing plugins show how to add a REST API
> > call to Orthanc when loaded ?
>
> Ah, I see: Samples/Basic/...
> :-)
Yes, and you can also check the following official plugins to have more
complete sample code:
http://www.orthanc-server.com/static.php?page=web-viewer
http://w
On Mon, Jan 18, 2016 at 11:54:28PM +0100, Karsten Hilbert wrote:
> > > submit_wl_entry_file
> > > remove_wl_entry_file
>
> does any of the existing plugins show how to add a REST API
> call to Orthanc when loaded ?
Ah, I see: Samples/Basic/...
:-)
Karsten
--
GPG key ID E4071346 @ eu.pool.
On Mon, Jan 18, 2016 at 09:49:59AM +0100, Sébastien Jodogne wrote:
> > first of all: I don't expect you to work on all this, much
> > less _now_.
> >
> > I am mainly asking to further my own understanding and to
> > assess what I can do or what I need to find someone to do.
>
> > Ah, I see. So,
Hi,
> first of all: I don't expect you to work on all this, much
> less _now_.
>
> I am mainly asking to further my own understanding and to
> assess what I can do or what I need to find someone to do.
OK ;)
> Ah, I see. So, assuming there _would_ be two REST calls
>
> submit_wl_entry_f
Hi Sébastien,
first of all: I don't expect you to work on all this, much
less _now_.
I am mainly asking to further my own understanding and to
assess what I can do or what I need to find someone to do.
> > > Yes. The only problem would be to remove the worklist once
> > > the device has uploaded
Hi,
On 15.01.2016 10:00, Sébastien Jodogne wrote:
>> There's a standard DICOM way of saying "remove this worklist entry"
>> (regardless of whether it is completed).
>
> This process is typically done by sending HL7 messages, not through
> DICOM messages.
>
> Maybe the N-DELETE from DICOM "norma
> > 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)
The current plugin wi
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
> When the ModalityWorkList plugin is loaded the Orthanc server
> gains the following capabilities:
>
> - watch a given path for files (which represent worklist entries in
> DICOM
> format)
> - when queried appropriately, return answers based on those files
>
> Is that correct
Hello Sébastien,
On Thu, Jan 14, 2016 at 12:00:55PM +0100, Sébastien Jodogne wrote:
> > > 1) Are you planning to provide something like this (pseudocode):
> > >
> > > curl PUT
> > > SERVER:worklist/WORLIST_NAME/worklist_file?data=data_of_worklist_file.wl
> > >
> > > That way, external soft
Hello Karsten,
> > I have got two questions regarding this plugin:
> >
> > 1) Are you planning to provide something like this (pseudocode):
> >
> > curl PUT
> > SERVER:worklist/WORLIST_NAME/worklist_file?data=data_of_worklist_file.wl
> >
> > That way, external software (like GNUmed)
On Thu, Jan 14, 2016 at 11:34:12AM +0100, Karsten Hilbert wrote:
> > Orthanc can serve DICOM worklists through its
> > "ModalityWorklists" official plugin [4], in a similar fashion
> > than DCMTK's wlmscpfs. This plugin is available in the
> > Orthanc official distribution, and is installed with t
On Wed, Jan 13, 2016 at 09:22:49AM +0100, Sébastien Jodogne wrote:
>>> I didn't figure out whether I can create a worklist.
>
> Orthanc can serve DICOM worklists through its
> "ModalityWorklists" official plugin [4], in a similar fashion
> than DCMTK's wlmscpfs. This plugin is available in the
> O
Am 13.01.2016 um 08:16 schrieb Andreas Tille:
> Hi Michael,
>
> On Tue, Jan 12, 2016 at 06:45:00PM -0500, Michael Onken wrote:
>>> What I would like to do: [typical imaging workflow]
>>
>> This can indeed be covered by Open Source tools. One well-known Open
>> Source DICOM toolkit is DCMTK [1] whi
On Wed, Jan 13, 2016 at 10:54:43AM +0100, Hilbert, Sebastian wrote:
> > I write you as the author of Orthanc [1] that you mentioned in your
> > question.
> > > > What I would like to do: [typical imaging workflow]
> > >
> Just to let you know. GNUmed [1] makes extensive use of the Orthanc REST AP
Am Wednesday 13 January 2016, 09:22:49 schrieb Sébastien Jodogne:
> Hello Sebastian,
>
> I write you as the author of Orthanc [1] that you mentioned in your
> question.
> > > What I would like to do: [typical imaging workflow]
> >
Just to let you know. GNUmed [1] makes extensive use of the Orthan
Hello Sebastian,
I write you as the author of Orthanc [1] that you mentioned in your question.
> > What I would like to do: [typical imaging workflow]
>
> This can indeed be covered by Open Source tools. One well-known Open
> Source DICOM toolkit is DCMTK which is developed in Germany. [...]
>
Hi Michael,
On Tue, Jan 12, 2016 at 06:45:00PM -0500, Michael Onken wrote:
> > What I would like to do: [typical imaging workflow]
>
> This can indeed be covered by Open Source tools. One well-known Open
> Source DICOM toolkit is DCMTK [1] which is developed in Germany. Since I
> am one the devel
Hi Sebastian,
> What I would like to do: [typical imaging workflow]
This can indeed be covered by Open Source tools. One well-known Open
Source DICOM toolkit is DCMTK [1] which is developed in Germany. Since I
am one the developers, I focus on these (and I am biased;). Of course
there are other (
19 matches
Mail list logo
