# Always on. Connected to everything. Every step named.

Chat puts the burden on whoever has the least time. An always-on agent works when nobody has anything open: the record read before the shift, the visit prepared, then one approval. This is what it runs on, and why your CISO can sign for it.

********

One night of the always-on system. The roster starts the run. In a machine of its own, with the care worker’s login and rights, Inora reads the EHR and prepares the visit. One approval. Only the report goes into the record; incident report, care plan and message are ready as drafts for their own system. The trail shows both Inora and the care worker.

## RAG is a checkbox. The advantage moved from answering to doing.

Every care organisation now has a chatbot on its documents, or buys one by Friday. What counts is what happens after the question is answered, and who still has to think of it then.

- Always on

  Work starts before anyone opens anything: the day prepared, the record read, the follow-up drafted.

- On top of what is there

  The EHR stays the memory. The work leaves: everything typed, retyped and copied.

- One layer

  Your rules, formats, corrections and open work in one place, yours, not a vendor’s underneath.

## Everything connects. Even without an API.

An agent works with the care worker’s login and rights, in a machine of its own. What that person may reach, the agent reaches, on day one and with no IT project.

- ### Official API

  - When

    The vendor offers one, such as Nedap Ons

  - How

    With your own approval, per connection

- ### Your document stores

  - When

    SharePoint, Azure, network drives

  - How

    Directly, with an owner per source

- ### Its own machine

  - When

    No API

  - How

    An operating system of its own per user, with that login and those rights

## Its own machine. Your rights. A complete trail.

Inora is the always-on system working over a Dutch EHR. Raw computer use is a component; the environment around it is the product. Built to NEN 7510 and ISO 27001.

- \[01]

  ### A machine per user

  Every agent runs in its own microVM with its own kernel, torn down per session.

- \[02]

  ### The agent is the person

  The identity and rights from your Entra ID or other IdP. Someone leaves, access ends by itself. SSO by default, one-click SCIM.

- \[03]

  ### Access per task

  One client and the protocols that apply, for one task, with short-lived keys.

- \[04]

  ### Closed by default

  Your data goes only where you send it, set per connection or named system, with a tested kill switch.

- \[05]

  ### A trail nothing can change

  Every action with who, for which client, from which source version, drafted for and approved by.

- \[06]

  ### Nothing lands without a person

  Every irreversible or outward action asks an approval. Everything in the record has an approver.

- \[07]

  ### What goes in stays yours

  Readable files. EU hosting or your own servers. No one trains a model on your data.

- \[08]

  ### Better through use

  Sources corrected by an owner, formats in the product, in days. 99.6% of messages answered.

## Nothing happens in care without a name behind it.

The market sells digital employees with their own logins and hopes policy follows. We turn it around: software borrows its authority from a professional, for one task, and leaves a trail. That design is how you go faster than anyone governing by memo.

## Send your CISO these links.

- [IT and security](https://axiomatic.digital/en/trust/security) The answers and the file for your assessment.
- [The story](https://axiomatic.digital/en/story) Why care is moving to a new kind of software.

## Put it to your CISO.

[Talk to our team](https://axiomatic.digital/en/contact#conversation) [Take the 5-minute AI scan](https://axiomatic.digital/en/scan)
