Skip to main content
All guides

A plan for when
the connection drops.

Know what can be saved on a device, what needs online confirmation, and how your team will review conflicting changes when the connection returns.

Read the guide7 minute read

Last reviewed

A receptionist checks an appointment ledger beside a tablet while rain falls outside the clinic.
Illustrative scene · AI-generated

Start with what can be local

Queue, selected patient context, drafts, and approved observations may be cached or queued. High-risk actions need an explicit policy and an online confirmation by default.

Make state readable

Use labels such as Saved on this device, Waiting to send, Provider outcome unknown, and Needs conflict review. Do not call every state syncing or realtime.

Distinguish the next action

Saved on this device
Local preservation does not establish synchronization.
Provider outcome unknown
Confirm the outcome before repeating the external action.
Needs conflict review
Preserve the versions for deliberate resolution.

Never silently overwrite

Identity merges, prescriptions, payments, and results need human resolution when another device changed the record. Preserve both versions and explain the next action.

Review the recovery path
before you need it.

Identify which actions can be saved locally, what requires online confirmation, and who reviews conflicting changes. Check that the team can tell the difference from the visible state.

This guide describes workflow considerations. Supported offline actions depend on device validation, policy, and implementation.

Explore the recovery decision tree
When connectivity changes
What is the visible state?
Saved locally

Preserve the work.
Check synchronization.

Outcome unknown

Confirm the response
before retrying.

Conflicting versions? Assign a review.
  1. 01Define supported local work
  2. 02Name provider-dependent actions
  3. 03Agree how conflicts are reviewed

Review the feature scope and the handovers around it.

Let’s discuss
your continuity needs.

Tell us about your devices, connectivity, and the work your team needs to preserve. Bractis is preparing for launch.

Talk to Bractis