Not a feature list. A day that runs properly.

The layer that works underneath

• A job queue that runs on the server, not when someone opens the page. Confirmations, reminders, the notice when an appointment moves or is cancelled, searching the waiting list, closing follow-ups and marking no-shows — all of them run on their own, on time.
• WhatsApp from the clinic’s own number. No business account, no verification, no unfamiliar number. The patient replies in the same chat, and the reply comes back to the day board.
• A permission blocks access; it doesn’t just hide the button. Four roles, and on top of them a grant or a block for one named person. If someone opens the link to a page they aren’t allowed, the request is refused before it reaches the data.
• Each clinic’s data is kept apart at the query. Every read from the database is built so that it must know the clinic, and without one it refuses to run at all.

What’s in the system

The clinic’s morning

• The whole day on one line, first appointment to last, with a marker at the current time.
• Booking, confirming, moving and cancelling, and checking patients in.
• An ordered waiting list; when an appointment is cancelled it offers the slot to a patient it suits, without anyone searching.
• No-shows are recorded, and the count opens onto the names — not a number you just look at.

During the consultation

• Conditions and diagnoses, medications, allergies, vitals, labs and imaging — each section with its own record and edit history.
• Allergies and active conditions stay pinned as badges at the top of the record, so they’re in front of you while you write, without scrolling to find them.
• As you type a drug name on the prescription, if a recorded allergy has roughly the same name, a quiet note appears beside it — a prompt to check, not a drug-interaction check.
• The start and end of each consultation are recorded, and the prescription is written from a shared drug list and printed on the clinic’s paper.
• Extra fields you add yourself, if your clinic records something that isn’t there by default.

After the visit

• The follow-up is set, and closes itself on its date without anyone remembering.
• Reminders and confirmations go out on their own, on time.
• If you want, the system suggests a draft follow-up message for the patient based on their history — you review it and send it yourself; nothing goes out without you seeing it.

The clinic team

• Four roles, plus a grant or a block for one named person.
• A permission blocks access, not just the button.
• Reception sees the day only — not the medical record, not the analytics.
• Tasks assigned across the team and closed off, with the number still open shown in the menu.
• Actions are recorded in an audit log, so you know who did what.

Messaging

• All messaging with patients runs on WhatsApp from the clinic’s own number, with no business account and no verification.
• The patient replies in the same chat, and the reply comes back to the day board.
• WhatsApp’s connection status shows live in Settings, so you know about a problem before a patient asks you.

Running the clinic

• One strip for the month: how many consultations, and the change from last month — up or down.
• More than one clinic on the same account, switching between them without signing out.
• Each clinic’s data is kept apart in the query itself — not a condition in the code someone could forget.

Research

• Build a patient cohort from criteria, with nested sub-groups (AND / OR) when the criteria are compound.
• Exports are de-identified by default — showing identity is a separate permission of its own.