The first question every group practice asks during a demo is some version of “does it work with our EHR.” The honest answer for behavioral health is more nuanced than a yes/no. There are about a dozen EHRs in serious use across the field, three of which account for most of the questions we get: Osmind, Kalix, and SimplePractice. This post walks through what the integration actually does, what it does not do, and what setup looks like without a paid integration consultant on either side.
The short version is that Nextvisit pushes the finished note, the diagnosis codes, and (where supported) the encounter metadata to the destination EHR after you sign. For Osmind and Kalix, the push is two-way, meaning the patient roster, demographics, and prior chart context flow back from the EHR into Nextvisit so Aria can reference them. For SimplePractice, the push is one-way today, with two-way support in active development.
What gets sent
When you sign an encounter in Nextvisit, the system packages the following and sends it to the configured EHR:
- The clinical note in the format the destination EHR expects (HTML, PDF, or structured fields, depending on the EHR’s API).
- The diagnosis codes (ICD-10) you accepted in the coding sidebar, with the primary code first.
- The CPT code or service code if your workspace has billing turned on.
- The encounter metadata: date and time, duration, service location, provider.
- Any structured screener scores (PHQ-9, GAD-7, AUDIT, CRAFFT, PCL-5) recorded during the visit.
The note arrives in the destination chart attached to the correct patient and the correct visit date. No copy/paste. No “export to PDF and re-upload.” If the EHR has a structured note field, the note is sent into that field. If it only accepts HTML, the note is sent as HTML with the headings preserved.
What comes back (Osmind, Kalix)
Two-way integration means the connection runs in both directions. For Osmind and Kalix, Nextvisit pulls:
- The patient roster, on a schedule and on demand.
- Patient demographics, contact info, and (where available) insurance.
- Prior chart context, scoped to what your authentication grants.
- Updates to the patient record made on the EHR side after the initial sync.
The benefit is not just bookkeeping. When AriaMD generates a Treatment Pulse or an AI Timeline view for a patient, it has access to the prior chart, not only the encounters that originated in Nextvisit. Polypharmacy, prior diagnoses, and longitudinal screener trends are visible to the model when it drafts the next note. That changes the quality of the draft on day one for an established patient, instead of week three.
What setup actually looks like
Setup is a settings flow, not an implementation project. The steps:
- In Nextvisit, go to Settings, Tools and AI, External Apps. Select your EHR.
- Authenticate. Osmind and Kalix use OAuth; SimplePractice uses an API token issued from your SimplePractice settings.
- Map your providers. Each Nextvisit provider is mapped to the corresponding EHR provider once. Mapping is one click for most workspaces.
- Choose the push behavior. The two relevant settings are when the push fires (on sign, by default) and what gets sent (note plus codes plus metadata, by default).
- Test with one encounter. Sign a real or test encounter and verify it lands correctly in the destination chart.
End to end, this takes about 20 minutes for a single-provider practice and an hour for a 10 to 50 provider group, most of which is the provider mapping step. There is no vendor consultant on either side. We do not charge an integration fee. Osmind, Kalix, and SimplePractice do not charge integration fees for their public APIs.
What we do not do
A few things to be specific about, because the integration story in this category is full of overpromises.
We do not modify existing notes after they have been pushed. If you unsign and re-sign an encounter in Nextvisit, the destination EHR receives the new version, but it does not overwrite the original; it appends or replaces depending on the destination EHR’s policy. Most practices configure this behavior explicitly during setup.
We do not write directly to fields the destination EHR does not expose via API. If your EHR has a structured custom-form field that is not in their public API, the note still arrives, but it lands in the standard note field, not the custom one.
We do not resolve the EHR’s own bugs. If a destination EHR has a known issue with the way it renders HTML notes (Kalix had one for a while in 2025; it is fixed now), our note inherits that rendering issue. We document these in the integration page in the app and update them when the EHR ships a fix.
What is in development
Two-way SimplePractice is the largest open item. The SimplePractice API exposes the patient roster but not the full chart history at the depth Osmind and Kalix do, so the read-side parity is not there yet. We expect to ship an initial two-way version in the second half of 2026, scoped to roster, demographics, and recent visits.
Beyond SimplePractice, the next EHRs on the integration roadmap are TheraNest, TherapyNotes, and one custom integration for a large Medicaid-behavioral-health group on a homegrown EHR. The pattern is the same: signed-encounter push first, two-way read second, no consultant required.
If your EHR is not on this list and you want to know whether an integration is feasible, the answer almost always is, provided the EHR exposes a documented API for notes and the patient roster. The booking link is in the demo CTA.