Running a Lab Where Power and Internet Are Unreliable

Most laboratory software is designed by people with reliable electricity. That assumption is invisible in a demo and expensive in production, and it is the single biggest architectural question for a laboratory outside a major metropolitan area.

The quick answer

A cloud-only laboratory system stops completely when connectivity does: no registration, no billing, no result entry, no report printing. An offline-first system keeps the database on the laboratory's own machine and continues working, reconciling with the cloud when the connection returns.

What actually stops

It is worth being concrete, because "it goes offline" undersells it. During an outage on a cloud-only system, a patient standing at your counter cannot be registered. A sample already on the analyzer produces a result that cannot be recorded. A report that was ready to print cannot be printed. Payment cannot be receipted. And none of it queues — the work simply does not happen until the line comes back.

The second-order cost is worse than the first. Staff start writing on paper to keep the queue moving, and then re-key it later from handwriting, at the end of a long day. That re-keying is where transposed values come from.

The design choices that matter

• Where the database lives. If the system of record is on your own machine, an outage is an inconvenience; if it is on someone else's, an outage is a closure.
• Where the analyzer link runs. An interface between the instrument and the local PC over a cable does not care about your broadband. One that routes through a vendor's servers does.
• Whether report generation is local. A PDF composed on your machine prints during an outage; one composed server-side does not.
• What sync does on reconnect. Catching up should be automatic and should not require someone to remember to press anything.
• What happens to a partially-entered record when power cuts without warning — not a graceful logout, an actual cut.

That last point is the one to test rather than take on trust. During an evaluation, pull the network cable mid-shift and pull the power on the machine, then see what survives. Any vendor confident in their answer will let you — ours is set out under security and where data lives, and the trial runs on your own data so you can try exactly this.

What you give up, honestly

Offline-first is not free. A local database means backups are your responsibility in a way they are not with a hosted system, and a machine that dies takes its data with it unless a backup exists somewhere else. Multi-site visibility needs sync to have run, so head office sees a branch as of its last reconnection rather than as of this second.

Those are real trade-offs and the right answer depends on your connectivity. A laboratory on a stable fibre connection in a capital city may reasonably prefer cloud-only. A laboratory that loses power daily is making a different calculation, and should be told which one it is buying rather than sold "the cloud" as an unqualified upgrade.

Questions worth asking any vendor

• Can I register a patient and print a report with the network cable unplugged? Show me.
• Where is the database physically, and can I take a copy of it?
• If my subscription lapses, do I keep access to the data already in the system?
• Does the analyzer interface depend on your servers?
• What is my backup, where does it go, and can I restore it myself?