'/%3e%3cpath%20d='M92%2044a34%2034%200%201%200%204%2033H66'%20fill='none'%20stroke='%23fff'%20stroke-width='12'%20stroke-linecap='round'%20stroke-linejoin='round'/%3e%3ccircle%20cx='96'%20cy='32'%20r='9'%20fill='%23FF6A2B'/%3e%3c/svg%3e)
Platform module
Appointments, Scheduling & Referrals
A real clinician calendar, double-booking prevented at the database, and referrals tracked to a decision.
What it is
Appointment books fail quietly: two clerks write the same slot, the clinician finds out at 9am. GSHS prevents overlapping bookings in the database itself, so no combination of screens, tabs or slow networks can create a clash.
Referrals are tracked as a conversation with an outcome — sent, accepted or declined with a reason — rather than a letter that disappears.
Provider calendar
Week view · Dr E. Adeyemi
Consultation
Referral
Consultation
Why teams value it
No double booking
Enforced at the database, not in the browser.
Week and day views
Provider calendars built from real bookings.
Reminders
Patients notified when an appointment is made or changed.
Referral outcomes
Accept or decline, always with a reason.
A grid that reflects reality
Bookings are made against a named provider, branch and appointment type, with start and end times. Booking a slot removes it from everyone else's view immediately.
- Week and day grids
- Booked, confirmed, checked-in, in progress, completed, no-show, cancelled
- Records whether staff or the patient booked
Check-in that leads straight into care
Checking a patient in moves the appointment through its states and hands the clinician a ready encounter, so the clinical note and the schedule never drift apart.
- Status changes are audited
- No-shows recorded rather than deleted
- Reason for visit carried into the encounter
Send a case with its clinical summary
A referral carries the reason, urgency and a clinical summary to the receiving organisation or department, and stays visible to the sender until a decision is made.
- Urgency levels
- Internal department or external organisation
- Resulting encounter linked back to the referral
A queue the receiving team actually works
Incoming referrals arrive in a worklist where the receiving team accepts or declines with a reason, closing the loop for the referring clinician.
- Decision reasons stored
- Status visible to both sides
- Feeds the receiving facility's appointment book
Questions about this module
Explore related modules
Patient Records & Global Patient ID
One record per patient per hospital, and one identity for that patient across every hospital on the network.
Read moreClinical Encounters, Admissions & Discharge
Consultations, ward rounds, admissions and discharge in a record that keeps its history instead of being overwritten.
Read moreLaboratory & Imaging
Orders, specimens, results and a separate verification step, with turnaround measured rather than estimated.
Read morePrescriptions, Pharmacy & Public Verification
Safe prescribing, real stock control, and a printable prescription anyone can verify as genuine.
Read moreSee this module on real screens
Book a walkthrough and we will demonstrate it using workflows that match your facility.