# Segmentation Storage: 1.2.840.10008.5.1.4.1.1.66.4

**URL:** <https://discourse.slicer.org/t/segmentation-storage-1-2-840-10008-5-1-4-1-1-66-4/4274>\
**Category:** Support\
**Tags:** dicom\
**Created:** [October 3, 2018, 3:54pm UTC](https://discourse.slicer.org/t/segmentation-storage-1-2-840-10008-5-1-4-1-1-66-4/4274 "2018-10-03T15:54:22Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![issakomi](https://avatars.discourse-cdn.com/v4/letter/i/b9e5f3/32.png) [@issakomi](https://discourse.slicer.org/u/issakomi)\
**Post date:** [September 16, 2020, 3:33pm UTC](https://discourse.slicer.org/t/segmentation-storage-1-2-840-10008-5-1-4-1-1-66-4/4274/21 "2020-09-16T15:33:26Z")

</div>

the issue in post linked in my post above, this one, not related to Slicer

> <https://github.com/InsightSoftwareConsortium/ITK/issues/1969>
>
> Description
> Hello. I am running into an error processing a medical image segmentation DICOM file from The Cancer Imaging Archive. When I...

---

<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:** [September 16, 2020, 3:34pm UTC](https://discourse.slicer.org/t/segmentation-storage-1-2-840-10008-5-1-4-1-1-66-4/4274/22 "2020-09-16T15:34:12Z")

</div>

> [@lassoan](#):
>
> There also a few dependencies to take care of

Indeed, this makes things more complex. I did not appreciate those issues. Potentially, we could separate dcmqi and DICOM plugin for Segmentations from QuantitativeReporting, but that would also not be very straightforward…

[Previous page](https://discourse.slicer.org/t/segmentation-storage-1-2-840-10008-5-1-4-1-1-66-4/4274.md?page=1)