El Tayseer Clinics — Scheduling
An internal operations system for a multi-branch clinic group: who works at which branch, on which days, delivering which service at which price — one reference the branches build their schedules on instead of scattered paperwork.
Overview
Multi‑branch reservation system with doctor schedules and working hours, patient management and per‑branch daily reporting.
01The challenge
The group runs several branches, each with different doctors, nurses, services and working days. The data lived in per-branch files, so any change — a doctor moving, a service added, a day off — needed updating in more than one place, and one of them was usually missed.
02What we built
We built one reference: branch, doctor, nurse, service, specialty and working days as connected entities — a doctor is tied to their days, degree and branch, and a service is tied to its category.
The effect is that a change happens in one place and propagates to everything that depends on it, and a question like "who is available at this branch on Wednesday" became a query rather than a phone call.
03The outcome
Branches read from the same reference, so conflicting copies of the schedule disappeared, and building the weekly rota got much faster because the underlying data is already there and already connected.
What the system does
The modules that were delivered and put into daily use.
-
01
Branch management, each branch with its own doctors, nurses and services.
-
02
Doctor records with degrees, specialties and defined working days.
-
03
Nursing records with degrees, and service categories with priced services.
-
04
One client base for the group instead of a list per branch.
-
05
An admin panel with permissions and editable global settings.
Technologies used
What this system is actually built on — not a generic list.