zaid-safadi/dicomcloud

Azure friendly DICOMweb part 13 .NET server with qido-rs, wado-rs, stow-rs, wado-uri RESTful implementation

dicomcloud's Issues

JSON converter doesn't include the TransferSyntax when converting to JSON

When converting a DICOM dataset to JSON the transfer syntax is not included. The transfer syntax is included when converting to XML

Add API documentation using Swagger

Create Wiki pages for the project - Documentation

Wiki pages

• overview
• Features
• DICOM Support
• Development
• ...

Create a SQL Server database project to maintain the DICOM server database and publish to SQL server

A SQL Server database project in Visual Studio will make it easier to:

1. Visualize the database
2. Publish to local SQL Server or Azure Database directly from VS
3. Provide version control to the database script

http://www.codeproject.com/Articles/825831/SQL-Server-Database-Development-in-Visual-Studio

Add Delete REST API support

Update XML/JSON converters to use new method for updating the TransferSyntax when setting the image

Improve the Developer User Experience of the DICOMcloud library

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
• Add API documentation using Swagger #12
• Create a SQL Server database project to maintain the DICOM server database and publish to SQL server #8

Add support for transfer syntax in WADO-RS and WADO-URI

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

Currently these are ignored.

Create unit test projects to cover the different examples of using the library

Stow-RS (WADO Store) doesn't return error code on Failure

When Stow-rs fails to store a DICOM dataset, the server returns http 200 status code.

Ther server should return one of the error codes defined in Part 18-2016 sec. 6.6.1

Simplify running the WADO Server from Visual Studio

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

Upgrade to latest fo-dicom v3.0.0.0

Implement a versioning mechanism for the library

Add a shared linked assembly version info to all projects.

Create an ARM template with deploy to Azure button

Build an Azure Resource Manager (ARM) template that allows deploying the DICOMcloud server by placing the standard Deploy to Azure button

Create Nuget packages for the library to bootstrap development

Nuget packages will be created to reference the library DLLs.

Also, a Nuget package should be created that can be added to a WepAPI project to transform it into a DICOMweb server with minimum config from the user

error on study query

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.

QIDO-RS service doesn't return StudyDescription field

Need to add support in the database. Currently this DICOM tag is not being stored.

Upgrade fo-dicom to v3.0.1

Any thoughts on having the repository moved to its own Github Organization Account?

Feel free to add a thumbs up/down or comment on this. My reasoning is:

1. Group other related repos. and new ones under one account, (e.g. DICOMcloud-webJS)
2. Source code licensed to the Organization contributors

Add anonymization support when storing DICOM images

Add support for on the fly generation of dataset according to transfer syntax in WADO-URI and WADO-RS

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.

Add support for returning "application/dicom+xml" in QIDO-RS

Hosted server slow on first request

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.

Resolution

Move the hosted server into a paid plan

Discuss adaptation requirements with "fo-dicom"

This is an issue to discuss what are the fo-dicom prerequisites for adaptation.

• target .NET Framework PCL profile 111 as much as possible

what is the followed standard? links?

WADO-RS and WADO-URI not returning default TransferSyntax

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