Built for outpatient departments in India
One record per patient, from OPD to pharmacy to bill.
FocusMD drafts the consultation note in English or Tamil, pulls the patient's ABHA history from other hospitals, verifies the prescription at the counter, and settles the bill. Nothing is filed until a registered prescriber signs it.
- Signed by HPR-verified practitioners only
- ABDM-linked, read-only where fetched
- DPDP requests answered on time
Conflicts with the patient's record
Patient said no diabetes this morning, but HbA1c 8.2 on 02 Oct says otherwise. Choose which is right — both are kept, marked as a discrepancy.
- Provisional diagnosis
- Exertional angina (I20.0), to be confirmed by ECG. Uncontrolled hypertension (I10).
- Advice and plan
- ECG today, troponin if abnormal. Start aspirin, titrate telmisartan. Review in 2 weeks.
- Suggested codes
- I20.0 · Stable angina — acceptedI10 · Hypertension — acceptedE11.9 · Type 2 diabetes — rejected
How sure is the draft
- LowDiabetes mention conflicts with HbA1c
- CheckE11.9 needs your decision
- GoodChest pain wording
From other hospitals, read-only
Diabetes review · Apollo Hospital, 28 Sep 2026
Recorded live in City Medical Centre, Chennai — every patient in the footage is synthetic.
How it works
Three steps, and none of them is typing
Register and triage
Counter registration works with just a name and a phone number — ABHA linking is offered, never required. The nurse records vitals, and a queue priority is suggested from the readings with its reasons shown, so the nurse can override it rather than argue with a black box.
Consult and review
The clinician talks as normal. FocusMD drafts history, examination, provisional diagnosis and advice in English or Tamil, suggests ICD-10 (WHO) codes with a rationale for each, and flags where it is unsure. Every line stays editable.
Sign, dispense, bill
Signing locks the note, issues the prescription with a short collection code, and queues the visit for ABDM. The pharmacist verifies the code rather than reading the paper, so an altered slip is detectable. Billing settles out-of-pocket at the counter.
Features
Built for how an Indian OPD actually runs
Nine things that matter more than a slick demo: provenance, clinical sign-off, counter safety, and honest failure states.
ABHA-linked patient history
Fetches past consultations, prescriptions and reports from other hospitals over ABDM. Everything fetched is badged read-only and carries its source, so a clinician can always tell what was recorded here and what came from elsewhere.
Drafted notes in English and Tamil
History, examination, provisional diagnosis and advice — drafted from the consultation itself. The Tamil face is bundled rather than left to the device, and printed prescriptions and instructions come out in Tamil too.
ICD-10 (WHO) coding
Suggested diagnosis codes, each with the reason it was suggested. A code is never added to a patient's problem list until a prescriber accepts it and signs the note.
Signed by registered practitioners
Only HPR-verified prescribers can sign. An unverified account can draft and edit but cannot finalise, and the screen says why rather than failing silently.
Pharmacy verification
The counter scans the collection code, not the paper, so an edited or forged slip is detectable. Expired, already-dispensed and signature-mismatch cases each get their own instruction — dispensing offline is deliberately not possible.
Out-of-pocket billing
Gross, concession, policy exclusions, co-pay and the amount payable now — all visible, all reconciling on screen. Concessions need a reason and a named approver, and large ones surface in the day-end summary.
Federation you can actually see
Every push to and fetch from ABDM sits in a queue with its validation checks shown. A failed push is a task with a named next step, because a silently dropped record is a visit no other hospital can see.
DPDP requests, answered
Access, correction, erasure and consent withdrawal in one place. Identity verification gates every action. Erasure may be refused — but the reason is recorded and sent to the patient, because silence is not an acceptable answer.
Works when the network doesn't
Notes can be captured offline and stored on the device, then sent when the connection returns. The four things that genuinely need the server — transcription, ABDM fetch, signing, federation — are listed as such rather than implied to work.
Privacy & security
Patient records deserve paranoia
Outpatient records are among the most sensitive data that exists, and India is not a jurisdiction where “we'll sort it out later” is an acceptable posture. FocusMD treats it that way:
- Deployment in an Indian data region — hospital records do not leave India
- Role-based access with per-role scoping and a full audit trail
- Every action on a consultation recorded: who, what and when
- ABDM consent requested per purpose and per data type, never one blanket yes
- Clinical records retained for the statutory period, with erasure requests refused explicitly and the reason recorded
- Speech processing under no-training API terms; consultation content is never used to train models
Consent is per patient, on their device
ABDM consent is requested on the patient's own phone via Aadhaar OTP or the Health ID app — the hospital cannot consent on their behalf. They can grant some data types and refuse others, and we record what was actually granted rather than what was asked for.
Withdrawing consent stops all future sharing immediately. Records already shared with other providers cannot be recalled, and patients are told that plainly rather than discovering it later.
See our privacy policy for exactly what is collected, how it is processed, and how long it is kept.
Pricing
Per hospital, priced with you
We are onboarding early hospitals directly, so plans can be shaped around your department size and how your counters actually work.
Talk to us about pricing
Book a demo and we will put together a plan for your hospital — no lock-in, and early hospitals get founding-customer pricing.
Contact usPrices in INR, exclusive of GST.
FAQ
Questions hospital teams ask us first
Who is responsible for the record?
The treating prescriber. FocusMD produces a draft and nothing reaches the patient record until an HPR-verified clinician reviews and signs it. Signing is the clinician's attestation that it is correct, not ours. An unverified account cannot sign at all.
What happens if the network drops mid-consultation?
The consultation itself is unaffected — you keep talking to your patient. Transcription needs a connection, so the note is typed instead and stored on the device, then sent automatically when you are back online. Signing and ABDM sharing wait for the server; we say so rather than pretending they work offline.
Can a pharmacist dispense without checking?
No. Verification needs the server, because a code cannot be checked against the prescriber's signature without it. The alternative — holding the prescription and phoning the hospital — is the safe failure mode. Dispensing an unverified one is not an option the software offers.
How accurate are the suggested codes?
Codes are suggested from the consultation content alongside the provisional diagnosis, each with the reason it was suggested, and every one needs an explicit accept or reject. Final coding responsibility stays with the clinician, as with any coding support tool.
What about a patient's right to erasure?
Signed clinical records have to be retained for a statutory period, so an erasure request is usually refused. What is not acceptable is ignoring it: the refusal records a specific reason and is sent to the patient. Access and correction requests are handled, gated on verified identity.
Do you submit insurance claims?
No. The hospital settles out-of-pocket at the counter. Insurance-assisted mode captures the policy and works out the patient's co-pay share, which the hospital reconciles with the insurer afterwards — but claims are not submitted from this platform.
Where does patient data live?
In an Indian data region. Hospital records do not leave India. That is a deployment requirement, not a feature, and it rules out hosting in some jurisdictions where Indian health data would otherwise sit outside Indian law.
How do staff get accounts?
The hospital admin invites staff by email and assigns a role. There is no public sign-up — access is always hospital-controlled, and each role sees only the screens its work requires.
Give patients your full attention.
The notes get written. The counter keeps working. The bill adds up.