Mercurial > hg > orthanc-book
diff Sphinx/source/faq/viewers.rst @ 3:3405c25deb53
What DICOM viewer is compatible with Orthanc?
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Fri, 22 Apr 2016 15:51:17 +0200 |
parents | |
children | 669ea65ba7fb |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Sphinx/source/faq/viewers.rst Fri Apr 22 15:51:17 2016 +0200 @@ -0,0 +1,37 @@ +What DICOM viewer is compatible with Orthanc? +============================================= + +Basically, any viewer that supports :ref:`DICOM query/retrieve +<query-retrieve>` should be compatible with Orthanc. + +Because the Orthanc project is focused on the promotion of free +software for medical imaging, we cannot keep track of the list of +proprietary DICOM viewers that are compatible with Orthanc. Here is a +list of free and open-source viewers that are known to be compatible +with Orthanc (do not hesitate to `warn us +<mailto:s.jodogne@gmail.com>`__ about other compatible FOSS): + +* `Horos <http://www.horosproject.org/>`__. +* `Gingko CADx <http://www.ginkgo-cadx.com/>`__ (a :ref:`configuration + guide <ginkgo-cadx>` is available). +* `3D Slicer <https://www.slicer.org/>`__. +* `medInria <https://med.inria.fr/>`__. +* `Aeskulap <http://aeskulap.nongnu.org/>`__. +* `OsiriX <http://www.osirix-viewer.com/>`__ (note however that the + openness of this particular software is `currently subject to + discussion + <http://blog.purview.net/an-open-letter-to-the-osirix-community>`__). + +Make also sure to check out the following official extensions to Orthanc: + +* `Web viewer plugin <http://www.orthanc-server.com/static.php?page=web-viewer>`__. +* `ImageJ extension <http://www.orthanc-server.com/static.php?page=imagej>`__. + +As far as Sébastien Jodogne is concerned, he uses the Web viewer +plugin and the ImageJ extension for simple analysis tasks. For more +intensive 3D viewing, he uses Ginkgo CADx. Finally, for advanced +usages (such as PET-CT fusion or contouring), he switches to 3D +Slicer. + +If you face problems when configuring DICOM networking, make sure to +follow the :ref:`troubleshooting guide <dicom>`.