Mercurial > hg > orthanc-book
diff Sphinx/source/faq/features.rst @ 661:36bf58dfb7f7
added core metadata
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Thu, 29 Apr 2021 12:50:01 +0200 |
parents | a6e371768a70 |
children | 8bda16db46cf |
line wrap: on
line diff
--- a/Sphinx/source/faq/features.rst Thu Apr 29 12:41:31 2021 +0200 +++ b/Sphinx/source/faq/features.rst Thu Apr 29 12:50:01 2021 +0200 @@ -121,8 +121,8 @@ Orthanc. Similarly, ``LastUpdate`` records, for each patient/study/series, the last time a DICOM instance was added to this resource. -* ``RemoteAet`` records the AET of the modality that has sent some - DICOM instance to Orthanc. +* ``RemoteAET`` records the AET of the modality that has sent some + DICOM instance to Orthanc using the DICOM protocol. * ``ModifiedFrom`` and ``AnonymizedFrom`` hold from which original resource, a resource was modified or anonymized. The presence of this metadata indicates that the resource is the result of a @@ -133,11 +133,21 @@ * ``IndexInSeries`` records the expected index of a DICOM instance inside its parent series. Conversely, ``ExpectedNumberOfInstances`` associates to each series, the number of DICOM instances this series - is expected to contain. + is expected to contain. This information is :ref:`not always + available <series-completion>`. * Starting with Orthanc 1.2.0, ``TransferSyntax`` and ``SopClassUid`` respectively stores the transfer syntax UID and the SOP class UID of DICOM instances, in order to speed up the access to this information. +* ``RemoteIP`` (new in Orthanc 1.4.0): The IP address of the remote + SCU (for REST API and DICOM protocol). +* ``CalledAET`` (new in Orthanc 1.4.0): The AET that was called by the + SCU, which normally matches the AET of Orthanc (for DICOM protocol). +* ``HttpUsername`` (new in Orthanc 1.4.0): The username that created + the instance (for REST API). +* ``PixelDataOffset`` (new in Orthanc 1.9.1): Offset (in bytes) of the + Pixel Data DICOM tag in the DICOM file, if available. + Metadata listed above are set privately by the Orthanc core. They are **read-only** from the perspective of the end user, as Orthanc