Connecting Weasis to DICOMCloud about weasis-pacs-connector HOT 3 CLOSED

The current implementation of weasis-pacs-connector creates a manifest for Weasis either by DICOM queries or directly by SQL queries but not yet by DICOMWeb (QIDO) queries.

The WADO URI is used by Weasis to download images, see this page to better understand the workflow.

This XML manifest is built on the server side because DICOM requests are not adapted for the web and therefore cannot be done on the client side. However, with the new DICOMWeb services, this becomes possible. I am currently implementing the QIDO directly in Weasis to allow the construction of the manifest without using weasis-pacs-connector. Like for example:
weasis://$dicom:rs --url "https://image.com/dicomweb" --studyList "1.3.4342.3,1.2432"

DICOMCloud is not a PACS because it does not contain the basic DICOM services and therefore cannot be configured simply with weasis-pacs-connector. Maybe implementation with SQL queries would be possible. Otherwise, you have to wait for the implementation of the QIDO directly in Weasis.

from weasis-pacs-connector.

You can try to connect directly Weasis 3.5.4 to DICOMCloud, see this post.

I haven't tried. Thank you for giving feedback.

from weasis-pacs-connector.

The services structure on DCIOMCould has been fixed, so now it is possible to connect directly to DICOMCloud via the WADO-RS services.

See the page, URL example:

$dicom:rs --url "https://dicomcloud.azurewebsites.net/api" -r "studyUID=1.2.840.113619.2.25.1.1762157631.873231884.123" -r "studyUID=1.3.6.1.4.1.5962.99.1.2280943358.716200484.1363785608958.3.0"

from weasis-pacs-connector.