Difference between revisions of "2015 Winter Project Week:DICOM References"
From NAMIC Wiki
(Created page with '__NOTOC__ <gallery> Image:PW-2015SLC.png|Projects List </gallery> ==Key Investigators== * Andrey Fedorov, BWH * Csaba Pinter, Queen's * Ste…') |
|||
| Line 17: | Line 17: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
| − | * | + | * Notification that a DICOM dataset being loaded is referencing things, and asking the user if they would like to load those too. I think this should be done in DICOM browser at the time of examine/load. |
| − | + | * Marking the hierarchy entries that have resolved or unresolved dependencies in the subject hierarchy (this could be done by highlghting of rows in red/yellow, for example) | |
| − | * | + | * Providing user with the mechanism to pull in unresolved dependencies (this could be done using "Related" pop-up menu in SH). |
| − | * | + | * Extend the ctkDICOMDatabase to cache references during the import process |
| + | * Reconcile the reference graph (which is a DAG) with the "composite context" (patient/study/series) which is a tree. They are handled quite differently in DICOM, but to me they should be very similarly handled and exposed to the user if possible (as it is in the subject hierarchy) | ||
</div> | </div> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
Revision as of 21:46, 20 December 2014
Home < 2015 Winter Project Week:DICOM References
Key Investigators
- Andrey Fedorov, BWH
- Csaba Pinter, Queen's
- Steve Pieper, Isomics
Project Description
Objective
- Lay down a plan to handle DICOM object references in Slicer
Approach, Plan
- Notification that a DICOM dataset being loaded is referencing things, and asking the user if they would like to load those too. I think this should be done in DICOM browser at the time of examine/load.
- Marking the hierarchy entries that have resolved or unresolved dependencies in the subject hierarchy (this could be done by highlghting of rows in red/yellow, for example)
- Providing user with the mechanism to pull in unresolved dependencies (this could be done using "Related" pop-up menu in SH).
- Extend the ctkDICOMDatabase to cache references during the import process
- Reconcile the reference graph (which is a DAG) with the "composite context" (patient/study/series) which is a tree. They are handled quite differently in DICOM, but to me they should be very similarly handled and exposed to the user if possible (as it is in the subject hierarchy)
