Booking the referred patient, confirmed against the schedule

After a referral is entered, someone books the visit. OpenAdapt can do that from a demonstration and confirm the booking another way. On our own scheduling app over a real remote-desktop connection (not Citrix), it booked 3 of 3 with a separate read confirming each, and stopped on 3 of 3 wrong-patient runs with nothing written.

Updated 2026-10-14

Today

  1. Find the patient in the scheduling system.
  2. Pick the visit type and provider.
  3. Find an open slot and book it.
  4. Confirm the booking and note it on the referral.

We assume about 3 minutes a booking (2 to 5). That's our assumption, not a study; we time yours in the access check.

With OpenAdapt

The booking form of our fictional scheduling app, seen over a remote-desktop connection, during the recording.
Real recording, still frame: the recording it learned from, over a real remote-desktop connection, 30 Jul 2026. Our fictional scheduling app; synthetic patient; a test script stood in for the person.

A staff member books one visit on a test patient while OpenAdapt records it. Each later booking runs through the same steps with the new patient, visit type and slot. A person approves the booking. Then OpenAdapt reads the schedule another way and confirms exactly one matching booking.

The same booking form during a later run with new values.
Real recording, still frame: a run with new values, 30 Jul 2026. Our fictional scheduling app; synthetic patient.

What's been tested

CaseResultCheck
New bookings3 of 3 confirmedA read-only database query of the appointments
The wrong patient's record open3 of 3 stopped; 0 rows writtenSame query
The screen changed3 of 3 stopped

Our own fictional scheduling app, synthetic patients, over a real remote-desktop connection (FreeRDP on Linux), 30 Jul 2026. 0 AI model calls.

What hasn't been tested

  • A commercial scheduling system or EMR scheduler.
  • A real Citrix session.
  • Choosing a slot by rules, such as the first opening with a given provider: the test used the slot it was given.
  • Telling the patient: that stays with staff.

Is it a fit?

  • The visit type and slot are decided before booking, by staff or a rule you set.
  • Your scheduler offers a second way to read a booking: a report, an API or a read-only database.
  • Your scheduler runs in a browser, an installed program or remote desktop.

Related: referral intake · filing reports · when the screen changes

Sources

  1. OpenAdapt remote-desktop test, 30 Jul 2026: a fictional clinic scheduling app over a real remote-desktop connection (FreeRDP, not Citrix), synthetic patients. 3 of 3 bookings confirmed by a read-only database query; 3 of 3 wrong-patient runs stopped with 0 rows written; 3 of 3 runs on a changed screen stopped. 0 AI model calls.

See it on your process

Bring one task your team types every day. We'll tell you whether it fits, and what a test on your own system would cover.