Offline clinic software: what "offline-capable" honestly means
· 6 min read
Ask a clinic owner what worries them about moving off paper, and "what happens when the internet goes?" comes up early. It is a fair question. In a lot of clinics the connection drops several times a week, and the power often goes with it. A paper register has never needed a signal.
Software that says it "works offline" is making a promise, and the promise is usually vaguer than it sounds. This post sets out what a clinic should actually expect: which work can carry on without a connection, what has to wait, and what happens to everything entered in between.
Offline-only, online-only, and the middle
Clinic software comes in three broad shapes.
- Online-only. Every screen asks the server. When the connection drops, the screen stops answering and the visit goes back onto paper, to be typed in later if someone remembers.
- Offline-only. The whole clinic lives on one computer. It never needs the internet, but the records are only as safe as that machine, and a second device at the front desk can't see what the doctor just wrote.
- Offline-capable. The records live on a server, and every device works from them. When the connection drops, the work that can't be postponed carries on, on the device, and is sent when the connection comes back.
The third is the useful one for most clinics, and also the easiest to oversell. "Offline-capable" doesn't mean everything works offline. It means a chosen set of things do, and it's worth knowing exactly which.
What should keep working
The test is simple: what does the clinic need to do while a patient is in front of it? That work should never wait for a signal.
- Finding the patient. Recent patients, anyone booked today and anyone seen in the last few days should already be on the device, with their history, so the record opens without the server.
- Registering a new patient. Someone walks in for the first time; they get a record.
- The consultation. Notes, a new case or a follow-up, and the prescription.
- Dispensing what was just prescribed. The visit that ended as the line dropped shouldn't leave the patient waiting at the counter.
- Taking payment and printing a receipt. The patient pays before they leave, whatever the router is doing.
In KeepPulsing, all of that carries on offline. Remedies and medicines can still be picked from the list, and an invoice issued offline is numbered on the device, so the receipt printed at the counter is the one the clinic keeps.
What should honestly wait
Some things depend on knowing what everyone else in the clinic has done, or on reaching the outside world. Software that pretends otherwise is guessing, and a guess in a clinical or financial record is worse than a short wait.
| Waits for the connection | Why |
|---|---|
| Signing in for the first time | The device has to collect the clinic before it can work without it |
| Stock purchases and corrections | Stock is the sum of every device's entries; one device alone can't know it |
| Paying an older invoice, or voiding one | The balance may have changed elsewhere since the device last looked |
| Dispensing an older prescription | Someone else may have dispensed it in the meantime |
| Reports and export | They are built from the whole clinic's records, on the server |
| Opening WhatsApp to message a patient | WhatsApp itself needs the internet |
| Seeing what another device just did | Until both are online, neither can tell the other |
None of these is needed to finish a visit. They are the back-office half of the day, and they can wait an hour.
What happens when the connection comes back
This is the part most "works offline" claims skip, and it's the part that decides whether the records can be trusted.
Everything goes up in the order it was entered. In KeepPulsing, offline work is queued on the device and sent through the same route an online device uses. There is no separate, less-tested way in, so a consultation entered offline is checked exactly like one entered online.
Offline work is mostly adding things. A new consultation, a new prescription, a new payment. Two devices adding different things don't collide, which is why most of a day's offline work goes up without anyone noticing.
When two devices do collide, a person decides. Suppose the doctor's phone and the front-desk computer both registered the same walk-in patient while the line was down. That becomes a task to merge the two records or dismiss one. If the same prescription was dispensed on two devices, the second is refused and the reason is shown. Neither is settled by quietly overwriting one side. In a clinical record, a silent overwrite is a lost fact.
You can see what is waiting. The app shows how many changes are saved on the device and not yet sent, so nobody has to wonder whether this morning's visits made it.
The honest risks
Offline-capable software moves a small amount of risk onto the device, and it's better to know where it is.
- Unsent work lives only on that device. If a phone is lost or broken before it reconnects, whatever it hadn't sent is lost with it. Everything already sent is on the server, and signing in from any other phone or computer brings the clinic back.
- Long outages build a longer queue. A day offline is fine. A week offline means a week of the front desk and the doctor not seeing each other's work, and a week of stock and reports waiting.
- Signing out clears the device. Cached patient records are removed when someone signs out, keeping only work the server hasn't received yet. That is deliberate: a shared or lost device shouldn't carry the clinic's records around.
Questions to ask any vendor
If you're comparing clinic software, these questions get past the word "offline" quickly:
- Can I see a patient, write a consultation and take a payment with the router switched off?
- Which patients are on the device when the line drops, and which aren't?
- What exactly needs the internet?
- When two devices change the same thing offline, what happens, and who decides?
- Where can I see changes that haven't been sent yet?
- If I lose the device, what do I lose?
A vendor who answers all six plainly has thought about it. A vendor who answers "everything works offline" hasn't.
Where KeepPulsing stands
KeepPulsing is offline-capable, not offline-only. Registering patients, consultations, prescribing, dispensing the visit that just ended, and issuing and taking payment on a new invoice all continue without a connection, on any device the clinic uses. Stock, reports, older balances and messaging wait for the line. When it returns, everything goes up in order, and anything that clashes is put in front of a person rather than decided for them.
The same answers, with the rest of how clinic records are kept and exported, are on the data and security page. The FAQ covers the short version. Both General Clinic and Homeopathy work this way.