Principle of the PeriData Link Mode

The Link Mode is the connection between EMR software and PeriData, that enables PeriData to show the stored visual field data of the current patient. The connection between the perimeter device and PeriData and the import of examination data is independent of the Link Mode and is only established on perimeter workstations.

1: EMR Software - Export and Call: The EMR Software sends a call to the PeriData app (shellexecute). The EMR software hands over the current patient data (name, birthdate, ID) using command line parameters. The EMR software defines the database path and file name and hands it over using a commandline parameter
Specification of the interface:  ONEPAT Link Mode

2: PeriData - Import: (automatically) PeriData starts, and reads the patient data and the database path from the commandline. The patient's database is opened and the stored examinations are shown.

A: PeriData - Database: (stores automatically) Each patient has his own small database on the server. The filename is specified by a commandline parameter. The database is opened at startup. If the file does not exist, it will be created. Some information about the database file structure

3: PeriData - Export: (automatically) Each time when a new examination has arrived from the perimeter and is stored in the database, PeriData writes a message file. These files (.MES) are written into the database directory. They contain the general examination information: Exam-date, time, eye and examination program. The structure is given in the Link Mode specifications.

4: EMR Software - Import: The EMR Software reads the message file, generates a new line in the patient record and deletes the file.

What is the task of the connection with the EMR Software? The IT specialist has to configurate the interfaces 1 and 4 in the EMR Software. PeriData needs no configuration.

How does PeriData know that the patient has changed in the EMR Software? PeriData does NOT know this! If you want to receive or view visual field data of another patient, PeriData has to be called again from the EMR Software. PeriData avoids a second instance, closes the current database and opens the database of the new patient.

Alignment: The file name (recommendation: based on the patient ID) is the only identification criterium between both programs. If the patient name has changed (e.g. by marriage), the ID in the EMR database and therefore the file name do not change. When the PeriData database is opened, the name is checked and PeriData will ask for confirmation of change. If the answer is OK, the patient name in the PeriData database is overwritten and the question will not appear again.

The start behaviour and data import during Link Mode is explained here: Link Mode Behaviour

If the integration is not possible, there is also the option of a parallel installation