Protecting patient data in a dental clinic

A dental clinic holds names, phone numbers, dates of birth, medical histories and photographs. That combination is more sensitive than most clinic owners assume, and it is held by an organisation with no IT department.

The good news is that almost every real-world incident in a small clinic comes from a short list of ordinary causes. Fixing those matters far more than anything sophisticated.

Give each person their own account

The single most common problem: one shared login that everyone uses, with the password on a note under the monitor.

Shared accounts mean you can never answer who viewed or changed a record. That question only ever comes up at the worst possible moment.

Give every person their own account. When someone leaves, disable it the same day — not next week. A departing employee with working credentials is the most common route to a real data loss.

Access by role, not by seniority

A receptionist needs names, phone numbers and the schedule. They do not need clinical notes or radiographs. An assistant needs the clinical record for today's patients. Only the treating dentist and the owner need everything.

This is not about mistrust. It limits the damage when one account is compromised, and it is the expectation in every data protection regime.

Backups: the part everyone gets half right

Most clinics have backups. Far fewer have backups they have ever restored.

Three questions to answer:

1. Where is it? A backup on the same machine as the data protects you from nothing. It must be somewhere else.
2. When did it last run? Check the date, not the setting.
3. Have you restored one? Try it once, on a test record. A backup nobody has restored is a hypothesis.

If your records are in cloud software, the vendor handles this — but confirm you can export your own data. Backup by the vendor is not the same as your ability to leave with your data.

Devices

• Screen lock on every device, one minute of inactivity. A logged-in reception computer facing the waiting room shows patient names to everyone sitting there.
• Encrypt laptops and phones that can open patient records. On modern devices this is a setting, not a project.
• Never store patient data in personal accounts — personal WhatsApp, personal cloud drives, personal email. When the employee leaves, the data leaves with them.
• Position the reception screen so it cannot be read from the waiting area. This is the cheapest fix on the list and the most frequently ignored.

Photographs

Clinical photographs are patient data. Photographs taken on a personal phone end up in a personal cloud backup and stay there for years.

Take them on a clinic device, move them into the patient record, and delete them from the camera roll the same day. If you want to use a photograph publicly, get written consent that says specifically that — general treatment consent does not cover publication.

What to do if something goes wrong

Decide now, not during the incident:

1. Who is told first
2. Which accounts get disabled immediately
3. What is written down: what happened, when, whose data, what was done
4. Whether affected patients must be notified — check your local requirement, since many regimes require notification within a fixed number of days

A lost phone with no screen lock and a logged-in session is a reportable incident in many jurisdictions. The same phone encrypted and locked usually is not.

The habits that matter most

• Never send clinical detail over a consumer messenger
• Never discuss patients where other patients can hear — reception areas carry
• Never leave a record open on an unattended screen
• Never reuse the clinic password anywhere else

None of these need a budget. They prevent most of what actually happens.

In DOQ, every user has their own account with role-based access, data is scoped per dentist, and you can export your full patient database at any time.