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: The Oculus program opens the patient with the matching patient name AND patient ID or creates a new record. If the ID in the Oculus database and the sent ID do not match, the patient is duplicated in the Oculus 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. Then, the check button "send ID" in the Export options is of no importance. It can be ON or OFF, dependent on whether the ID is wished for the Oculus database.