# Issue Retrieving Patient DICOMS from Visbion PACS

**URL:** <https://discourse.slicer.org/t/issue-retrieving-patient-dicoms-from-visbion-pacs/42520>\
**Category:** Support\
**Tags:** dicom\
**Created:** [April 10, 2025, 1:04pm UTC](https://discourse.slicer.org/t/issue-retrieving-patient-dicoms-from-visbion-pacs/42520 "2025-04-10T13:04:07Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![sandigeeup](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/sandigeeup/32/13722_2.png) [@sandigeeup](https://discourse.slicer.org/u/sandigeeup)\
**Post date:** [April 10, 2025, 1:04pm UTC](https://discourse.slicer.org/t/issue-retrieving-patient-dicoms-from-visbion-pacs/42520/1 "2025-04-10T13:04:07Z")

</div>

Hi I am using the Dicom Networking, Query and Retrieve option to access a Visbion PACS system. I am able to retrieve the DICOM using the ID and it says Retrieve Process finished, however it then does not appear in my show dicom database, nor does it appear in the destination database location. Can anyone help with this, I have checked my firewall and re-downloaded Slicer. A colleague has no issues on her system which is set up the same. Many thanks Sandie

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/b/7/b7ec3d6ff7320c3d35d4d9eef8ea1aa21ddd2025.png)

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [April 10, 2025, 6:59pm UTC](https://discourse.slicer.org/t/issue-retrieving-patient-dicoms-from-visbion-pacs/42520/2 "2025-04-10T18:59:38Z")

</div>

> [@sandigeeup](#):
>
> A colleague has no issues on her system which is set up the same

Thanks for the report. Can you also confirm that the same version of Slicer is used in both cases ?

---

<div class="post-metadata">

**Author:** ![sandigeeup](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/sandigeeup/32/13722_2.png) [@sandigeeup](https://discourse.slicer.org/u/sandigeeup)\
**Post date:** [April 10, 2025, 7:31pm UTC](https://discourse.slicer.org/t/issue-retrieving-patient-dicoms-from-visbion-pacs/42520/3 "2025-04-10T19:31:58Z")

</div>

Hi Jean Christophe, my colleague downloaded the latest 5.8.1 release on her Mac, and it worked fine. I’m using Windows 11 and it initially worked with version 5.6.2. to which I initially managed to download one DICOM from the PACS system using DICOM networking, but all subsequent attempts with DICOM IDs reached the point shown in the screenshot and then failed to appear in the DICOM database. I also tried version 5.8.1, but the same issue persists. This is urgent for my PhD project as the PACS system will be replaced by Petcloud next week. I’ve been desperately trying to download all the DICOMs I need before then, but it keeps failing. I’m with Cambridge University.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [April 10, 2025, 8:01pm UTC](https://discourse.slicer.org/t/issue-retrieving-patient-dicoms-from-visbion-pacs/42520/4 "2025-04-10T20:01:26Z")

</div>

> my colleague downloaded the latest 5.8.1 release on her Mac, and it worked fine […] This is urgent for my PhD project as the PACS system will be replaced by Petcloud next week

Waiting this is sorted out, you may consider copying the local database directory already available on your colleague workstation onto your own workstation and locally importing the DICOM series from it.

In the interim, would that be a workable solution ?

---

<div class="post-metadata">

**Author:** ![sandigeeup](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/sandigeeup/32/13722_2.png) [@sandigeeup](https://discourse.slicer.org/u/sandigeeup)\
**Post date:** [April 11, 2025, 3:46pm UTC](https://discourse.slicer.org/t/issue-retrieving-patient-dicoms-from-visbion-pacs/42520/5 "2025-04-11T15:46:40Z")

</div>

My colleague is in a different part of the country and the dicoms are currently being transferred to the new cloud platform, however, I think I may have resolved the issue, although it takes along time to download and quite often crashes, before reaching to the dicom database. I will keep trying. Are there any others with issues, do you have a any debugging methods. 🙂

---

<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:** [April 11, 2025, 4:59pm UTC](https://discourse.slicer.org/t/issue-retrieving-patient-dicoms-from-visbion-pacs/42520/6 "2025-04-11T16:59:14Z")

</div>

Note that DICOM DIMSE, the standard way of communicating with PACS is meant to be a local area network protocol, so using it to access a remote cloud server can lead to slow performance or timeouts. If possible you should try to use the newer DICOMweb standard, which is designed for this use case.

Note that under the hood Slicer uses DCMTK, which offers some useful command line options that can probably set longer timeouts that could improve the robustness of the transfer.

---

<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:** [April 11, 2025, 5:31pm UTC](https://discourse.slicer.org/t/issue-retrieving-patient-dicoms-from-visbion-pacs/42520/7 "2025-04-11T17:31:06Z")

</div>

The new DICOM browser (that you can actuvate using the dropdown menu of the “Show DICOM database” button has much more advanced and more robust DICOM query/retrieve implementation.

Is your computer and the PACS on the same local network? What protocol does the server support for retrieve: C-GET or C-MOVE? Is your computer registered as known host in the PACS?

---

<div class="post-metadata">

**Author:** ![Kylie\_Selmy](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/kylie_selmy/32/82913_2.png) [@Kylie\_Selmy](https://discourse.slicer.org/u/Kylie_Selmy)\
**Post date:** [October 8, 2026, 7:01pm UTC](https://discourse.slicer.org/t/issue-retrieving-patient-dicoms-from-visbion-pacs/42520/8 "2026-10-08T19:01:35Z")

</div>

One thing worth checking is whether the issue is occurring at the PACS query/retrieve level or specifically when Slicer is trying to retrieve the study.

For a DICOM/PACS workflow, I would check the AE Titles, calling and called AE configuration, network connectivity and whether the PACS actually supports the requested C-FIND/C-MOVE or C-GET operation. It is also worth checking the PACS logs to see whether the association is accepted and whether the requested study can be retrieved.

If the PACS supports DICOMweb, that can also be an alternative approach, particularly when the workflow is intended to work with modern web-based applications.

This is the kind of issue where experience with [pacs development](https://wtt-solutions.com/en/pacs-picture-archiving-and-communication-system-development-services) and DICOM interoperability can be useful.