Mercurial > hg > orthanc-book

comparison Sphinx/source/dicom-guide.rst @ 609:0dde82745e0d

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
documentation of DICOM TLS
author Sebastien Jodogne <s.jodogne@gmail.com>
date Fri, 29 Jan 2021 14:35:55 +0100
parents eaa6cdfa7ba6
children cfeb018b9150
comparison
equal deleted inserted replaced
608:a6d27fe89650 609:0dde82745e0d
669 We conclude this brief overview of DICOM by insisting on the fact that 669 We conclude this brief overview of DICOM by insisting on the fact that
670 the **DICOM protocol inherently targets the Intranet** of a single 670 the **DICOM protocol inherently targets the Intranet** of a single
671 hospital, not the Internet or the cloud. This protocol might be 671 hospital, not the Internet or the cloud. This protocol might be
672 blocked by outbound firewalls, and there is no convention ensuring 672 blocked by outbound firewalls, and there is no convention ensuring
673 that the AETs are globally unique across all the 673 that the AETs are globally unique across all the
674 hospitals. Furthermore, even though the DICOM protocol supports TLS 674 hospitals. Furthermore, even though :ref:`Orthanc supports DICOM TLS
675 encryption, this feature is rarely enabled. 675 encryption <dicom-tls>`, this feature is rarely enabled within
676 hospitals.
676 677
677 Depending on your application, you might therefore want to leverage 678 Depending on your application, you might therefore want to leverage
678 the **HTTP protocol** in the context of DICOM. Such Web-based 679 the **HTTP protocol** in the context of DICOM. Such Web-based
679 protocols are probably more familiar to physicians/physicists/software 680 protocols are probably more familiar to physicians/physicists/software
680 engineers, are easier to work with, can be transparently encrypted 681 engineers, are easier to work with, can be transparently encrypted