> ## Documentation Index
> Fetch the complete documentation index at: https://docs.healos.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connection methods

> How HealOS connects to EHRs and hospital systems, what you provide and what HealOS does

HealOS connects to each EHR in one of six ways. The method decides what you hand over, how fast setup is, and what keeps working when nobody is at a desk. Each [EHR page](https://docs.healos.ai/ehr-actions/overview.md) names its method and lists exactly what to provide.

| Method | How it works | You provide | HealOS does | Used by |
| - | - | - | - | - |
| **Official API (OAuth)** | HealOS calls the EHR's own API with a token you authorize | Approve HealOS in the EHR's consent screen; some EHRs first need an API app or API access from the vendor | Refreshes tokens, retries rate limits, never asks for a password | Acuity Scheduling, DrChrono, Elation, Halaxy |
| **Official API (API credentials)** | HealOS calls the EHR's API with a key or API user you create | An API key or API user, issued in the EHR or by its support team | Stores the credentials encrypted; uses them only for the actions you enable | Cerbo, Hint, ModMed, Tebra, athenahealth (note sending), Acuity Scheduling (API key option) |
| **SMART on FHIR** | Standards-based FHIR connection approved per health system | Your FHIR base URL (and tenant ID on Oracle Health); your health system enables the HealOS app; a clinician signs in once | Reads the patient, encounter and practitioner; writes the note back as a document | Epic, Oracle Health (Cerner) |
| **HealOS cloud browser** | For EHRs without a usable API, HealOS signs in to the EHR's web app from a secure, US-based cloud browser and acts like a careful staff member | A login (ideally a dedicated user), plus the two-factor setup the EHR uses: an authenticator secret, or a code inbox or phone set up with HealOS | Verifies the login before saving; stores credentials encrypted; keeps one signed-in session per practice and renews it during business hours; generates or reads two-factor codes itself | athenahealth, CharmHealth, CurveHero, eClinicalWorks, NextGen Office, Practice Fusion, SimplePractice, TheraNest, TherapyNotes, WebPT |
| **Chrome extension** | The HealOS extension works inside the clinician's own signed-in EHR tab | Install the [extension](https://docs.healos.ai/guides/scribe/chrome-extension.md) and keep the EHR open in Chrome | Fills AI Scribe notes into the open note for the clinician to review and sign; nothing about the EHR login reaches HealOS | AdvancedMD, CureMD, Cliniko, Kalix, Office Ally and others; also many API EHRs for note filling |
| **HL7 feed** | The hospital's interface engine sends HL7 v2 messages to HealOS | An interface-engine feed over HTTPS, or MLLP over a site-to-site VPN | Builds patients, appointments and results from the feed for AI Scribe context | Hospital systems such as MEDITECH. See [HL7 feeds](https://docs.healos.ai/connections/hl7.md) |

## Choosing a method

* **An official API is the most durable.** Setup can take days when the vendor must grant API access or a fee applies, but it keeps working through password changes.
* **The cloud browser is the fastest to set up** (minutes, with a login), and the only option for EHRs without a usable API. Give HealOS a dedicated user: some EHRs allow one active session per login, and a shared user's password changes break the connection.
* **The Chrome extension needs no credentials**, but it works only while the clinician's EHR tab is open, so it suits note filling, not after-hours phone calls.

## Where you connect

| Product | Where in HealOS | Who can connect |
| - | - | - |
| AI Frontdesk (AI Receptionist) | **AI Frontdesk → Integrations → Connect an EHR** ([guide](https://docs.healos.ai/guides/receptionist/connect-your-ehr.md)) | Organization admins |
| AI Scribe | **Integrations** (AI Scribe Integrations), or the [Chrome extension](https://docs.healos.ai/guides/scribe/chrome-extension.md) | Clinicians and admins |
| HL7 feed | **Integrations → Connect HL7 Feed**, with the tenant code HealOS gives you | Organization admins |

Other ways the AI Frontdesk can book without an EHR connection: [HealOS Scheduling](https://docs.healos.ai/guides/receptionist/overview.md) and [Google Calendar](https://docs.healos.ai/guides/receptionist/google-calendar.md).

## Security

* Credentials are encrypted at rest and used only by the HealOS service that runs your enabled actions. They are never returned by the HealOS API: [`GET /ehr/connections`](https://docs.healos.ai/api-reference/ehr/list-your-ehr-connections) reports connection status only.
* Every action runs against your live EHR, never a sandbox, and writes that change appointments are enabled per practice. See [Security](https://docs.healos.ai/security.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.