front desk
The EHR Is the Source of Truth. Booking AI Should Act Like It.
2026-10-08 · 3 min read
The short answer: most double-bookings from online scheduling don't come
from bad software. They come from two calendars. When a booking tool keeps
its own copy of the schedule, that copy drifts from the real one. A provider
blocks an afternoon, a nurse visit runs long, someone books by phone, and the
copy doesn't know. The patient picks a time that no longer exists, and the
front desk spends the next morning calling people back.
The design rule we built Medora Front Desk on is simple. **The practice's
schedule in the EHR is the source of truth. The AI doesn't keep a second
one.**
Why a second calendar always drifts
An allergy schedule is not a grid of identical slots. New-patient visits need
time for skin testing. Shot clinic runs on its own rhythm. Patch-test patients
come back for the Day 2 reading and again on Day 3 or 4, and those return
visits have to land on days the testing room is staffed. The rules live in
the EHR's templates and in the heads of the people who run the front desk.
Any tool that copies the schedule and then books from the copy has to
re-learn all of that and keep it in sync, all the time. It won't. The gap
between the copy and the truth is where the bad bookings come from.
The rule, in practice
Medora Front Desk works from the practice's real schedule:
- Patients book online into the practice's real open slots. Not a
separate availability list someone has to maintain.
- The website chat and the phone agent work from the same knowledge. A
patient who calls at night and a patient who chats on the website are
offered the same answers.
- Every request lands in one queue the staff already works. Phone, chat
and online requests don't end up in three inboxes.
- Staff approve a booking before it goes into the EMR. The AI proposes,
and a person on the team confirms. Nothing is written into the schedule
behind the front desk's back.
- After-hours requests are captured instead of going to voicemail, so
Monday morning starts with a queue, not a list of messages to call back.
What Front Desk doesn't do matters just as much. It doesn't give medical
advice or triage symptoms, and it doesn't book without staff approval.
Why "the AI proposes, a person confirms" works everywhere
We use the same rule across Medora. In the note, Medora Copilot drafts and
the clinician signs. At the front desk, Medora proposes the booking and staff
approve it. Each time, the record that matters (the chart, the
schedule) stays under the practice's control, and the AI's job is to take
the busywork out of keeping it current.
For an allergy practice that means the EHR stays the one place the truth
lives. Your staff stop reconciling two systems, and patients stop being
offered times that were never really open.
Questions practices ask
Does Medora keep its own copy of our schedule?
No. Patients are offered the practice's real open slots, and bookings go
into the EMR only after staff approve them.
Can it book on its own overnight?
It captures the request overnight. A person on your team approves it before
it goes into the EMR.
Which EHRs does it work with?
Medora works with supported EMRs. Ask us about yours on the
Does it answer clinical questions?
No. Front Desk handles booking, refill routing and cancellations, and
leaves clinical questions to the clinical team.