# Dicom segmentation object Q/R

**URL:** <https://discourse.slicer.org/t/dicom-segmentation-object-q-r/12762>\
**Category:** Support\
**Created:** [July 28, 2020, 8:05pm UTC](https://discourse.slicer.org/t/dicom-segmentation-object-q-r/12762 "2020-07-28T20:05:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Krishna\_Nanda](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/krishna_nanda/32/7632_2.png) [@Krishna\_Nanda](https://discourse.slicer.org/u/Krishna_Nanda)\
**Post date:** [July 28, 2020, 8:05pm UTC](https://discourse.slicer.org/t/dicom-segmentation-object-q-r/12762/1 "2020-07-28T20:05:43Z")

</div>

Hello,

We have setup the 3D Slicer dicom browser to be able to Q/R into a vendor software. The query shows all the series, including a dicom segmentation object (modality SEG). The retrieve is successful in pulling all other series except dicom seg. We were expecting the dicom seg to behave like other dicom series with regards to Q/R. We were wondering if there is any specific function that needs to be enabled to make this work?

Thanks

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [July 28, 2020, 8:24pm UTC](https://discourse.slicer.org/t/dicom-segmentation-object-q-r/12762/2 "2020-07-28T20:24:20Z")

</div>

That’s interesting - glad you were able to get the rest working and I agree it’s odd the SEG wouldn’t come over. I can’t think of anything in the Slicer/ctk dicom networking layer that would even care what kind of instance it is.

Can you confirm that it’s not actually in the database and it’s just not being loaded correctly? You would need the Quantitative Reporting extension installed to load. Can you load it if you download a different way?

Another thing to try would be using the dcmtk command line tools to CGET the instance and see if it works. I know some dimse implementation need to be configured to allow storage of certain SOP classes, and maybe they also need to be configured to allow retrieval too.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [November 2, 2021, 12:22pm UTC](https://discourse.slicer.org/t/dicom-segmentation-object-q-r/12762/3 "2021-11-02T12:22:52Z")

</div>

Maybe the presentation contexts needs some adjustment, similarly to how the configuration had to be tuned for fixing sending of DICOM segmentation objects:

> <https://github.com/Slicer/Slicer/commit/21f8ba46beb67ae169387dd94237b0d7f8087302>
>
> The default configuration provided with the DCMTK dicomscu program used to send …data from Slicer does not allow the transfer of DICOM-SEG. This patch provides:
> \- an alternative configuration that includes the needed presentation context UID needed for DICOM-SEG files to be sent using DICOM and DICOMweb (using dicomscu)
> \- retry logic that first attempts to transfer the DCM instance using the standard configuration and (if that fails) will attempt a second transfer using the fallback configuration