Difference between revisions of "Documentation/Nightly/Extensions/QuantitativeReporting"
m |
|||
Line 43: | Line 43: | ||
* 3-d segmentation (label map). | * 3-d segmentation (label map). | ||
The 3-d segmentations are stored as binary image masks, and are serialized into DICOM Segmentation Storage objects, which in turn can be referenced from the AIM XML document. | The 3-d segmentations are stored as binary image masks, and are serialized into DICOM Segmentation Storage objects, which in turn can be referenced from the AIM XML document. | ||
+ | | | ||
+ | [[Image:Reporting-Prostate.png|thumb|300px|]] | ||
|} | |} | ||
{{documentation/{{documentation/version}}/module-section|Release Notes}} | {{documentation/{{documentation/version}}/module-section|Release Notes}} | ||
− | '''Installation:''' Reporting module is available as an extension that can be installed using [[Documentation/{{documentation/version}}/SlicerApplication/ExtensionsManager|Slicer Extension Manager]]. Make sure Extension Manager is enabled in the Application settings (as shown [[Documentation/{{documentation/version}}/SlicerApplication/ExtensionsManager#Extensions_Manager_Settings|here]]). Follow the Extension Manager usage instructions to find and install Reporting extension. Once installed, you need to restart Slicer before you can use the Reporting module | + | '''Installation:''' Reporting module is available as an extension that can be installed using [[Documentation/{{documentation/version}}/SlicerApplication/ExtensionsManager|Slicer Extension Manager]]. Make sure Extension Manager is enabled in the Application settings (as shown [[Documentation/{{documentation/version}}/SlicerApplication/ExtensionsManager#Extensions_Manager_Settings|here]]). Follow the Extension Manager usage instructions to find and install Reporting extension. Once installed, you need to restart Slicer before you can use the Reporting module. |
'''Potential issues related to extensions and multiple versions of Slicer:''' Slicer settings are stored in a dedicated system-specific location. These settings are not reset when you install a new Slicer version. If you observe unstable behavior, you could try resetting the settings as follows: | '''Potential issues related to extensions and multiple versions of Slicer:''' Slicer settings are stored in a dedicated system-specific location. These settings are not reset when you install a new Slicer version. If you observe unstable behavior, you could try resetting the settings as follows: | ||
Line 53: | Line 55: | ||
* '''Windows''': settings are located in ''C:\Users\<your_user_name>\AppData\Roaming\NA-MIC'' folder -- remove it or move to a different location. | * '''Windows''': settings are located in ''C:\Users\<your_user_name>\AppData\Roaming\NA-MIC'' folder -- remove it or move to a different location. | ||
'''WARNING:''' the configuration file contains the path to your DICOM database. Once the configuration file is removed, you will need to re-configure the DICOM module to point it to the location of the database! | '''WARNING:''' the configuration file contains the path to your DICOM database. Once the configuration file is removed, you will need to re-configure the DICOM module to point it to the location of the database! | ||
+ | |||
+ | This limitation is also described on the [[Documentation/Nightly/SlicerApplication/Settings#Limitations| Limitations]] page. | ||
Please note that this module is under active development, and is being made available for the purposes of beta testing and feedback evaluation! The functionality, GUI and workflows may change in the subsequent releases of the module. | Please note that this module is under active development, and is being made available for the purposes of beta testing and feedback evaluation! The functionality, GUI and workflows may change in the subsequent releases of the module. | ||
Line 74: | Line 78: | ||
{| | {| | ||
| | | | ||
− | # | + | # A DICOM imaging study that will be annotated should be loaded into Slicer DICOM database using Slicer DICOM module. If you are unsure what this means, see [[Documentation/{{documentation/version}}/Modules/DICOM|documentation of the DICOM module]]. '''NOTE''': only volumes loaded from DICOM module can be used in this module! |
# In the Reporting module, new report should be created (see explanation of the module GUI panels below) (Input panel) | # In the Reporting module, new report should be created (see explanation of the module GUI panels below) (Input panel) | ||
# The volume that will be annotated should be selected (Input panel). Following this, the slice viewers will be initialized to show the volume being annotated. | # The volume that will be annotated should be selected (Input panel). Following this, the slice viewers will be initialized to show the volume being annotated. | ||
Line 82: | Line 86: | ||
# The tree view in the module Markup panel will be showing all markup elements that have been added to the active report. | # The tree view in the module Markup panel will be showing all markup elements that have been added to the active report. | ||
# To attach a 3-d segmentation to the report, the segmentation image should be either loaded from file and added to Slicer scene (see [[Documentation/{{documentation/version}}/Modules/Data|instructions on how to use Data module]]), or a new segmentation should be created using the "Segmentation volume" drop-down. Segmentation can then be edited using the Editor panel that is available in the Reporting GUI (see [[Documentation/{{documentation/version}}/Modules/Editor|Editor module]] documentation for using Editor tools). | # To attach a 3-d segmentation to the report, the segmentation image should be either loaded from file and added to Slicer scene (see [[Documentation/{{documentation/version}}/Modules/Data|instructions on how to use Data module]]), or a new segmentation should be created using the "Segmentation volume" drop-down. Segmentation can then be edited using the Editor panel that is available in the Reporting GUI (see [[Documentation/{{documentation/version}}/Modules/Editor|Editor module]] documentation for using Editor tools). | ||
− | # " | + | # "Export" functionality can be used to save the report into AIM XML format, and the segmentations (if exist) as DICOM Segmentation objects into the specified location. "Import" functionality can be used to load the report back into Slicer. |
| | | | ||
|[[Image:Slicer4-Reporting-markupToolbar.png|thumb|280px|Slicer toolbar buttons that should be used for placement of fiducial/ruler markups.]] | |[[Image:Slicer4-Reporting-markupToolbar.png|thumb|280px|Slicer toolbar buttons that should be used for placement of fiducial/ruler markups.]] | ||
Line 94: | Line 98: | ||
** '''Annotated volume''': volume being annotated | ** '''Annotated volume''': volume being annotated | ||
* ''Annotation'' panel | * ''Annotation'' panel | ||
− | ** contains the name of the structure being annotated and the colored patch showing the label color. Clicking the colored patch will bring up the selection of the supported named structures. Currently supported terminology is based on Slicer [[Slicer3:2010_GenericAnatomyColors|General Anatomy Colors lookup table]]. Integration of this table with | + | ** contains the name of the structure being annotated and the colored patch showing the label color. Clicking the colored patch will bring up the selection of the supported named structures. Currently supported terminology is based on Slicer [[Slicer3:2010_GenericAnatomyColors|General Anatomy Colors lookup table]]. Integration of this table with standardized lexicon is under development. |
* ''Markup'' panel | * ''Markup'' panel | ||
** contains the text listing the slice viewers that should be used for placing fiducial/ruler markups. | ** contains the text listing the slice viewers that should be used for placing fiducial/ruler markups. | ||
− | ** | + | ** Table view widget shows the markups that are associated with the report. The "eye" button toggles visibility of the markup element. Clicking the row with the markup aligns the slices with the location of the markup. |
* ''Segmentation'' panel | * ''Segmentation'' panel | ||
** ''Segmentation volume'' selector allows to choose the volume containing the segmentation, or to create a new segmentation. For an existing label map (segmentation) to be associated with the active report, the geometry of the image volume containing the segmentation should match the geometry of the annotated volume. New segmentation volume can be created to match the geometry of the active volume using the segmentation selector. | ** ''Segmentation volume'' selector allows to choose the volume containing the segmentation, or to create a new segmentation. For an existing label map (segmentation) to be associated with the active report, the geometry of the image volume containing the segmentation should match the geometry of the annotated volume. New segmentation volume can be created to match the geometry of the active volume using the segmentation selector. | ||
** Once the label volume is selected/created, it can be edited using the [[Documentation/{{documentation/version}}/Modules/Editor|Editor]] tools: these are available by expanding the "Edit Selected Label Map" panel (see figure on the right). | ** Once the label volume is selected/created, it can be edited using the [[Documentation/{{documentation/version}}/Modules/Editor|Editor]] tools: these are available by expanding the "Edit Selected Label Map" panel (see figure on the right). | ||
− | * '' | + | * ''Import/Export'' panel allow to export/import the report into AIM format. |
+ | |||
+ | DICOM Segmentation objects that are imported to the user-defined location on disk are also automatically inserted into the local DICOM database. They can be loaded back into Slicer as segmentation labels independently of the report using [Documentation/{{documentation/version}}/Modules/DICOM|DICOM module]]. | ||
+ | |||
| | | | ||
− | [[Image:Slicer4-Reporting.png|thumb|480px|Module GUI | + | [[Image:Slicer4-Reporting-4.2.png|thumb|480px|Module GUI]] |
− | |||
− | |||
[[Image:Slicer4-SegmentationSelector.png|thumb|280px|New label volume can be created using the "Segmentation volume" selector]] | [[Image:Slicer4-SegmentationSelector.png|thumb|280px|New label volume can be created using the "Segmentation volume" selector]] |
Revision as of 02:58, 4 November 2012
Home < Documentation < Nightly < Extensions < QuantitativeReporting WARNING: This module is Work in Progress, which means:
|
Introduction and Acknowledgements
Extension: Reporting | |||||||
|
Module Description
The purpose of the Reporting module is to provide Slicer interface for creating image annotations/markup that are stored in a structured form, and can be exported into Annotation Image Markup (AIM) XML-based format. Currently, Reporting module allows to create three types of markup:
The 3-d segmentations are stored as binary image masks, and are serialized into DICOM Segmentation Storage objects, which in turn can be referenced from the AIM XML document. |
Release Notes
Installation: Reporting module is available as an extension that can be installed using Slicer Extension Manager. Make sure Extension Manager is enabled in the Application settings (as shown here). Follow the Extension Manager usage instructions to find and install Reporting extension. Once installed, you need to restart Slicer before you can use the Reporting module.
Potential issues related to extensions and multiple versions of Slicer: Slicer settings are stored in a dedicated system-specific location. These settings are not reset when you install a new Slicer version. If you observe unstable behavior, you could try resetting the settings as follows:
- Linux and Mac: settings are stored in your home directory in .config folder (remove ~/.config or move it to a different location)
- Windows: settings are located in C:\Users\<your_user_name>\AppData\Roaming\NA-MIC folder -- remove it or move to a different location.
WARNING: the configuration file contains the path to your DICOM database. Once the configuration file is removed, you will need to re-configure the DICOM module to point it to the location of the database!
This limitation is also described on the Limitations page.
Please note that this module is under active development, and is being made available for the purposes of beta testing and feedback evaluation! The functionality, GUI and workflows may change in the subsequent releases of the module.
Use Cases
This module is designed for the use cases that require creation and/or exchange of self-containing documents describing a certain finding in a DICOM image, such as lesions and anatomical structures.
Tutorials
Not available at this time.
Panels and their use
Before you start using the module, you need to be familiar with 3D Slicer interface and main features. Please see instruction on using the main application GUI and various tutorials to learn about 3D Slicer.
Reporting module uses internal data structure called "report" to organize the markup/annotations and associate them with the image volume being annotated.
The steps to create a new report are the following:
|
GUI of the module contains the following elements:
DICOM Segmentation objects that are imported to the user-defined location on disk are also automatically inserted into the local DICOM database. They can be loaded back into Slicer as segmentation labels independently of the report using [Documentation/Nightly/Modules/DICOM|DICOM module]]. |
![]() Segmentation can be edited using Editor module tools provided in the "Edit selected label map" panel. |
Similar Modules
References
- Quantitative Imaging Network (QIN)
- Main page summarizing the scope and development of this functionality: http://wiki.na-mic.org/Wiki/index.php?title=AIM_Annotations_integration_with_3DSlicer
- Annotation Image Markup home page
Information for Developers
- Source code of the module: https://github.com/fedorov/Reporting
Section under construction. |