Tethr.
A consultant carrying two hundred active patients has one system of record.
Their own memory.
Clinical tools belong to the clinic — the EMR stays at the desk, the appointment book belongs to the receptionist, the billing system is the hospital's. A consultant who works across three practices per week has no system that travels with them. They remember because they have to. They remember which patient mentioned a latex allergy in passing. Which clinic owes them for last Tuesday. Which follow-up was supposed to happen two weeks ago. Most of the time they remember correctly. The times they do not are the ones that matter.
Tethr is the operational layer between the consultant's clinical brain and the reality of working across multiple locations. It holds the things too granular for a calendar, too personal for a billing system, and too important to keep only in memory. The interface is a chat. Not because chat is fashionable, but because a consultant mid-session does not have time to navigate a dashboard. `paid 1500`. `next Monday`. `done`. Commands are short. Responses are scannable. Every morning, a brief arrives: who you are seeing today, who is overdue, who has been stuck too long. Every evening, another: who you saw, what was paid, what still needs following up. When a cycle completes — one treatment episode, deliberately closed — the record is frozen. Issues, diagnosis, revenue. It cannot be edited. The record is what it is.
What people told us
—
“I work across four hospitals. Before Tethr, I was running entirely on memory and habit. Now I actually know where every patient stands.”
Dr. Kavitha Nair, Consultant Rheumatologist
—
“The watch-out field alone is worth it. A patient mentioned a latex allergy once, in passing. Tethr remembered.”
Dr. Arjun Pillai, Consultant Orthodontist
Clinic software belongs to the clinic. Tethr belongs to you. It travels with you across every practice you work from and holds the operational detail that clinic systems cannot — watch-outs, personal notes, payment records, follow-up schedules. The two are not in competition. They serve different purposes.
The commands are short phrases: `paid 1500`, `next Monday`, `done`. Most consultants learn them in the first session. There is no dashboard to navigate, no form to fill in, no interface to explore. Everything happens in a single chat input.
A cycle is one treatment episode — from first contact to deliberate completion. When you type `done`, the current state of that patient is frozen permanently into their timeline: presenting issues, diagnosis, revenue. The timeline is immutable. Completed cycles cannot be revised. The record is what it is.
It shows who you are seeing today, who is overdue by a few days, and who has been stuck for over a week. It is generated from your actual schedule in Tethr, not a calendar integration. It takes ten seconds to read.
Tethr stores what you put into it. It is designed for operational notes — watch-outs, payment records, follow-up dates, brief clinical observations. It is not a replacement for an EMR or clinical documentation system. The distinction is intentional.
That is exactly what Tethr is built for. Patients can be linked to multiple clinics. Finance tracks per-practice revenue. The evening brief breaks down patients seen by clinic. The whole system assumes you are working across locations because that is the reality of consultant practice.
- Historical briefs for any past date (`brief 5 jun`, `brief yesterday`)
- Push notifications at 8:00 AM and 8:00 PM IST
- Revenue notes carried through to the evening brief per patient
- Data export in JSON and CSV
- Beta launch
- Patient, clinic, and task management with cycle model
- Morning and evening briefs
- Immutable timeline on cycle completion
Tethr started as a workaround — a WhatsApp chat one consultant used to message himself reminders about patients.
The search failed, the history accumulated, and the things that mattered disappeared into the noise.
We built Tethr for the gap that clinical tools do not see: the operational layer that belongs to the consultant, not the clinic.
Forgetting is a system failure, not a personal one.
The interface should not require a training session.
The record of a completed cycle is permanent. It cannot be revised.
A brief that shows everything is a brief that shows nothing.
One sentence of input. One scannable response.