Designed for unreliable connectivity, not for none
People often describe Moana as an offline system. It is not, and the difference matters.
Moana is designed for connections that come and go. When the link drops in the middle of a ward round, the nurse keeps recording vitals and doses. The record saves on the device and joins a queue.
When the connection returns, the queue syncs in order and the rest of the hospital sees the update.
Why not fully offline
A health system is a network. Lab results need to reach the doctor who ordered them. A referral needs to reach the receiving hospital. A ministry needs facility data to see an outbreak. None of that happens on a device that never connects.
So the design question is not how to avoid the network. It is how to make sure the network going down never stops care, and never loses data.
What that takes
- Every change is stored locally first, then queued for sync.
- Deleted records are tracked, so an old copy cannot come back to life when a device reconnects.
- When two people change the same record while apart, the conflict is held for review rather than silently overwritten.
- Some things are never queued. Passwords and governance changes, for example, only happen online.
The same platform runs in places with fast, stable networks. There it simply feels fast.
The resilience is there for the day it is needed, which in a lot of the world is most days.
