Data protection

Data protection training that sticks

How to train GP, dental and clinic staff on data protection so it changes behaviour: short scenarios, role-based refreshers and simple checks.

Ava research teamPublished 6 min read

On this page
  1. Why the annual course is not enough
  2. Build training around real moments
  3. Running a five-minute scenario
  4. Model answers to three common scenarios
  5. A training plan by role
  6. A year of training in small pieces
  7. Checking that it works
  8. Example: from completion to behaviour
  9. Making it part of the culture
  10. Frequently asked questions
  11. References

Key takeaways

  • Annual e-learning meets the requirement; short, practice-specific scenarios through the year change behaviour.
  • NHS GP practices need at least 95% of staff trained in data security and protection in the last twelve months.
  • Different roles make different mistakes, so tailor refreshers for reception, clinicians, admin and managers.
  • Check understanding by watching what people do, not just by quiz scores.

Why the annual course is not enough

Most practices meet their training requirement with an annual online module. For NHS GP practices, the 2026-27 Data Security and Protection Toolkit asks whether at least 95% of staff, directors, trustees and volunteers have completed training on data security and protection, and cyber security, in the last twelve months[1]. That target matters, and it is worth hitting.

Toolkit standard: staff trained in the last twelve months
Toolkit standard: staff trained in the last twelve monthsDonut chart. Minimum share of staff trained: 95%.Minimum share of staff trained: 95%95%
  • Minimum share of staff trained 95%

Source: NHS England (Data Security and Protection Toolkit), 2026[1]

Show the data
ItemValue
Minimum share of staff trained95%

But a module completed in a quiet week rarely changes what happens at the front desk on a busy Monday. Many organisations do not train at all: only 19% of UK businesses had provided any staff cyber security training in the 2025 government survey[2]. Practices do better than that because of the toolkit, but the real test is whether a receptionist pauses before reading an address back to a caller, or a clinician thinks twice before photographing a wound on a personal phone.

The Caldicott Principles put it simply: everyone with access to confidential information should be aware of their responsibilities[3]. Awareness that only exists in a certificate does not meet that standard.

Build training around real moments

People remember situations, not rules. Collect the moments where data protection decisions actually happen in your practice, and build training around them. Ask staff for examples; they know better than anyone where the tricky calls are.

  • A caller asks for a result and gets the date of birth slightly wrong.
  • A parent asks what their 15-year-old discussed with the nurse.
  • A police officer phones asking whether someone was seen at the practice last night.
  • An email arrives from a solicitor with a consent form attached, from a free email address.
  • A patient at the desk can see another patient's details on the screen.
  • A colleague asks to borrow a smartcard because theirs is at home.
  • A clinician wants to send a photo of a rash to a colleague by WhatsApp.
  • A former patient emails asking for all their records within a week for a court case.
  • A text reminder goes to a number that now belongs to someone else.
  • A new AI tool promises to save time on letters, and someone has started using it.

Running a five-minute scenario

  1. Set the scene in one sentence

    Read the scenario aloud, using your own practice's names for systems and rooms so it feels real.

  2. Ask, then wait

    Ask ‘What would you do?’ and give people a minute to talk it through in pairs before anyone answers.

  3. Hear two or three answers

    Take answers from different roles. Disagreement is useful; it shows where the policy is unclear.

  4. Agree the practice answer

    State what the practice expects, why, and where the policy or script is written down.

  5. Note any fix

    If the discussion reveals a gap, such as a missing script or a confusing process, write it down and give it an owner.

Model answers to three common scenarios

  • The parent asking about a 15-year-old: do not confirm what was discussed. Explain that young people can have confidential consultations, offer to pass a message to the clinician, and suggest the parent talks with their child. The clinician decides whether and how to involve the parent, based on the young person's competence and wishes.
  • The police officer on the phone: do not confirm whether the person is a patient or was seen. Take the officer's name, rank, force and number, explain that requests must be made in writing, and pass it to the manager or Caldicott Guardian. Call back through the force switchboard if needed.
  • The screen visible to a waiting patient: lock the screen or switch to a neutral view straight away, then move the monitor or fit a privacy filter. Report it as a near miss so the layout gets fixed for everyone.

Write your own model answers for every scenario on your list and keep them in a shared folder. New starters can read them during induction, and they become the practice's working knowledge rather than something only experienced staff carry in their heads.

A training plan by role

Tailor refreshers to the risks each role actually meets.
RoleMost common risksFocus for refreshers
Reception and care navigatorsIdentity checks, overheard conversations, screens in view, relatives asking for informationScripts for calls, desk layout, when to escalate
CliniciansPersonal devices, messaging apps, clinical photos, sharing with other providers, AI toolsWhat to share for direct care, approved tools, recording decisions
Admin and secretariesLetters to wrong addresses, attachments, subject access requests, third-party requestsDouble-checking recipients, the request process, redaction
Managers and partnersSupplier contracts, breaches, impact assessments, cultureBreach decisions, contracts, modelling good behaviour
Locums, students and volunteersUnfamiliar systems, borrowed access, unclear rulesInduction before access, who to ask

A year of training in small pieces

  1. Induction, before access

    No new starter, locum or volunteer gets system access before completing the mandatory module and a 15-minute practice briefing on identity checks, the reporting route and the clear-desk rules.

  2. Annual module

    Everyone completes the core course, and the IG lead tracks completion monthly so nobody drifts past twelve months.

  3. Monthly scenario

    Five minutes at a team huddle: one scenario from the list, discussed in pairs, then the agreed answer. Rotate who presents.

  4. Quarterly role session

    A 20-minute session for each staff group on its own risks, using recent incidents and near misses.

  5. After incidents

    Within a week, share what happened and what should happen next time, without naming individuals.

  6. When something changes

    New systems, suppliers or processes get a short briefing before go-live.

Small and often beats long and rare. Twelve five-minute scenarios across a year will do more for behaviour than an extra hour of e-learning.

Checking that it works

Quiz scores show what people know on the day. Behaviour shows what they do. Use a mix of light checks, agreed with staff in advance so they feel like support rather than surveillance.

  • Walk-rounds: look at screens, printers, desks and bins at different times of day.
  • Record spot-checks: are identity checks and disclosures noted when information is shared by phone?
  • Request log review: are subject access and third-party requests handled within deadlines?
  • Incident and near-miss reporting: a rise in near misses after training often means people are noticing more, which is good.
  • Short follow-up questions a month after a session: ‘What would you say if…?’

Record what you check and what you find. The evidence is useful for the toolkit and for CQC, and the trend over a year shows whether the approach is working. Share the findings with the team as well: people respond better to ‘we found two day lists on the printer this month, down from six’ than to a reminder that rules exist.

Example: from completion to behaviour

Example: Parkside Dental, a fictional practice, has every member of staff's annual module complete, yet a walk-round finds patient day lists left on the printer and a waiting patient able to read the reception screen. The manager introduces a monthly five-minute scenario at the Tuesday huddle, starting with the screen and printer issues, and moves the reception monitor.

Example: three months later, walk-rounds find no day lists on the printer, and staff report two near misses, both wrong-number texts caught before sending. The manager shares both at the next huddle and thanks the people who reported them.

Making it part of the culture

Training sticks when people see it matters to the partners or owner, when reporting a mistake is met with thanks, and when the rules make daily work easier rather than harder. Serious UK GDPR infringements can attract fines of up to £17.5 million or 4% of turnover[4], but that is not the message to lead with. Lead with patients: their information is special category data[5], and every decision at the desk or in the consulting room is a decision about their trust.

Use this alongside the IG lead's calendar, clear desk and screen rules, caller identity checks and the rules on sharing records for direct care.

Frequently asked questions

How often must practice staff do data protection training?

For NHS GP practices, the toolkit expects at least 95% of staff to have completed it in the last twelve months[1]. Add short refreshers through the year.

Do locums need data protection training?

Yes. Anyone with access to patient information should complete training and a practice briefing before getting access.

What should data protection training cover?

The law in outline, and above all the practice's own situations: identity checks, requests for records, devices, messaging, breaches and how to report them.

How do we prove training is effective?

Keep completion records, and add evidence from walk-rounds, record spot-checks, request logs and near-miss reports.

References

  1. NHS England (Data Security and Protection Toolkit) (2026). Outcomes, assertions and evidence items for the Data Security and Protection Toolkit 2026-27 version 9 (opens in a new tab) ↑

  2. GOV.UK (Department for Science, Innovation and Technology) (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑

  3. GOV.UK (National Data Guardian) (2020). The Caldicott Principles (opens in a new tab) ↑

  4. legislation.gov.uk (The National Archives) (2026). UK GDPR Article 83: General conditions for imposing administrative fines (opens in a new tab) ↑

  5. legislation.gov.uk (The National Archives) (2026). UK GDPR Article 9: Processing of special categories of personal data (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo