The loss of examination data can have significant consequences for patient treatment. Backing up the data is therefore a top priority. With today’s technology, an automated daily backup with several safety levels is possible. It is essential that the backup files are located in, or moved to, a directory that is included in the daily institutional data backup routine.
The database of the perimeter device contains the original examination data. The backup is usually set up in the device software.
Recovery in the event of: loss or errors in the device database
The PeriData database contains all the data that PeriData has imported from the device. To set up the backup, ensure that the directory containing the PeriData files is included in the daily institutional data backup routine, or move a copy of the files to that location.
If PeriData is fully integrated intothe medical software, the PeriData files are stored on a server and are included in the server backup. In other set-ups, there is only a single PeriData database comprising two files. For speed reasons, this database is often stored locally on the PC next to the perimeter (receiving PC). A daily copy must be made to the server (institutional data backup area).
With this additional function, a copy of the newly imported data is stored in an additional PeriData database. A new database is created every month. The files are named, for example, “PeridataBackup-Import-2026-03.phf” (and .phd) for March 2026. This backup is performed only on the receiving PC that imports the data.
To set up the backup, an import backup directory must be specified in the Options > Miscellaneous tab. If this field is left blank, no import backup will take place. The directory should be located on the server (institutional data backup area).
Restoration in the event of: loss or errors in the PeriData database AND the PeriData database backup.
Note: Older data is also stored in the month in which the transfer took place. Only data originating directly from a Perimeter device is saved. Data that is transferred to the 'correct' database via copy and paste is NOT additionally backed up to the monthly database.
The original raw data sent by the device to PeriData is deleted after import. With this function, a copy of the original raw data is saved. Each examination is a file whose name identifies the examination (date of birth, patient ID, abbreviated patient name, PERI=perimetry, examination date, examination time, examination method – example: 1991-08-23_ID_1234567890_SOMEBODYJA_PERI_OS_2024-10-04_11-30h_24-2__ZETA.DCM). The file extension corresponds to the original file type, i.e. DCM = OPV-DICOM format, PDI = PDIF format, OC1 = Octopus format, HFA = HFA1/2 format.
To set up the backup, select “Save a copy of the original raw data” in the Options > Miscellaneous tab. The import backup directory must be defined.
Restoration in the event of: loss or errors in the PeriData database AND the PeriData database backup; or loss or errors in the device database -- Option to transfer data to other perimetry programmes that read raw data.