PeriData is capable to send the current patient data (name, first name, birthdate, ID) to the perimeter program. This saves the effort of typing in all the patient data at the perimeter. The perimeter program is started if necessary.
The preparation for the data transfer PeriData >> EyeSuite consists of 2 jobs:
1. EXPORT configuration in Peridata in the menu Extra > Options > Perimeter. The check button send ID must be ON
2. IMPORT configuration in the program EYESUITE:
button "Data >> Perimeter" or key or key
The data of the current patient are sent. If several patients are in the database list the patient under the cursor bar is sent.
EyeSuite is started, if it is not yet running. EyeSuite opens the patient or puts him in the worklist.
This function uses the special folder C:\ PeriDataExchange \ GDT2Perimeter. PeriData writes the file "PERIPERI.GDT" containing the patient data. The perimeter program reads the data and deletes the file. And the batch file "StartPerimeter_Eyesuite.bat" is started.
If the program EyeSuite does not open, the start command in the batchfile has to be changed. It can be adjusted with an editor.
If the patient is not activated in EyeSuite or does not show up in the worklist, and the file "PERIPERI.GDT" is still in the special directory, the Source folder in EyeSuite may be wrong.
Patient ID: The ID (originally from the EMR software) must be send (see above). EyeSuite opens the patient with the matching ID or creates a new record. The patient name is not used for assignment. This behaviour cannot be changed in EyeSuite. - NOTE: If the ID in EyeSuite and the ID in the EMR software do not match, the patient may be duplicated in the EyeSuite database. A missing ID also leads to problems.