Industry

Paper First, Offline Often: 8 Data Rules for Community Health Worker Programmes

Community health workers reach people no clinic can, and much of what they record starts on paper or on a phone with no signal. This guide covers the 8 data rules that decide whether that work reaches the people who plan, fund and run health programmes.

Suhina Singh
Suhina Singh
Founder & CEO, Jonda Health
November 20, 2026
·
11 min read

In many countries, the first and sometimes only contact a family has with the health system is a community health worker. They test for malaria, measure children for malnutrition, follow up pregnancies, check blood pressure, refer people to clinics and record what they see. The World Health Organization (WHO) guideline on community health worker programmes recognises their substantial potential, while noting that support for them and their integration into health systems remains uneven across and within countries.1

Data is a large part of that integration. What community health workers record shapes how programmes find gaps, target resources, report to funders and show impact. Yet it often starts in a paper register, passes through a supervisor's tally sheet, and reaches a national system weeks later, if it reaches it at all. As programmes move from donor funding to national ownership, and as governments digitise their health systems, the quality of community data matters more than ever.

This guide is written for national programme managers, implementing partners and NGOs, and the teams that build tools for community health workers. It is organised in three parts: capturing data in the field, making it accurate and connected, and keeping it trustworthy.

 

Household visit tests, measurements, counselling, referral CHW record phone app (offline) or paper register Health facility referrals, supervision, monthly summaries National DHIS2 and other national systems never synced or never transcribed duplicated or unlinked people referrals never closed, totals differ Every hand-off is a chance for data to be delayed, duplicated, changed or lost.

Figure 1. Community health data travels from a household visit, through a community health worker's phone or register and a health facility, to national systems such as DHIS2 (District Health Information Software 2). The pink markers show where it is most often lost along the way: records never synced or transcribed, people duplicated or not linked, and referrals or totals that never reconcile.

 

Figure 1 shows the journey this guide follows. Each of the 8 rules below is about one of these hand-offs, or about the trust that holds the whole chain together.

 

Part one

Capturing data in the field

1. Design for the worst connectivity day

A tool that works well in a city office can fail in a village with no signal. Community health tools need to work fully offline, including the checks that catch mistakes. The DHIS2 Android Capture app, for example, is built to work fully offline: users can capture data, run validations and apply programme rules without a network connection, and synchronisation happens later.2

Offline work raises its own questions. What happens when the same person's record is updated on two devices before either syncs? How long can data safely sit on a phone? What does a worker see when a sync fails? Agree the answers before rollout, test them in the places with the worst coverage, and give supervisors a simple view of which devices have not synced recently.

 

2. Plan for paper, because it is not going away

Even in digital programmes, paper stays: registers kept as a back-up, tally sheets for monthly reporting, referral slips carried by patients, and forms used when a phone is broken or a battery is flat. Many programmes are still mostly paper-based, and years of historical records exist only on paper.

Treat paper as a data source, not a failure. Use standard forms with clear boxes, so they can be read consistently. Where registers are photographed, turn the photo into structured data rather than storing it as an image nobody will search. Link each record to a person and household, and flag anything unclear for review. A study in South Africa that compared paper and phone-based systems for community health workers found that only 40 per cent of workers consistently achieved more than 90 per cent accuracy when transferring data on paper.3 Paper is not going away, so the route from paper to data has to be reliable.

 

3. Identify people without relying on a national ID

Following people over time is what turns visits into care: a child's growth, a pregnancy through to delivery, a referral through to treatment. In many communities, people do not have a national ID number, names are spelt differently by different workers, and dates of birth are estimated.

Use a household-based identifier alongside personal details, record how each person is related to the household head, and capture a phone number or national ID where one exists without making it required. When records reach the facility, match them on several details rather than name alone, and send uncertain matches to a person to confirm. Without this, one child becomes three records and coverage figures become impossible to trust.

 

4. Keep forms short and standard

Every extra question costs time in a household visit and adds a chance of error. Research in Malawi found that the quality of data collected by health surveillance assistants improved markedly after the data collection instruments were adjusted and their workload reduced.4

Agree a minimum dataset that serves the programme's decisions, align it with national and WHO indicator definitions, and resist adding fields for one-off requests. Where several partners run programmes in the same area, aim for one shared form rather than a different form for each funder. A shorter form completed well is worth more than a long form completed partly.

 

Part two

Making data accurate and connected

5. Capture point-of-care readings reliably

Community health workers increasingly use rapid diagnostic tests (RDTs), thermometers, blood pressure monitors, glucometers and arm-circumference tapes. Each produces a reading that has to be interpreted and written down correctly. Faint lines on a test cassette are easy to misread, and numbers copied from a device screen are easy to mistype.

 

1. Photograph C T test cassette or device screen 2. Read automatically result: positive, negative or invalid status: clear or unclear linked to person, worker, date and location 3a. Clear result recorded and counted photo kept as evidence 3b. Unclear result faint line, blurred photo: flagged for review

Figure 2. A photo taken at the point of care becomes a reviewed result. The photo is read into a result with a status, linked to the person, worker, date and place. Clear results are recorded, unclear ones (a faint line, a blurred image) are flagged for review, and the photo stays as evidence for supervision.

 

Figure 2 shows an approach that is gaining ground. Taking a photo of the test or device screen creates a record that can be read consistently and reviewed later. In one field evaluation with community health workers in Kenya, a smartphone-based reader called RDTScan achieved 96.3 per cent accuracy compared with expert interpretation of malaria tests.5 In Rwanda, Jhpiego, Audere and the Rwanda Biomedical Center have worked with community health workers on an AI-supported app for malaria testing that also generates real-time surveillance data.6 Whatever tool is used, keep the photo, record whether the reading was clear, and send unclear results to a person.

 

6. Connect community data to facility and national systems

Community data is most useful when it joins up with the rest of the health system. That means referrals that close the loop (did the child who was referred reach the clinic, and what happened?), and community activity that shows up in national reporting rather than sitting in a separate system. DHIS2, for example, supports community health workers capturing data on the same platform used for facility reporting, or reporting basic data by SMS where smartphones are not available.7

Whether community data is captured directly in the national system or in a separate tool, three things decide whether it connects: shared indicator definitions, identifiers that link the same person across community and facility records, and a mapping from the programme's data to national indicators that is written down and maintained. Where several tools and partners feed the same system, structure and map their data to one agreed model before it is loaded.

 

Part three

Keeping data trustworthy

7. Check quality where data is captured, not only at the end

Data quality problems in community programmes are well documented. A mixed-methods study in Kenya and Malawi found that only 15 per cent of data was reported consistently between community health workers and their supervisors, and identified barriers including missing data collection tools, inadequate training and supervision, a lack of quality control and incomplete registers.8 In Rwanda, a study of 204 community health worker registers found composite accuracy of 61 to 72 per cent across health centres when registers were compared with household interviews and client records.9

 

Kenya and Malawi: data reported consistently, CHW to supervisor 15% Regeru et al., Health Policy and Planning, 2020 Rwanda: composite accuracy of CHW registers, by health centre 61 to 72% Journal of Community Health, southern Kayonza study (range across health centres)

Figure 3. Two studies of community health data quality. In Kenya and Malawi, only 15 per cent of data was reported consistently between community health workers and their supervisors. In Rwanda, the composite accuracy of community health worker registers ranged from 61 to 72 per cent across health centres. The lighter part of the second bar shows the range.

 

As Figure 3 shows, the gap between what happens in households and what reaches reports can be large. The same Kenya and Malawi study found that supportive supervision was highly valued as an enabler of data quality.8 Build simple checks into the tool (impossible values, missing required fields, a visit dated before a birth), review a sample of records against registers or households routinely, and give workers and supervisors feedback they can act on. WHO's Data Quality Review toolkit sets out standard measures, including completeness, timeliness and consistency, that programmes can adapt.10

 

8. Protect people's data on shared and lost devices

Community health workers carry sensitive information about whole households: HIV status, pregnancies, mental health, family planning. Phones are shared with family members, lost on long journeys and occasionally stolen. Paper registers sit in homes and health posts.

Encrypt data on devices, require individual logins rather than shared accounts, limit each worker's access to their own households, and remove data from devices once it is safely synchronised where the programme allows. Explain to households what is recorded and why, and follow national rules on consent and on where health data is stored and processed. Many governments now expect health data to stay in country, and programmes moving from donor funding to national ownership need data arrangements that will satisfy them.

 

The community health data checklist

Table 1 brings the 8 rules together for programme, technology and monitoring and evaluation teams.

 

#RuleWhat good looks like
1Worst connectivity dayFully offline capture and checks, clear sync and conflict rules, visibility of devices not synced
2Plan for paperStandard forms, photos turned into structured data, records linked to people, unclear items flagged
3Identify peopleHousehold identifiers, relationships recorded, matching on several details, uncertain matches confirmed
4Short, standard formsA minimum dataset aligned with national and WHO indicators; one shared form where possible
5Point-of-care readingsPhotos of tests and screens kept, readings recorded with a status, unclear results reviewed
6Connected systemsReferrals that close the loop; data mapped to national indicators and systems such as DHIS2
7Quality at captureBuilt-in checks, routine sample reviews, supportive supervision and feedback
8Privacy on devicesEncryption, individual logins, limited access, data removed after sync, national rules followed

Table 1. A checklist of the 8 data rules for community health worker programmes.

 

The thread running through all 8 rules: design for the conditions community health workers actually work in, and make every hand-off from household to national system one that keeps the data intact.

 

How Jonda Health can help

Programmes usually come to us at one of two moments. Some are planning a new digital tool, a transition from donor funding or a move to national systems, and want the data design right from the start. Others have years of paper registers and records from several tools, and need them turned into data a national system can use. We support both.

Jonda Health Services
Design programme data that holds up
  • Minimum dataset and form design aligned with national and WHO indicators
  • Data flow design from household to facility to national systems, including identifiers and referral loops
  • Planning for paper registers and historical records, starting with a sample
  • Privacy and data-flow design, including in-country processing and what to pseudonymise
  • Data quality checks and review processes that fit supervision in practice
JondaX
Turn field records into usable data
  • One API for photographed paper forms, lab reports, medical device readings and digital exports
  • AI and machine vision with clinical review built in for anything flagged
  • Harmonisation and mapping to medical coding standards, or to your programme's own code sets
  • Structured, standards-based output that can feed national systems
  • Can be deployed and processed fully in country; ISO 27001 certified and designed to comply with HIPAA, GDPR and PDPA

 

JondaX has processed more than 500,000 files and 26 million data points at 99.9 per cent field-level accuracy, across more than 10 languages including French. It already turns photographed medical device readings into data for a chronic disease programme run with an insurer in Africa. Because register and form layouts differ between programmes, the most useful first step is a sample run on a set of your own forms, so you can see how they perform before committing to anything.

 

Book a free 30-minute data readiness conversation

Tell us about your programme, your tools and the paper you hold. We will help you work out where to start and what it will take.

 

Frequently asked questions

 

Why is data quality a challenge in community health worker programmes?

Community health workers often work on paper, without reliable connectivity, with long forms and limited supervision, and their data passes through several hands before it reaches a national system. A study in Kenya and Malawi found that only 15 per cent of data was reported consistently between community health workers and their supervisors.8

 

Can community health workers collect data offline?

Yes. Tools such as the DHIS2 Android Capture app are built to work fully offline, including validations and programme rules, and synchronise when a connection is available.2 Programmes still need clear rules for what happens when the same record is changed on two devices before syncing.

 

How can paper registers from community health workers be digitised?

Paper registers and forms can be photographed and turned into structured data, rather than stored as images. This works best when forms are standard, photos are taken with simple guidance, each record is linked to a person and household, and anything unclear is flagged for review rather than guessed.

 

Can a smartphone read a malaria rapid diagnostic test?

Research systems have shown this can work. In one field evaluation with community health workers in Kenya, a smartphone-based reader achieved 96.3 per cent accuracy compared with expert interpretation.5 Photos of test cassettes also create a record that supervisors can review later.

 

How does community health data reach national systems like DHIS2?

Community data can be captured on the same platform used for facility reporting,7 or captured in a separate tool and then structured, checked and mapped to national indicators before it is loaded. Either way, programmes need agreed indicator definitions, identifiers that link people across levels, and quality checks along the way.

 

How should community health programmes protect personal data on mobile devices?

Devices are shared, lost and stolen, so data on them should be encrypted, protected by individual logins, limited to what each worker needs and removed once synchronised where possible. Programmes should also follow national rules on consent and on where health data is stored and processed.

 

References

  1. World Health Organization. Selected highlights: WHO guideline on health policy and system support to optimize community health worker programmes. 2018. who.int
  2. DHIS2. Android implementation: executive summary. docs.dhis2.org
  3. Development of a cell phone-based and paper-based monitoring and evaluation system for community health workers in South Africa. PMC4150556
  4. Completeness of child health records in the community health information system in Ethiopia, citing Admon et al. 2013 on Malawi. Maternal and Child Health Journal. 2020. link.springer.com
  5. Park C, Ngo H, Lavitt LR, et al. The Design and Evaluation of a Mobile System for Rapid Diagnostic Test Interpretation. Proceedings of the ACM on Interactive, Mobile, Wearable and Ubiquitous Technologies. 2021;5(1). ubicomplab.cs.washington.edu
  6. Jhpiego. Using artificial intelligence to ensure the right people receive malaria meds. jhpiego.org
  7. DHIS2. DHIS2 for community health. dhis2.org
  8. Regeru RN, Chikaphupha K, Bruce Kumar M, Otiso L, Taegtmeyer M. 'Do you trust those data?': a mixed-methods study assessing the quality of data reported by community health workers in Kenya and Malawi. Health Policy and Planning. 2020;35(3):334 to 345. researchonline.lshtm.ac.uk
  9. Community health worker data accuracy in household registers, southern Kayonza, Rwanda. Journal of Community Health. doi.org/10.1007/s10900-014-9977-9
  10. World Health Organization. Data Quality Assurance (DQA) and Data Quality Review toolkit. who.int

 

About the author. Suhina Singh is the Founder & CEO of Jonda Health, a health data infrastructure company that turns fragmented clinical data, digital and non-digital, into structured, standardised information that clinicians and systems can actually use. Jonda Health is ISO 27001 certified and works with health programmes, ministries, laboratories, hospitals and digital health companies. Get in touch at hello@jonda.health.

Try JondaX free

30 free transformations. No credit card required.