Patient scheduling without the phone-tag
Self-booking
patients book without an account
Records
history, notes and documents
Gated
server-side staff authentication
A practice can run its whole front desk from one screen, and a clinician can read a patient's allergies and history before walking into the room.
The problem
A practice needed patient-facing booking and a staff view without building a scheduling system from zero. The harder half was everything after the booking: a medical history that nobody could read back, and a staff area that had no real lock on it.
Our approach
We built the full platform. Patients self-book in about two minutes with no account, complete their history before arriving, and get SMS confirmations. Staff get a filterable worklist, a full patient record with allergies surfaced first, and append-only clinical notes. Staff access is gated server-side, before any patient data is fetched, and the public directory carries map pins and structured data so the practice can be found in local search.
In their words
“Booking with local doctors now takes patients much less time.”
Behind the build
Scheduling sounds simple until cancellations, reminders and time zones all have to stay in sync. The part worth talking about is less glamorous: the admin area was originally gated by a passkey compared in the browser, which meant the patient list was already in the HTML before the prompt appeared. Moving that check server-side, ahead of the data fetch, mattered more than any feature we added on top.
— North Foundry, on building this
Built with
Want something like this?
Next project