Data is transferred from the HFA3 to PeriData using a FILE. The HFA3 exports the file to a defined folder. PeriData reads the file from this folder and then deletes it afterwards. There are 2 important details to note here:
The HFA3 is able to export different types (formats) of DICOM files. All of them have the similar file extension .dcm, but differ internally. The difference is only noted when the file is read/opened. Only the format DICOM-OPV contains utilisable visual field data and is suitable for PeriData.
Non-fitting DICOM formats: DICOM-EPDF (embedded PDF) is a PDF wrapped into a DICOM container. HFA3 Format is a proprietory Zeiss format with unpublished structure. If PeriData finds a not-fitting DICOM file in the import folder, it gives a notification "wrong SOP class" and deletes the file
The HFA exports (writes) the DICOM OPV files to a specified folder. The HFA software requires that the folder must be mapped for this purpose. To ensure that the mapping always works, it is best to create the Exchange folder on the HFA3 itself. It is shared on the network and then mapped as a network drive. The PeriData app on the receiving PC in the perimeter room accesses the folder via the UNC path, reads the files, and deletes them.
NOTE: An Exchange directory on the receiving PC or a server is possible, but has the disadvantage that the mapping is unstable if the external PC is not running when the HFA is started. In addition, the mapping on the HFA must be changed when switching PCs. For this reason, we have been recommending the above configuration since 2024, which does not need to be changed during the lifetime of the HFA3.
Pitfall: In the "Report Export Location" field where you select the mapped drive, it is also possible to enter a UNC path or connect a network drive. However, this can cause problems. Therefore, the previously mapped drive letter must always be entered.