Difference between revisions of "AHM2012-DICOM-Huddle"
From NAMIC Wiki
Line 1: | Line 1: | ||
[[AHM_2012#Agenda|Back to AHM Schedule]] | [[AHM_2012#Agenda|Back to AHM Schedule]] | ||
+ | == Goals == | ||
An organizational discussion of all the DICOM-related projects going on in the NA-MIC community: | An organizational discussion of all the DICOM-related projects going on in the NA-MIC community: | ||
Line 13: | Line 14: | ||
* Others? | * Others? | ||
− | + | == Slicer4 topics == | |
* Multiple parsing of DICOM headers (slow loading) | * Multiple parsing of DICOM headers (slow loading) | ||
* Mapping non-image DICOM data into MRML | * Mapping non-image DICOM data into MRML | ||
Line 29: | Line 30: | ||
*** Slicer Data Bundle (lollipop) is a zip file in a private tag of a secondary capture | *** Slicer Data Bundle (lollipop) is a zip file in a private tag of a secondary capture | ||
− | Organizational Topics | + | == Organizational Topics== |
* How can we organize ourselves to minimize duplicated effort | * How can we organize ourselves to minimize duplicated effort | ||
* Who is 'on the hook' to deliver functionality related to DICOM? | * Who is 'on the hook' to deliver functionality related to DICOM? |
Latest revision as of 15:51, 9 January 2012
Home < AHM2012-DICOM-HuddleBack to AHM Schedule
Goals
An organizational discussion of all the DICOM-related projects going on in the NA-MIC community:
- CTK DICOM and application hosting
- Slicer4 DICOM Module, and related projects
- Annotations: AIM, SR, and QIN
- DICOM RT efforts
- ITKv4 DICOM
- XNAT Gateway DICOM CGET
- Others?
Slicer4 topics
- Multiple parsing of DICOM headers (slow loading)
- Mapping non-image DICOM data into MRML
- header metadata
- annotations
- RT sturcutres and doses
- time series
- Mapping MRML data into DICOM
- Exporting images
- Secondary Capture
- 'real' CT or MR profiles
- Segmentations
- Surfaces
- Scenes
- Slicer Data Bundle (lollipop) is a zip file in a private tag of a secondary capture
- Exporting images
Organizational Topics
- How can we organize ourselves to minimize duplicated effort
- Who is 'on the hook' to deliver functionality related to DICOM?
- What is funding the effort?
- What is the use case and deliverable?
- What toolkit will be used?
- What synergy is there with other efforts?
- Are there specific issues that we can work out this week as a team?