Availability is not authority
A screen can remain available while its underlying decision authority has disappeared. Good offline design distinguishes cached reference material, locally staged work, actions that can be committed later and actions that must stop.
That distinction is particularly important in healthcare operations. A polished offline control must not imply that stale data or an unaudited local decision is safe.
Make the queue legible
Every pending operation needs an identity, a visible state and a reconciliation rule. “Saved” is too vague when it could mean stored only on one device, accepted by a local node or committed by the authoritative service.
The interface should show what is waiting, what failed, what was superseded and which person must review a conflict.
- Stable operation identity
- Visible local and committed states
- Bounded retry and expiry
- Human review for unsafe ambiguity
Reconnect is a workflow
Connectivity returning is not the end of offline behavior. The system still has to compare versions, preserve provenance and avoid replaying an action twice.
Livara Chat documents a concrete reconnect cursor for account changes. Dr. Livara treats offline clinical editing as future, safety-sensitive work and does not claim it today. The same word—offline—describes different guarantees.
Never let an offline icon carry more authority than the underlying state.
