Clinic management — from online booking to the last collected claim
A successful polyclinic is rarely killed by a shortage of patients — it is killed by chaos: lost appointments, angry queues at reception, paper files nobody can find. This page walks through running a clinic or polyclinic from the first booking to the last collected insurance claim, on one Arabic-first system.
Online booking and WhatsApp reminders: an empty slot is silent loss
A clinic run on a paper book and a phone loses twice: once in front-desk time burned on calls, and again in the patient who booked and forgot. Here the patient books themselves from a link on your page or straight from WhatsApp, sees the doctor slots that are genuinely free, and gets an instant confirmation plus an automatic WhatsApp reminder before the visit — with one-tap confirm or cancel. A cancelled slot returns to the pool the same second for another patient instead of evaporating, and each doctor schedule fills with real bookings, not phantom ones that vanish on the day.
A smart queue screen instead of front-desk chaos
Reception crowds are not fate. The patient checks in and joins their specific doctor queue, the waiting-room screen shows turns and calls live, and the doctor sees their own queue and calls the next patient with one tap. The front desk knows at any moment who arrived, who is late and who is inside — and the endless "how many before me?" that drains half the staff energy ends, along with the arguments when someone slips in out of turn. At the end of the day you get actual waiting times per doctor, so you know where patients pile up and why.
One patient record, however many branches you run
Medical history, visits, prescriptions, lab results and uploaded documents live in one file opened by mobile number or national ID. A patient seen at one branch today follows up at another tomorrow, and the doctor has the full picture: what was prescribed, what a colleague noted last visit, what the labs said. Results are attached to the file the moment they arrive, so the doctor finds them at the next visit without asking. No duplicate entry, no "the file is at the other branch", no patient retelling their story from scratch every time.
Revenue cycle: visit to collection with no leakage
Every visit becomes an itemized invoice automatically: consultation, follow-up, procedure or service. For insured patients the system splits the patient share from the insurer share from the first moment, then batches claims with their documents per insurance company, tracked from one screen: what was submitted, what is pending, what was rejected and why, and what was actually collected. Doctor payouts are computed automatically per each doctor agreement — a percentage or a fixed value per visit — so the end-of-month argument ends with numbers both sides read from the same source.
Compliant e-invoices from the same front-desk screen
In Egypt the invoice or e-receipt goes out compliant with the ETA e-invoicing system; in Saudi Arabia, compliant with ZATCA requirements — issued from the same payment screen at reception, with no external system, no double entry, and no employee "posting invoices" at the end of the day. The accountant finds everything already booked the moment it is issued, so month-end close becomes a review, not a reconstruction.
Patient data is a trust — and it stays on your server
Medical data is the most sensitive data there is. The system is built with full awareness of the Saudi Personal Data Protection Law (PDPL) and Egypt data protection law: granular permissions so reception sees appointments but never diagnoses, an access log recording who opened which file and when, and — above all — hosting on your own server, inside your clinic or on your own cloud. Medical files never leave your control, with scheduled backups, full export anytime, and no lock-in whatsoever.
Ehgzli is not a slide deck — it is this system, running today
Everything on this page is Ehgzli in production: booking, reminders, queues and the unified patient record run today in real clinics, built on the same Jirsi foundation. Click and see it live.
Ehgzli ←We've run on a paper book and a phone for years — what actually changes?
The first thing you feel: reception stops spending half its day on the phone, and cancelled slots get rebooked instead of evaporating. A month in, you hold something the paper book will never give you — real numbers on no-shows, occupancy, and revenue per doctor and per branch.
Our doctors have no time to learn a new system
The doctor screen is designed for the rhythm of a fast consultation: their queue, the patient file with full history in front of them, prescription and notes written in under a minute. Training is in Arabic on their own screens — and a doctor who tries it for a week rarely goes back to paper.
We work with many insurance companies — can it keep up?
Each company coverage and price list is defined once; after that the system splits patient and insurer shares automatically on every visit, batches claims with documents per company, and tracks pending, rejected and collected for each — so no claim silently falls through.
We have several branches — do we need a system per branch?
No — one system for all branches: a unified patient record, appointments and revenue reported per branch or consolidated, and permissions scoping who sees what in each branch. Management watches the whole picture from one screen.
Patient data is extremely sensitive — who can see it?
The system runs on your own server, and each user sees only their role scope: reception sees appointments and invoices, doctors see their patients, accounting sees numbers without diagnoses. A full log records who opened which file and when — and we never see your data.
What happens when the internet drops?
The system can run on a local server inside the clinic network, so check-in, consultations and invoicing continue even if the outside connection dies — only WhatsApp reminders wait for the connection to return, then send automatically.
Watch Ehgzli run on a clinic that looks like yours — a live demo with Saleh on WhatsApp.