Orthanc setup outline/configuration

Hello everyone

First of all, kudos to Sébastien Jodogne and the Osimis team, from what I can understand you guys are doing an awesome job with this project.

I am quite new to servers and network setups, so apologies if my questions are obvious.

I am trying to use Orthanc in a setup where it is installed on a main computer/server with a good GPU to do image manipulations, mostly on CT and PET images.
I do understand how I connect to different scanners and viewer software, and it works.

But I am not quite sure how researchers will be able to access the OrthancExplorer of the server, without them also setting up their own orthanc server instance, and then connecting them as “peers”. - Is this even possible?
I know of the WebViewer, but I would like the layout and capabilities of the OrthancExplorer.

Best regards
Jakob

Orthanc_setup.png

Jakob,

There are probably multiple ways to accomplish something like you are suggesting. It might depend a little upon where your users are located and what kind of access controls you need. It makes it a little easier if it is within the same institution and you don’t want fine access controls, and having a single instance of Orthanc running on decent hardware would probably be easier than maintaining multiple instances of Orthanc in a distributed network, although that can be done also. If the researches all have something like HOROS or OSIRIX, they can be networked with Orthanc pretty easily really. I think HOROS is sort of like a mini-PACS anyways. I have that also on Mac OSX and it works well with Orthanc.

I’ve actually been working on some ideas for something similar to that as part of a RIS project. I have a GitHub project for that, although I have to update the source code there.

A live demo is here: https://sias.dev:8000/browsestudies/index.html, which is a studies browser. I’ll have to write up some documentation, but it basically allows you to list all of the studies on the Orthanc Server in a paginated format, and you can search for studies, filtering on quite a few different parameters now. You can also view the studies in the Osimis Viewer or OHIF (this little magnifying glass to the left of study in the list. The little reports icon doesn’t do much here, but I do have a reporting feature on the RIS that I’ll try to move there. The litter airplane is under development, but would basically allow you to fetch a study and route it to a modality or AET, like a workstation. The “DCM” and “ZIP” download image archives. The “ALL” thing doesn’t do anything here, but I’ll make it show all of the studies for that particular patient. Patient History if the the RIS, but there is a DICOM field for “Additional Patient Info”, that I. might be able to display there if the RIS populates that. You’d have to play around with the Date Selector and other select lists at the top.

There is a much busier page here: https://sias.dev:8000/browsestudies/restapi.html

Basically a dev tool and API tester, although there is demo there about creating a PDF from HTML and then attaching that to a study.
(createPDF, Attach to Study, Open After Created). If you do that it’ll attach the PDF to the study, and when you view there will be a little document icon as an instance. If you drag that to the viewer it’ll display the PDF. You are welcome to try. It does that for just one study, so I check every now and then to delete any that were added.

It is an open site for now, so you are welcome to play with that.

Also, just generally, the demo is using the “ServeFolders” plug-in for that front-end, something that you or your developers might find useful because you can basically build your own front-end.

The demo is also running behind an NGINX or OpenResty server as a reverse proxy. There are some authentication tools for that kind of setup that can allow you to implement some sort of access controls, and you could actually provide access to the Orthanc Explorer through such a mechanism to remote users. I have that turned off now, and still exploring how best to do that (e.g. Oauth or something else). It isn’t that difficult to setup really, but the authentication part requires some thought. Osimis has an “Advanced Authentication” Plug-in that you might find useful.

/sds

Hello,

Thanks for your support.

You should learn about the “reverse proxy” mechanism (e.g. of nginx or Apache) to publish the “Orthanc Explorer” interface by a Web server. This would allow your researchers to connect to Orthanc Explorer from a remote computer.
https://book.orthanc-server.com/faq/nginx.html

https://book.orthanc-server.com/faq/apache.html

Sébastien-

Hey

Thanks for the very elaborate answer Sds, your project looks very promising, but for now I just need to setup a little test network.

And thanks Sébastien, the reverse proxy looks like what I need in the long run!

  • But for now I just settled with people accessing the server only on the Intranet.

/Jakob

mandag den 24. august 2020 kl. 10.12.40 UTC+2 skrev s.jo...@gmail.com:

Additional question for you Sébastien.

Regarding the new version 1.73, are you expecting to release it as stable one the Ubuntu packages site, so it can be installed automatically? As the current version available is only 1.5.8.

  • I reckon this is probably not as easy as it sounds.

I tried to install this file orthanc_1.7.2+dfsg-4_amd64.deb but even though I have the libboost-regex1.71.0 installed, it throws and error saying I am missing the libboost-regex1.71.0-icu67, but to me it looks like this package should be included ind the libboost-regex-1.71.0. ?

For now I just made a static build, which seems to work, but it would be nice to have an easy install where libraries are shared with the system.

/Jakob

tirsdag den 25. august 2020 kl. 09.25.44 UTC+2 skrev Jakob:

The same question has been answered recently:
https://groups.google.com/d/msg/orthanc-users/_U-SKPxCzfU/5PIU3HReAQAJ

The Debian Sid (unstable) package is already upgraded to 1.7.3:
https://packages.debian.org/unstable/orthanc

My apologies for missing both of them.

I will have to try the installment through the Debian system then.

/Jakob

tirsdag den 25. august 2020 kl. 11.09.56 UTC+2 skrev s.jo...@gmail.com: