How we look after patient data
What is in place today - we only list what is true, and we will add certificates here only once we hold them.
Each clinic kept apart
- Every clinic has its own separate database schema and its own folder for files
- A staff login works only at the clinic that issued it
- Patient-app logins can never open staff screens
Access and accountability
- Each person has their own login and role; staff see only what their role needs
- Repeated wrong passwords lock the account
- Key actions are recorded in an audit log the clinic can review
- Messages and clinical photos are kept in the record and never edited
The patient app
- Opening it needs the patient's own phone and their PIN
- Five wrong PINs lock it until the clinic issues a new code
- The clinic can end a patient's or carer's access on every phone at once
- Notifications never show medical details
Where data lives
- Each country's clinics are hosted separately: UK clinics in the UK, Egyptian clinics in Egypt
- This public demo runs on a separate demo server with fictional patients only
- Daily backups of every clinic's data and files
- Connections are encrypted (HTTPS)
No third parties by default
- Built with open-source software, run on servers we manage
- No advertising or tracking scripts on this website
- Reminders can be sent with no paid service at all; a paid provider is used only if the clinic connects its own account
In progress
- UK: Cyber Essentials, clinical safety documentation (DCB0129), data processing agreement for clinics
- Egypt: registration and licensing under the Personal Data Protection Law
See it working in two minutes
Open the live demo as reception, nurse, doctor or cashier - no sign-up.