A practice evaluating an AI Agents Platform needs to know whether the agent will book appointments in the EHR or drop requests into a staff queue. The interface standard sets what's technically possible; the EHR vendor's permissions decide what's actually allowed. Health Level Seven (HL7 v2) and Fast Healthcare Interoperability Resources (FHIR) are the two standards EHRs use to exchange scheduling data with outside systems, and a single AI vendor often connects through both, using whichever one the EHR exposes for a given action.

With EHR write-back, an AI agent saves the booking, cancellation, or record update in the EHR itself during the interaction instead of sending the work to staff. The booking is complete only when the schedule change is saved in the EHR, and the interface's write permission determines whether the EHR accepts the change.

HL7 v2 Pushes Notifications and FHIR Answers Requests

The message direction determines whether an outside system can change the schedule or only report changes staff already made.

An outbound HL7 v2 Schedule Information Unsolicited (SIU) feed reports scheduling activity after the fact: it notifies another system that staff already created, moved, or canceled an appointment, but it does not reverse direction and authorize that system to change the schedule. Staff still book the appointment, and the notification arrives only after a scheduler completes the booking.

An authorized inbound scheduling request message (SRM) or a FHIR booking operation changes the workflow, because the EHR can accept the scheduling request itself. With that configuration, an outside application can book appointments and modify or cancel them, whether the request came in over the phone or through a chat.

Federal Rules Require Read Access, and Read-Only Leaves the Booking to a Scheduler

No federal rule requires an EHR vendor to accept appointment write-back from a third-party application. The Office of the National Coordinator for Health Information Technology (ONC) requires FHIR R4 read services for patient data at § 170.315(g)(10), and its test method states that these services "specifically exclude 'write' capabilities, where authenticated and authorized third-party applications would be able to create or modify EHI through a secure API".

The federal HTI-5 proposed rule, published December 29, 2025, would require FHIR interfaces to move beyond read-only access, but it is still only a proposal. Until a final rule requires write-back, a practice must establish the EHR-side connection separately.

A scheduler finishes the job when the AI agent can see provider availability but cannot book through a read-only connection. On your floor, that gap can leave a patient who ends the call or closes the chat window believing the appointment is booked while a scheduler works a request queue, reconciles requests by hand, and risks double bookings from sync lag. An approved write-back connection closes that gap: the patient hears or sees a confirmed booking.

What to Verify Before Trusting a FHIR Write-Back Claim

No EHR vendor supports third-party appointment write-back the same way, and each grants access through its own partner program, interface, and approval process. Don't treat a product's claim that it supports FHIR as proof of appointment write access.

Before trusting a vendor's write-back claim, check:

• FHIR version and operation: which version is supported and which operations (read, slot search, booking, update) it exposes
• Partner program requirements: whether the EHR vendor requires enrollment in a specific integration or marketplace program
• Production approval: whether the write-back connection has been approved for the live production tenant, not just a sandbox
• Documented limits: which appointment types, specialties, or workflows the connection excludes

Those details determine whether staff avoid another request queue and patients leave any channel with an appointment that is actually on the schedule.

How Write-Back Access Differs by EHR Vendor

The write-back path varies by vendor. Assort Health integrates bidirectionally with 37 EHR and PMS systems, including Epic and athenahealth, with the specific production write-back connection approved for each practice location:

• Epic: gates access through a vendor program with site-specific approval.
• Oracle Health: may exclude appointments tied to a clinical order or a specific care-team member.
• athenahealth: often routes scheduling writes through a separate proprietary interface rather than its certified FHIR endpoint.
• ModMed: may require Marketplace participation for appointment writes.
• eClinicalWorks and Veradigm: both frequently require a separate proprietary or HL7 v2 interface for bidirectional scheduling.

In each case, confirm the exact production path and its documented limits before assuming the agent can book end-to-end.

How Assort Health Books Inside the EHR During the Interaction

Assort Health's AI Agents Platform holds approved write-back connections across the supported EHRs, part of a deep bidirectional integration spanning 37 EHR and PMS systems. The same interface carries writes from every channel the agent operates in, from the AI voice agent on the phone to the web chat agent on the practice website.

In each case, the agent reads live provider availability, applies the practice's specialty-specific scheduling logic, insurance rules, and per-physician requirements, then books the appointment in the EHR during the interaction and syncs the change back in real time.

South Shore Orthopedics Cleared Its Voicemail Backlog After AI Began Writing Back in Real Time

South Shore Orthopedics, an orthopedic practice running on athenahealth, needed to clear 600 to 1,000 voicemails that staff couldn't reach for weeks. The practice partnered with Assort Health's team on an agent with a defined call workflow. It answers inbound calls, then books, reschedules, confirms, and cancels while writing each action into athenahealth. When a patient gives up a slot at night, the next caller books it instead of leaving a voicemail for staff to work in the morning.

 "Patient access is the number one thing we've built our practice around: great access with great outcomes. If you're not answering the phone or giving patients ways to reach you, even after hours, you can lose business. Assort's agent lets us be there 24/7, keeping schedules full and making a huge difference for both our patients and our front office staff."  

David Kobasa, Chief Operating Officer, South Shore Orthopedics

At booking, South Shore's agent applies the practice's scheduling logic, care protocols, and decision pathways across specialties. It matches the visit type to an appropriate provider and slot. The same approved write-back connection also records interaction outcomes for web chat and outbound campaigns.

Go-Live Includes HL7 and FHIR Write-Back Testing

Assort Health's engineering team partners with your practice during implementation to match the live scheduling connection to EHR approvals, scheduling logic, provider requirements, and the workflows patients and staff will use across every channel. The team tests booking, rescheduling, cancellation, authentication, handoffs, and authorization for any integration middleware (a translation layer that sits between the AI vendor and the EHR).

After each EHR release, Assort Health re-tests the live connection to confirm the EHR still accepts bookings, reschedules, and cancellations directly from every channel, so scheduling changes keep landing on the provider's schedule instead of a staff queue.

At go-live, staff should know which requests the AI agent completes on its own in the EHR and which it hands off to a person with full interaction context. That split keeps the live workflow aligned with the write-back paths approved and tested during implementation.

Book a demo with Assort Health, and the team will demonstrate accurate scheduling changes in your EHR during a call or a web chat.

Frequently Asked Questions

How Do You Verify an AI Vendor's EHR Write-Back During a Demo?

Ask the vendor to book a live appointment in a test tenant configured like production, then confirm the booking landed on the correct provider's schedule with the right visit type and duration inside the EHR itself, not just in the vendor's dashboard. Run the same test from every channel the agent operates in, then cancel each one and watch the slot reopen.

What Happens When the Agent Cannot Write a Booking Back to the EHR?

When the write-back path doesn't cover a request, the AI agent collects the patient's information, then hands the interaction to a staff member with a full-context dashboard so patients never have to repeat themselves. The practice decides in advance which requests route to a person, such as a workflow the agent is not configured for (for example, certain orthopedic workflows that require clinical judgment) or any patient who asks for a human.

Can EHR Upgrades Break AI Write-Back?

Yes, if a release changes authentication, API behavior, or interface configuration, previously working write-back can start failing silently on one channel or across all of them. Confirm the AI vendor re-tests the production connection from every channel after each EHR release before patients rely on it.