Careful with clinical data — honest about what's certified
Tabeeb leads with role-based access and least-privilege scoping, audit-logs sensitive actions, and only publishes compliance claims it can stand behind.
How Tabeeb protects clinical data today
Practical controls in the private beta — without overstating formal certifications.
Role-based access control
Admin, Doctor, and Receptionist — every route and API is scoped to the role, deny by default.
Least-privilege scoping
Doctors see only their own patients and earnings; reception can't open finance, analytics, or settings.
Secure login + MFA
Email/password with authenticator (TOTP) MFA enforced for admin and reception; forced password change on first sign-in.
Row-level security
Postgres row-level security on tenant tables as defense in depth, on top of the API's role checks.
Audit log
Sensitive mutations are logged with actor, action, and before/after — searchable by admin.
Server-side money
All money math runs on the server, and doctor commission never appears on patient-facing data.
What we don't claim yet
We only publish what's true today. These are explicitly not claimed until the work — or the certification — is done.
- HIPAA — not claimed
- GDPR — not claimed
- ISO 27001 / SOC 2 — not claimed
- Regional health frameworks (DHA, NABIDH…) — not claimed
- PMDC license verification — typed text, not a live check
- Data residency — not a published fact yet
- Backups / PITR — until ops confirms
- Encryption at rest — not claimed yet
The safe, true line: access is role-based, sensitive actions are audit-logged, and clinical notes are written only by the treating doctor.
Have a security questionnaire?
We're happy to walk your team through Tabeeb's access model and data handling — with honest answers on what's shipped today.