Most AI scribes assume a clinic that never loses signal. A lot of Indian clinics don’t have that luxury. AI Medical Scribe by Patient Square captures the visit offline on the device, encrypted with AES-256-GCM, and syncs the note once the connection comes back. So a dropped tower or a power cut at 11am in a tier-2 OPD doesn’t cost you the record. You keep working; the note catches up.
Key takeaways
- Offline capture runs on the device, encrypted with AES-256-GCM. The note syncs when the connection returns.
- Visit audio is processed and discarded once the note is drafted, so no audio archive piles up on the phone.
- Built for tier-2 and tier-3 clinics where signal drops mid-OPD and a cloud-only scribe would simply stop.
- Languages don’t change offline: English, Hindi, and 20+ Indian languages in, clean clinical English out.
on-device encryption for the offline capture buffer
audio recordings retained: processed, then discarded at note draft
from end of visit to a reviewable note, once synced
Why does a cloud-only AI scribe fail in a low-signal clinic?
Because the capture step is waiting on bandwidth it doesn’t have.
A pure cloud scribe streams the visit to a server in real time. That’s fine in a metro hospital on fibre. It’s a problem in a town where the tower drops for an hour at midday, the power flickers, and the 4G icon turns into an E. When the stream breaks, a cloud-only tool either errors out, loses the segment, or makes you start over. None of those are acceptable when there are forty patients in the corridor and you can’t stop to debug a network.
This isn’t a rare edge case in India. Connectivity outside the big metros is genuinely present but genuinely unreliable, and a clinic can’t predict which fifteen minutes of the day the signal will vanish. So the question for any scribe you evaluate isn’t “does it support offline?” as a checkbox. It’s “what exactly happens to this visit if the connection dies in the middle of it?”
How does offline capture actually work?
One design principle holds the whole thing up: capture should never depend on the network. Only sync should.
So capture happens on the device. When you start a session, the visit is captured locally on the phone or laptop, signal or no signal. The scribe doesn’t phone home to begin. It just works. That local capture is encrypted with AES-256-GCM on the device, so it isn’t sitting there in plain form waiting for a connection. Lose the phone, or have it seized, and the buffer still isn’t readable.
Audio gets discarded, not hoarded. Visit audio is processed and then discarded the moment the note is drafted, so the offline buffer never grows into a library of recordings on your phone. What stays is the structured note. And the sync step is only for that note, encrypted in transit. When the device reconnects, the note syncs over TLS 1.2 or newer, and the structured SOAP note, ICD-10 suggestions, and prescription draft become available to review and sign, in clean clinical English. You review it a little later than usual. You don’t lose it.
AI Medical Scribe by Patient Square is an ambient AI medical scribe that listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Offline-first capture is what keeps that promise true when the clinic’s connection won’t cooperate.
A real scene: the signal drops at 11:40am
Picture a single-doctor clinic in a tier-3 town. Forty-eight patients booked, a busy Saturday OPD. At 11:40 the local tower goes down, the way it does most weeks. A cloud-only scribe would stall on the next patient, and the doctor would be back to scribbling on paper for an hour, then retyping it that night.
Here, capture keeps running on the device. Patients twenty-two through thirty-one are seen and captured offline, each buffer encrypted on the phone. At 12:50 the signal returns. Those ten visits sync, and ten clean English notes are waiting to review and sign over the lunch break. The doctor lost nothing but a slightly delayed review. That hour of dead signal didn’t become an hour of pajama-time charting at 9pm.
That’s the moat. Not that we “support offline,” but that the worst hour of the clinic’s network day is a non-event.
Is offline capture secure, or is it a soft spot?
Fair question, and the honest answer is that offline is only safe if it’s encrypted offline.
The risk people imagine is a phone full of unencrypted patient recordings. That’s a real risk with a badly built offline mode. Ours avoids it two ways. First, the on-device buffer is encrypted with AES-256-GCM, so what’s stored locally isn’t readable without the key. Second, audio is processed and discarded once the note is drafted, so there’s no growing audio archive on the device to begin with. Notes are encrypted at rest with AES-256 and belong to your practice; you can export or delete any visit at any time.
This also matters under the DPDP Act 2023. The principle is purpose limitation and reasonable security: keep only what you need, protect what you keep. An offline buffer that’s encrypted and short-lived fits that far better than a scribe that streams and stores. The full posture is on our security page, and the data residency post covers where the synced data lives.
Does offline mode cost more, and how does the price compare?
No. Offline capture is part of the product, not a premium add-on, and there’s no feature gating between tiers.
AI Medical Scribe by Patient Square launches at ₹1,199 per clinician per month ex-GST on annual billing, about ₹1,415 once you add 18% GST, with a 7-day free trial. The published India-native anchor, EkaScribe Pro, is ₹1,499 per doctor per month. The full ladder, with the with-GST math, is on the India rate card and the pricing page. For a tier-2 or tier-3 clinic, the offline behaviour is worth more than the price gap, because the alternative is losing notes on the days the network has a bad afternoon.
If you run a solo practice and want to see whether the monthly cost pays back against your patient volume, the solo-doctor payback post works the math against a 40-to-60-patient OPD day.
How do you test offline capture before you commit?
Don’t take our word for it. Break the connection on purpose.
During the 7-day free trial, run a real OPD morning, and at some point put the phone in airplane mode mid-visit. Keep seeing patients. Then turn the signal back on and watch the notes sync. That’s the test that matters for a low-connectivity clinic, and it takes ten minutes to run. If a vendor’s offline mode loses the visit, you’ll know on day one instead of on the worst Saturday of the year.
When you want to see it on your own clinic’s network conditions, book a demo and we’ll show the airplane-mode test live. If the multilingual side is your bigger question, the Hindi and Hinglish post shows a code-mixed consult becoming an English note, online or off.