DICOM Server Configuration

Currently, there are four methods to import DICOM image data into a study database.

1. The PMOD user loads images from disk or CD files and saves them to a study database. This has the advantage, that the user will be listed as data creator in the database. However, be aware that the images in the database will not be the original image data, but objects created by PMOD.
2. The original images are sent to a PMOD DICOM server, which saves the images to a dedicated database. This has the advantage, that the original image data are saved without any modification. However, the DICOM server will be listed as the data creator, so there is no identification possible who introduced the data.
3. Images are dropped into a dedicated directory which is regularly scanned and the data imported into a database. This is a variant of the DICOM server solution and has the same advantages and disadvantages.
4. The data are brought into a database by replication from another database. In this case the user who initiates the replication will be listed as the data creator.

Data Import Recommendation

The following organization is recommended:

1. The dedicated Import database is used as an intermediate data pool from which the data are further distributed to the actual study databases.
2. A PMOD DICOM server process is established which is able to receive image data per DICOM network protocol and saves all received images as original data to the Import database.
3. The dedicated PMOD user ATL_Manager is given access rights to the Import database and all study databases. This user is in charge of moving the received image data to the appropriate study databases, ending up with the original images.

The sections below describe the configuration of the DICOM server to implement this organization.