Skip to content

Security and data, stated plainly

A dental record holds a person’s health history. This page says what Dently does to protect it today, and what is still to come.

Each clinic is kept apart

  • Every clinic’s data lives in its own PostgreSQL schema. Requests are tied to one clinic, and queries run against that clinic’s schema only.
  • Appointments, treatments, prescriptions and invoices never leave the clinic that created them.

Shared patient records

  • A patient’s personal details and medical history are shared with another clinic only after the patient approves that clinic, in person or in the patient portal. They can decline, or withdraw later.
  • Shared details are encrypted with AES-256-GCM. Patients are matched between clinics by a keyed hash of phone, name and date of birth, so the matching key does not reveal them.
  • Every change to a shared record is logged with the clinic and the fields changed, and a clinic admin can erase the shared record when a patient asks.

Signing in

  • Passwords are stored as bcrypt hashes.
  • After repeated wrong passwords, further attempts for that email or connection are refused for 15 minutes.
  • Staff roles limit what each person sees. A receptionist does not see the accounts; an accountant does not see the dental chart.
  • Patients sign in to the portal with a one-time code sent to their phone.

Backups and records

  • The database is backed up with pgBackRest, and uploaded files with Borg, on a schedule.
  • Sign-ins and changes to records are written to an audit log.