Dr Gamal Hospital ERP
A medical booking platform with three surfaces: a patient-facing site, a doctor dashboard for schedules and bookings, and an admin panel for specialties, services and degrees — with a fully bilingual API for the mobile app.
Overview
A medical booking platform with three surfaces: a patient-facing site, a doctor dashboard for schedules, bookings and patient files, and an admin panel for specialties, services and degrees — with translated content and a mobile API.
01The challenge
Booking happened over the phone: a receptionist opened a book, asked which doctor, hunted for a free slot and wrote a name down. The result was double bookings on the same slot, patients arriving on a doctor’s day off, and no record to go back to.
The content itself — specialty, service and degree names — has to render in Arabic for local patients and English for expatriates, and it changes constantly, so hard-coding it was not an option.
02What we built
We modelled the schedule as data: each doctor has defined working days and hours, and a booking is only accepted inside a genuinely open window — so double booking disappeared by rule rather than by staff vigilance.
Doctors got their own dashboard: their schedule, their bookings, their patient files, and the ability to change their own hours without going through admin. Admin manages specialties, services, degrees and marketing content in one place.
Every text field is translated in its own table, so content renders in the request’s language whether it comes from the site or the app. The API is split cleanly into three groups — client, doctor and public — each with its own JWT-based authentication.
03The outcome
Booking became self-service from the site or the app, and reception now supervises instead of being the system. Slot conflicts are no longer possible because it is the time window itself that gets booked.
What the system does
The modules that were delivered and put into daily use.
-
01
Self-service booking from the site and app inside genuinely open per-doctor time windows.
-
02
A doctor dashboard: schedule, bookings, patient files, and self-service editing of working days and hours.
-
03
Management of specialties, services and service types, degrees, and each doctor’s service list.
-
04
Content translated at the data layer: services, degrees and specialties in Arabic and English.
-
05
An API split into client, doctor and public route groups, secured with JWT.
-
06
Site content from the panel: sliders, FAQs, countries and cities, and global settings.
Technologies used
What this system is actually built on — not a generic list.