Pre Dicom Import

You might have some process running that uses based dcm4che command line tools to issue a C-MOVE command to download datasets to the application /data folder. The script that runs might look something like this:



mkdir $BASE/$NUM.tmp
dcmqr -L$CALLINGAE@$PORT $TARGETAE -qAccessionNumber=$NUM -cmove $CALLINGAE -cstoredest=$BASE/$NUM.tmp
mv $BASE/$NUM.tmp $BASE/$NUM

In the above, we see that dcmqr is used to call C-MOVE to dump a bunch of dicoms into a folder named based on a number, which is likely an accession number as it is a common query. The last line of the script renames the *.tmp folder by removing the extension, which then notifies the watcher that the folder is done.

Dicom Import

When the watcher detects a FINISHED session directory in the folder being watched (/data in the container, mapping to data in the application base folder on the host), the process of importing the images into the database is started. This means the following steps:

1. Adding Models to Database

Each dicom file is read, and during reading, added as an Image object to the database. The Header Fields and values are added for each image.

2. Saving Dicoms

All files in the folder are assumed to be dicom, as it is the case the extensions may vary. If a file is attempted to be read as dicom fails, a warning is issued and the file skipped, but the process continued. The file is not removed, in case inspection is warranted later (is this how we want it?) (some notification?)

The dicom file itself, when saved to the model, is saved with the application’s media at /images. Once the file is saved here, it is deleted from it’s temporary folder in /data.

3. Finishing Batch

All the images found in a folder are considered to be a “batch,” and when all files for a batch have been added, the batch is finished and available for query.