Resolving database replication conflicts in the health care information system project early phase

Considering that any public health care information system is based on a distributed database management system that consists of many dozens distributed databases, and IS itself can consist of at least few dozens of applications, database replication conflicts can make significant problems to administrators in the system implementing phase. All world known database platforms (like Oracle or SQL Server) have implemented methods for establishing and resolving replication conflicts, but even with them, there is a possibility that transaction ends up in the error queue and someone must manually resolve the conflict. This paper presents our approach for resolving replication conflicts as one of major problems of distributed DBMS in an early phase of projecting the system. Our goal was not to wait for replication conflicts to establish and resolve them, but to prevent them at the very start of IS projecting as much as possible.