1 / 9

Requirements Document Slicer3 Workflow Based Interface for NAV-RFA

Requirements Document Slicer3 Workflow Based Interface for NAV-RFA. Slicer will be configured with the following modules* : Data – manage scene graph. EM Segmenter – Potentially used for automatic segmentation (maybe not in the initial setup).

berne
Télécharger la présentation

Requirements Document Slicer3 Workflow Based Interface for NAV-RFA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirements DocumentSlicer3 Workflow Based Interface for NAV-RFA

  2. Slicer will be configured with the following modules*: • Data – manage scene graph. • EM Segmenter – Potentially used for automatic segmentation (maybe not in the initial setup). • Editor – Used for manual segmentation and modification of automated • segmentation. • Fiducials – Used for marking the fiducials. • Linear registration – for fiducial based registration. • OpenIGTLink – for tracking. • *It is not clear if NAV-RFA should be a Slicer module that uses other modules, or a configuration consisting of several existing modules and some that we needto add.

  3. STEP 1 User selects “FileAdd volume”. The user then selects a single slice from a DICOM series. Slicer will loads the series from the directory containing the selected file. NOTE: Slicer assumes that the directory contains a single series. Once the series is loaded it is displayed in the Slicer interface and the user will move to the editor module.

  4. STEP 2 User selects the fiducial module from the loaded modules. User manually marks all fiducials.

  5. STEP 3 User selects the Interactive editor module from the loaded modules. User manually marks tumor, entry region, and no pass zone. Once this is done the user selects a module that exports and runs the optimization program (next slide).

  6. Probe information [mm]: a: b: c: Sample spacing [mm]: x: y: z: Angular resolution [degress]: Maximal # of ablations: Maximal # of trajectories: Maximal # of punctures: STEP 4 User selects the export and run RFA planning module, with the following interface: NOTE: All data fields must be positive values. Probe is modeled as an ellipsoid (x^2/a^2 + y^2/b^2 + z^2/c^2 = 1). Module is initially just a stub, need to implement the code that actually does dilation of tumor and data export. Tumor margin [mm]: Button becomes active once all data fields have been filled correctly. When pressed the button will export the information to file and run the planning program, navRFAPlanner.exe. Export and run Planning

  7. STEP 5 User selects the load RFA plan module, with the following interface: Read a text file and create a set of MRML nodes describing probe trajectories and target points. Each trajectory and target are represented by a cylinder (probe entry to target point) and ellipsoid (based on probe sizes, step 4) at the target point. Load Plan

  8. STEP 6 User selects the OIGTLink module, and sets the digitizer tool ip port, then starts the IGSTK OpenIGTLink client and acquires the fiducial points and registers, linear registration module. Haying, does this need to be seperated into two steps (data acquisition, registration) or can this be done in one?

  9. 1 3 STEP 7 User selects the RFA navigation module. The user selects a trajectory and ablation target, these are updated in the display and the navigation is performed. Select trajectory Slider that selects the trajectory (cylinder) that is currently displayed. Select ablation Slider that selects the target (ellipsoid) that is currently displayed. Current guidance will use Slicer’s standard display, after we have a working version we need to change the display to provide the off axis views and the targeting views currently available in IGSTK.

More Related