An addition, not a system change: why Carenji sits alongside your care documentation

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 an addition, not a replacement.

What Carenji takes on — and what it does not

Carenji takes on the medication and bedside part of the day: the medication schedule with its versions, the administration round, PRN and individual medication, stock together with the pharmacy reorder, and vitals at the bedside. The nurse documents where the action happens — with a timestamp and an initial, at the resident's side.

What stays with your leading care record: the care process, care planning, reports and everything your facility manages there today. Carenji does not create a second record out of it. It delivers a traceable, exportable handover: an ordered account of what was documented, when and by whom, which your team enters in the place it already uses.

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.

An addition takes the opposite route. It takes the part of the day that most often ends up on paper slips and in Excel lists today — medication, stock, vitals — and brings it to the point of care without touching the load-bearing system. The existing product stays the leading record.

"No upfront integration project" — 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 automatically 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 Carenji alongside your existing software without first wiring systems together.

Competencies and the ongoing evaluation

An addition 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; 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 Carenji alongside their existing software under real conditions. Anyone who would like to help shape it is welcome to get in touch.