Retrieve a selection of dicom from a PACS

[riep]

Hi everyone,
I am talking about the dicom retrieve in Slicer. Currently, we cannot retrieve from the PACS, a selection of dicom series of the selected study. The whole study has to be retrieved. It can take time if the study is big, and we are only interested to a single series.
Probably a wrong call to currentStudiesSelection instead of currentSeriesSelection

CTK/Libs/DICOM/Widgets/ctkDICOMQueryRetrieveWidget.cpp

Line 305 in a75a736

QStringList selectedSeriesUIDs = d->dicomTableManager->currentStudiesSelection();

I can do a PR if needed.

[lassoan]

It is not a typo, but the retrieve currently operates at study level now. Since we get information on all the series, it could make sense to retrieve the selected studies. You can also choose to use DICOMweb for query/retrieve (using DICOMweb Browser extension), which supports series-level retrieve already.

If you choose to stick with classic DIMSE networking then it would be also great if you could make a few very easy improvements, such as make the "Data sources" section collapsible (but probably keep the search option visible), because once you have configured the data sources, you don't need to see them anymore, yet they now take up a lot of screen space.

[riep]

I am not very familiar with DICOMweb and I think in hospital environments DICOMweb is probably not available. For instance, we are using dicom4chee and DICOMweb is not available to my knowledge.
So, if I add in addition a collapisble button for "Data sources" (generaly improve this window) and change currentStudiesSelection to currentSeriesSelection you would considered it for review?

[lassoan]

dicom4chee has been supporting DICOMweb for many years. You may just need to enable it.

While still classic DIMSE networking is used in most clinical environments, it is not that important, because researchers very rarely get direct access to clinical servers. IT administrators worry that researchers mess up things - overload the server, upload invalid data, etc. - that will interfere with patient care.

Many modern research tools only support DICOMweb (Kheops, OHIF viewer, Javascript DICOMweb server, MONAILabel, etc. just to name a few that quickly comes to mind), because it behaves the same way as all other web services and therefore it is easy to use robust and well-established frameworks in Javascript and Python. Most PACS and viewers support both DIMSE and DICOMweb anyway, so DICOMweb is already the most universally usable protocol among various DICOM software.

So, if I add in addition a collapisble button for "Data sources" (generaly improve this window) and change currentStudiesSelection to currentSeriesSelection you would considered it for review?

Yes, sure. People must still use DIMSE networking in certain scenarios, so these improvements would be welcome.

[riep]

ok good to know, thanks for the info! I will do a PR today because as of now we use DIMSE networking.
Do you have any info on speed DICOMweb vs DIMSE networking

[pieper]

Do you have any info on speed DICOMweb vs DIMSE networking

This is a good place to start:
https://www.dicomstandard.org/dicomweb