A cross-platform .NET library for reading, writing, and communicating with DICOM medical imaging files and services.
Fellow Oak DICOM (fo-dicom) is an open-source .NET library for working with DICOM (Digital Imaging and Communications in Medicine) files and protocols. It provides tools to read, write, manipulate, and transmit medical imaging data, enabling integration of DICOM standards into .NET applications. The library solves the problem of handling complex medical imaging formats and network protocols in cross-platform .NET environments.
.NET developers building medical imaging applications, PACS (Picture Archiving and Communication System) components, healthcare software, or research tools that need to process DICOM data. It's particularly valuable for teams requiring cross-platform support across Windows, mobile, and web environments.
Developers choose fo-dicom because it's the most comprehensive, actively maintained open-source DICOM implementation for .NET, with modern async APIs, dependency injection support, and multiple rendering backends. Its cross-platform capabilities and adherence to current DICOM standards make it superior to older or platform-specific alternatives.
Fellow Oak DICOM for .NET, .NET Core, Universal Windows, Android, iOS, Mono and Unity
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Targets .NET Standard 2.0, supporting .NET Core, .NET Framework, UWP, Android, iOS, and Unity, enabling deployment across diverse devices and platforms.
Provides a fully asynchronous API using async/await, optimizing I/O and network operations for scalable, high-performance applications.
Handles multiple compression formats like JPEG, JPEG-LS, and JPEG2000 through additional packages, ensuring compatibility with a wide range of DICOM images.
Supports on-demand content loading for very large datasets, preventing memory overflow when processing big medical imaging files.
Setting up dependency injection and image rendering backends requires manual steps and additional NuGet packages, adding initial complexity.
API documentation is split between versions 4 and 5, which can confuse developers seeking current or version-specific information.
The README admits that first-class AspNetCore support is pending, necessitating workarounds like manually setting the service provider.