Difference between revisions of "2013 Summer Project Week:Patient hierarchy"
(Moved from non 2013 summer project week location) |
|||
| Line 24: | Line 24: | ||
The plan for the project week is to give a short demo of the current functionality and solicit feedback, then continuing to work on implementation. | The plan for the project week is to give a short demo of the current functionality and solicit feedback, then continuing to work on implementation. | ||
| + | |||
| + | Consider renaming options for this feature ('patient' being inappropriate for mice, for example). "Study Hierarchy" is a current candidate name. | ||
</div> | </div> | ||
Revision as of 01:48, 13 June 2013
Home < 2013 Summer Project Week:Patient hierarchy
Initial GUI
Key Investigators
- Queen's: Csaba Pinter, Andras Lasso
- Isomics: Steve Pieper
Objective
Discussing the progress about the Patient Hierarchy module and implement further enhancements and utilisations.
Approach, Plan
The approach is to have a mechanism that maps the DICOM hierarchy to be used within Slicer. This involves visualizing and editing the loaded DICOM hierarchy, connecting the data objects that are connected on a DICOM level, and utilizing this knowledge for the widest imaginable manner.
The plan for the project week is to give a short demo of the current functionality and solicit feedback, then continuing to work on implementation.
Consider renaming options for this feature ('patient' being inappropriate for mice, for example). "Study Hierarchy" is a current candidate name.
Progress
- Patient Hierarchy module shows the hierarchy, enables reparenting and adding from outside the Patient Hierarchy.
- Some steps toward utilization of Patient Hierarchy has been implemented (SlicerRT #278)
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as a Slicer Loadable Module inside the SlicerRT extension. In the long term, integrating this functionality in the Slicer core would be desirable.
