Connecting your EHR is a settings flow, not a project. There is no consultant on either side and no integration fee. Most single-provider practices finish setup in twenty minutes. A 10 to 50 provider group takes about an hour, most of which is provider mapping.
The three EHRs in this article cover the majority of behavioral-health practices on Nextvisit. The same pattern applies to other EHRs with public APIs.
Where the setting lives
Open Settings, then Tools and AI, then External Apps (/settings). The External Apps panel lists the EHR connectors.
Click the EHR you want to connect. The next steps depend on whether the EHR uses OAuth or an API token.
Osmind (OAuth)
Click Connect. A browser window redirects to Osmind. Log in with your Osmind admin credentials. Authorize Nextvisit to read the patient roster and write notes. You return to the Nextvisit External Apps panel with the connection marked Active.
Osmind is two-way. After connection, the patient roster syncs into Nextvisit on a schedule. Demographics, contact info, and prior chart context are available to AriaMD when it drafts notes for an established Osmind patient.
Kalix (OAuth)
Same pattern as Osmind. Click Connect, complete the OAuth flow with your Kalix administrator account, return to Nextvisit. Kalix is also two-way. The roster, demographics, and prior context flow back into Nextvisit so AriaMD can reference them.
SimplePractice (API token)
SimplePractice uses an API token. Generate one in your SimplePractice account settings under API or Integrations (the exact location moves around). Copy the token, paste it into the Nextvisit External Apps panel, click Connect.
SimplePractice is one-way today. The push from Nextvisit to SimplePractice works the same as Osmind and Kalix. The read direction (roster sync into Nextvisit) is in development and expected in the second half of 2026. For now, you create patients in SimplePractice and add them in Nextvisit separately, or rely on Aria’s per-encounter capture without longitudinal context.
Provider mapping
Once the connection is active, map your providers. Every Nextvisit provider needs to map to the corresponding EHR provider so the note arrives under the correct clinician’s name in the destination chart. Mapping is a single click per provider for most workspaces. The panel suggests matches based on name and email; verify and confirm.
For groups, this is the longest step. A 10 to 50 provider group typically takes 30 to 45 minutes for the admin to verify all matches.
Push behavior
Default push behavior covers most practices: the note pushes on Sign, with the diagnosis codes, CPT or service code (if billing is on), encounter metadata, and structured screener scores included.
The relevant settings:
- When to push: on Sign (default), on Unsign, or both.
- What to send: note plus codes plus metadata (default), or note only.
- Update behavior: append a new version, or replace the prior version. Default is append, which preserves history in the destination chart.
Test with one encounter
Before letting a full clinic day push automatically, sign one real or test encounter. Open the destination EHR. Confirm the note landed on the correct patient and the correct visit date, with the codes and metadata you expected.
If anything looks wrong, do not retry. Check the Connection status in the External Apps panel and read the most recent log entry. Most setup-time errors are a missing provider mapping or a permission scope that was not granted during OAuth. Both are quick fixes.
If you need help, email hello@nextvisit.ai with the EHR, the connection date, and the encounter ID. The integrations
team responds in hours.