The server is hosted on a free azure website plan that shutdown the web application after some period of inactivity. So first request should wait for the web application to warm up and start running which causes the delay on the client side and might time-out.
Currently the server only supports retrieving (WADO-RS and WADO-RI) DICOM datasets that have been pre-stored with a configured Transfer Syntax.
Add the ability to transform an in-memory dataset to the requested transfer syntax from the query parameter in WADO-URI or the accept parameter in WADO-RS when this dataset is not available on the server.
When requesting a DICOM dataset using WADO-RS or WADO-URI with no transfer syntax parameter the server returns the dataset with the transfer syntax used at storage.
Server should return the default transfer syntax: ExplicitVRLittleEndian
Currently once you clone the DICOMcloud code, you must create a database and update the web.config with the connection string along with the location where the images should be stored.
Also, the code structure which configures the server could be improved for better readability and customization.
This process should be enhanced such that the user can run the server immediately after cloning with no to little configuration
For WADO-URI: the server should return the transfer syntax in the query param
For WADO-RS: The server should return the transfer syntax in the accept header
Since the initial development of the DICOMcloud library and the focus has been to add and support as many features possible defined in the DICOMweb protocol to provide a reference implementation as a standalone DICOMweb Server.
I’ve been trying lately to improve the user experience working with the library, understanding the functionality and API, how to run a development environment and deployment.
In order to track the status of these activities in a single place, I’ll be adding here the related issue’s title with a link and any work that is yet to be done. Any suggestions are welcome!
Create Nuget packages for the library to bootstrap development #26
Simplify running the WADO Server from Visual Studio #24
Implement a versioning mechanism for the library #23
Create an ARM template with deploy to Azure button #19
Create unit test projects to cover the different examples of using the library #18
question on the dicom cloud project
i get this error on study query from the demo project to cloud application
An exception of type 'System.TypeInitializationException' occurred in DICOMcloud.Wado.Core.dll but was not handled in user code
Additional information: The type initializer for 'DICOMcloud.Wado.Core.DefaultDicomQueryElements' threw an exception.