NAV-RFA workflow and requirements

From NAMIC Wiki
Revision as of 16:05, 26 June 2008 by ZivYaniv (talk | contribs) (→‎NAV-RFA Workflow)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Home < NAV-RFA workflow and requirements

NAV-RFA Workflow

  1. Place fiducials on patient.
  2. Acquire volumetric data set, CT or cone-beam CT (corresponding modality DICOM tags are either CT or XA) at end expiration.
  3. Segment the volume using a semi-automatic approach.
  4. Enable manual segmentation to correct the semi-automatic results.
  5. Export the segmentation to the planning module.
  6. Import the plan back into 3D Slicer.
  7. Start IGSTK based tracking process.
  8. Localize fiducials on 3D data set.
  9. Digitize fiducials using calibrated needle.
  10. Perform rigid registration.
  11. Show navigation GUI with current ablation path and target.


Additional comments

  1. Needle calibration - requires implementation in IGSTK.
  2. Interaction with planning/optimization module should be done using an xml file format.
  3. Setup of the tracker process should be performed using an xml file. This should be output provided by Slicer.

The XML file will contain:

  1. ip address to which we write data.
  2. All communication settings required for the Aurora (COM port, baud rate, etc.).
  3. For each tool:
    1. The desired ip and port to which the data should be written.
    2. The physical port on the control box that corresponds to this tool.
    3. Optional, the physical channel on the port
    4. Optional, the SROM file for the tool.
  1. Expected GUI:
    1. Axial, off axial, off sagittal, and down the barrel views (see this page for definitions).
    2. Axial, off-axial and sagittal views display the planned trajectory and the needle projection.
    3. Down-the-barrel view displays concentric circles denoting needle tip hub and target. In addition a depth gauge displaying the distance from the target.
    4. Respiratory signal as estimated from tracking data.
    5. Allow user to choose each trajectory and show ablation targets starting with the one farthest from the entry point along the trajectory.