A lightweight and efficient Dicom server to receive and store medical images such as CT, MRI, RX, MG, XRF, XA, NM, PET, US etc., as well as Structured Radiation Dose Reports (non-image SOP classes). The application (C++ compiled) implements the Dicom Storage SCP Service and runs as an automatic MS Windows service (x86/x64 platform Win 7-8-10-11).
-
Can receive medical images and structured reports on radiation dose in Dicom format from company PACS and radiology equipment
-
Multithreaded architecture to handle concurrent client connections
-
Creates a tree-architecture folder system (based on study ID or patient name) for archiving study images. Cabability to create the DICOMDIR directory file.
-
Some simple scripts and files are provided to manage and configure the application as automatic MS Windows system service (24 hrs)
Please read the file ReadMe_DcmStore.pdf for more details and for the installation instructions.
First release available, Sep, 2023 - vers. 1.1
- Possibility to increase the maximum number of worker threads to improve performance in case of concurrent client connections.
- An option that allows image names to be indexed based on the Dicom Image Number tag, as an alternative to the cryptic naming of the image's SOP Instance UID.
- Capability to create the DICOMDIR directory file for each study stored.
- It is now possible to manage a custom list of DICOM images and non-image DICOM objects, read from a configuration file. Negotiation of a set of transfer syntaxes (including compression) with the SCU client application is also enabled. If the configuration file is not found, the server works regularly for a set of default Dicom SOP classes.
- A new option is available that allows you to choose whether to save any Structured Report in a single folder, rather than in a tree structure of subfolders.
- The server attempts to intercept anomalous cases in which images from different acquisitions but belonging to the same study and series are sent by the modality even with the same instance index as other previously stored images. Consequently, a filename splitting mode (extension numbering) has been implemented to prevent overwriting during archiving.This side effect should not occur if files are named using Dicom unique identifiers (UID).
Author: Giacomo Belli - Health Physics Unit – AOU Careggi Florence - Italy