Clinical visit + devices
Dr. Ahmed Maher Clinics
A nutrition-clinic system for a team of doctors: the visit produces a diet number, a plan, a prescription and labs; devices have their own hourly diary; each doctor has a ledger.
- 4
- branches
- 6
- specialists
- 7
- bookable devices
- 46
- labs in catalogue
Three layers
The site, the portal and the system — each layer does its own work.
-
01
Public site
The brand, six programmes, the team, and four branches with booking.
-
02
Patient portal
Registration, appointments, and follow-up after the visit.
-
03
Operations
Doctor workspace, diet number, devices, stock, vaults and doctor ledgers.
What makes it itself
Clinical visit + devices
- Doctor workspace and daily queue
- Diet number and progress code
- Full circumference measurements
- Lab catalogue ordered from the visit
- Hourly device diary
- Per-doctor ledger and daily close
The screens are operating models with sample data. No patient records are shown.
The challenge
A multi-doctor, multi-branch clinic fails if the visit stays on paper, and if each doctor’s share is settled from notebooks at month-end.
The patient was also being followed by the scale alone, with no circumferences and no plan number to come back to.
The solution
The doctor workspace opens today’s queue and the visit: intake, plan, diet number, prescription, a lab request from the catalogue, and injections. Measurements are circumferences, not weight alone.
Each device has an hourly day. Stock warns on low. Vaults are split, with a daily close. Each doctor has collected / due / net. Each doctor has exam and follow-up prices and an online schedule.
The result
The team on the landing page is the team in the system. The visit became a file that moves: reception, doctor workspace, diet number. Devices and doctor ledgers are not a side job; they sit inside the same system.
- Client
- Dr. Ahmed Maher Clinics
- Year
- 2026
- Category
- Clinic systems
- Stack
- Laravel, Livewire, MySQL, WhatsApp Cloud
