Difference between revisions of "Slicer RT: DICOM-RT Export"
From NAMIC Wiki
(Created page with '__NOTOC__ <gallery> Image:PW-SLC2013.png|Projects List <!--Image:genuFAp.jpg|Scatter plot of the original FA data through the genu of the co…') |
m (moved Slicer RT: DICOM-RT Export (Greg Sharp, Kevin Wang, Csaba Pinter) to Slicer RT: DICOM-RT Export) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 7: | Line 7: | ||
==Key Investigators== | ==Key Investigators== | ||
| − | |||
* MGH: Greg Sharp | * MGH: Greg Sharp | ||
| + | * PMH Toronto: Kevin Wang | ||
* Queen's: Csaba Pinter | * Queen's: Csaba Pinter | ||
| Line 22: | Line 22: | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
| − | * | + | * Investigat the existing DICOM export mechanism. |
| − | * | + | * Implement simple interface functions in Plastimatch |
| + | * Implement a loadable module to utilize the interface functions in Plastimatch for saving DicomRT objects. | ||
* Implement a plugin mechanism just like the Dicom import plugin framework to determine which plugin is better to export the mrmlnode. Decide which objects to export in the first round and identify the obstacles for the other objects | * Implement a plugin mechanism just like the Dicom import plugin framework to determine which plugin is better to export the mrmlnode. Decide which objects to export in the first round and identify the obstacles for the other objects | ||
| − | |||
* Have the export function use the Patient Hierarchy to fill the proper DICOM tags | * Have the export function use the Patient Hierarchy to fill the proper DICOM tags | ||
| Line 33: | Line 33: | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | * | + | * . |
| − | + | ||
'''To do''': | '''To do''': | ||
Latest revision as of 15:25, 30 May 2013
Home < Slicer RT: DICOM-RT Export
Key Investigators
- MGH: Greg Sharp
- PMH Toronto: Kevin Wang
- Queen's: Csaba Pinter
Objective
The goal is to migrate the DICOM RT export function in Plastimatch to be able to export the RT objects of SlicerRT, leveraging the Patient Hierarchy tree and the Slicer DICOM Database.
Approach, Plan
- Investigat the existing DICOM export mechanism.
- Implement simple interface functions in Plastimatch
- Implement a loadable module to utilize the interface functions in Plastimatch for saving DicomRT objects.
- Implement a plugin mechanism just like the Dicom import plugin framework to determine which plugin is better to export the mrmlnode. Decide which objects to export in the first round and identify the obstacles for the other objects
- Have the export function use the Patient Hierarchy to fill the proper DICOM tags
Progress
- .
To do:
- create a loadable module and corresponding module logic
- organize google hangout with Greg to follow up with how to implement dicom export using the plastimatch lib.
- Implement a save function, and utility functions to construct corresponding plastimatch data structure for saving structure set.
- follow up with Steve and Csaba on how to implement the plugin mechanism
- follow up on patient hierarchy model.
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as a Slicer module, as part of the SlicerRT extension
