Skip to main content

What HealOS does in DrChrono

AI Frontdesk

What the AI Frontdesk (AI Receptionist) can do in DrChrono during a call: Connect it from AI Frontdesk → Integrations → Connect an EHR (Connect your EHR).

AI Scribe

How a finished AI Scribe note gets into DrChrono:

Connection

Method: Official API (OAuth), Chrome extension. How the methods compare. You provide
  • Create an API application in the DrChrono developer portal and paste its Client ID and Client Secret. Give the application a name unique to your practice, such as HealOS_<clinicname>: DrChrono rejects an application name another account already uses, so a plain HealOS can fail.
  • When DrChrono asks for a Redirect URI, paste the Redirect URL shown in HealOS’s DrChrono connect dialog (it has a copy button); it must match exactly.
  • Then approve HealOS in DrChrono’s consent screen, from AI Frontdesk → Integrations → Connect an EHR or Integrations (AI Scribe Integrations).
HealOS does
  • Uses DrChrono’s official API with OAuth 2.0 and refreshes the access token automatically.
  • Sends finished AI Scribe notes to the chart.
  • 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 actions

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.
HealOS supports 5 actions in DrChrono. Action names (drchrono.<action>) are stable.

Search patients

drchrono.search_patients · patients · version 1 Find an existing patient in the EHR by phone number, name, date of birth or email.
Safety
  • External effect: read
  • Writes to the EHR: No
  • Idempotent: Yes
  • Safe to retry: Yes
  • Dry run: Not supported
  • Touches the practice’s live EHR: Yes
Inputs Send at least one field. Outputs

Create patient

drchrono.create_patient · patients · version 1 Register a new patient chart in the EHR. Some EHRs need extra fields (for example a mailing address on NextGen).
Safety
  • External effect: write
  • Writes to the EHR: Yes
  • Idempotent: No
  • Safe to retry: No. After a timeout or unclear result, check the EHR before trying again
  • Dry run: Not supported
  • Touches the practice’s live EHR: Yes
  • Duplicate check: not run by HealOS before creating
Inputs Outputs

Search appointment slots

drchrono.search_slots · scheduling · version 1 List open appointment times, optionally narrowed to a window, provider, visit type or location.
Safety
  • External effect: read
  • Writes to the EHR: No
  • Idempotent: Yes
  • Safe to retry: Yes
  • Dry run: Not supported
  • Touches the practice’s live EHR: Yes
Inputs Outputs Each item in slots:

Book appointment

drchrono.book_appointment · scheduling · version 1 Book an appointment for an existing patient, from a slot returned by search_slots.
Safety
  • External effect: write
  • Writes to the EHR: Yes
  • Idempotent: No
  • Safe to retry: No. After a timeout or unclear result, check the EHR before trying again
  • Dry run: Not supported
  • Touches the practice’s live EHR: Yes
Inputs Send slot_id or start_at_utc. Outputs

List upcoming appointments

drchrono.list_appointments · scheduling · version 1 List a patient’s upcoming appointments.
Safety
  • External effect: read
  • Writes to the EHR: No
  • Idempotent: Yes
  • Safe to retry: Yes
  • Dry run: Not supported
  • Touches the practice’s live EHR: Yes
Inputs Outputs Each item in appointments: