For the stable Slicer documentation, visit the 4.10 page.
Introduction and Acknowledgements
- A new DICOM infrastructure was put in place beginning with Slicer 4.0.
- DICOM data is stored in a local data base, which is based on SQLite.
- DICOM data can be imported from disk into this data base.
- DICOM data can be created from the scene contents and exported to DICOM files.
- DICOM data can be retrieved from a PACS system after proper configuration of Slicer.
- DICOM data can be loaded into Slicer from the local database. A graphical user interface with display of thumbnails is available for data selection.
- Plans for the near future include support for storing data from slicer into the data base and uploading data from the data base into a PACS system.
This module is used for DICOM import and export.
DICOM is a widely used and sophisticated set of standards for digital radiology (see the References section for more information). Slicer provides support for a subset of DICOM functionality, with the particular features driven by the needs of clinical research.
To organize the data and avoid redundant calculations, Slicer keeps a DICOM Database of information about the DICOM data. You can have multiple databases on your computer at a time, and switch between them if, for example, they include data from different research projects. Each database is simply a directory on your local disk that has a few SQLite files and subdirectories to store image data. Don't manually modify the contents of these directories. DICOM data can enter the database either through manual import or via a DICOM network transfer. Modules may also populate the DICOM database with the results of computation.
By right clicking on a Patient, Study, or Series, you can delete the entry from the DICOM database. Note that to avoid accidental data loss, Slicer does not delete the corresponding image data files.
By selecting a Study and right clicking to get a context menu, you can choose to Export data from Slicer into DICOM. The metadata from the select study will be automatically filled in to the Export dialog and you can select a Slicer volume to export. Note that you should exercise extreme caution when working with these files in clinical situations, since non-standard or incorrect DICOM files can interfere with clinical operations. You can also choose to encapsulate the current MRML scene (via an MRB file) inside a DICOM dataset, which will be treated as a DICOM Secondary Capture document (note that the export feature has not been widely tested and should be considered experimental).
DICOM Data on the File System
The basic steps are as follows:
- Click the Import button in the DICOM Browser
- Select the folder which contains the data
- Optionally select the Copy option so that the files are copied into the database directory. Otherwise they will only be referenced in their original locaion.
Note that the DICOM standard does not specify how files will be organized on disk, so if you have DICOM data from a CDROM or otherwise transferred from a scanner, you cannot in general tell anything about the contents from the file or directory names. However once the data is imported to the database, it will be organized according the the DICOM standard Patient/Study/Series hierarchy.
Data in the scene
Data in the scene can be exported to the DICOM database:
- Select data to be exported in Subject Hierarchy module or initiate export from DICOM browser
- Edit tags for exportables
- Exported files are added to the DICOM database
DICOM is also a network communication standard. Slicer supports a DICOM Listener, DICOM Query/Retrieve interface, and a DICOM Send option. Note that in order to use these features, you must coordinate with the operators of the other DICOM nodes with which you wish to communicate. For example, you must work out agreement on such topics as network ports and application entity titles (AE Titles). Be aware that not all equipment supports all networking options, so configuration may be challenging and is often difficult to troubleshoot.
Port 104 is the standard DICOM port. All ports below 1024 require root access on unix-like systems (Linux and Mac). So you can run Slicer with the sudo command to be able to open the port for the DICOM Listener. Or you can use a different port, like 11112. You need to configure that on both sides of the connection. You can only have one process at a time listening on a port so if you have a listener running the second one won't start up. Also if something adverse happens (a crash) the port may be kept open an you need to either kill the storescp helper process (or just reboot the computer) to free the port. Consult the Error Log for diagnostic information.
DICOM Loading/Saving and Plugins
A main function of the DICOM module is to map from acquisition data organization into volume representation. That is, DICOM files typically describe attributes of the image capture, like the sequence of locations of the table during CT acquisition, while Slicer operates on image volumes of regularly spaced pixels. If, for example, the speed of the table motion is not consistent during an acquisition (which can be the case for some contrast 'bolus chasing' scans, Slicer's DICOM module will warn the user that the acquisition geometry is not consistent and the user should use caution when interpreting analysis results such as measurements.
From a developer perspective, the DICOM module exposes a plug-in architecture that allows acquisition-specific and modality-specific interpretation of DICOM data. From a user perspective this means that often Slicer will be able to suggest multiple ways of interpreting the data (such as reading DICOM files as a Diffusion dataset or as a scalar volume. When it is computable by examining the files, the DICOM module will select the most likely interpretation option by default. As of this release, standard plugins include scalar volumes and diffusion volumes, while extensions are available for segmentation objects, RT data, and PET/CT data. More plugins are expected for future versions. It is a long-term objective to be able to represent most, if not all, of Slicer's data in the corresponding DICOM data objects as the standard evolves to support them.
- See the RSNA 2012 Training on Visualization for description and sample data (Direct link to slides as pdf).
- This screen capture animation shows how to import and load DICOM data (also includes inspection of the file contents, which is an optional step).
Referring to the "DICOM in use" image in the top left of this page, the most important controls for day-to-day use are highlighted with gray callouts. The are described here in the order you are likely to use them.
- LocalDatabase (appears when >> button next to the menu bar is clicked): allows you to select a location on disk for Slicer's database of DICOM files. The application manages content of this folder (stores metadata and copy of imported DICOM files): do not manually copy any data into this folder.
- Import all DICOM files in the selected folder (including subfolders) will be parsed and basic information from file headers will be stored in Slicer's DICOM database. If enabled, then Slicer will make a copy of the imported files into the database folder.
- Patient list shows patients in the database. Studies available for the selected patient(s) are listed in study list. Multiple patients can be selected.
- Study list: shows studies for the currently selected patient(s). Multiple studies can be selected.
- Series list shows list of series (images, structure sets, segmentations, registration objects, etc.) available for selected studies.
- Search boxes Each patient/study/series can be filtered by typing in these fields.
- Examine button Runs each of the DICOM Plugins on the currently selected series and offers the result in the Load Options table.
- Plugin options (appears when Advanced checkbox is checked): you can choose which plugins will be allowed to examine the selected series for loading.
- Loadables list displays all possible interpretations of the selected series by the selected plugins. The plugin that most likely interprets the series correctly, is selected by default. You can override the defaults if you want to load the data in a different way. There will not always be a one-to-one mapping of selected series to list of loadable items.
- Load click this to load currently selected loadables into slicer.
- Metadata click this button to see metadata stored in file headers of selected series.
How to export data from the Slicer scene to DICOM files
- Open Data module, go to Subject Hierarchy tab (it is the tab shown by default)
- Make sure the data nodes that you want to export are in a DICOM-compliant hierarchy: parent of the data node is a Study, parent of the study is a Subject. To create a hierarchy, right-click in an empty area of the tree, select "Create new subject", then right-click on the newly created subject and select "Create child study", then drag-and-drop your data nodes under this study.
- Right-click on the data node to be exported and click "Export to DICOM..." to display DICOM export window (you can also show it by clicking "Export" button in the toolbar of DICOM browser module)
- Choose Output folder: By default, files are written into the folder where Slicer DICOM database is located.
- Click Export button: Export may take a few minutes. In case of error, the message is displayed in red on the left side of the dialog in the line of the "Save tags on export" checkbox.
This workflow is also explained in a 2-minute video tutorial
- DICOM export window can be also opened from the DICOM browser, by clicking "Export" button in the toolbar
- Export mode:
- Export series: export one or more selected series, to be viewed on a standard DICOM-compliant viewer
- Export entire scene: save the entire Slicer scene into a DICOM secondary capture file; the content can be stored on a DICOM archival system but can only be edited in Slicer
- Export type: Once the user selected a node, the DICOM plugins generate exportables for the series they can export. The list of the results appear in this section, grouped by plugin. The confidence number will be the average of the confidence numbers for the individual series for that plugin.
- Editing DICOM tags:
- DICOM tag editor consists of a list of tables. Tables for the common tags for the patient and study on the top, and the tags for the individual series below them (see image about tag editor below)
- "Tags" in the displayed table are not written directly to DICOM tags, they are just used by the DICOM plugins to fill DICOM tags in the exported files. This allows much more flexibility and DICOM plugins can auto-populate some information and plugins can expose other export options in this list (e.g. compression, naming convention).
- Save tags to scene: Checkbox to allow saving the tags back to the MRML nodes as attributes.
- Import exported data: if checked, the exported files are added to Slicer's DICOM database.
- The Edit->Preferences->DICOM page can be used to select options
- Load referenced series will give you the option of easily loading, for example, the master volume of a segmentation when you open the segmentation. This can also be made to happen automatically.
- Scalar Volume
- You can choose what back-end library to use (currently GDCM, DCMTK, or GDCM with DCMTK fallback with the last option being the default. This is provided in case some data is unsupported by one library or the other.
- Acquisition geometry regularization option supports the creation of a nonlinear transform that corrects for things like missing slices or gantry tilt in the acquisition
- Autoloading subseries by time is an option break up some 4D acquisitions into individual volume, but is optional since some volumes are also acquired in time unites and should not be split.
How to obtain DICOM metadata
- Open DICOM browser
- Select the data set that you want to load by clicking on a series (item in the listbox in the bottom)
- Click Metadata button
- Click Copy Metadata button
- Paste the copied text to any text editor
- Remove patient name, birthdate, ID, and all other patient identifiable information
- Copy-paste remaining text to Slicer forum post or email
- Loading Data Can read scalar volume DICOM data, bypassing the database.
- Reporting Extension reads and writes DICOM Segmentation Objects (label maps).
- SlicerRT reads and write DICOM Radiation Therapy Objects and provides tools for processing them.
- LongitudinalPETCT reads all PET/CT studies for a selected patient and provides tools for tracking metabolic activity detected by PET tracers.
- See the Slicer DICOM FAQ
- The DICOM Homepage: http://dicom.nema.org/
- DICOM on wikipedia: http://en.wikipedia.org/wiki/DICOM
- Clean and simple DICOM tag browser: http://dicom.innolitics.com
- A useful tag lookup site: http://dicomlookup.com/
- A hyperlinked version of the standard: http://dabsoft.ch/dicom/
- A handy book about DICOM: http://www.amazon.com/Digital-Imaging-Communications-Medicine-DICOM/dp/3642108490/ref=dp_ob_title_bk
Information for Developers
The overall DICOM Implementation in 3D Slicer consists of two main bodies of code embedded within the application. CTK code is responsible for the implementation of the DICOM database and networking layer. The CTK code is implemented C++ and follows the Qt style. The DICOM Module exposes this functionality to slicer users, and provides hooks through which other module can register DICOM Plugins to handle the conversion of specific DICOM data objects into the corresponding MRML representation. Once the data is in slicer, it can be operated on via the standard slicer mechanisms.
Customize table columns in DICOM browser
Columns in the browser can be renamed, reordered, shown/hidden, etc. An example snippet to customize the browser can be found in the script repository
The changes made like this are written into the database (ColumnDisplayProperties table), so the column customizations can be done only once per database.
Customize DICOM browser table content
The way the raw DICOM tags are represented in the fields of the DICOM tables is determined by the displayed field generator rules. These rules are subclasses of the ctkDICOMDisplayedFieldGeneratorAbstractRule class, and need to be registered to the displayed field generator in order to take part of the generation.
The fields are updated when 1) files are added to the database or 2) the database schema is updated (happens when opening an older database with a newer Slicer). In the current version only those files (i.e. instances) are processed for which the displayed fields have never been generated.
When updating the displayed fields, every rule defines the fields it is responsible for using the cached DICOM tags in the database. Tags can be requested to be cached in the rules from the getRequiredDICOMTags function. New field values are generated by the rules instance by instance. First, the getDisplayedFieldsForInstance function is called for each rule in which the custom values are generated from the raw tags, then the results are merged by calling mergeDisplayedFieldsForInstance for all the rules. Each field can requested to be merged with "expect same value", which uses the only non-empty value and throws a warning if conflicting values are encountered, or with "concatenate", which simply concatenates the displayed field values together.