●       This document outlines all the requirement definitions to allow remote HF site admin users to monitor the database events being sent/synchronized from the SESP HF remote site/database (sender) to the SESP central site/database (receiver) using the DBSync web console.

●       The BDSync Sender UI will be accessed by the remote sites for the purposes stated on the section 1.1 Objective.

●       The Sender UI will allow only the visualization of DBSync events for monitoring purposes, and no patient demographic or clinical data will be displayed on the DBSync Sender UI. 

●       The dashboard provides the ability to see OpenMRS database changes which requires one to be familiar with the OpenMRS database structure. It is not user friendly. If one is registering a patient for ART services, and entering a ficha resumo, unless one is familiar with the database structure, it will be impossible to know if the database changes were synchronized from the HF to the central provincial server. Therefore, the ability for clinical partners to validate the data is being transmitted, is noted in an SOP, which recommends clinical partners identify a few low volume health facilities and generate PEFPAR MER and MISAU Resumo Mensal reports at the HF level and for the HF at the central provincial server for the same time period to see if the results match. This is a separate SOP and is outside the scope of this document.