Integrations

Runs on the EHR
you already have.

Adentris is live on six EHRs today, and all six are ready to connect for new customers. It connects either by API or through the AI Web Agent, which reads the EHR through its user interface the way a trained reviewer would. Either way, clinicians keep documenting where they document now, and nobody on your side builds anything.

Request a demo Get a free revenue check
In production

Six EHRs, live with customers.

We list a system here once a customer runs Adentris on it, not before. If yours is missing, read the section below the list.

  • eClinicalWorks

    Ambulatory and multi-specialty care Live · ready to connect

  • Kipu Health

    Addiction treatment and behavioral health Live · ready to connect Case studies Solutions 2 Recovery →Resilient Recovery →

  • Alleva

    Addiction treatment and behavioral health Live · ready to connect Case study Sobrius Health →

  • Ritten

    Addiction treatment and behavioral health Live · ready to connect

  • Ease Health

    Behavioral health and addiction treatment Live · ready to connect

  • PIMSY

    Mental and behavioral health practices Live · ready to connect
How Adentris connects

Two routes in. Same review on the other side.

Which route applies depends on what your EHR exposes. The findings, the audit trail, and the security controls are identical either way.

API integration

Where the EHR exposes chart data through an API, Adentris reads it directly. Records arrive structured, so the review runs continuously against the live census rather than on periodic exports.

AI Web Agent

Where there is no useful API, the AI Web Agent reads the EHR through its interface, the same way a trained reviewer would. It also reads what APIs and HL7 feeds tend to leave behind: scanned PDFs, free-text addenda, and signature blocks. There is nothing for IT to build and nothing to maintain.

Not on the list?

Tell us what you run. We confirm the route first.

The AI Web Agent is not tied to a particular vendor, so an EHR outside this list is a scoping question, not a partnership negotiation. On a short call we look at your system, confirm how Adentris would connect, and give you a timeline before anything is signed.

Security does not change with the route. All inference runs inside Microsoft Azure under a signed BAA, patient data is never sent to consumer LLM APIs, and every agent action is kept in an audit trail. Trust and security details.

Book a 30-minute call
Integrations FAQ

Common questions.

01 Which EHRs does Adentris work with today?

Adentris is live on eClinicalWorks, Kipu Health, Alleva, Ritten, Ease Health, and PIMSY, and each of them is ready to connect for a new customer.

02 Do we need an IT project to connect our EHR?

No integration project on your side. The AI Web Agent reads the EHR through its interface, so there is nothing for your IT team to build or maintain. Where the EHR offers an API, the connection is configured during onboarding.

03 Our EHR is not on the list. Can we still use Adentris?

Usually, yes. The AI Web Agent is not tied to a particular vendor, so an EHR outside this list is a scoping question rather than a partnership negotiation. Tell us what you run and we confirm the route and the timeline before anything is signed.

04 How long does it take to go live?

It depends on your EHR, how many sites you start with, and which modules you turn on, so we agree the timeline with you during scoping rather than promise one number up front. For reference, Sobrius Health went from contract to full production, with the entire compliance team onboarded, in 60 days.

05 Does patient data leave a controlled environment?

All inference runs inside Microsoft Azure under a signed BAA. Patient data is never sent to consumer LLM APIs, the architecture supports 42 CFR Part 2 programs, and every agent action is kept in an audit trail.