Dienst lifecycle

The full arc of a Dienst — from the moment it is created, through documenting patients on it, to closing, exporting, and reprinting. This page is for operators working on the tablet.

A Dienst (duty/shift) is the operator-facing name for what the app internally calls an event. Everywhere you read "Dienst" in the app, that is the container that holds this shift’s protocols and its material tally.

The phases at a glance

  CREATE ──▶ CONNECT + READINESS ──▶ DOCUMENT ──▶ CLOSE PROTOCOLS ──▶ CLOSE DIENST ──▶ EXPORT / PRINT
                                        ▲                                                     │
                                        └──────────────── REOPEN / REPRINT ◀─────────────────┘

  1. Create the Dienst (admin panel, or offline on the tablet).

  2. Connect a tablet with the Shift-PIN and establish Einsatzbereitschaft (readiness).

  3. Document — create and fill in protocols, plus the Dienst-level material tally.

  4. Close each protocol via the Übergabe (handover) wizard.

  5. Close the Dienst — only once every protocol is closed.

  6. Export / print — PDF and email-archive, once protocol and Dienst are both closed.

  7. Reopen / reprint — correct or reprint a closed protocol without reopening the whole Dienst.

Phase 1 — Create the Dienst

There are two ways a Dienst comes into existence:

Admin panel (preferred)

An administrator creates the Dienst in the admin panel, sets its Shift-PIN, and assigns personnel. The Dienst then syncs down to the enrolled tablets automatically.

Offline on the tablet

On the entry screen, choose „Neuen Dienst anlegen". This asks for the Firmen-PIN (company PIN) and then a short form to name the Dienst. Use this when no Dienst has been synced — for example, a spontaneous callout with no network.

See PINs for which PIN does what.

Phase 2 — Connect and establish readiness

  1. On the tablet, enter the Shift-PIN to connect to the Dienst.

  2. The readiness checklist („Einsatzbereitschaft herstellen") appears — it confirms the roster that is actually present for this shift.

  3. Confirm the roster; the app opens the Dienst dashboard.

If another tablet has already established readiness for this Dienst, later tablets skip the checklist and go straight to the dashboard. Readiness is a property of the Dienst, not of each individual tablet.

Phase 3 — Document the Dienst

The Dienst dashboard is the working home for the shift. From here you:

  • Create and fill in protocols. The dashboard lists this Dienst’s protocols; add a new one and document the patient. See Writing a protocol.

  • Record material use. A Dienst-level Kleinstbehandlungen / material tally captures minor treatments and consumed items. See Material catalog.

Offline-first

Everything is stored locally in SQLite first and syncs in the background. You can work with no network the entire shift. If the tablet is offline, a deferred sync toast appears — your data is safe locally and will sync when connectivity returns.

Phase 4 — Close a protocol

Each protocol is closed through the Übergabe (handover) wizard. Completing it moves the protocol from open to closed, and a closed protocol leaves the active list on the dashboard.

A protocol’s status is one of:

Status Meaning

open

Active — still being documented, appears in the active list.

closed

Finished via the handover wizard — moved to the closed list.

reopened

A closed protocol reopened for correction (see Phase 7).

archived

Retained after the Dienst is archived.

Phase 5 — Close the Dienst

The Dienst can only be closed once ALL of its protocols are closed. If any protocol is still open, close it first (Phase 4). Closing the Dienst is what unlocks export and printing.

Phase 6 — Export and print

PDF export and email-archive require BOTH the protocol AND the Dienst to be closed. Until both are closed, the export actions are not available.

  • PDF. The protocol PDF is rendered with Typst in Rust; the in-app preview you see is a rasterized PNG of that document.

  • Thermal print. Printing goes to the PeriPage A40 thermal printer. See Printing for pairing and paper handling.

Phase 7 — Reopen and reprint

Closed protocols do not disappear — they remain on the Dienst dashboard under „Abgeschlossene Protokolle" (closed protocols). Tapping one opens an action sheet:

Action What it does

Ansehen

Open the protocol read-only.

Drucken

Open the preview and reprint the PDF.

Bearbeiten

Reopen for correction. This is confirmation-gated and moves the protocol to reopened. When done, re-close it with „Abschließen".

Reprinting does NOT require reopening the whole Dienst. Use Drucken on the closed protocol to print another copy directly. Only use Bearbeiten when the content itself needs a correction.

Related pages