Insights
Can a hospital information system run when internet is unreliable?
Hospitals in English-speaking Africa are routinely told to “go cloud” as if the last mile were a given. Many sites have a good morning and a bad afternoon. An HIS that becomes a brick when DNS fails is not a clinical system; it is a dependency.
HospitalMgr is used as a cloud-connected platform with a serious Windows client and Flutter systems for Android and iOS. Teams keep working on the devices they already own. Sync and backup jobs are first-class modules, not an afterthought zip of a laptop folder.
Backups stream table by table, compress with gzip, and stay inside the hospital tenant. Restore is a controlled, permissioned action. That design came from real operational pain: large invoice tables, limited PHP memory, and the need to not download another hospital’s patients.
Unreliable internet also changes training. We do not train staff to “refresh if it spins.” We train them to complete the encounter in front of them: register, prescribe, dispense, collect. Reports can wait for a stable hour. Configuration such as AI model keys is stored encrypted so a later connected feature does not require pasting secrets into a chat.
If your facility has a VSAT budget one month and none the next, choose software whose vendor has shipped other Uganda systems under the same constraint. Digital Monster’s hotel, POS, and microfinance products already assume intermittent networks. HospitalMgr inherits that honesty.
Practical deployment pattern
Put the primary workstation at reception and pharmacy — the two counters that never stop. Give clinicians the mobile system for rounds. Keep a weekly backup download with the in-charge. Do not make radiology the first module if the modality is still paper.
Windows, then mobile
The Windows client is the workhorse for reception and pharmacy. Flutter systems on Android and iOS cover rounds and the clinician who will not sit at the desk. Neither replaces a generator plan. Both beat a browser tab that dies when DNS fails.
Backups you can explain to an auditor
Gzip, table by table, one hospital_id. Restore is permissioned. That is the sentence an in-charge can say to a board. A zip of a laptop folder is not.