Does cloud prescription software stop working during load-shedding?
It is the first question a Bangladeshi chamber doctor should ask, and the honest answer is: it depends on the design, not on the word “cloud”. Load-shedding and patchy mobile data are a daily reality, so any serious tool has to survive a connection that comes and goes. The failure people fear — you finish a consultation, the internet blinks, and the prescription you were writing vanishes — is an engineering choice, not an inevitability of cloud software.
What genuinely needs a live connection is narrower than “everything”: pulling a patient’s full past history from the server, and issuing the finished prescription — the step that mints a serial number and, on a verifiable platform, the public link a pharmacy can use to confirm the prescription is real. Building a draft, by contrast, can happen entirely on the device.
Cloud-first vs offline-first: what each actually protects
Strip away the marketing and the two designs protect different things.
- Cloud-first with on-device draft resilience. Records live on the server; the app keeps your in-progress prescription safe on the device and syncs it when the connection returns. You can keep working through an intermittent drop, but you can’t cold-start with no connection at all, and you can’t browse full patient history offline.
- Offline-first with a local record store. A copy of patient records is kept on the device, so the app keeps working with no internet for longer — genuinely useful where connectivity is simply absent. The cost is that patient data physically lives on the tablet or phone.
The trade-off nobody mentions: where your patients’ data lives
Offline capability is usually sold as a pure win. It isn’t — it has a quiet cost. To work with no internet, an offline-first app has to store patient records on the device. That is a real advantage in a no-connectivity chamber, and it is also a real exposure: a shared reception tablet, a phone left in a drawer, or a lost device now carries a copy of a patient database. A cloud-first design that keeps records on the server — and never caches a patient page on the device — means the device holds nothing sensitive if it goes missing. Under Bangladesh’s move toward stronger health-data expectations, that is not a small point. Neither choice is wrong; they optimise for different risks.
How Prescriply handles a connection drop
To make this concrete, here is exactly what Prescriply does — stated plainly, because overpromising on offline behaviour is the fastest way to lose a doctor’s trust:
- As you build a prescription, it autosaves to your device (the browser’s IndexedDB) and a sync outbox pushes it to the cloud the moment the connection returns — so a load-shedding drop mid-visit doesn’t lose the prescription you were writing.
- The app is an installable PWA and shows a clean offline screen instead of a browser error.
- Issuing the finished prescription — and its public BM&DC-tied authenticity link — and loading a patient’s past records need a connection.
- Prescriply keeps patient records in the cloud, never cached on the device, and clears local drafts on logout, so a shared or lost chamber tablet holds no patient database.
So Prescriply protects an in-progress prescription through an intermittent drop, but it is not a full offline-first store you can cold-start with no connection at all. If prescribing with no internet is your daily reality, an offline-first tool is the better fit, and we say so plainly in our honest Doctors Canvas comparison.
How to choose for your chamber
- Map your real connectivity. Is the internet absent (rural, no reliable line) or intermittent (it drops during load-shedding, then returns)? Absent → lean offline-first. Intermittent → cloud-first draft resilience is usually enough.
- Decide where patient data should live. If a shared or portable device is a real theft/loss risk, keeping records off the device matters.
- Check what actually breaks offline. Ask a vendor specifically: does an in-progress prescription survive a drop? Can you cold-start with no internet? Where are records stored?
- Weigh it against the rest. Offline is one axis. Chamber-wise fee settlement, tax reporting, and prescription authenticity are others that a busy chamber needs anyway.
Frequently asked questions
Does cloud prescription software stop working during load-shedding?
It depends on the design. A well-built cloud-first app keeps working through a short power cut or a flaky tower if it autosaves your in-progress prescription on the device and syncs when the connection returns — so you don't lose the prescription you were writing. What it can't do is load a patient's full history or issue the final, verifiable prescription with no connection at all. An offline-first app keeps a copy of records on the device so it can do more with no internet, at the cost of storing patient data locally.
Is offline-first always better for a Bangladeshi chamber?
Not always. If your chamber routinely runs with no internet — a rural or Upazila setting with unreliable connectivity — offline-first is genuinely more capable. But if your reality is intermittent connectivity (power and internet drop, then return), cloud-first with on-device draft resilience protects your in-progress work while keeping patient records off the device, which is safer if a chamber tablet is shared or lost.
Where are my patients' records stored?
That's the trade-off most comparisons skip. Offline-first apps keep a copy of patient records on the device so they work with no internet — which also means that health data physically lives on the tablet or phone. Cloud-first apps keep records on the server and (in Prescriply's case) never cache a patient page on the device, so a shared or lost device holds no patient database. Neither is 'wrong' — it's a choice between offline capability and on-device data exposure.
Does Prescriply work offline?
Prescriply is cloud-first, but it is not 'fails offline'. As you build a prescription it autosaves to your device (in the browser's IndexedDB) and a sync outbox pushes it when the connection returns, so a load-shedding drop mid-visit doesn't lose your work; the app is an installable PWA with a clean offline screen. Issuing the finished prescription (and its public BM&DC-tied authenticity link) and loading past records need a connection. Prescriply deliberately keeps patient records in the cloud and clears local drafts on logout.