In development · Healthcare
A clickable prototype for small Indian OPD clinics. It connects simulated ABHA-based intake, consultation, bilingual e-prescriptions, GST and UPI billing, WhatsApp reminders, a consented patient record, and clinic-owner visibility. A source-linked patient context model is being explored as the next phase.
The problem
Registration, consultation, prescribing, billing and follow-up are often disconnected — different books, different apps, different staff. Context is lost between them.
The thesis
One visit should move as one thread — not as a chain of departmental handoffs. The clinician stays focused on the patient, and the clinic owner sees the whole day at a glance.
The workflow
Scan-and-share style intake collects patient context before the visit begins.
One thread carries context, deltas since the last visit, and missing-information flags to the consultation.
Draft prescription generated for the clinician to review; nothing leaves the room without approval.
Billing and receipts are produced from the same visit thread — not a separate ledger.
Follow-ups and instructions are queued from the visit record with explicit patient consent.
The record is written back to a consented patient store, owned by the patient, visible to the clinic owner.
All external integrations shown above are simulated in the current prototype.
The AI direction
We use "patient context model" — not "digital twin" — because the current prototype is a simulated workflow, not a predictive, multidimensional patient representation.
Human control
Drafts assist. They do not decide. Every prescription, every summary and every downstream instruction is reviewed and approved by the clinician before it leaves the room.
Trust
Evidence
Bring us the problem that crosses product, AI and operations. We start with a diagnosis.
Talk to a senior partner