This package provides a set of utilities for extracting data contained in DICOM files into an HDF5 database containing patients' medical images as well as binary label maps obtained from the segmentation of these images (if available). The HDF5 database is then easier to use to perform tasks on the medical data, such as machine learning tasks. It is a higher-level library that builds on the excellent lower-level pydicom library.
Anyone who is willing to contribute is welcome to do so.
Digital Imaging and Communications in Medicine (DICOM) is the international standard for medical images and related information. The working group DICOM WG-23 on Artificial Intelligence / Application Hosting is currently working to identify or develop the DICOM mechanisms to support AI workflows, concentrating on the clinical context. Moreover, their future roadmap and objectives includes working on the concern that current DICOM mechanisms might not be adequate to cover some use cases, particularly bulk analysis of large repository data, e.g. for training deep learning neural networks. However, no tool has been developed to achieve this goal at present.
The purpose of this module is therefore to provide the necessary tools to facilitate the use of medical images in an AI workflow. This goal is accomplished by using the HDF file format to create a database containing patients' medical images as well as binary label maps obtained from the segmentation of these images (if available).
pip install dicom2hdf
pip install git+https://github.com/MaxenceLarose/dicom2hdf
There are 3 main concepts in this code :
PatientDataModel: It is the primarydicom2hdfdata structure. It is a named tuple gathering the image and segmentation data available in a patient record.PatientsDataGenerator: A Generator that allows to iterate over several patient folders and create aPatientDataModelobject for each of them.PatientsDatabase: An object that is used to create/interact with an HDF5 file (a database!). ThePatientsDataGeneratorobject is used to populate this database.
The PatientsDataGenerator has two important variables: a path_to_patients_folder (which dictates the path to the folder that contains all patient records) and a series_descriptions (which dictates the images that needs to be extracted from the patient records). For each patient/folder available in the path_to_patients_folder, all DICOM files in their folder are read. If the series descriptions of a certain volume match one of the descriptions present in the given series_descriptions dictionary, this volume and its segmentation (if available) are automatically added to the PatientDataModel. Note that if no series_descriptions dictionary is given (series_descriptions = None), then all images (and associated segmentations) will be added to the database.
The PatientsDataGenerator can therefore be used to iteratively perform tasks on each of the patients, such as displaying certain images, transforming images into numpy arrays, or creating an HDF5 database using the PatientsDatabase. It is this last task that is highlighted in this package, but it must be understood that the data extraction is performed in a very general manner by the PatientsDataGenerator and is therefore not limited to this single application. For example, someone could easily develop a Numpydatabase whose creation would be ensured by the PatientsDataGenerator, similar to the current PatientsDatabase based on the HDF5 format.
Since this module requires the use of data, it is important to properly configure the data-related elements before using it.
Images files must be in standard DICOM format and segmentation files must be in DICOM-SEG or RTStruct format.
If your segmentation files are in a research file format (.nrrd, .nii, etc.), you need to convert them into the standardized DICOM-SEG or RTStruct format. You can use the pydicom-seg library to create the DICOM-SEG files OR use the itkimage2dicomSEG python module, which provide a complete pipeline to perform this conversion. Also, you can use the RT-Utils library to create the RTStruct files.
This dictionary is not mandatory for the code to work and therefore its default value is None. Note that if no series_descriptions dictionary is given, i.e. series_descriptions = None, then all images (and associated segmentations) will be added to the database.
The series descriptions are specified as a dictionary that contains the series descriptions of the images that needs to be extracted from the patients' files. Keys are arbitrary names given to the images we want to add and values are lists of series descriptions. The images associated with these series descriptions do not need to have a corresponding segmentation volume. If none of the descriptions match the series in a patient's files, a warning is raised and the patient is added to the list of patients for whom the pipeline has failed.
Note that the series descriptions can be specified as a classic dictionary or as a path to a json file that contains the series descriptions. Both methods are presented below.
Using a json file
Create a json file containing only the dictionary of the names given to the images we want to add (keys) and lists of series descriptions (values). Place this file in your data folder.
Here is an example of a json file configured as expected :
{
"TEP": [
"TEP WB CORR (AC)",
"TEP WB XL CORR (AC)"
],
"CT": [
"CT 2.5 WB",
"AC CT 2.5 WB"
]
}Using a Python dictionary
Create the organs dictionary in your main.py python file.
Here is an example of a python dictionary instanced as expected :
series_descriptions = {
"TEP": [
"TEP WB CORR (AC)",
"TEP WB XL CORR (AC)"
],
"CT": [
"CT 2.5 WB",
"AC CT 2.5 WB"
]
}It is important to configure the directory structure correctly to ensure that the module interacts correctly with the data files. The patients folder, must be structured as follows. Note that all DICOM files in the patients' folder will be read.
|_📂 Project directory/
|_📄 main.py
|_📂 data/
|_📄 series_descriptions.json
|_📂 patients/
|_📂 patient1/
|_📄 ...
|_📂 ...
|_📂 patient2/
|_📄 ...
|_📂 ...
|_📂 ...
The easiest way to import the package is to use :
from dicom2hdf import *This will import the useful classes PatientsDatabase and PatientsDataGenerator. These two classes represent two different ways of using the package. The following examples will present both procedures.
This file can then be executed to obtain an hdf5 database.
from dicom2hdf import PatientsDatabase
patients_database = PatientsDatabase(
path_to_dataset="data/patient_database.h5",
)
patients_database.create(
path_to_patients_folder="data/Patients",
tags_to_use_as_attributes=[(0x0008, 0x103E), (0x0020, 0x000E), (0x0008, 0x0060)],
series_descriptions="data/series_descriptions.json",
overwrite_database=True
)The created HDF5 database will then look something like :
This file can then be executed to perform on-the-fly tasks on images.
from dicom2hdf import PatientsDataGenerator
import SimpleITK as sitk
patients_data_generator = PatientsDataGenerator(
path_to_patients_folder="data/Patients",
series_descriptions="data/series_descriptions.json"
)
for patient_dataset in patients_data_generator:
print(f"Patient ID: {patient_dataset.patient_id}")
for patient_image_data in patient_dataset.data:
dicom_header = patient_image_data.image.dicom_header
simple_itk_image = patient_image_data.image.simple_itk_image
numpy_array_image = sitk.GetArrayFromImage(simple_itk_image)
"""Perform any tasks on images on-the-fly."""
print(numpy_array_image.shape)You can find more in the examples folder.
- Generalize the use of arbitrary tags to choose images to extract. At the moment, the only tag available is
series_descriptions.
This code is provided under the Apache License 2.0.
@article{dicom2hdf,
title={dicom2hdf: DICOM to HDF python module},
author={Maxence Larose},
year={2022},
publisher={Université Laval},
url={https://github.com/MaxenceLarose/dicom2hdf},
}
Maxence Larose, B. Ing., [email protected]