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 >> OCULUS consists of 2 jobs:
1. EXPORT configuration in PeriData > Options
2. IMPORT configuration in the program OCULUS "GO.EXE"
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.
This function uses the directory 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_Oculus.bat" is started.
If the OCULUS program (GO.EXE) does not open, the path in the batchfile may be wrong. It can be adjusted with an editor.
Patient ID: It may occur that the ID in the perimeter and the ID in the EMR system do not match. Then, the patient could be doubled in the perimeter database. This conflict can be avoided by a change in the file "GO.XML". Change this element to True: <GDTignoreID>True</GDTignoreID> and restart the Oculus program -- Sometimes it may help to switch off the "send ID" option in the PeriData Options.