Not an HMSThe revenue layer above the one you already run — orchestration for hospitals, health aggregation for employers.See the difference →

For Indian clinics, 1–5 doctors

Your day book records what came in.
Not what should have.

A five-doctor OPD practice does not have a claims problem. It has four leaks that never produce a transaction — so nothing in a cash book shows them, and they persist for years.

FREE · DAY BOOK · FREE
● Walk-ins in order
● Calendar one view
● No-show risk flagged
✓ the desk stops arbitrating
What happens nowThe version everybody runs, on paper
Where it failsThe step nobody owns
What to changeOne thing, this week

The four leaks

None of them produce a transaction.
That is why they survive.

Follow-ups nobody chased
None of them produce a transaction — which is why nobody notices.
01The balance nobody wrote down

A consultation is ₹600. The patient pays ₹500 and says they will bring the rest. In a paper system that intention survives about four hours. Most of this money is collectable — it is simply forgotten by both sides.

02The follow-up nobody booked

“Come back in two weeks.” The patient nods and leaves. Nothing records that a follow-up was intended, so there is nothing to chase. This is the largest of the four and the least visible.

03No-shows against a full book

Commonly 15–30%, higher for follow-ups. A slot that goes unused displaced a patient who would have attended. What matters is notice, not politeness — a cancellation 24 hours out is refillable.

04Procedures done, not billed

A dressing or an injection during a consultation that was already being paid for. Trivial individually. Not across a year — and only visible if the clinical record and the bill are the same record.

The product

Twenty-seven modules and an assistant.

Named after what the work is called, not after where it sits in an org chart.

Why these names →

What you run it on

The whole practice, in one record.

OPD queue and consultationVitals, SOAP notes, and a token queue the front desk can actually run at eleven in the morning.
Prescriptions the patient can readVernacular output in Hindi, Marathi and Tamil, with allergy gating before it prints.
Coding without a coderIndian clinical shorthand resolved offline in about a millisecond. “Sugar”, “koch’s” and “kamzori” all land on the right code.
Billing joined to the recordA procedure in the notes and no line on the bill becomes a flag, not a loss.
Balances that follow the patientAn unpaid amount surfaces at the next visit, which in an OPD practice with regulars is usually within weeks.
ABHA linking at the deskConsent capture a receptionist can complete in a queue, not a process that needs a specialist.

Getting started

Live the same week.

Days 1–2Single clinic

Records migrated from spreadsheets or your current system, doctors and staff set up, prescriptions and billing running. A single-doctor practice can be live the same week.

First monthThe numbers you could not produce before

Outstanding balances over 30 days. No-show rate by doctor and slot. Advised follow-ups against booked follow-ups — a number most clinics cannot produce at all.

When you growNothing to migrate again

The clinic tier runs the same platform as the hospital tiers. Adding beds or branches changes the plan, not the software.

Deployments

Clinics running this today

Anonymised by agreement — no names, no logos. What is shown is the mechanism that was put in place.

4 doctors · Indore, Madhya PradeshUncollected balances and unbooked follow-ups
  • Patient balance persists against the record
  • Advised follow-ups tracked against booked ones
  • Procedure recorded in notes reconciled to the bill
2 doctors · Kochi, KeralaImmunisation recall and no-shows
  • Recall schedule generated from the record
  • Reminders timed for notice, not politeness
  • No-show rate reported by slot and doctor
5 doctors · Nagpur, MaharashtraCoding time per encounter
  • Indian clinical shorthand resolved offline
  • Clinic-specific phrases learned after two uses
  • Unspecified catch-all codes flagged

All 22 deployments →

Built to standards, not to a demo

ABDMABHA linking, consent flows
FHIR R4Records and claim bundles
NHCXBundles built & validated
DPDPConsent and purpose limitation
Indian data centresHosted in Indian data centres
Offline codingNo API key, no per-call cost

What a day book records, and what it misses

The day book

  • Who came in
  • What they paid
  • Nothing about who did not come
  • Nothing about who should have

What you also need

  • Who cancelled and was never replaced
  • Who was told to come back and did not
  • Which slot has stood empty three weeks running
  • Which patient has not been seen since March
Emptya slot nobody refilled is the cheapest thing to fix and the least noticed
Freethe whole patient-facing half, permanently
1record per patient, across every clinic they visit on Drapto
Calendars per doctor
Rooms and walk-in queue
Waitlist, automatic
Family booking on one number
Prescriptions in plain words
Follow-ups raised and chased

What we will never do

Things we have promised not to do

  • Take a cut of a consultation fee
  • Charge per appointment
  • Sell a position in the directory
  • Host star ratings
  • Move a free thing behind the paywall

How we are actually paid

  • Hospitals, for revenue integrity
  • Companies, for corporate health
  • Labs and pharmacies, for their modules
  • Implementation, because it is somebody’s week
  • Nothing from a patient, ever

One room or two hundred beds.

A solo doctor with one room
A clinic with three chairs
A 30-bed hospital billing insurers
A 200-bed group across branches
A company covering its staff
A lab or a pharmacy alongside

What runs without being asked

Improved most weeks
No AI key The waitlist

A cancellation is offered to the next person in order, with a window, until somebody takes it.

No AI key The follow-up chaser

Raised when the prescription is written, chased twice, then it stops. It does not nag.

No AI key Critical results

An abnormal value escalates after thirty minutes if nobody named has acknowledged it.

No AI key Claim risk

Twenty-four rules, scored before submission and sorted by exposure rather than raw risk.

No AI key Nadi, 24 commands

Ctrl-K from any screen. These are database queries, so they work offline and cost nothing.

Your key Free-text questions

Ask in your own words. Bring your own Anthropic or OpenAI key, or run Ollama on your hardware and nothing leaves the building.

We are deliberate about which is which. Most of what runs here is rules, not a model — because a rule is auditable, works when the connection drops, and cannot invent a figure. We build and improve both every week, and we will always tell you which one answered you.

Prescriptions a patient can actually read

Four live, four in clinical review
Prescriptions a patient can actually read
LanguageStatus
EnglishLiveReviewed
Hindi — हिन्दीLiveReviewed
Marathi — मराठीLiveReviewed
Tamil — தமிழ்LiveReviewed
Bengali — বাংলাIn reviewAwaiting a clinician
Telugu — తెలుగుIn reviewAwaiting a clinician
Gujarati — ગુજરાતીIn reviewAwaiting a clinician
Kannada — ಕನ್ನಡIn reviewAwaiting a clinician

We do not machine-translate a dose. A model asked to render “one tablet twice daily after food” will usually be right, and usually is not a standard that applies to a dose instruction — a dropped negation reaches a patient with no clinician present to catch it. So every phrase is a fixed table, translated once, and it is not offered to a clinic until a doctor who speaks that language has read all twenty-three. Anything outside the table stays in English: a phrase somebody must ask about is far safer than a confident mistranslation they act on.

The booking page is free, permanently.

No cap, no commission, and it does not move behind the paywall later.

A day book records what came in.

Not who cancelled and was never replaced, and not who was told to come back and did not.