18 releases

0.8.0 Nov 6, 2024
0.7.0 Apr 25, 2024
0.6.3 Nov 21, 2023
0.6.0 Jul 23, 2023
0.1.0 Aug 31, 2019

#72 in Images

Download history 423/week @ 2024-07-31 320/week @ 2024-08-07 797/week @ 2024-08-14 454/week @ 2024-08-21 623/week @ 2024-08-28 241/week @ 2024-09-04 734/week @ 2024-09-11 545/week @ 2024-09-18 657/week @ 2024-09-25 561/week @ 2024-10-02 539/week @ 2024-10-09 834/week @ 2024-10-16 765/week @ 2024-10-23 616/week @ 2024-10-30 788/week @ 2024-11-06 726/week @ 2024-11-13

3,016 downloads per month
Used in 8 crates (7 directly)

MIT/Apache

3MB
47K SLoC

DICOM-rs

CratesIO Documentation

dicom is a library for the DICOM standard. It is part of the DICOM-rs project, an ecosystem of modules and tools for DICOM compliant systems.

This collection provides a pure Rust implementation of the DICOM standard, allowing users to read and write DICOM data over files and other sources, while remaining intrinsically efficient, fast, intuitive, and safe to use.

Using as a library

This crate exposes the dicom-object crate directly via the object module, which has a high-level API for reading, writing, and manipulating DICOM objects. Other key components of the full library are available in this one as well, albeit representing different levels of abstraction.

An example of use follows. For more details, please visit the dicom-object documentation or the full library documentation.

use dicom::core::Tag;
use dicom::object::{open_file, Result};

let obj = open_file("0001.dcm")?;
let patient_name = obj.element_by_name("PatientName")?.to_str()?;
let modality = obj.element_by_name("Modality")?.to_str()?;
let pixel_data_bytes = obj.element(Tag(0x7FE0, 0x0010))?.to_bytes()?;

Cargo features

This crate enables the inventory-based transfer syntax registry by default, which allows for a seamless integration of additional transfer syntaxes without changing the application. In environments which do not support this, the feature can be disabled. Please see the documentation of dicom-transfer-syntax-registry for more information.

The following root modules are behind Cargo features enabled by default:

  • ul: the DICOM upper layer protocol library
  • pixeldata: the pixel data abstraction library. The Cargo features image, ndarray are re-exported from dicom-pixeldata and may be enabled at will through the parent crate.

If you do not intend to use these modules, you can disable these features accordingly.

Dependencies

~8–19MB
~265K SLoC