A clinic operating system, live in three clinics

ELTH is the software a clinic actually runs on. Reception books and checks patients in; nurses take vitals; doctors consult, prescribe and print; pharmacy dispenses against stock; billing invoices and collects; marketing runs the public booking portal, health camps and WhatsApp reminders. Sixty-plus features across nine departments, eight staff and partner roles, and four patient-facing portals — multi-clinic from the ground up.

I did not write the code. My co-founder built and deployed. What I owned was everything upstream of that: sitting with clinic owners, doctors and reception staff to find out what the day actually looked like, turning it into a product decision, designing the interface, and deciding what got built next.

The interesting problems here were never technical. Two receptionists spell the same patient's name three ways, so what counts as a duplicate? A patient pays online for a slot that has already been resold — who is right? Should paying upfront be optional, discounted, or required, and does that answer change per clinic? Those are operations questions with a UI attached, which is the work I have been doing since the juice counter.

The care-programme side — diabetes and weight-loss programmes, coach and nutritionist tooling, GLP-1 titration tracking, a member portal with self-booking — was designed alongside our design-partner clinic, working from their own plan sheets rather than an invented spec. It shipped as a generic programme engine, so the next clinic gets the same machinery with its own content.

The platform is live and in daily use in three clinics. Patients book, pay, get their reminders on WhatsApp and see their reports without anyone at the desk doing it by hand. I led product on it to April 2026.