# DICOM multiframe support

**URL:** <https://discourse.slicer.org/t/dicom-multiframe-support/4806>\
**Category:** Development\
**Tags:** dicom\
**Created:** [November 19, 2018, 3:58pm UTC](https://discourse.slicer.org/t/dicom-multiframe-support/4806 "2018-11-19T15:58:30Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [November 19, 2018, 6:20pm UTC](https://discourse.slicer.org/t/dicom-multiframe-support/4806/5 "2018-11-19T18:20:06Z")

</div>

> [@lassoan](#):
>
> Shouldn’t we report the error to ITK developers and ask them to fix multiframe support? It should not be difficult.

I think I already reported some of those on Jira, this issue came up before, but now that ITK Jira is gone, no way to confirm…

Based on a discussion here: [Slicer DICOM Scalar volume plugin relies on (old) GDCM: why do we not use DCMTK? - #24 by pieper](https://discourse.slicer.org/t/slicer-dicom-scalar-volume-plugin-relies-on-old-gdcm-why-do-we-not-use-dcmtk/354/24), looks like the “home” for ITK DICOM development is [GitHub - KitwareMedical/ITKDICOM: Better support for DICOM in ITK.](https://github.com/KitwareMedical/ITKDICOM), but I do not see a lot of activity there, and there are issues open since 2017. Not clear if ITK community prioritized DICOM support over many competing interests. I am sure something like “deep learning in ITK” would be much higher on the list! 😃

---

_[View the full topic](https://discourse.slicer.org/t/dicom-multiframe-support/4806)._