Closed-Loop Patient Referral Tracking Between Village Health Workers and District Hospitals
When a village health worker refers a patient to a hospital, nobody usually finds out whether the patient arrived, what happened, or whether follow-up is needed. Build an offline-first referral app and a simple hospital desk screen that close the loop: referral slip with a short code, arrival check-in, outcome note and a follow-up task back to the worker. Measure how many referrals get an outcome recorded.
Intermediate
A small team, or one strong student willing to learn something new.1 semester · 2 to 3 students
7 to ship
4 optional extrasSuggested stack
What you should ship
- A referral form for health workers that works offline and generates a short referral code and printable or SMS slip
- A hospital desk screen where staff look up the code, mark arrival and add a short outcome
- Automatic follow-up tasks back to the referring worker after discharge
- Reminders when a referred patient has not arrived after an agreed time
- A sync design that handles conflicts when several devices edit the same referral
- A dashboard of referral completion rates by area and reason
- A test with simulated referrals across several devices going on and offline
If you have time left
- Integration with an existing health record through FHIR resources
- Transport help requests for urgent referrals
- Language switching between English and a local language
- Analysis of where referrals are lost: never left home, never arrived, or no outcome recorded
The problem: referrals that disappear
Community health workers refer pregnant women, sick children and people with suspected TB to larger facilities. In many districts in South Asia and Africa, the referral is a handwritten slip. The worker rarely learns whether the patient went, what the hospital found, or whether she should visit afterwards. Hospitals see patients arrive with no context. Patients fall through the gap, especially when travel is expensive.
What already exists and the gap
- DHIS2 Tracker, OpenMRS and the Community Health Toolkit can model referrals inside large deployments.
- Hospital information systems record admissions but rarely link back to the community worker.
- WhatsApp groups are used informally, with no structure and serious privacy problems.
The gap is a light, focused tool for one job: send a referral, confirm arrival, record the outcome, trigger follow-up. It should work on cheap phones with weak signal and need almost no training at a busy hospital desk.
Inspiration
The WHO "Classification of Digital Health Interventions" (2018) lists referral coordination and tracking as distinct functions that digital tools should support, because so many health systems lose patients at that step. Use it to describe what your system does in standard terms.
What you build
- Health workers create a referral in under a minute, offline, and see its status later.
- Hospital desk staff enter a code, see why the patient was sent and record a short outcome.
- District managers see completion rates and where referrals are lost.
The technically interesting part
- Offline sync. Referrals are created offline and updated on another device. Design identifiers, timestamps and conflict rules carefully, and test them with devices dropping off the network.
- Short codes. Patients may only have a slip or an SMS. Codes must be short, hard to mistype and unique.
- Minimal data. Store only what the referral needs. Think about who can see a patient's name.
- Measuring the loop. Define each step clearly so the dashboard numbers mean something.
How to evaluate it
- Sync correctness: no lost or duplicated referrals across 1,000 simulated edits with random disconnections.
- Completion rate in a role-play exercise with students acting as workers and desk staff.
- Desk time: seconds to find and update a referral.
- Error rate of code entry.
Suggested plan
- Weeks 1 to 3: map the referral journey, with a public health student or doctor if possible.
- Weeks 4 to 8: mobile app, offline storage and sync.
- Weeks 9 to 11: hospital desk screen, reminders and follow-up tasks.
- Weeks 12 to 15: dashboard, testing, report and demo.
Path to a product
Health programmes, NGOs and private hospital networks all care about referral completion, and donors often ask for it as a measure. A small, reliable referral module that can connect to bigger systems through FHIR is a realistic product. The offline sync work is also strong evidence for mobile engineering roles.
Scope warning
Use simulated patients only, unless you have ethics approval and a partner facility. Do not build a full health record. Keep the clinical content to the reason for referral and a short outcome.
Learn what you need on Sefism
- Mobile roadmap: offline-first apps and sync.
- Backend roadmap: APIs and conflict handling.
- SQL and databases roadmap: modelling referrals and their states.
- Flutter documentation: building the phone app.
- PostgreSQL tutorial: the server database.
Get help with this idea
Offline sync is where these projects break. Tauseef can help you design the data model and the test that proves no referral is lost. If you are new here, create a free account first.
Ideas and guidance, not finished projects
These are project ideas and scoping guidance, published free for students to use as a starting point. I do not build, write, or sell final-year projects, and I do not complete coursework for anyone. Take an idea, make it yours, and build it.
Not sure this one fits you?
I help students pick an idea that matches their skills and their deadline, then scope it down until it is finishable. Guidance only, never done for you.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
Follow along
New writing, resources and project ideas land here first.