Difference between revisions of "2012 Project Week:DICOM"

From NAMIC Wiki
Jump to: navigation, search
 
(8 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 
<gallery>
 
<gallery>
−
Image:PW-SLC2011.png|[[2011_Winter_Project_Week#Projects|Projects List]]
+
Image:PW-SLC2012.png|[[2012_Winter_Project_Week#Projects|Projects List]]
 
Image:Slicer4-DICOM-2011-12-05.png|Slicer4 DICOM current state
 
Image:Slicer4-DICOM-2011-12-05.png|Slicer4 DICOM current state
 
</gallery>
 
</gallery>
Line 9: Line 9:
 
* Isomics: Steve Pieper
 
* Isomics: Steve Pieper
 
* Queen's: Andras Lasso
 
* Queen's: Andras Lasso
 +
* WUSTL: Misha Milchenko
  
  
Line 25: Line 26:
 
* Consider how DWI and DICOMRT should integrate with DICOM module
 
* Consider how DWI and DICOMRT should integrate with DICOM module
 
* Review the Slicer Data Bundle (lollipop)
 
* Review the Slicer Data Bundle (lollipop)
 +
* DICOM RT
 +
* DICOM SR
 +
* Consider how 4D data should integrate ?
 +
* In general, modules should be able to access all DICOM fields of a loaded image
 +
* Introduce DICOM import plugin modules? (modules that are notified when the user selects a DICOM file for loading and can extract various objects: images, models, etc.)
 +
* Consider how DICOM module mechanisms could be used by the CLI modules for accessing/parsing DICOM studies?
 
</div>
 
</div>
  
Line 30: Line 37:
  
 
<h3>Progress</h3>
 
<h3>Progress</h3>
−
 
+
* Significant discussion as part of DICOM and DICOM RT breakout sessions
 +
* General agreement with overall goals for networking
 +
* Specific feedback collected on interface
 +
** Need better display Patient/Study browser (ctkDICOMModel)
 +
** Need to improve SQL schema (ctkDICOMDatabase)
 +
* New infrastructure
 +
** DICOM Module needs hooks for loading specific DICOM types
 +
*** DICOM RT
 +
*** DWI DICOM
 +
*** (perhaps) DICOM SR
 +
** Need to have software process for contributing enhancements upstream to CTK and DCMTK
  
  
Line 43: Line 60:
  
 
==References==
 
==References==
−
 
+
* Networking and Qt
−
 
+
** http://www.commontk.org
 +
* Utilities
 +
* http://dicom.offis.de
 +
* http://code.google.com/p/pydicom/
 +
* RT
 +
** http://support.dcmtk.org/wiki/dcmrt/start
 +
** http://plastimatch.org/
 +
* Surfaces and segmentations:
 +
** http://qibawiki.rsna.org/index.php?title=Segmentation_and_Markup_Formats
 +
** ftp://medical.nema.org/medical/dicom/final/sup132_ft.pdf
 +
** ftp://medical.nema.org/medical/dicom/final/sup111_ft.pdf
 
</div>
 
</div>

Latest revision as of 21:15, 12 January 2012

Home < 2012 Project Week:DICOM

Key Investigators

  • BWH: Andrey Fedorov
  • Isomics: Steve Pieper
  • Queen's: Andras Lasso
  • WUSTL: Misha Milchenko


Objective

Discuss and test DICOM current state and use cases in slicer4

Approach, Plan

  • Test DICOM networking with sample servers.
  • Review layout of the widget.
  • Consider how DWI and DICOMRT should integrate with DICOM module
  • Review the Slicer Data Bundle (lollipop)
  • DICOM RT
  • DICOM SR
  • Consider how 4D data should integrate ?
  • In general, modules should be able to access all DICOM fields of a loaded image
  • Introduce DICOM import plugin modules? (modules that are notified when the user selects a DICOM file for loading and can extract various objects: images, models, etc.)
  • Consider how DICOM module mechanisms could be used by the CLI modules for accessing/parsing DICOM studies?

Progress

  • Significant discussion as part of DICOM and DICOM RT breakout sessions
  • General agreement with overall goals for networking
  • Specific feedback collected on interface
    • Need better display Patient/Study browser (ctkDICOMModel)
    • Need to improve SQL schema (ctkDICOMDatabase)
  • New infrastructure
    • DICOM Module needs hooks for loading specific DICOM types
      • DICOM RT
      • DWI DICOM
      • (perhaps) DICOM SR
    • Need to have software process for contributing enhancements upstream to CTK and DCMTK


Retrieved from "https://www.na-mic.org/w/index.php?title=2012_Project_Week:DICOM&oldid=73408"