2010 Winter Project Week MRI Guided Robotic Prostate Intervention
Key Investigators
- Andras Lasso (Queen's University)
- Junichi Tokuda (BWH)
Objective
We will continue to develop 3D Slicer's ProstateNav module for MRI-compatible devices for transrectal and transperineal prostate interventions. Based on our experiments in Fall 2009, we will improve the usability and stability of the module and prepare for clinical trials of transperineal device planned in Spring 2010.
Approach, Plan
A number of ProstateNav and Slicer problems and feature requests had been identified, that are important for using ProstateNav module in the OR. During the week the list of problems should be reviewed, analysed, then fixed or a fix should be planned.
Goals for the Project Week:
- Review list of ProstateNav and Slicer problems/enhancements, enter bug reports, discuss plan for fixing them
- Slice viewer can become unresponsive if calib markers are moved around a lot
- Fiducial marker, slice display manipulation is slow
- DICOM issues (slow loading of large sets of images; Philips multi-frame MR image loading)
- Display original image slices
- Get information about how to package the module using extension manager. This is particularly important once we bring 3D Slicer ORs and start clinical studies.
- Get information about possibilities for GUI testing
Progress
The current version of the module is already tested in a few phantom experiments. Further improvements are needed to make the module usable in clinical trials.
- Evaluated Slicer bugfix/feature request list and organized plans
- Problem reports entered into Mantis
- Incorrect window width/level for prostate volumes http://www.na-mic.org/Bug/view.php?id=716
- Add option to show slices in the orientation that they were acquired http://www.na-mic.org/Bug/view.php?id=726
- Allow the user to adjust window width/level by dragging the image http://www.na-mic.org/Bug/view.php?id=559
- Slice viewer becomes unresponsive after repeated moving of fiducials http://www.na-mic.org/Bug/view.php?id=728
- Additional problem reports entered into Mantis
- Incorrect coordinate values displayed in the status bar http://www.na-mic.org/Bug/view.php?id=756
- Slice positions are incorrect if "Rotate to volume plane" function is used http://www.na-mic.org/Bug/view.php?id=757
- Mouse wheel/arrow buttons don't always browse through the image slices http://www.na-mic.org/Bug/view.php?id=758
- Long Fiducial lists slow the software down http://www.na-mic.org/Bug/view.php?id=702
- Measurement module crashes when used after a scene is loaded http://www.na-mic.org/Bug/view.php?id=759
- DICOM Files reviewed:
- Multiframe dicom images appear not to have spacing, position, and orientation parsed correctly in ITK http://www.na-mic.org/Bug/view.php?id=725
- Slicer GUI has bad performance on large DICOM directories with many series Loading images from DICOM directory with many frames is very slow http://www.na-mic.org/Bug/view.php?id=727
- New features for sorting DICOM files to subdirectories will help and have general utility.
- Problem reports entered into Mantis
- Several minor fixes and enhancements were done in the ProstateNav module
- Defined a strategy for managing extensions for selected stable Slicer versions, for OR use (create a separate Slicer branch and merge stable trunk versions when needed)
- Partially completed support for a new biopsy device (transperineal template)
References
- Lasso, A., J. Tokuda, S. Vikal, C. M. Tempany, N. Hata, and G. Fichtinger, "A generic computer assisted intervention plug-in module for 3D Slicer with multiple device support", Medical Image Computing and Computer-Assisted Intervention (MICCAI), London, UK, 2009
- Tokuda, J., G. Fischer, C. Csoma, S. DiMaio, D. Gobbi, G. Fichtinger, C. Tempany, and N. Hata, "Software strategy for robotic transperineal prostate therapy in closed-bore MRI", Medical image computing and computer-assisted intervention (MICCAI), vol. 11, no. Pt 2: Department of Radiology, Brigham, Women's Hospital, Harvard Medical School, 75 Francis St , Boston, MA 02115, USA tokuda@bwh harvard edu, pp. 701-709, 2008.
Notes
TCON Dec 7, 2009, 16:00-16:50
- Recent feedbacks
- Transrectal device
- Phantom study with new software to determine if it is feasible for clinical studies
- Numerical results are the same as old software
- Advantage of 3D Slicer over the previous software: felxibility of 3D display where the needle, target, etc are.
- Issues: image quality for fiducial detection. The sequence has been optimized for Philips scanner at NIH, but not for Siemens at JHH. Currently the accuracy of registration is 1.5mm at NIH, while it is 2.5mm at JHH.
- 3D Slicer's performance issue: fiducial, slice view (zooming), DICOM compatibility (Slicer crashes when it loads DICOM data from the scanner... but the data might have some errors in location field.)
- Transperineal device
- Repeatability was quite good; there was systematic errors
- Registration accuracy should be improved; currently the registration is based on a single-slice image; it could possible to improve the accuracy by increasing the number of slices used for the registration.
- DICOM transfer was not practical. Currently we use DICOM listener at the lab. During the experiment, we logged in the laboratory network from the scanner room remotely, transfer images from the scanner to the listener using DICOM transfer, copy DICOM images from the laboratory network to the local machine, which ran 3D Slicer, and then finally loaded them.
- Transrectal device
- Potential goals for the Winter Project Week
- Improved Z-frame tracking (multi-slice registration)
- Prepare for the clinical application (biopsy)
- Improved GUI -- Andras has created more specific lists. We will track them using tracking system at Queen's.
- Packaging using extension manager. This is particularly important once we bring 3D Slicer ORs and start clinical studies.
- Secondary monitor based on the multiple camera support, recently implemented in 3D Slicer.
- Features for needle biopsy/brachytherapy based on template
- Tina suggested to integrate prostate integration with ProstateNav Module: this should be independent, because the segmentation module can be used alone.