The questions every doctor asks before starting.

A diary records what happened, but it doesn’t remind anyone of what should happen tomorrow. The difference isn’t in the recording — it’s that confirmations, follow-ups and empty slots get something responsible for them every day, instead of resting on someone’s memory at the front desk.

Reception sees one screen: who’s coming today, who’s arrived, and who’s waiting. They don’t see the medical record, the analytics or the settings, so there’s nothing to get lost in. That isn’t hiding from the menu — the permission itself blocks access.

It stays kept apart to your clinic. That isolation is in the query itself: every read from the database is built so that it must know the clinic, and without it refuses to run. All traffic is over HTTPS, passwords are stored hashed with bcrypt, and actions are recorded in an audit log.

The full details on the security page

You don’t need to move an archive to start. You can start with tomorrow’s appointments, and patient records build up with every consultation recorded — there’s no separate data-entry step. Accounts are opened one at a time, set up with someone from our side.

The steps in order on the “How it works” page

The cancellation and data-retention policy hasn’t been published yet, and we can’t write anything here before it’s settled. If this question decides it for you — and it’s a fair question — ask it word for word in your access request before you start, and once the policy is published you’ll find it on this page.

No. Patients never install anything or create an account. All messaging runs on WhatsApp from the clinic’s own number — confirmations, reminders and follow-ups, and even booking happens in the same chat.

It’s written in Arabic from the ground up, and the whole interface runs right to left — not a flipped English version. Clinical terms are stored in standard English, as they’re known in medicine, so the record stays readable to anyone who reads it.