# Nedap Ons, eCare Puur and Medimo are connected.

Your EHR stays the source. Inora never reads with more rights than the care worker has, and the report goes back on approval.

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

Inora’s connection library: the client record, document management, Microsoft 365, identity, rostering and HR and the learning platform, each with its switch. A custom MCP server is added by name and server URL and appears in the library, connected.

## What comes in. What goes back.

Your care workers stop being the connection between your systems.

From the EHR into Inora come reports, the care plan, the episode and the planning. On the care worker’s approval, the report goes back to the EHR. The incident report, care plan change and message are ready as drafts for their own systems.

- ### Always the latest.

  When the care plan changes in your EHR, the preparation changes with it.

- ### Nothing typed twice.

  An approved report goes to the right place, with date, time and name.

- ### The record gets what belongs in it.

  What is relevant from a conversation goes to the record. A text between colleagues stays a text.

## The connection with Nedap Ons.

Through Ons Podium, on each care worker’s own rights.

1. Find Nedap Ons under Connections and give access through Ons Podium.

2. Reports, care plan and episode, on each care worker’s own account.

3. The approved report goes to the client’s record in Ons, with date, time and name.

The Nedap Ons connection under Connections in Inora: connected through Ons Podium, for two district teams, in SOAP.

[Inora for Nedap Ons](https://inora.ai/en) [Inora alongside Nedap Ons](https://axiomatic.digital/en/expertise/compare/inora-vs-nedap-ons)

## Day one needs no connection.

In the pilot your team works on its own logins. After that, your IT turns the connections on; without an API, it stays their own login.

- The log: on behalf of J. Smit, Inora reads the care plan and the reports and drafts the report; J. Smit approves, and the report goes to the EHR.

  ### Inora works on someone’s behalf, never with more rights than that person has.

  The log names both. It shows per step what Inora did and on whose behalf, never what anyone asks.

[IT and security](https://axiomatic.digital/en/trust/security)

## Inora in the systems you already use.

Each with its own page: what you do there, how it works, how to switch it on.

- #### [Copilot](https://inora.ai/en)

  By Axiomatic

  Your working agreements and the client record, from Copilot.

- #### [Teams](https://inora.ai/en)

  By Axiomatic

  The message before the visit and your approval after it, in Teams.

- #### [Nedap Ons](https://inora.ai/en)

  By Axiomatic

  The record stays in Ons. Inora prepares what follows.

- #### [Attendi](https://inora.ai/en)

  By Axiomatic

  Your team keeps dictating. Inora prepares what follows.

- #### [Zenya](https://inora.ai/en)

  By Axiomatic

  The version that counts from your approved protocol, where the question is asked.

- [Inora in your apps](https://inora.ai/en)

## Your other systems are in the library too.

- ### [Client record.](https://inora.ai/en)

  Nedap Ons and eCare Puur for the record, Medimo for medication.

- ### [Document management.](https://inora.ai/en)

  Zenya, SharePoint and OneDrive as sources for your instructions and agreements.

- ### [Microsoft 365.](https://inora.ai/en)

  Teams and Outlook. Copilot reads your approved agreements through Inora, with your handbook as the source, and what the care worker may see in the record.

- ### [Identity and access.](https://axiomatic.digital/en/trust/security)

  Entra ID, Okta, Google or any other SAML/OIDC provider.

- ### Rosters and HR.

  Current teams, roles and staffing from your own systems.

- ### [Learning platforms.](https://inora.ai/en)

  Theory, test results and competence records, connected to Matrix.

## Your administrator switches it on.

One switch per connection, with the rights your organisation gives.

- 01

  ### Single sign-on by default.

  On your own identity management. No shared accounts or passwords.

- 02

  ### Accounts through SCIM.

  Accounts open and close from your own management.

- 03

  ### Your own MCP server.

  A name and a server URL, and your own application is connected.

[IT and security](https://axiomatic.digital/en/trust/security) [MCP](https://inora.ai/en)

## It sits on top. Nothing goes away.

- ### Is the connection with Nedap Ons available?

  Yes. Your IT turns the connection on after the pilot.

  In the pilot Inora reads on your team’s own logins. From then on it reads from Ons through the connection and the report goes back on approval.

  [Inora for Nedap Ons](https://inora.ai/en)

- ### Will this be tab seven?

  Inora comes as a message.

  Record, planning and medication stay on their screens. What people retype disappears.

- ### Do we have to drop Attendi?

  Your team keeps dictating.

  Inora picks up what follows the spoken sentence, from care plan to incident report.

  [Inora for Attendi](https://inora.ai/en)

## Connect your existing systems to Inora.

Talk your systems through with our team, or find out with the AI scan where a connection returns the most.

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