Residents & admissions

Capture a verified resident record once and reuse approved information for defined purposes; reduce duplicate entry and confusion between people.

Maintain resident identity, external identifiers including issuer, contacts, funding bodies, consent and representation authority with validity interval and revision. Changes must not overwrite historical states or permissions that applied at the time.

Identity registration distinguishes verified, unverified and incomplete information; a name or date of birth alone does not establish an identity. Resident numbers are display attributes, not technical keys.

Record life history, preferred communication language, communication aids, personal preferences and explicitly expressed wishes in structured form with supplementary free text; their source and approved purpose must be established.

Provide projections of individual fields for care, the kitchen, support and administration. Resident language and user language are separate attributes; a resident profile never changes the logged-in person's UI language.

Manage representation with scope, evidence, start, end and possible revocation effect. Every use checks the current legal basis; historical evidence remains available.

Responsibility

Resident administration manages master data; nursing staff verify professionally permitted information; data protection and representation checks have clearly bounded actions; the kitchen reads only nutrition and assignment information. Technical administrators have no blanket editing authority.

Automation & AI

Local AI may convert scanned documents into a draft with evidenced provenance and flag missing information. Identity checks, representation, consent and conflict resolution remain confirmed by people; the full manual workflow is available. AI features require activation at your request. Processing remains on Oronela's own servers in Switzerland.

Connection & offline use

Only the minimum approved resident dataset can be read within a valid offline lease; local drafts of master data are possible. Identity checks, activation of consent or representation and current access approval require an online connection.

Carry out admissions and state changes as guided workflows with reused data, clear responsibility and traceable downstream tasks.

Record admission, internal transfer, hospital absence, return, discharge and death with the event time, source, responsible person and a correction procedure requiring reasons.

Admission and transfer use a confirmed bed reservation from M05. A multistep workflow distinguishes requested, confirmed, failed and clarification required; partial failures create neither incorrect occupancy nor lost responsibility.

An absence does not end an identity; periods of stay remain traceable over time. A return must not automatically reauthorise previous medication and clinical plans.

Checklists for documents, reconciliation, aids and information are configurable, versioned and identify responsible roles. Administrative completeness must not imply clinical approval.

Discharge or death triggers cancellation of scheduled operational services through versioned events; services already delivered are not deleted. An incorrect status change has a defined correction path.

Responsibility

Administration performs operational admission and discharge; nursing staff and doctors confirm only their clinical handovers; unit management is responsible for transfers. Clinical competence is checked for each action.

Automation & AI

AI summarises admission documents and outstanding points and creates draft tasks. It does not confirm a stay, death, medication reconciliation or legal status. AI features require activation at your request. Processing remains on Oronela's own servers in Switzerland.

Connection & offline use

Preparation as a local draft is permitted; binding admission, transfer, return, discharge and dependent approvals require an online connection. Unsynchronised entries are visibly separate from the effective stay status.

Identify duplicate registrations early and resolve them with a second-person check, without losing medical provenance or previous identities.

Candidate comparisons show explainable matches and differences; similar names create only a review case. Rules and thresholds are versioned.

Merging requires specific verified source and target identities, different qualified reviewers and approval of the exact revisions compared.

Source identities remain as resolvable alias and provenance references. Module references are handled through a versioned identity resolution port; there are no unchecked table updates in other modules.

Conflicting consents, representations, allergies, stays or prescriptions are flagged as domain conflicts. Merging does not grant additional consent and does not automatically adopt the interpretation posing the greatest risk.

Correcting an incorrect merge supports a documented clarification and separation process with impact analysis; signed historical entries remain unchanged and show their original assignment.

Responsibility

Trained resident administration staff perform the check; an independent second authorised person confirms it; clinical staff resolve clinical discrepancies. The person proposing the change may not give both approvals.

Automation & AI

AI may explain candidates and differences, works only with authorised data and logs sources. Every merge and correction remains a controlled human decision. AI features require activation at your request. Processing remains on Oronela's own servers in Switzerland.

Connection & offline use

A candidate note may be drafted locally; comparison against current data, approval, merging and correction are online only.