Everything around the medical record, and nothing inside it.
Billing, reminders and front-desk calls, all reading from the diary you already keep.
Clinic management software comes in two parts. The medical record system holds notes, prescriptions and results, connects to the health information exchange and stays with your record vendor. Around it sit billing, a patient portal, reminders and front-desk calls, which we build. Where the law keeps patient data inside the country, as UAE law does, it stays there.
Clinical work stays in your medical record system.
Clinical notes, diagnoses, prescriptions, results and the connection to the health information exchange belong in your electronic medical record. In the UAE, NABIDH is the Dubai Health Authority's exchange, Malaffi is the Department of Health Abu Dhabi's, and Riayati is the Ministry of Health and Prevention's platform, and the three have been linked. Your record vendor carries that connection.
We do not build medical record systems, we do not connect to NABIDH, Malaffi or Riayati, and we make no claim about DHA, DoH or MOHAP compliance. We build the work around the record. Where your record system has an API or a scheduled export, we read from it. Where it has neither, we point that out before you pay for anything.
Around the record, five parts that read from one diary.
Each of these usually lives in a separate tool or a spreadsheet today:
- Billing that matches the visit. Procedure or package to invoice to ledger on ERPNext, with each line's VAT treatment applied exactly as your tax adviser classifies it, and nothing retyped from the diary.
- Claim-ready invoices. The invoice and its supporting documents assembled for your insurer submission. Submission stays in your existing claims channel, and any direct payer connection is scoped and priced per payer.
- A patient portal. Appointments, invoices and documents, where each patient sees their own file and nothing else. Access is enforced at the read, never filtered afterwards. Client portals.
- Reminders and recalls. Appointment reminders and follow-up recalls from your diary, on the channel the patient answers, carrying a time and a place rather than clinical detail.
- Front-desk calls, summarised. Calls transcribed and summarised against the right patient, and the call-backs created as tasks. Voice and conversation systems.
Patient data stays where health data law keeps it.
In the UAE, Federal Law No. 2 of 2019, on the use of information and communication technology in health fields, bars storing or processing health data about services provided in the UAE outside the country, except in the cases set by decision. Ministerial Decision No. 51 of 2021 lists those cases.
So for a clinic there, anything that touches patient data runs on UAE hosting, quoted separately, or on your own servers, and never on our default hosting in Germany. Wherever a health-data law keeps patient data inside its country, the same boundary holds. Speech models run self-hosted, so call recordings stay with the rest of the patient data. Private models explains the self-hosted setup.
Inside that boundary, no clinic shares a container, a database or credentials with any other. Your lawyer confirms how the law applies to your clinic. We build to their answer and give no legal advice ourselves.
Automation works at the desk, never in the consultation.
It summarises calls, drafts replies for a person to send, answers opening hours and directions from your own documents, and reads scanned referral letters and insurance cards into fields for a person to confirm.
Nothing we build diagnoses, triages, prescribes or advises a patient. A wrong automated decision there is life-safety critical, and that is work we do not take on. Anything that reaches a patient for the first time waits for a person, and that rule is enforced in code, outside the model.
Booking stays in your record system's diary.
We no longer build booking systems as a service. Appointments stay in your record system's diary and everything on this page reads from it, which is what one diary means: no second copy to disagree with the first.
Bookesto, our own booking desk for service businesses, is in early access. Its availability and slot holds run today, while its merchant workspace and payments are still being built. It is not a clinic system, and we do not offer it as one.
From a morning at the front desk to go-live.
- A morning at the front desk. A few hours watching the desk tell us more than any requirements document.
- The record system's edges. What your medical record system exposes by API or export, and what it does not.
- Rules. Practitioners, packages, deposits, cancellation terms, insurance handling and the VAT treatment your adviser gives each line.
- Build and migrate into a staging copy. Open invoices and patient contact details reconciled before cutover.
- A parallel fortnight. The old way and the new way side by side until the differences are zero.
- Live, then tune. Reminder timing adjusted once there is real no-show data to look at.
It is priced as one fixed total against the signed scope, and warranted for 12 months while it runs on our hosting.
Frequently asked questions
Where do clinic billing and patient portals sit beside the medical record?
Clinic management software comes in two parts. The medical record system holds notes, prescriptions and results, connects to the health information exchange and stays with your record vendor. Around it sit billing, a patient portal, reminders and front-desk calls, which we build. Where the law keeps patient data inside the country, as UAE law does, it stays there.
Do you connect to NABIDH, Malaffi or Riayati?
No. The exchange connection belongs to your medical record system and its vendor, and it stays with them. We read from that system where it offers an API or an export, and build billing, the patient portal and reminders around it.
What is a patient portal, and what would ours show?
A secure page where each patient signs in to see their own appointments, invoices and documents. Ours reads from your record system's diary and from your billing, and every patient sees their own file and nothing else.
Can patient data be hosted in Germany?
It depends where you treat patients. In the UAE we do not propose it: Federal Law No. 2 of 2019 keeps health data about UAE services inside the country, except in cases set by ministerial decision, so patient systems there run on UAE hosting or on your own servers. Elsewhere, your lawyer confirms what your health-data law allows, and systems holding no patient data can use our default German hosting.
Will software answer our patients?
Only within a narrow band, such as opening hours, directions or where an invoice stands, answered from your own documents. Anything clinical, and anything it is unsure of, goes to a person with the conversation attached. First contact with a patient always waits for a person.
We are one clinician with one room. Is this overkill?
Probably. A clean set of books and a reminder schedule on top of your record system is a small engagement, usually the right one, and the first call is the place to find out.