Difference between revisions of "2012 Project Week:DICOM"

From NAMIC Wiki
Jump to: navigation, search
(Added two questions to be discussed to Approach, Plan section)
Line 30: Line 30:
 
* In general, modules should be able to access all DICOM fields of a loaded image
 
* 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.)  
 
* 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>
  

Revision as of 14:54, 29 December 2011

Home < 2012 Project Week:DICOM

Key Investigators

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


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