Difference between revisions of "2012 Project Week:DICOM"

Latest revision as of 21:15, 12 January 2012

Home < 2012 Project Week:DICOM

Discuss and test DICOM current state and use cases in slicer4

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?

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

This work will be delivered to the NA-MIC Kit as a core functionality of 3D Slicer v.4

@@ Line 9: / Line 9: @@
 * Isomics: Steve Pieper
 * Queen's: Andras Lasso
+* WUSTL: Misha Milchenko
@@ Line 36: / Line 37: @@
 <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