Principle of the PeriData Link Mode
Principle of the PeriData Link Mode
PeriData is a flexible program. In case of FULL INTEGRATION with an EMR software, each patient a gets separate database stored on the data server. PeriData is started with the commandline parameter /MODE:ONEPAT. This sets PeriData into the LinkMode. The configuration is determined only by commandline parameters and is in the hands of the EMR software. If the parameters are missing, PeriData starts in normal mode. Information about all 4 installation types
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 database folder on the server is created by the IT technician. The filename is defined by the EMR program (usually the patient ID). Filename and path are handed over as a commandline parameter. The database is opened at startup. If the file does not yet exist (first exam), 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. There is no configuration inside PeriData.
How does PeriData know that the patient has changed in the EMR Software? PeriData does NOT know this! If the patient has changed, PeriData needs a new call from the EMR Software. PeriData changes the database (no second instance). In case of new examination data, PeriData checks the name avoiding the storage to the wrong patient.
Alignment: The file name (recommendation: based on the patient ID) is the only identification criterium between both programs. If the patient name changes (e.g. by marriage), the ID in the EMR database does not change and therefore the file name keeps identical. PeriData always checks the name when the database is opened, and will ask to confirm the 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 are also other installation types