Difference between revisions of "2012 Summer Project Week:LeanSlicer"

From NAMIC Wiki
Jump to: navigation, search
Line 41: Line 41:
 
==Delivery Mechanism==
 
==Delivery Mechanism==
  
This work will be delivered to the NA-MIC Kit as modifications in the Slicer main repository.
+
Summary of discussions and planned next steps will be posted on this page.
  
 
==References==
 
==References==
 
* [[Leadership:SlicerIGT_2007]]
 
* [[Leadership:SlicerIGT_2007]]
 
* [[AHM_2007:Slicer3_Developer_Feedback]]
 
* [[AHM_2007:Slicer3_Developer_Feedback]]
 +
* http://www.osirix-viewer.com/AboutOsiriX.html (same libs as Slicer)
 +
* http://www.mcim.georgetown.edu/MCIM2007/Uploads/Presentations/FDA%20Perspective%20on%20Open%20Source%20Software.pdf
 +
* http://www.economist.com/node/21556098
 +
* http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2039836/

Revision as of 13:09, 17 June 2012

Home < 2012 Summer Project Week:LeanSlicer

Key Investigators

  • Queen's: Andras Lasso
  • Robarts: Chris Wedlake
  • Harvard SPL: Ron Kikinis
  • Kitware: Stephen Aylward
  • Isomics: Steve Pieper
  • Other Slicer core developers?
  • Taylor Braun-Jones?

Objective

Build a stripped down version of Slicer containing core functionalities only. To be used for image-guided therapy in the OR. Need to be stable enough for OR use and feasible to apply for Health Canada / FDA approval.

Approach, Plan

Discuss past experiences in obtaining approval for clinical use of Slicer.

Analyze all the dependencies of Slicer, see which of them are really needed. Try to remove those that are not essential.

Develop a use-case scenario. It would be important to have an easy way to toggle between FDA compliant and standard mode, including customizations and plug-ins.

Progress

Delivery Mechanism

Summary of discussions and planned next steps will be posted on this page.

References