Support for WADO-URI about dicomweb-client HOT 3 OPEN

So far, we only considered the RESTful Web Services and ignored the URI Web Service.

I am not sure whether we should try to integrate both services in the exiting class, given that the URI service only supports retrieve transactions, but not the search and store transactions. Furthermore, the retrieve transaction of the URI service only supports retrieval at the instance level (and to a certain extent at the frame level, but only a single frame can be retrieved per request). Therefore, the only methods that are useful for the URI Service are retrieve_instance, retrieve_instance_rendered, retrieve_instance_frames, and retrieve_instance_frames_rendered.

If we think that it would be valuable to add support for the URI Web Service to the library, I would suggest implementing a separate class (e.g., DICOMwebUriClient or something along those lines) that only has the above retrieve methods.

from dicomweb-client.

Thanks for the reply, these are good points. I will play around with creating a DICOMwebUriClient

from dicomweb-client.

Have you considered leveraging a DIMSE/DICOMweb adapter (if you're able to deploy server-side)?

from dicomweb-client.