Mercurial > hg > orthanc-book
changeset 153:008091376e7a
dicom-sr
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Fri, 22 Jun 2018 10:54:20 +0200 |
parents | 0fe3156b43a3 |
children | 365427cebb64 |
files | Sphinx/source/faq/supported-images.rst |
diffstat | 1 files changed, 10 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/Sphinx/source/faq/supported-images.rst Tue May 29 11:58:56 2018 +0200 +++ b/Sphinx/source/faq/supported-images.rst Fri Jun 22 10:54:20 2018 +0200 @@ -6,11 +6,17 @@ Orthanc can **receive/store/send** any kind of standard DICOM files (cf. the `DICOM conformance statement <https://bitbucket.org/sjodogne/orthanc/src/default/Resources/DicomConformanceStatement.txt>`__). +Note that the ``UnknownSopClassAccepted`` :ref:`configuration option +<configuration>` can be set to `true` if interfacing with modalities +that are producing non-standard SOP classes. -However, its core engine is not able to **render** all of them as PNG -images. An image that Orthanc cannot decode is displayed as -"Unsupported" by Orthanc Explorer. Currently, the core engine of -Orthanc can decode: +Orthanc Explorer can **display the raw DICOM tags** of any such DICOM +file (including notably DICOM-SR structured reports). + +However, the core engine of Orthanc is not able to **render all of the +DICOM files as PNG images**. An image that Orthanc cannot decode is +displayed as "Unsupported" by clicking on the "Preview" buttons of +Orthanc Explorer. Currently, the core engine of Orthanc can decode: * uncompressed (raw) DICOM files, * JPEG DICOM files, and