# 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:** 9

<div class="post-metadata">

**Author:** ![thewtex](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/thewtex/32/32_2.png) [@thewtex](https://discourse.slicer.org/u/thewtex)\
**Post date:** [November 19, 2018, 8:32pm UTC](https://discourse.slicer.org/t/dicom-multiframe-support/4806/9 "2018-11-19T20:32:24Z")

</div>

> [@fedorov](#):
>
> > 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…

ITK’s Jira Issue Tracker is dead. Long live [ITK’s GitHub Issue Tracker](https://github.com/InsightSoftwareConsortium/ITK/issues)! 👑

If there are issues with ITK’s reading of multi-frame DICOM files, please report it there. To the best of my knowledge, reading multi-frame DICOM volumes works well.

The old [Jira issue tracker](https://insightsoftwareconsortium.atlassian.net/projects/ITK/issues/ITK-3546?filter=allopenissues) is still available – if there is a relevant issue that you find important, please migrate them to the GitHub issue tracker.

> [@fedorov](#):
>
> 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! 😃

Deep learning is wonderful, and ITK helps apply deep learning methods to medical imaging data. To perform deep learning on medical imaging data, we definitely need good DICOM support!

---

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