The Tracker requires a more reliable internet connection than the aggregated module.frequent outages lead to synchronization failures and loss of data being entered.

Prolonged power outages without backup systems (UPS, solar) and a lack of maintenance for computers or tablets are slowing down adoption.

The server may experience slowdowns ("Bad Gateway”), discouraging users who then have to work late at night or early in the morning.

Trained staff are often transferred, which requires an ongoing training effortto prevent the tool from being abandoned.

Without a robust unique identifier (e.g., National Patient Identifier, NPI), it is difficult to reconcilerecords of patients who change facilities, which skews retention indicators.

Collect only the data strictly necessary for care and reporting indicators. Everyunnecessary field increases the risk of error and the time required for data entry.

Set up automatic alerts and hide irrelevant sections to guide the user and reducecognitive load.

Best practice is to enter data during the consultation. This eliminates double entry (paper then digital) and allows the clinician to use the system’s alerts in real time.

In areas with unstable connectivity, opt for the mobile app that enables offline data entry and automatic synchronization as soon as a network is detected.

Implement weekly routines for deduplication and correction of outlier data

Ensure that screens are not visible to the public and thatsessions close automatically after a period of inactivity.

Create simple visualizations for each site (e.g., graph of expected vs. actual patients today, site viral load clearance rate).

Use the lists generated by the Tracker (e.g., list of alerts for high viral load) as a basis for discussions among the care team.