Skip to main content

Heidi Integrations Overview

All you need to know about Heidi Integrations

Updated yesterday

Heidi integrates with a growing number of electronic health record (EHR) systems and clinical platforms. This article explains the two types of integration Heidi offers, what each one does, and how to find the right setup guide for your system.

Our list of supported integrations is always growing. If you don't see your EHR listed here, or you're unsure which integration type applies to you, chat with our team, we're happy to help.


Integration types

Heidi offers two broad styles of integration. The experience, features, and plan requirements differ depending on which type your EHR uses.

Embedded integrations

An Embedded integration places Heidi directly inside your EHR as a pop-up or side panel, typically through a widget comparable to the Heidi Chrome Extension (such as Vim Connect). You stay in your existing clinical workflow and interact with Heidi without switching windows.

Key characteristics:

  • Heidi appears as an overlay or sidebar within the EHR

  • Recording, note generation, and note push all happen from inside the EHR window

  • Setup usually involves installing through your profile in the EHR Partner. Chat with our team if you run into issues.

Connect integrations

A Connect integration is a deeper, back-end link between Heidi and your EHR. In most cases you access it through the Heidi app itself (web or desktop), and the integration handles tasks like pulling in your appointment schedule, syncing patient context, and pushing completed notes back into the correct patient record.

Key characteristics:

  • Set up and accessed from within Heidi → Settings → EMR Integrations

  • Appointment schedules sync into Heidi automatically

  • Notes are pushed back to the EHR with a single click from Heidi

  • Features vary by EHR partner — some support field-level mapping, others push to a single note field


Plan requirements

As a general guide:

  • Embedded integrations are typically available on the Clinician tier.

  • Connect integrations and Embedded integrations delivered through a partner (e.g. Vim for eClinicalWorks) typically require a Practice (or higher) tier.

These are general guidelines, not hard rules. Plan requirements can vary by integration partner and may change as new integrations are released. Always check the specific setup article for your EHR, or ask our team, to confirm exactly what's needed.


Available integrations

Below is a summary of currently documented integrations. For full setup instructions, click through to the relevant article.

Connect integrations

EHR

Plan required

Setup guide

Best Practice

Practice

Cliniko

Practice

Athena

Practice

Veradigm

Practice / Enterprise

Zedmed

Practice

Genie

Practice

Embedded integrations

EHR / Platform

Method

Plan required

Setup guide

Any web-based EHR

Heidi Chrome Extension

Clinician

eClinicalWorks

Vim Connect widget

Practice

Don't see your EHR? Check our integrations page for the latest list, or reach out to our team, new integrations are added regularly.


How do I know which type I have?

If you open Heidi as a separate app (or browser tab) and see your appointments synced in from your EHR, you're using a Connect integration.

If Heidi appears as a pop-up or panel inside your EHR window (for example, through the Chrome Extension or a Vim widget), you're using an Embedded integration.

Some clinics use both — for instance, a Connect integration to sync schedules and push notes, alongside the Chrome Extension for quick access during telehealth consultations in a browser.

Can I have multiple integrations connected to my Heidi?

No, Heidi profiles can only be linked to one integration. If you require integration to more than one EHR, then chat to the team and we will be happy to answer any questions.


Need help?

If you're not sure which integration is right for your setup, or you'd like help getting started, reach out to the Heidi team through the chat widget below or contact your account representative.

Did this answer your question?