Skip to main content

How autosave works

LOSPOR records a clinical change on the device before trying to send it. The screen can therefore continue to show unsent work after a short network loss or an app restart.

In simple terms​

Think of Autosave Manager as one clerk assigned to each case:

  1. The clerk writes the change into a local tray.
  2. Changes for that case are sent one at a time, in the order they were made.
  3. The server acknowledges the change and returns the section's new revision.
  4. Only then is the change removed from the tray.

Preoperative, intraoperative, and postoperative forms all use this same process. The mobile app stores its tray in SecureStore. The web/PWA stores it in IndexedDB.

Timetable events​

Adding, editing, and deleting a timetable item are separate operations with stable IDs. Editing or deleting one drug, fluid, vital, or event does not replace the whole timeline. Retrying the same operation is safe.

Timeline clock and timezone​

Starting a case saves two pieces together: the exact UTC instant and the IANA timezone used by the clinician, such as Europe/Sofia. The visible HH:MM remains for display, but it is never used by itself to reconstruct a date.

The start-time patch is sent before the first timetable event. Live clocks, five-minute columns, reopen backfill, web projection, and mobile projection all use that same exact instant. This works across positive, negative, half-hour, and daylight-saving offsets.

Legacy cases that have only an HH:MM remain readable, but LOSPOR does not invent timestamps for their saved columns. A legacy snapshot is converted to events only when a trustworthy startedAt exists, and conversion is rejected if it would synthesize future observations.

Two devices​

Each case section has an increasing revision number. A save says which revision the user edited. If another device advanced it first, the server returns the newer revision. LOSPOR retries the changed fields once against that revision. Different fields can therefore merge without replacing the complete form.

Reopening and finalizing​

When a case is reopened, LOSPOR loads the server copy and reapplies anything still in the local tray. A case cannot be finalized while its tray still contains unsynced changes.

A field rejected for privacy​

If the server detects likely identifying information, Autosave Manager keeps that field on the device and shows the reason beside it. Other safe fields in the same form can still save.

The rejected text is not repeatedly sent. It stays blocked until the clinician changes that field, then LOSPOR tries it once again. Reopening the case restores the local blocked text over the server copy so it is not lost.

The probable-name check is skipped only for structured selections from the ICD-10, procedure, medication, and allergy catalogues. EGN, long-number, date, and email checks still apply to those labels.

When the server cannot be reached​

A save always reaches durable storage on the device before any network request is attempted, so an unsent save is queued rather than lost. That property is what lets the application stop trying quickly.

Until 8.4.0 every save waited the full network timeout — eight seconds — before concluding it was offline, and intraoperative writes are serialised per case, so one unreachable save delayed everything queued behind it, and the next save paid the same cost again. The application spent seconds arriving at an answer it already had.

Now the timeout is three seconds, and after a failure the application writes straight to the queue without attempting the network until a short interval has passed. It clears that state the moment any request reaches the server — even an error response proves the network is up — and whenever the application returns to the foreground, since the connection may well have changed while it was away.

The interval is deliberately shorter than the periodic flush, so every flush still makes one genuine attempt and a recovered connection is picked up on the next cycle rather than being locked out.

Settings → Diagnostics shows whether the application currently considers the server reachable, and how many edits are waiting.

Operational notes​

  • Schema migration: 20260723000000_autosave_manager_revisions
  • Revision headers:
    • x-lospor-preop-revision
    • x-lospor-intraop-revision
    • x-lospor-postop-revision
  • Legacy timestamp conflict headers remain accepted during migration.
  • Signing out or deleting a draft clears the relevant local clinical queues.