Skip to main content
HealOS works with 31 EHRs and practice-management systems. The AI Frontdesk works in 19 of them during calls, and AI Scribe gets notes into 25. Open an EHR for what each product does there, how to connect it, and its API actions.

Integrations

AI Scribe notes: Sent from HealOS writes the finished note to the chart through the EHR connection; Chrome extension fills it into the EHR page open in the clinician’s browser. Connection methods are compared in Connection methods; hospital HL7 feeds are covered in HL7 feeds.
  • Yes: works once the practice connects the EHR (or, for the Chrome extension, installs it).
  • On request: built; HealOS turns it on for a practice after a review with them.
  • Specific setups: built for particular practice configurations; ask us before relying on it.
A Yes means the workflow exists, not that every practice’s setup allows it: practice settings, user permissions and the EHR plan can still limit it, so confirm during onboarding.

API action catalog

This is a catalog of what HealOS can do in each EHR. Running these actions through the HealOS API is coming later. Listing them (GET /ehr/actions) and checking which EHRs your organization has connected (GET /ehr/connections), with the ehr:read scope, are rolling out: they work on staging but are not yet available on api.healos.ai. Every action runs against the practice’s live EHR, never a sandbox.
The catalog lists the 114 actions HealOS runs in 19 EHRs: finding and registering patients, scheduling, and pushing Scribe notes. Each action has a stable name (athena.search_patients), input and output fields, and a safety box.

Endpoints

Reading the safety box

Output fields are documented from the integration code (schema_completeness: best_effort); EHRs can omit optional fields.

Actions

Actions by EHR