# HG changeset patch # User Sebastien Jodogne # Date 1619619393 -7200 # Node ID 55a93745e87444b44ab484e2bd2a713d9fa90d13 # Parent 35dde917804abd5007c4565feee62c0b4861e9b2 use little endian explicit instead of implicit diff -r 35dde917804a -r 55a93745e874 Sphinx/source/faq/troubleshooting.rst --- a/Sphinx/source/faq/troubleshooting.rst Wed Apr 28 16:04:55 2021 +0200 +++ b/Sphinx/source/faq/troubleshooting.rst Wed Apr 28 16:16:33 2021 +0200 @@ -48,6 +48,17 @@ The core team of Orthanc will **only provide support for DICOM files that are reported as valid** by ``dciodvfy``. +* Side-note: The default transfer syntax of DICOM is Little Endian + Implicit (``1.2.840.10008.1.2``). For DICOM files that include + private tags, **we recommend using Little Endian Explicit** + (``1.2.840.10008.1.2.1``) instead Little Endian Implicit whenever + possible. Instead, in Little Endian Explicit, each DICOM tag has an + explicit declaration of its value representation (type), which + contrasts with Little Endian Implicit that necessitates to configure + the dictionary of private tags to be properly handled in some + operations (cf. the ``Dictionary`` :ref:`configuration option + `). + Orthanc Explorer ---------------- @@ -133,13 +144,13 @@ Orthanc stores, in its database, an `MD5 hash `_ of the files stored in its -:ref:`storage area ` (that notably contains the DICOM -files), provided that the ``StoreMD5ForAttachments`` configuration -option is set to ``true``. +:ref:`storage area ` (which notably includes the +DICOM files), provided that the ``StoreMD5ForAttachments`` +configuration option is set to ``true``. -This MD5 corresponds to the hash of the stored files in memory, before -they are written to the disk by Orthanc. This information is safely -stored inside the database for any incoming file attachment. +This MD5 corresponds to the hash of the files in memory, before they +are written to the disk by Orthanc. This information is safely stored +inside the database for any incoming file attachment. It is possible to ask Orthanc to check by itself whether some attachment file was corrupted (i.e. to check whether the MD5 hash stored in the