Skip to main content

What HealOS does in Practice Fusion

AI Frontdesk

What the AI Frontdesk (AI Receptionist) can do in Practice Fusion 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 Practice Fusion:

Connection

Method: HealOS cloud browser, Chrome extension. How the methods compare. You provide
  • Cloud connection: a Practice Fusion email and password, in AI Frontdesk → Integrations → Connect an EHR. Practice Fusion’s two-factor code is sent by phone; HealOS receives it on a number set up with you during onboarding, or a staff member enters it.
  • Extension connection: the HealOS Chrome extension, with a staff member signed in to Practice Fusion in Chrome.
HealOS does
  • Checks the sign-in before saving anything: a login that fails is not stored.
  • Stores the credentials encrypted and signs in from a secure, US-based cloud browser.
  • Keeps one signed-in session per practice and renews it during business hours, so calls don’t wait for a login.
  • Queues AI Scribe notes and sends one at a time per patient.
Limits
  • Looking up, cancelling and rescheduling appointments need the cloud connection.
  • With the extension connection, actions run only while a signed-in Chrome tab is open.
  • 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 8 actions in Practice Fusion. Action names (practicefusion.<action>) are stable.

Search patients

practicefusion.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
  • Practice Fusion has no public API. Actions run through the HealOS browser extension in a staff member’s signed-in Practice Fusion tab, or through the HealOS cloud connection.
Inputs Send at least one field. Outputs

Create patient

practicefusion.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: searches by last name and date of birth first, and links an exact single match instead of creating a chart
  • Practice Fusion has no public API. Actions run through the HealOS browser extension in a staff member’s signed-in Practice Fusion tab, or through the HealOS cloud connection.
Inputs Outputs

Search appointment slots

practicefusion.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
  • Practice Fusion has no public API. Actions run through the HealOS browser extension in a staff member’s signed-in Practice Fusion tab, or through the HealOS cloud connection.
Inputs Outputs Each item in slots:

Book appointment

practicefusion.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
  • Practice Fusion has no public API. Actions run through the HealOS browser extension in a staff member’s signed-in Practice Fusion tab, or through the HealOS cloud connection.
Inputs Send slot_id or start_at_utc. Outputs

List upcoming appointments

practicefusion.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
  • Practice Fusion has no public API. Actions run through the HealOS browser extension in a staff member’s signed-in Practice Fusion tab, or through the HealOS cloud connection.
  • Needs the cloud connection.
Inputs Outputs Each item in appointments:

Cancel appointment

practicefusion.cancel_appointment · scheduling · version 1 Cancel one of the patient’s appointments. Refused unless the appointment belongs to that patient.
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
  • Ownership check: the appointment must belong to the patient, or the action is refused
  • Practice Fusion has no public API. Actions run through the HealOS browser extension in a staff member’s signed-in Practice Fusion tab, or through the HealOS cloud connection.
  • Needs the cloud connection.
Inputs Outputs

Reschedule appointment

practicefusion.reschedule_appointment · scheduling · version 1 Move one of the patient’s appointments to a new time. Refused unless the appointment belongs to that patient.
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
  • Ownership check: the appointment must belong to the patient, or the action is refused
  • Practice Fusion has no public API. Actions run through the HealOS browser extension in a staff member’s signed-in Practice Fusion tab, or through the HealOS cloud connection.
  • Needs the cloud connection.
Inputs Send slot_id or start_at_utc. Outputs

Push clinical note

practicefusion.push_note · notes · version 1 Write a HealOS Scribe note into the patient’s chart in the EHR.
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
  • Practice Fusion has no public API. Actions run through the HealOS browser extension in a staff member’s signed-in Practice Fusion tab, or through the HealOS cloud connection.
  • Asynchronous: the write is queued and completed by the HealOS browser extension or cloud connection, so the result reports a queued job, not a saved note. One pending push per patient.
Inputs Outputs