Difference between revisions of "2013 Summer Project Week:Patient hierarchy"
m (Text replacement - "[http://www.na-mic.org/Wiki/images/" to "[https://na-mic.org/w/images/") |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 25: | Line 25: | ||
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). | + | Consider renaming options for this feature ('patient' being inappropriate for mice, for example). "Subject Hierarchy" is a current candidate name. |
</div> | </div> | ||
| Line 33: | Line 33: | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | *Patient Hierarchy module shows the hierarchy, enables reparenting and adding from outside the Patient Hierarchy. | + | *Patient Hierarchy module shows the hierarchy, enables reparenting and adding from outside the Patient Hierarchy. Also facilitates grouped toggling of visualization, deformation, and exporting |
| + | **[https://na-mic.org/w/images/6/6f/Pinter_SlicerRt_PatientHierarchy_Introduction_NA-MIC_2013_Summer.pptx Presentation] | ||
*Some steps toward utilization of Patient Hierarchy has been implemented (SlicerRT [https://www.assembla.com/spaces/slicerrt/tickets/278#/activity/ticket: #278]) | *Some steps toward utilization of Patient Hierarchy has been implemented (SlicerRT [https://www.assembla.com/spaces/slicerrt/tickets/278#/activity/ticket: #278]) | ||
| + | *Roadmap and plan for generalizing to Subject Hierarchy and its integration into Slicer core | ||
| + | **[http://www.na-mic.org/Wiki/index.php/2013_Summer_Project_Week_Breakout_Session:RT#Patient_Hierarchy Meeting minutes] | ||
</div> | </div> | ||
| Line 44: | Line 47: | ||
==References== | ==References== | ||
| − | * [ | + | * [https://www.slicer.org/wiki/Documentation/Nightly/Modules/PatientHierarchy Patient Hierarchy module in SlicerRT] |
* [https://www.assembla.com/spaces/slicerrt/tickets SlicerRT issue tracking system] | * [https://www.assembla.com/spaces/slicerrt/tickets SlicerRT issue tracking system] | ||
Latest revision as of 18:27, 10 July 2017
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). "Subject Hierarchy" is a current candidate name.
Progress
- Patient Hierarchy module shows the hierarchy, enables reparenting and adding from outside the Patient Hierarchy. Also facilitates grouped toggling of visualization, deformation, and exporting
- Some steps toward utilization of Patient Hierarchy has been implemented (SlicerRT #278)
- Roadmap and plan for generalizing to Subject Hierarchy and its integration into Slicer core
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.
