Terminal Server Architecture

The following description can also be used for CITRIX server

In a terminal server architecture, PeriData is installed only on the server. Multiple access to the app from different users is possible. Multiple access to the data files is also possible. The permission rights are controlled by the option ViewingMode at the viewing workstations. The workstation in the perimeter room needs a special solution. It depends on the mode of transmission (file or RS-232 cable)

Basic settings in the options

At the server, you start PeriData as Admin and make the following settings in the Options (Extra menu)

• Options - Tab General: Viewing Mode = ON (default since V3.7.2.2)
• Options - Tab Perimeter: each USER has his own Perimeter settings = ON. By this setting, the File "PeriWin_Opt_Are_User_Specific.txt" is written into the directory "C:\PeriDataExchange". After that, this switch cannot be reversed. The perimeter settings are now stored into the registry "HKEY_CURRENT_USER".

The following settings are applied only for the "Perimeter Workstations" which are connected to a perimeter and used for data reception

Case 1: Raw data files are stored to the standard import directory "C:\PeriDataExchange" on the terminal pc

This is the easiest case. The perimeter uses FILE export, and one of the following situation is given:

• The perimeter control program is sending data always to this directory (fixed export directory)
• The export directory in the perimeter control program can be configurated, and this directory was chosen
• An auxillary program (move app) moves the raw data from another directory into the standard import directory

1A. LOCAL PC (outsied of the RDP window)

• Create the directory "C:\PeriDataExchange". The PeriData program is NOT installed !
• Check: Perform an export action on the perimeter >> new raw data files (extension *.pdi *.oc1 *.dcm - depending on the type) appear in the directory

Case 2: Raw data files are stored to a directory on the server

Situation:The perimeter uses FILE export, and the export directory was configurated in this way -- IMPORTANT: Each perimeter workstation needs a SEPARATE directory on the server to avoid a data mismatch from different perimeters. The name should define the workstation (user name, location) clearly. Example: ..\Peri_AntwerpZuid_Room3

2A. SERVER

• Create the special directory
• Check: Perform an export action on the perimeter >> new raw data files (extension *.pdi *.oc1 *.dcm - depending on the type) appear in the directory

Case 3: Data are sent via cable

Situation: The perimeter uses cable transmission. The cable is connected with the PC at the COM port or with a USB serial adapter -- In the "Receiver Mode Solution" PeriData is running in TWO instances. On the terminal PC it is running in the "Receiver Mode" and stores the cable data to a raw data file in the IMPORT directory. On the terminal PC Peridata is running in normal mode and imports the raw data file into the database.

After the installation PeriData is running on the local PC in the Receiver Mode (may be minimized) and a second time in the RDP window. The result may look like that (case 3 - CABLE export) :

More situations are possible, e.g. with a serial ethernet adapter (e.g. MOXA). There are also several perimeters of different type at one workstation possible. The installation on different workstations is without problems because the settings are user-specific. Please call our technical support, we will give you advice.

Practical procedure of a data transmission (all cases):

1. RDP window: Start PeriData out of the EMR software >> PeriData is waiting for data

2. Perimeter or perimeter program on the PC, resp.: store a finished examination (triggers automatic data transmission if configurated) - or - open stored examinations and press "Export" or "Send" button >> examinations will appear in the PeriData of the RDP window

FINISHED !