Documentation/4.2/Modules/DICOM - Revision history

UpdateBot: Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

2013-06-14T07:38:02Z

Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

Pieper at 19:58, 26 December 2012

2012-12-26T19:58:23Z

Pieper: /* Useful links */

2012-12-26T19:51:11Z

Useful links

Pieper: /* DICOM Loading and Plugins */

2012-12-14T17:15:30Z

DICOM Loading and Plugins

Pieper at 17:14, 14 December 2012

2012-12-14T17:14:33Z

Pieper: /* DICOM Loading and Plugins */

2012-12-14T17:12:19Z

DICOM Loading and Plugins

Pieper at 17:11, 14 December 2012

2012-12-14T17:11:47Z

Pieper: /* DICOM Loading and Plugins */

2012-11-07T19:59:33Z

DICOM Loading and Plugins

Pieper at 19:47, 7 November 2012

2012-11-07T19:47:52Z

Pieper: /* DICOM Loading and Plugins */

2012-11-07T19:26:03Z

DICOM Loading and Plugins

← Older revision		Revision as of 07:38, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	<!-- ---------------------------- -->		<!-- ---------------------------- -->
	{{documentation/{{documentation/version}}/module-header}}		{{documentation/{{documentation/version}}/module-header}}

@@ Line 115: / Line 115: @@
 {{documentation/{{documentation/version}}/module-section|Information for Developers}}
 <!-- ---------------------------- -->
 {{documentation/{{documentation/version}}/module-footer}}
 <!-- ---------------------------- -->

← Older revision		Revision as of 19:51, 26 December 2012
Line 114:		Line 114:
	<!-- ---------------------------- -->		<!-- ---------------------------- -->
	{{documentation/{{documentation/version}}/module-section\|Information for Developers}}		{{documentation/{{documentation/version}}/module-section\|Information for Developers}}
		+
		+	[[Image:DICOM-architecture.png]]

@@ Line 85: / Line 85: @@
 <!-- Tutorials ---------------------------- -->
 {{documentation/{{documentation/version}}/module-section|Tutorials}}
 * See [http://www.na-mic.org/Wiki/index.php/RSNA_2012#3D_Interactive_Visualization_of_DICOM_images the RSNA 2012 Training on Visualization] for description and sample data (Direct link to [http://www.na-mic.org/Wiki/images/6/66/3DVisualizationDICOM_RadiologyApplications_SoniaPujol_RSNA2012.pdf slides as pdf]).

@@ Line 86: / Line 86: @@
 {{documentation/{{documentation/version}}/module-section|Tutorials}}
 Links to tutorials that use this module (not yet available)
-* See [http://www.na-mic.org/Wiki/index.php/RSNA_2012#3D_Interactive_Visualization_of_DICOM_images the RSNA 2012 Training on Visualization] ([http://www.na-mic.org/Wiki/images/6/66/3DVisualizationDICOM_RadiologyApplications_SoniaPujol_RSNA2012.pdf] pdf).
+* See [http://www.na-mic.org/Wiki/index.php/RSNA_2012#3D_Interactive_Visualization_of_DICOM_images the RSNA 2012 Training on Visualization] for description and sample data (Direct link to [http://www.na-mic.org/Wiki/images/6/66/3DVisualizationDICOM_RadiologyApplications_SoniaPujol_RSNA2012.pdf slides as pdf]).

@@ Line 95: / Line 95: @@
 <!-- Similar modules ---------------------------- -->
 {{documentation/{{documentation/version}}/module-section|Similar modules}}
-[[Documentation/{{documentation/version}}/SlicerApplication/LoadingData|Loading Data]]
+* [[Documentation/{{documentation/version}}/SlicerApplication/LoadingData|Loading Data]] Can read scalar volume DICOM data, bypassing the database.
 <!-- References ---------------------------- -->

@@ Line 49: / Line 49: @@
 DICOM is a widely used and sophisticated set of standards for digital radiology (see the [[#References|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.
-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 [[Documentation/{{documentation/version}}#Diffusion|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.
+=DICOM Organization=
-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 [http://sqlite.org/ SQLite] files and subdirectories to store image data.  Don't manually modify the contents of these directories.
+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=
-*Click on import
 *Select the folder which contains the data
 =DICOM Networking=
 == Connection Ports ==
 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 [[documentation/{{documentation/version}}/SlicerApplication/ErrorLog|Error Log]] for diagnostic information.
 =DICOM Loading and Plugins=
 <!-- Tutorials ---------------------------- -->

@@ Line 89: / Line 89: @@
 {{documentation/{{documentation/version}}/module-section|References}}
 See the [http://commontk.org CTK web site] for more information on the internals of the DICOM implementation.  This tool uses the [http://dicom.offis.de DCMTK DICOM library].
 <!-- ---------------------------- -->