ITK/Release 4/DICOM/Meeting 2011.09.01 Roadmap: Difference between revisions

From KitwarePublic
< ITK‎ | Release 4‎ | DICOM
Jump to navigationJump to search
No edit summary
Line 23: Line 23:
** SQL database
** SQL database
** Future work - might not happen
** Future work - might not happen
* Implementation
** Code will be in a layer/repo that augements DCMTK ("DCMTK::PACSModule")
** Code will be shared by CTK and ITK::DCMTKModule
** http://support.dcmtk.org/wiki/dcmtk/howto/dcmscu-example
* Slicer
** Will use cmd line methods from DCMTK for now (RSNA Release)
** Will use DCMTK::PACSModule and ITK::DCMTKModule when they are ready
* Testing
* Testing
** DCM4CHEE as main test
** DCM4CHEE as main test

Revision as of 16:02, 1 September 2011

Agenda

  1. Review roadmap


Attendees

  • Alex, Steve, Stephen, and William

Notes

  • DCMTK Module
    • Modularization of ITK has been helpful
    • DCMTK was forked by CTK, but now uses direct DCMTK repo
    • Need to patch DCMTK to expose build settings
    • Need to fix findpackage commands
      • Need a UseDCMTK.cmake file
  • Need ITK ImageFile reader/writer based on DCMTK
    • Focus of Dan's team
  • Consistent population of MetaData Dictionary between DCMTK and GDCM
    • Work in progress
  • Need way of storing header info from DICOM objects in memory and on disk in an established way
    • SQL database
    • Future work - might not happen
  • Implementation
  • Slicer
    • Will use cmd line methods from DCMTK for now (RSNA Release)
    • Will use DCMTK::PACSModule and ITK::DCMTKModule when they are ready
  • Testing
    • DCM4CHEE as main test
    • dicom.co.uk as an alternative test
    • Safe sequence of clinical PACS testing - as a "am I compatible with ITK DICOM" executable
  • Funding
    • Alex
      • 1 FTE for 2 weeks
    • Dan/William/Mayo
      • Underspent