Slicer3:BrainLabModule
Contents
Aim
BrainLab (http://www.brainlab.com) has recently introduced a customized client/server architecture called VectorVision Link (VV Link) to communicate with external IGT environment. This software API, open but not free, allows other programs to acquire tracking information and images from the BrainLab system. We propose to create a comprehensive workflow to interface 3D Slicer to BrainLab system and to use it for research. Specifically, we create simplified steps for neurosurgeons to use Slicer to perform some research in DTI visualization in OR while BrainLab is used as the primary navigation tool. Here is the scenario:
BrainLab system will still run as usual; we won't install any software and hardware on the BrainLab computer and won't affect its FDA status either. Slicer runs on a different computer. These two computers will be connected to each other using a network or router. During surgical procedures, the BrainLab sends real-time tracking data and/or images to Slicer. The tracking information may be used to seed dynamic DTI visualization in Slicer.
Research Plan
To easily handle the integration between BrainLab and 3D Slicer, we propose the following workflow:
- Set up connection between BrainLab and Slicer
- Load a scene (default or user specific) into Slicer
- Navigate with DTI visualization in Slicer as surgeon performs tracking with BrainLab
We will implement the workflow by developing a Slicer module called BrainLabModule. This interactive module uses OpenIGTLink (http://www.na-mic.org/Wiki/index.php/OpenIGTLink) for data communication between BrainLab and Slicer, and uses Fiducial, DTMRI and FiducialSeeding modules for DTI visualization. Also, it uses existing Slicer functions to load MRML scenes.
The development of BrainLabModule will be completed in two phases. In the first phase, a BrainLab simulator will be created. That is, a sequence of synthetic tracking points (not from BrainLab system) will be streamed to Slicer where fiducial-driven DTI visualization will be performed. In the second phase, a real BrainLab system will be needed to test the entire workflow. Upon completion, both modes (Simulator and BrainLab) will co-exist in the module; the user may choose which mode to execute.
Both modes are accompanied by training materials and documentation to ensure usability.
Design of Module
Key Personnel
Haiying Liu
Noby Hata
Ron Kikinnis
Progress
- 03/29/10
- Ron, Noby and Haiying met at Ron's office to discuss the specs of the module and time frame for implementation.
Dependency
The following modules are required for BrainLab module to work properly:
Fiducial
OpenIGTLink
DTMRI
FiducialSeeding