● Live · one clinic · ELTH — clinic operating system · case file 08
A clinic operating system, live in one clinic
Led product on a clinic operating system now live in one clinic — 60+ features across nine departments, eight staff and partner roles, four patient-facing portals.
Overview
Led product on a clinic operating system now live in one clinic — 60+ features across nine departments, eight staff and partner roles, four patient-facing portals.
My role
Co-founder · Product & UI lead
Team
- GA
- NV
Ganesh A · Nikith Vijay
Built with
Figma · Claude Code
Timeline
2025 — Apr 2026
Live · one clinic

● Impact overview
- One clinic runs on itReception, nursing, doctors, pharmacy and billing moved onto one system. Three went live; one runs it daily and takes the product over in a month or two.
- Sixty-plus features, nine departmentsRequirements taken from doctors and front-desk staff, turned into a build order, and shipped feature by feature while the clinic kept seeing patients.
- Patients in the loopFour patient-facing portals: patients book, pay, get their reminders on WhatsApp and see their reports without anyone at the desk doing it by hand.
01
What it is
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.
02
My half of it
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.
03
Built with the clinic, not for it
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.
04
Where it stands
Three clinics went live. Two have since been pulled back, and the platform is in daily use in one, which takes the product over in a month or two. 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.
05
In pictures

















06
What’s inside
- Appointments
- Patient records
- Consultations and prescriptions
- Vitals and labs
- Pharmacy stock
- Invoicing, split payments and online prepay
- Public booking portal
- Health camps
- WhatsApp and email reminders
- QR feedback with NPS
- Care programmes and member portal
- Multi-clinic tenancy, roles and audit logs
Total: 60+ features
07
