DICOMcloud
A standalone DICOMweb server with RESTful implementation of QIDO-RS, WADO-RS, STOW-RS, and WADO-URI services for medical imaging.
What is DICOMcloud?
DICOMcloud is a standalone DICOMweb server that implements the DICOM Part 18 standard, providing RESTful APIs for querying, retrieving, and storing medical imaging data. It solves the problem of accessing DICOM images and metadata over the web using modern, standards-based protocols, enabling cloud-native medical imaging applications.
Healthcare IT developers, medical imaging software engineers, and organizations building or integrating Picture Archiving and Communication Systems (PACS) or telemedicine platforms that require DICOMweb compliance.
Developers choose DICOMcloud because it offers a complete, open-source implementation of DICOMweb services with Azure integration, extensible architecture, and compatibility with any DICOMweb client, eliminating the need to build these complex standards from scratch.
Overview
Azure friendly DICOMweb part 18 .NET server with qido-rs, wado-rs, stow-rs, wado-uri RESTful implementation
Use Cases
Best For
- Building cloud-based medical imaging archives with DICOMweb APIs
- Integrating DICOM data with web-based viewers like OHIF
- Developing telehealth platforms that need standards-compliant image retrieval
- Migrating traditional PACS systems to cloud-native architectures
- Creating custom medical imaging workflows with RESTful services
- Research projects requiring programmatic access to DICOM metadata and images
Not Ideal For
- Teams requiring full DICOMweb standard compliance out-of-the-box, as features like dicomKeyword group element and TimezoneOffsetFromUTC in QIDO-RS are unsupported.
- Non-Azure or non-.NET environments, since the server is optimized for Azure deployment and built on .NET Framework 4.5.2, limiting cross-platform use.
- Projects needing advanced WADO-URI features like annotations, region retrieval, or charset support, which are not implemented.
- Simple DICOM file management without web APIs, as DICOMcloud focuses on RESTful services rather than basic file handling.
Pros & Cons
Pros
Implements core DICOMweb services like QIDO-RS, WADO-RS, and STOW-RS with support for pagination, fuzzy matching, and multipart uploads, enabling compliant medical imaging workflows as detailed in the documentation tables.
Offers one-click deployment to Azure via ARM templates and integrates seamlessly with Azure Blob Storage and SQL Database, simplifying cloud-native setups as highlighted in the README.
Uses StructureMap for Dependency Injection, allowing developers to customize storage layers and services without modifying core code, evidenced by the layered architecture description.
Provides built-in services for the OHIF viewer, facilitating web-based visualization of DICOM studies with formatted metadata, with specific documentation available.
Cons
Missing key DICOMweb features such as dicomKeyword group element in QIDO-RS and several WADO-URI parameters like annotation and region support, as admitted in the support tables.
Built on .NET Framework 4.5.2, which restricts deployment to Windows environments and lacks cross-platform support compared to modern .NET Core alternatives.
While extensible, the default configuration and documentation heavily favor Azure services, making adaptation to other clouds or on-premises setups more complex and potentially leading to vendor lock-in.
Frequently Asked Questions
Related Projects
OHIFOHIF zero-footprint DICOM viewer and oncology specific Lesion Tracker, plus shared extension packages
Cornerstone[Deprecated] Use Cornerstone3D Instead https://cornerstonejs.org/
PapayaA pure JavaScript medical research image viewer.
DicoogleDicoogle - Open Source PACS
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.