2014 Project Week:DICOM enhanced multiframe - Revision history

Fedorov: /* Key Investigators */

2014-01-10T05:41:20Z

Key Investigators

Fedorov: /* Project Description */

2014-01-09T23:16:38Z

Project Description

Fedorov at 18:41, 6 January 2014

2014-01-06T18:41:59Z

Fedorov: /* Project Description */

2014-01-06T01:26:44Z

Project Description

Fedorov at 18:29, 24 December 2013

2013-12-24T18:29:44Z

Fedorov: Created page with 'NOTOC Image:PW-SLC2014.png|Projects List ==Key Investigators== * BWH: Andrey Fedorov, Alireza Mehrtash * David Clu…'

2013-12-16T16:50:07Z

Created page with '__NOTOC__ <gallery> Image:PW-SLC2014.png|Projects List </gallery> ==Key Investigators== * BWH: Andrey Fedorov, Alireza Mehrtash * David Clu…'

New page

__NOTOC__
<gallery>
Image:PW-SLC2014.png|[[2014_Winter_Project_Week#Projects|Projects List]]
</gallery>

==Key Investigators==
* BWH: Andrey Fedorov, Alireza Mehrtash
* David Clunie
* Isomics: Steve Pieper
* MGH: Jayashree Kalpathy-Cramer
* Iowa: Reinhard Beichel
* GE: Jim Miller

==Project Description==

<div style="margin: 20px;">
<div style="width: 27%; float: left; padding-right: 3%;">
<h3>Objective</h3>
* Most commonly, DICOM images are stored such that each frame (slice) is stored as a separate file. Enhanced multiframe objects allow to reduce storage requirements and simplify interaction with the DICOM data. These objects are also versatile to support various use cases such as storing perfusion or multi-echo data in a single object.
* Our goal is to investigate current level of DICOM enhanced multiframe support in Slicer and related tools, and improve it to support communication of perfusion data (potential replacement for NRRD used by MultiVolume)

</div>
<div style="width: 27%; float: left; padding-right: 3%;">
<h3>Approach, Plan</h3>
* Use Pixelmed tools to convert sample datasets (3D volumes and perfusion) into enhanced multi-frame representation
* test if the generated objects can be read by Slicer, debug the unsupported use cases
* discuss experience of using multi-frame data with the interested project attendees and collect sample datasets that can be shared
* discuss with Jim integration of multiframe for DCE communication in PkModeling CLI
</div>
<div style="width: 27%; float: left; padding-right: 3%;">
<h3>Progress</h3>
*
</div>
</div>

@@ Line 33: / Line 33: @@
+*
 </div>
 </div>

@@ Line 19: / Line 19: @@
 * Most commonly, DICOM images are stored such that each frame (slice) is stored as a separate file. Enhanced multiframe objects allow to reduce storage requirements and simplify interaction with the DICOM data. These objects are also versatile to support various use cases such as storing perfusion or multi-echo data in a single object.
 * Citing Suppl 157: "The enhanced family of modality-specific multi-frame IODs as currently defined does not permit a simple mapping of the legacy single-frame IOD attributes to the enhanced multi-frame IOD attributes, due to the requirement for much more mandatory information, and the requirement to use standard codes and pre-defined strings for many features that are unspecified or unsupported in the older IODs." To address this limitation, Legacy Converted modality-specific OIDs have been introduced.
-* Our goal is to investigate current level of DICOM enhanced (and legacy converted enhanced) multiframe support in Slicer and related tools, and improve it to support communication of perfusion data (potential replacement for NRRD used by MultiVolume)
+* Our goal is to investigate current level of DICOM enhanced (and legacy converted enhanced) multiframe support in Slicer and related tools, and improve it; we will also investigate the use of miltiframe DICOM to support communication of perfusion data (potential replacement for NRRD used by MultiVolume)
 </div>

@@ Line 11: / Line 11: @@
 * Iowa: Reinhard Beichel
 * GE: Jim Miller
 ==Project Description==

@@ Line 31: / Line 31: @@
 <div style="width: 27%; float: left; padding-right: 3%;">
 <h3>Progress</h3>
+* Among the evaluated tools (dicom3tools, gdcm, Pixelmed, dcmulti from dicom3tools of David Clunie is most functional (support for dimensions and stacks initialization, sorting, initialization of functional groups)
 </div>

@@ Line 18: / Line 18: @@
 <h3>Objective</h3>
 * Most commonly, DICOM images are stored such that each frame (slice) is stored as a separate file. Enhanced multiframe objects allow to reduce storage requirements and simplify interaction with the DICOM data. These objects are also versatile to support various use cases such as storing perfusion or multi-echo data in a single object.
-* Our goal is to investigate current level of DICOM enhanced multiframe support in Slicer and related tools, and improve it to support communication of perfusion data (potential replacement for NRRD used by MultiVolume)
+* Citing Suppl 157: "The enhanced family of modality-specific multi-frame IODs as currently defined does not permit a simple mapping of the legacy single-frame IOD attributes to the enhanced multi-frame IOD attributes, due to the requirement for much more mandatory information, and the requirement to use standard codes and pre-defined strings for many features that are unspecified or unsupported in the older IODs." To address this limitation, Legacy Converted modality-specific OIDs have been introduced.
 </div>

2014 Project Week:DICOM enhanced multiframe - Revision history

Fedorov: /* Key Investigators */

Fedorov: /* Project Description */

Fedorov at 18:41, 6 January 2014

Fedorov: /* Project Description */

Fedorov at 18:29, 24 December 2013

Fedorov: Created page with '__NOTOC__ Image:PW-SLC2014.png|Projects List ==Key Investigators== * BWH: Andrey Fedorov, Alireza Mehrtash * David Clu…'

Fedorov: Created page with 'NOTOC Image:PW-SLC2014.png|Projects List ==Key Investigators== * BWH: Andrey Fedorov, Alireza Mehrtash * David Clu…'