Skip to main content

Keep work saved.
Keep its status clear.

Keep approved local work available through a weak connection. See what is saved on the device, what is waiting to sync, and what needs review when the connection returns.

Talk to us about your clinic.

Connection unavailable

Saved on
this device.

Supported local work stays visible.

  1. Local draftSaved on the device
  2. Waiting to syncConnection required
  3. Review conflictsConfirm the right version
Illustrative state sequence. Supported actions vary.

From a lost connection
to reconciled work.

Connectivity can change during a clinic day. Keep each step visible so the team knows what can continue and what needs confirmation.

Know what is saved
and what is still waiting.

Keep local save state, pending changes, connection status, and conflicts close to the task. A local draft must remain distinguishable from a synchronized record.

Illustrative synchronization states with sample data. This page does not store clinical work offline.

  • Cached queue and selected patient context
  • Encrypted local drafts and durable operation queue
  • Visible item and global sync state
  • High-risk conflict review with no silent overwrite

Keep the local work
within a clear boundary.

Cached queue information, selected patient context, and encrypted local drafts support approved work on a configured device. Show when information may be stale.

Signing, sharing, and other higher-risk actions may need an online confirmation. Offline availability depends on the action and the validated device policy.

Read the offline operations guide
  1. 01Selected information available on the device
  2. 02Draft changes saved with a visible state
  3. 03Actions requiring confirmation kept explicit
  1. 01Compare the local and server versions
  2. 02Identify the person responsible for review
  3. 03Record the resolution before continuing

Bring important conflicts
to a person who can decide.

Prescription, payment, patient identity, and result conflicts require deliberate review. A newer timestamp alone must not silently replace high-risk information.

Make the competing versions and their state visible, then preserve the decision made during reconciliation.

Give each role
the status it needs.

Reception, clinicians, and support need to see the state of their work and the next action available to them.

Treat an unknown outcome
as work to reconcile.

A timeout does not confirm whether a payment, message, or other provider action succeeded. Keep the outcome unresolved until it can be checked.

Show local, server, and provider states separately so the clinic can follow the appropriate recovery path.

Saved on this device is not presented as synchronized

Provider timeouts remain unknown until reconciled

High-risk data never uses silent last-write-wins

Review offline scope and availability

Bractis is preparing for launch. Current evaluation status: planned. Last reviewed: 2026-08-12.

Pilot scope: this page describes the intended workflow and safe demonstration states, not a live patient record.

Offline signing, mobile device management, and conflict policy are gated by clinical safety and device validation.

Explore all capabilities

Questions about
working through outages.

What local work, synchronization, and recovery mean for the clinic.

Does saved locally mean synchronized?

No. Local save and synchronization are separate states. The interface must show when changes are still waiting to reach the server.

Can every action be completed offline?

No. Offline scope is action-specific. Signing, sharing, and other high-risk actions may need online confirmation and validated device controls.

What happens when two versions conflict?

Low-risk changes may be merged under the configured policy. High-risk prescription, payment, identity, and result conflicts stop for review.

Does a provider timeout mean the action failed?

No. A timeout can leave an unknown outcome. The action needs reconciliation before its final state is confirmed.

Is offline operation available for our clinic now?

Bractis is preparing for launch. Offline signing, device management, and conflict policy require clinical safety and device validation. Talk to us about your environment.

Plan for the connections
your clinic works with.

Tell us about your devices, connectivity, and the work that needs continuity.

Talk to Bractis