Difference between revisions of "2012 Summer Project Week:Reporting"
From NAMIC Wiki
| Line 16: | Line 16: | ||
* export these hierarchies and Slicer internal data structures into other formats (e.g., AIM) | * export these hierarchies and Slicer internal data structures into other formats (e.g., AIM) | ||
This development is currently happening within Reporting module (available on github). | This development is currently happening within Reporting module (available on github). | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
</div> | </div> | ||
| Line 29: | Line 22: | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
| − | + | * present the capabilities of the Reporting module to the interested groups | |
| + | * discuss the missing features and roadmap for future development | ||
| + | * cross-check with the AIM experts (Pat) that the AIM output is correct | ||
| + | * discuss the possibility of integrating Reporting module with the native AIM API, which is currently under development by Pat Mongklowat's group | ||
| + | * consider integrating Reporting as an extension | ||
| + | * discuss how support of DICOM SEG should be integrated into Slicer | ||
</div> | </div> | ||
Revision as of 21:26, 15 June 2012
Home < 2012 Summer Project Week:Reporting
Key Investigators
- BWH: Andrey Fedorov, Nicole Aucoin, Steve Pieper, Ron Kikinis, Fiona Fennessy
- Northwestern U: Pat Mongklowat
Objective
As part of BWH QIN project, we are working on implementing support for
- organizing Slicer markup and annotations into hierarchies to maintain their relationship with the original volumes
- export these hierarchies and Slicer internal data structures into other formats (e.g., AIM)
This development is currently happening within Reporting module (available on github).
Approach, Plan
- present the capabilities of the Reporting module to the interested groups
- discuss the missing features and roadmap for future development
- cross-check with the AIM experts (Pat) that the AIM output is correct
- discuss the possibility of integrating Reporting module with the native AIM API, which is currently under development by Pat Mongklowat's group
- consider integrating Reporting as an extension
- discuss how support of DICOM SEG should be integrated into Slicer
Progress
Delivery Mechanism
Reporting module is available as a Slicer4 loadable module, source code available on github: https://github.com/fedorov/Reporting
References
- Slicer AIM integration project: AIM_Annotations_integration_with_3DSlicer
- Reporting module source code: https://github.com/fedorov/Reporting
