Scheduling
Every appointment, remembered.
Naibor reads the clinic’s schedule and messages each patient before the visit: a confirmation when it is booked, a reminder the day before, preparation when the visit needs it, and a short check afterwards. When the schedule changes, the messages change with it.
Example messages. Each hospital sets its own wording, in every language it serves.
One sequence, two clocks
Some messages count from the moment of booking, others count back from the appointment. A hospital sets the steps, the timing and the wording, and a named clinician signs each sequence off before it sends anything.
- At bookingA confirmation: when, where, with whom, and the number to call to change it.
- 3 days beforePreparation, when the visit needs it: fasting, a medication list to bring, where to go on arrival.
- 1 day beforeA reminder with the same details, sent inside the hospital’s quiet hours.
- After the visitA short check in the patient’s own language. The answers are on the appointment’s record for the team to read.
When the schedule moves, the messages follow
The schedule is the source of truth, and it changes every day. Nothing has to be cancelled by hand.
- Moved: the old reminders are withdrawn and a fresh confirmation goes out for the new time.
- Cancelled: nothing more is sent.
- Booked too close to the appointment for a step: that step is skipped, never sent late.
- Once the appointment has started, nothing more goes out about it.
However the schedule reaches us
A clinic can start before any integration exists and move to a feed later, without changing a single message.
From the EHR
FHIR Appointment resources or HL7 SIU messages from your interface engine, as bookings are made, moved and cancelled.
From the portal
Where there is no interface, a supervised robot reads the scheduling screen the clinic already uses.
From a spreadsheet
Upload the clinic’s list as a CSV. It is checked on screen first, then handled exactly like a feed.
Rules the hospital sets
- Cohorts decide who gets which sequence: by service, specialty, location, clinician, notice period, first visit or day of the week.
- Nothing sends until a named clinician signs the sequence off, and every version is kept.
- Consent per channel, STOP honoured at once, quiet hours respected, and every message in the patient’s own language.
- A text message first, and e-mail when there is no mobile number.
What you can see
The dashboard shows how many upcoming appointments have a reminder planned or sent, delivery by channel, why any were not sent, how far ahead bookings arrive, and opt-outs. When the schedule feeds back who attended, a holdout group shows what the reminders changed at your hospital.
Beside readmissions follow-up, on the same platform
Scheduling shares the patient record, consent, channels, languages and sign-in with readmissions follow-up. Each hospital switches on the modules it uses, and staff see only the ones they work in.
See it with your own schedule
In the demo we run the reminders on a sample of your clinic’s list.