The decimal ElectronRT application supports importing DICOM patients via a DICOM listener/receiver. This guide details the process for enabling and configuring this method of DICOM patient import into the eRT application.

The following guide details how to download, install, and configure the ElectronRT DICOM Receiver to automatically accept and import files into the ElectronRT application for import.

1. Download the ElectronRT DICOM Receiver via
2. Extract the ElectronRT_dicom_receiver.zip file to an appropriate directory of your choosing (e.g.: C:\ElectronRT_DICOM_Receiver)
3. Edit the receiver_config.json file to set the following fields:
   1. local_ae_title: The name of the listener (Note: this is not explicitly enforced, it's only for reference)
   2. local_port: The local port for the listener to monitor on
   3. timeout: The timeout, in seconds, for which to wait for files/connections. The default value is an appropriate setting.
   4. storage_location: The shared network location to save files to that the ElectronRT app will be able to access and monitor (refer to Importing a Patient from a DICOM Receiver for more details on this process within the eRT application)

The ElectronRT DICOM Receiver has two options for running:

The following scripts can be used to add, remove, or restart the Windows Service for the ElectronRT DICOM Receiver.

• service_install.bat
  • Installs the ElectronRT DICOM Receiver as a Windows Service
• service_uninstall.bat
  • Removes the ElectronRT DICOM Receiver from the Windows Services
• service_restart.bat
  • Restarts the Service if changes are made to the configuration file.

The ElectronRT DICOM Receiver can be run as a stand alone application. This option does not require administrative privileges.

1. Open Windows Explorer to the ElectronRT DICOM Receiver installation directory
2. Run the ElectronRT DICOM Receiver.exe to start the receiver as configured

Notes:

• Any time the Computer is restarted (e.g.: windows updates) the stand along application will need to be manually run.
• Any time the receiver_configuration.json file is changed, the application will need to be manually restarted to load the new configuration