概念
DICOM identifiers
Very importantly, the DICOM standard specifies DICOM tags that allow to index each single DICOM resource:
- Patients are indexed with
PatientID (0x0010, 0x0020)
(part of the patient module). - Studies are indexed with
StudyInstanceUID (0x0020, 0x000d)
(part of the study module). - Series are indexed with
SeriesInstanceUID (0x0020, 0x000e)
(part of the series module). - Instances are indexed with
SOPInstanceUID (0x0008, 0x0018)
(part of the SOP module).
The DICOM standard orders StudyInstanceUID, SeriesInstanceUID and SOPInstanceUID to be globally unique. In other words, it is mandatory for two different imaging devices to never generate the same identifiers, even if they are manufactured by different vendors. Orthanc exploits this rule to derive its own unique identifiers.
Importantly, even if the PatientID must be unique inside a given hospital, it is not guaranteed to be globally unique. This means that different patients imaged in different hospitals might share the same PatientID. For this reason, you should always browse from the study level (and not from the patient level) as soon as you deal with an application that handles patients from different hospitals.
Configuration of Orthanc
Configuring Orthanc simply consists in copying and adapting the default configuration file. This file is in the JSON file format. You can generate a sample configuration file with the following call:
$ Orthanc --config=Configuration.json
Then, start Orthanc by giving it the path to the modified Configuration.json path as a command-line argument:
$ Orthanc ./Configuration.json
The default configuration file would: