Appointments, transport & tasks

Record an appointment once and track transport, accompaniment, documents and external confirmation directly against it.

Link appointments to the resident, participants, location, location time zone, duration, accompaniment, transport, preparation and approved documents; manage external organisations and contact channels separately from internal people.

Show requested, confirmed, postponed, cancelled and unclear separately. Sending or technically receiving a request is not professional confirmation of an appointment.

Check conflicts involving residents, staff, rooms and vehicles. For each item, it must be visible which resources are firmly reserved and which have only been requested.

Assign external responses with their source, time and reference. Free-text or telephone responses require authorised confirmation of the structured values.

Explicitly model time zones, daylight-saving changes, half-open intervals and changes to recurring appointments; a single exception must not silently change the entire series.

Calendar exports and participant views minimise resident data; no health content appears in publicly accessible calendar links or unprotected emails.

Responsibility

Appointment administration and assigned care staff plan; employees confirm their own accompaniment within their competence; external parties receive narrowly limited booking information.

Automation & AI

AI converts telephone or document notes into appointment drafts and formulates booking requests. Confirmed time, location and preparation require a verified source; nothing is invented when a response is missing. AI features require activation at your request. Processing remains on Oronela's own servers in Switzerland.

Connection & offline use

Read assigned appointments with their data status and record a request draft locally; external booking confirmation and binding resource reservations take place online.

Automate recurring coordination and ensure every outstanding task has a responsible person and verifiable completion.

Maintain tasks with source, dependencies, due date, priority, responsible person or role, representative, required competence and completion criterion.

Distinguish created, assigned, offered, accepted, started, blocked, professionally completed and cancelled. A push or read receipt is neither acceptance nor completion.

Check the dependency graph for cycles and make unmet prerequisites visible. Critical tasks must not receive an unsecured automatic completion.

Version server-side deadlines, recurrence and escalation chains; do not depend on a browser remaining open or guaranteed mobile push delivery.

An automatically created task has a stable professional deduplication reference from its source, revision and task type. A new source can invalidate it but cannot delete a service already documented.

Acknowledgement and execution must check current permissions, competence and source revision; changes of substitute require a traceable handover.

Responsibility

Task creators act only within their own domain; responsible people accept permitted tasks; management maintains escalation chains within its authority.

Automation & AI

AI structures draft tasks, groups outstanding queries and suggests responsibilities. It must not bypass deadlines or competencies or infer completion from a message. AI features require activation at your request. Processing remains on Oronela's own servers in Switzerland.

Connection & offline use

Non-critical evidence can be recorded provisionally locally; binding assignment, delegation, critical completion and deadline changes require an online connection. Synchronisation checks current permissions and professional status and preserves necessary clarification evidence.

Coordinate medical appointments, clinical preparation, transport, accompaniment and catering from confirmed information, and update them reliably when changes occur.

Use fasting and other clinical preparation requirements only from a confirmed order revision with its source, validity window, exceptions and responsible professional.

A morning appointment, an assumed examination type or AI output does not justify a restriction. An unclear free-text instruction creates a query and an unresolved status.

The workflow revision binds the appointment, order, transport, accompaniment, documents and catering request. Dependent orders receive the source revision and a stable idempotency reference.

Rescheduling or cancelling an appointment, or a new order, invalidates affected open tasks and requests any necessary reconfirmation. A journey, meal handover or communication already completed remains a recorded fact and generates the required correction task.

The permitted consumption time may come only from a confirmed source; pending approval after an examination is passed on as pending, not calculated from the appointment end.

Changes across modules are managed as a monitored sequence of states with retries and clarification cases; no distributed all-or-nothing transaction is claimed. A downstream change not yet confirmed remains visible.

Responsibility

Appointment planning coordinates; clinically authorised doctors and care staff confirm orders; the kitchen confirms its orders; accompaniment staff acknowledge handovers and professionally permitted tasks. No one takes over another person's clinical approval.

Automation & AI

AI extracts unclear information as a suggestion and formulates queries, workflow overviews and change summaries. Deterministic rules generate follow-up tasks from approved sources only. AI features require activation at your request. Processing remains on Oronela's own servers in Switzerland.

Connection & offline use

Read the approved workflow view and provisionally record non-critical notes. Accepting orders, permitting consumption and binding appointment or follow-up changes take place online; cached data displays its status and a warning.