Patient Scheduling App — Thornridge Health
A patient scheduling app with offline-first sync for low-connectivity clinics, cutting missed appointments 22%.
Industry
Healthcare
Timeline
12 weeks
Team
2 engineers, 1 designer, 1 QA
Category
Mobile App
Where things stood
Thornridge's rural clinics had patchy internet, and the scheduling app they'd tried before would hang or lose changes whenever a connection dropped mid-visit.
How we got there
Offline-first sync engine
Built the app to write to a local store first and reconcile with the server in the background, so a dropped connection never blocks a scheduling action.
Conflict resolution rules
Defined explicit rules for what happens when two staff members edit the same appointment offline, instead of leaving it to silently overwrite.
Field testing at two clinics
Piloted at two low-connectivity clinics for three weeks before wider rollout, fixing sync edge cases the office network never surfaced.
What changed
22%
Reduction in missed appointments
0
Reported data loss from dropped connections since launch
14
Clinics running on the app
Tech stack
React Native
One codebase for iOS and Android so clinics only needed to support one app.
Expo
Over-the-air updates to ship sync fixes without waiting on app store review.
SQLite
Local-first storage so scheduling actions write instantly, connection or not.
Node.js
Handles the sync and conflict-resolution logic between local and server state.
PostgreSQL
The source of truth appointments reconcile back to once a clinic's connection returns.
Twilio
Sends automated appointment reminder texts even to patients without the app installed.
“Our staff don't even notice when a clinic's connection drops mid-appointment — the app just keeps working. That reliability is what we actually needed.”
Elena Ruiz
Clinical Director, Thornridge Health
