Zeiss Humphrey II-i series, User Manual

Page: 356 / 580

Networking
Humphrey Field Analyzer II-
i
series User Manual 2660021145640 A
14-18
Synchronizing Databases on Two or More HFA II-
i
Perimeters
It is possible to synchronize multiple HFA II- i instruments with each other using your HFA-NET Pro
software. Synchronization is the process of ensuring that each HFA II-
i
in the office has the same
database after synchronization.
Note: DICOM Gateway 2.0 allows saving and retrieving raw exam data to and from a DICOM
archive which acts like a “central database”. Using DICOM Gateway 2.0, automatic or manual
archiving and synchronization of patient records is not needed as there is only one database (the
DICOM archive) that all HFAs save to and retrieve from. See
Appendix (H) for more information.
CAUTION: HFA II-i series system software 5.x creates a different database structure
that is not fully compatible with previous software releases. You can only synchronize
an HFA II-i version 5.x instrument with other HFA II-i version 5.x instruments.
WARNING: Every patient has an identifier that consists of Name, Date of Birth, Patient
ID, and Issuer of ID. To avoid unintentional automatic merging of patient records,
VERIFY a unique combination of Name, Date of Birth, Patient ID, and Issuer of ID
exists when patients are copied, transferred, retrieved from an archive, or restored
from a backup. There is no way to separate the combined records of erroneously
merged patients. Automatic merging of patient records occurs when a patient exists
in the local database with the EXACT SAME Name, Date of Birth, Patient ID, and
Issuer of ID as a patient that is copied, transferred, retrieved from an archive, or
restored from a backup.
For example, consider the following scenario:
Patient A: This patient is currently on the local HFA database and was automatically
assigned a unique Patient ID by the instrument because it was a blank field prior to a
software upgrade to V5.x software or during an import to the HFA through a copy,
transfer, retrieval from archive, or a restore from backup.
Patient B: This patient is about to be transferred to the local HFA database and has
the same Name and Date of Birth as Patient A, but does not have a Patient ID (i.e.
field is blank). When Patient B is copied, transferred, retrieved from an archive, or
restored from a backup to the local HFA database, Patient B will automatically be
assigned the same Patient ID and Issuer of ID as Patient A, and Patient B will be
merged with Patient A.
Synchronization consists of moving data from two or more perimeters into a centralized archive on
the network server. This function is known as “archiving.” Once all the data is gathered on the file
server, it can be retrieved back to any or all of the perimeters from which various portions of the
overall data originated. This function is known as “retrieving.” In this way, the data sources are
synchronized, so that each perimeter contains the same data as all the other perimeters.
The first archiving that is performed will archive the entire database from the HFA II-
i
hard disk to
the server. This should be done for each HFA II-
i
in the network. Subsequent archiving operations
will archive only new data that has been collected since the last archiving was completed.