Difference between revisions of "2017 Winter Project Week/LiverResectionPlanning"

From NAMIC Wiki
Jump to: navigation, search
 
(One intermediate revision by the same user not shown)
Line 31: Line 31:
 
|
 
|
 
<!-- Progress and Next steps bullet points (fill out at the end of project week) -->
 
<!-- Progress and Next steps bullet points (fill out at the end of project week) -->
* Future work: Generalize to other types of resections (particularly pancreas)
+
* Using VTK field data to store / retrieve extra information for resection surfaces
* Generally interested in customizing Slicer, as in the future we may tailor slicer for this "pipeline"
+
* Structure in place for loading / saving resection surfaces (resectionSurfaceNodes inheriting from modelNode, reader, registering IO...)
 +
Fruitful discussions:
 +
* Learnt more about options for customizing Slicer
 +
* Plan to use SegmentationNode to solve issues with needing to load many models
 +
* Feedback on modules, should try to generalize the vessel segmentation to be usable on other images (not just contrast enhanced CT of the liver)
 
|}
 
|}
  

Latest revision as of 16:11, 13 January 2017

Home < 2017 Winter Project Week < LiverResectionPlanning

Key Investigators

  • Louise Oram, The intervention centre - Oslo University Hospital
  • Andrey Fedorov, BWH
  • Christian Herz, BWH
  • Andras Lasso, Queens

Project Description

Objective Approach and Plan Progress and Next Steps
  • To create an extension that allows surgeons to create 3D models and plan liver resection surgeries.
  • This extension will contain modules for segmenting parts of the liver (parenchyma, tumours, portal and hepatic veins), as well as a module for creating a resection plan in the resulting 3D model.
  • Possible need for special type of model node when importing / saving data? (have a vtkMRMLResectionSurfaceNode, which will contain a list of control points for the resection surface)
  • Refactoring current modules to improve code and fit into extensions structure
  • Using VTK field data to store / retrieve extra information for resection surfaces
  • Structure in place for loading / saving resection surfaces (resectionSurfaceNodes inheriting from modelNode, reader, registering IO...)

Fruitful discussions:

  • Learnt more about options for customizing Slicer
  • Plan to use SegmentationNode to solve issues with needing to load many models
  • Feedback on modules, should try to generalize the vessel segmentation to be usable on other images (not just contrast enhanced CT of the liver)

Background and References

http://normit.no/en/