What implementation teaches us.

Short essays connecting field experience with the questions that matter for stronger public-health systems.

Digital health · HIV outcomes · Diagnostic networks

Digital health · Scale-up

Scaling DHIS2 is an implementation question before it is a technology question.

DHIS2 can support both aggregate programme reporting and individual-level longitudinal tracking within one platform. Scaling the individual-level function across more than 700 ART sites is not simply a matter of enabling software. Each site operates through people, routines, reporting expectations and local constraints. A technically sound platform can still underperform when workflows are unclear, users lack confidence or support does not respond to implementation realities.

Scale therefore needs to be assessed through more than coverage. Meaningful questions include whether staff use the system consistently, whether the data are complete enough to support follow-up, whether managers act on the information and whether less-resourced facilities experience the same benefits as better-supported sites.

This is where practice becomes a research agenda: adoption, fidelity, sustainability and equity are measurable implementation outcomes. A national digital-health programme becomes stronger when it treats those outcomes as seriously as the deployment count.

Strategic Information · Data quality

A zero in routine programme data is a question—not an answer.

Routine HIV data often contain zeros, sudden drops or patterns that appear immediately important. The temptation is to interpret them as service failure. But a zero can represent no activity, delayed reporting, a misunderstood indicator, an incomplete source document or a data-entry problem.

Responsible performance review separates observation from explanation. The first task is to identify the pattern; the second is to verify it against source records and programme context. Only then should teams decide whether the response is service improvement, documentation support, indicator clarification or system correction.

This discipline protects programmes from acting confidently on weak evidence. It also makes data-quality work more constructive: the objective is not to find fault, but to establish which explanation is true and what action will improve both services and information.

Diagnostic systems · Care continuity

A laboratory result creates value only when the care system can act on it.

Diagnostic systems are sometimes evaluated by whether a test was performed and a result produced. For HIV programmes, that is only part of the pathway. Viral-load information must also move reliably from the analyser to the information system, from the information system to the responsible team and from the responsible team to appropriate clinical action.

Fragmentation at any point can weaken the value of a technically successful laboratory. Interoperability, clear ownership, timely review, complete client identifiers and practical follow-up workflows are therefore part of diagnostic quality—not separate administrative concerns.

This systems perspective is central to my doctoral direction. It creates research questions about result timeliness, data integration, continuity of care, viral suppression and the organisational conditions that allow diagnostic networks to improve outcomes.

Exchange ideas

Working on a related research or implementation question?

I welcome conversations with supervisors, research groups, programme teams and partners exploring how evidence can improve delivery.

Start a conversation