A companion, not a replacement: why Carenji does not displace your care software

In most Austrian nursing homes the care record already runs on an established system — Myneva, Sanocon, Vivendi, or a comparable product. These systems map the care process in full, and switching is a large, risky undertaking. Carenji deliberately does not start there. Carenji is meant as a companion, not a replacement.

What "companion" actually means

Carenji does not displace your existing care software. It sits alongside it and looks after one narrow, clearly bounded slice: capturing PRN medication right at the point of care. The nurse records the administration in the moment it happens — with a timestamp and an initial, at the resident's side.

Out of this comes a traceable, exportable handover: an ordered account of what was documented, when, and by whom. The team then transfers that handover into the leading care record. Carenji orders and records — it does not decide, it does not dose, it does not monitor, and it does not warn clinically. Carenji is not a medical device.

Why not "replace everything"?

For a home with 50 to 100 beds, a full system change is a substantial undertaking: data migration, training, parallel operation, weeks of getting up to speed. During that time the team works under two logics at once, and that is exactly when errors and friction appear.

A focused companion takes the opposite route. It picks out a single, well-defined process — here PRN medication — and improves it without touching the load-bearing system. The existing product stays the leading record. Carenji only contributes one clean building block, which the team enters in the place it already uses.

"No classical interface costs" — what that means

In its current state Carenji deliberately forgoes a deep technical coupling to the leading systems. The handover is produced as an export that the team transfers into the care record. That is the design intent behind it: no middleware project of its own, no bespoke interface build per site, before any benefit is even visible.

This is explicitly not a promise of zero cost, and not a claim that Carenji "integrates seamlessly" or works "without any change to your workflow". An export step is still a work step, and every home has its own routines. The point is only this: getting started does not require an upfront integration project. You can try the companion slice without first wiring systems together.

Competencies and the ongoing evaluation

A companion changes nothing about nursing competencies. The basis remains the GuKG; responsibility for the order stays with the DGKP. Carenji is prepared for a possible future regulation within the ongoing evaluation of the Wiener Pflegeheimgesetz — whether and how, for instance, a collective subdelegation becomes permissible is open. Carenji explicitly makes no claim that a collective subdelegation would be permissible today.

Status and invitation

Carenji is in its demo phase. There are no homes in live operation yet; all data in the test and demo environment is test data. We are looking for pilot partners from Austrian long-term care who want to try the companion approach alongside their existing software under real conditions. Anyone who would like to help shape it is welcome to get in touch.