Continuity is one system for the whole patient journey — the enquiry, the booking, the treatment record, the aftercare and an app the patient keeps — in Persian, Arabic, English and Kurdish. Designed and built by me, end to end.
Shown on a live demo with a fictional clinic. Every name and figure on this page is invented.
Demand is rarely the issue. Value leaks away in the gaps between visits — and each gap has a fix.
A message from Instagram or WhatsApp sits unanswered for hours. By the time someone calls back, the patient has booked somewhere else.
In ContinuityEvery enquiry lands in one pipeline, with a response timer that respects opening hours, follow-up tasks, and escalation when nobody answers.
The first rebooking is the fragile one. Patients who leave without their next visit booked often don’t come back.
In ContinuityRebooking at checkout, reminders timed to each treatment, and packages and memberships that carry a patient to the third visit.
The patient goes home, something feels wrong, and they don’t know whom to ask. Messages after hours go nowhere.
In ContinuityAftercare journeys with check-ins at the right moments. A red-flag answer reaches a clinician at once, day or night, with an on-call rota behind it.
Which product, which batch, which practitioner, which photos — kept in a notebook or a chat, out of the patient’s reach.
In ContinuitySigned clinical records, photos with consent and their originals preserved, and a patient app where patients hold their own history.
The front desk, the treatment room and the owner work in the same place, and the patient sees their side of it in their own app.
Upcoming visits, care that needs attention, open enquiries and collected revenue — for every branch together, or one at a time.
Website, Instagram, WhatsApp and phone enquiries on one board, from new to won, with the source of each one and a response target that turns red when it is missed.
Rooms, devices, staff hours and practitioner licences are checked before a visit is saved. Patients book online, pay a deposit, and the clinic’s own cancellation terms apply.
Aftercare plans are written once per treatment and approved by the medical director. Every patient gets the right check-in at the right time; urgent answers open an alert immediately.
A separate app with the clinic’s name on it. Patients sign in with a one-time code — no password, no app store.
Sign up with any email at the fictional clinic. The demo code is 123456.
Persian, Arabic, English and Kurdish, right-to-left where it should be. Staff and every patient each choose their own language.
Solar Hijri or Gregorian dates and Persian digits; rials, tomans, dirhams or dollars; each branch in its own time zone.
Rule packs for Dubai, Abu Dhabi, Saudi Arabia, Iran and the EU: consent types, retention periods, messaging windows and advertising wording.
The demo runs branches in Tehran, Dubai and Boston: shared patients, separate schedules, reports per branch or together.
Nine roles with a permission matrix the owner controls. The front desk and marketing never see clinical notes.
Each look at a patient’s health information is logged, and staff sign in with a second step.
Sensitive fields and original photos are stored encrypted.
Export one patient or the whole clinic at any time, in open formats: CSV, JSON, PDF and images.
Short narrated videos, each following one task from start to finish — at the clinic and on the patient’s phone. In English, with subtitles.
Continuity runs end to end on the live demo. What changes for a real clinic is its connection to the outside world — your WhatsApp, SMS and payment providers, your treatments and protocols, your patient list. In the demo those are simulated; for your clinic, connecting them is the setup work.
You tell me how the clinic runs today. I show you the system with treatments like yours.
Your branches, services and languages set up privately, so your team can try it before deciding.
Patients imported, providers connected, templates and aftercare plans approved, staff shown how to use it.
Every part runs on the demo with fictional data. For your clinic, the remaining work is setup — connecting your messaging and payment providers and loading your services and patients. I’ll tell you plainly what that involves before you decide.
It was designed right-to-left from the start. Persian uses the Solar Hijri calendar and Persian digits, and each patient sees the app in their own language.
Yes. Patients and enquiries import from a CSV file, with a preview and duplicate detection before anything is saved.
Your clinic owns it and can export all of it at any time. Where it is hosted is decided per clinic.
No app store. The patient app opens from a link and can be added to the home screen; sign-in is a one-time code.
It depends on the number of branches and what needs setting up. After a short conversation I send a written proposal with a clear scope.
Tell me about your clinic — how many branches, which treatments, which languages. I reply within two working days with a time for a walkthrough.
Or write directly to reza.sabourinejad@gmail.com
All clinics, people and data shown are fictional.