Data protection

Does your practice need a Data Protection Officer?

When a data protection officer is mandatory for GP, dental and private practices, how shared DPO services work and how to avoid conflicts of interest.

Ava research teamPublished 7 min read

On this page
  1. The short answer
  2. Why NHS practices count as public authorities
  3. Dental practice models and what they mean
  4. Private clinics: what counts as large scale?
  5. What a DPO does
  6. Independence and conflicts of interest
  7. Shared DPO services
  8. What happens if you do not appoint one
  9. Example: a practice fixes its DPO arrangement
  10. Frequently asked questions
  11. References

Key takeaways

  • GP practices and NHS dental contractors are public authorities for their NHS work, so a data protection officer is mandatory.
  • Wholly private clinics must appoint one if their core activities involve large-scale processing of health data; smaller ones often still benefit from one.
  • Shared DPO services are lawful and common, but the DPO must be independent and free of conflicts of interest.
  • Publish the DPO's contact details and tell the regulator who they are.

The short answer

Article 37 of UK GDPR requires a controller to designate a data protection officer in three situations: where processing is carried out by a public authority or body, where core activities involve regular and systematic monitoring of people on a large scale, and where core activities involve large-scale processing of special category data such as health information[1]. For most practices the first test settles the question.

  • NHS GP practice: yes, a DPO is mandatory.
  • NHS or mixed dental practice: yes, for the NHS side of the business, which in practice means the whole practice.
  • Wholly private clinic or dental practice: only if health data processing is large scale and part of your core activities, but many choose to appoint one anyway.
  • Any practice: the DPO's contact details must be published and given to the regulator[1].

Why NHS practices count as public authorities

UK GDPR does not define 'public authority' itself. The Data Protection Act 2018 does, and it points to the Freedom of Information Act 2000: for UK GDPR purposes, public authorities are those defined in that Act, along with Scottish public authorities and a few bodies named in regulations[2].

The Freedom of Information Act lists, in its first schedule, any person providing primary medical services or primary dental services under NHS contracts or arrangements, in respect of information relating to the provision of those services[3]. That brings GP partnerships, single-handed GPs and NHS dental contractors in England within the definition. The 'in respect of' wording means the status attaches to NHS work, but because the same people, systems and records serve all patients, mixed practices are best treated as public authorities for data protection purposes across the board.

A practice does not escape the requirement by being small. Article 37 does not set a size threshold for public authorities. A single-handed GP needs a DPO just as a large partnership does.

Dental practice models and what they mean

In 2026, 38% of dentists in England worked fully or mainly in NHS care, 23% in a mixed NHS and private model and 37% fully or mainly in private care[4]. The first two groups will almost always be working in practices that hold NHS contracts, so a DPO is required. The private group needs to apply the large-scale test.

How dentists in England worked, 2026
How dentists in England worked, 2026Donut chart. Fully or mainly NHS: 38%; Fully or mainly private: 37%; Mixed NHS and private: 23%.Fully or mainly NHS: 38%Fully or mainly private: 37%Mixed NHS and private: 23%2026
  • Fully or mainly NHS 38%
  • Fully or mainly private 37%
  • Mixed NHS and private 23%

Source: Care Quality Commission, 2026[4]

Show the data
ItemValue
Fully or mainly NHS38%
Fully or mainly private37%
Mixed NHS and private23%

Note that the chart describes dentists, not practices. A practice can employ dentists who work mainly privately while still holding an NHS contract for some activity. What matters for the DPO question is whether the practice, as the controller, provides NHS primary dental services.

Private clinics: what counts as large scale?

For private providers, the question is whether their core activities consist of processing special category data on a large scale[1]. Health data is special category data by definition[5], and for any clinic treating patients it is part of the core activity. The open question is scale, which the law does not define.

Regulators and practitioners generally weigh four factors. Use them to reach a reasoned decision and write it down.

  1. Number of patients, both as a total and as a share of the population you serve.
  2. Volume and range of data: full clinical records, imaging and test results weigh more than appointment details alone.
  3. Duration: records kept for many years add up.
  4. Geographic reach: multiple sites, online services or patients across the UK point towards large scale.

A single practitioner with a modest list is unlikely to be processing at large scale. A clinic group with several sites, online consultations and tens of thousands of records almost certainly is. Between the two, the safer course is usually to appoint, because the cost of a part-time or shared DPO is modest compared with the effort of defending a decision not to have one.

What a DPO does

  1. Inform and advise

    Explain the practice's obligations to partners, managers and staff, and advise on questions as they arise, from lawful bases to sharing requests.

  2. Monitor compliance

    Check policies, training, contracts and audits against the law, and report findings to the partners or directors.

  3. Advise on impact assessments

    Give advice whenever a new system or process needs a data protection impact assessment, and check the result.

  4. Be the contact point

    Act as the point of contact for patients exercising their rights and for the regulator, including during breach investigations.

  5. Report to the top

    Report directly to the highest level of management, which in a partnership means the partners.

The DPO advises; the practice decides. Responsibility for compliance stays with the controller, which is the partnership or company, not with the DPO personally.

Independence and conflicts of interest

A DPO must be able to work independently, must not be told how to carry out their tasks and must not be penalised for doing them. They can have other duties, but those duties must not create a conflict of interest. That rules out anyone who decides the purposes and means of processing, which is why the practice manager, a partner or the IT lead is usually the wrong choice.

This is the most common error in small practices: naming the practice manager as DPO because they already handle information governance. The manager can be the information governance lead, doing the day-to-day work, while an external or shared DPO provides the independent oversight.

Shared DPO services

Article 37 allows a single DPO to be designated for several public authorities, taking account of their structure and size[1]. Many integrated care boards and primary care networks commission a shared DPO service for their GP practices, and commercial providers offer the same to dental and private practices. Before signing up, ask:

  • How many organisations does each named DPO cover, and how quickly do they respond to urgent queries such as a breach?
  • Do they understand primary care systems, the Data Security and Protection Toolkit and NHS records guidance?
  • Will they review DPIAs and supplier contracts, or only give general advice?
  • Do they provide template policies and staff training, and keep them current?
  • Who covers when the named DPO is away?

What happens if you do not appoint one

Failing to appoint a required DPO breaches the controller obligations in Articles 25 to 39, which carry fines of up to £8.7 million or 2% of worldwide turnover, whichever is higher[6]. In practice, enforcement against a small practice is more likely to take the form of a reprimand, but the gap usually surfaces at a bad moment: during a breach, a complaint or an inspection, when the practice has nobody independent to turn to.

If you realise your practice has no valid DPO, fix it calmly rather than in a rush. Choose a provider or an independent person, sign an agreement setting out their tasks and hours, update the contact details in your privacy notice and in your registration with the regulator, and tell staff who to contact. Then ask the new DPO for a short baseline review, so the first months are spent on your highest risks rather than on paperwork.

Example: a practice fixes its DPO arrangement

Example (fictional): a two-site mixed dental practice had listed its practice manager as DPO for years. When a patient complaint about a disclosed radiograph reached the regulator, the manager found herself both investigating the incident and advising on whether the practice had acted lawfully. The owners moved to a commercial shared DPO service, kept the manager as information governance lead and updated the privacy notice and the regulator's records with the new contact details.

The new DPO's first review found two supplier contracts without data processing terms and an out-of-date privacy notice. Both were fixed within a quarter. The owners now receive a short written DPO report twice a year.

For the wider set of duties, see our guides to UK GDPR for private clinics and the data protection fee.

Frequently asked questions

Is a DPO mandatory for a GP practice?

Yes. GP practices are public authorities for their NHS work under the definitions used by the Data Protection Act 2018[2], and Article 37 requires public authorities to designate a DPO[1].

Can our practice manager be the DPO?

It is usually unwise. A DPO must be independent and free of conflicts of interest, and the practice manager normally takes decisions about how data is used. The manager can be the information governance lead instead.

Can several practices share one DPO?

Yes. Article 37 allows a single DPO for several public authorities, taking account of their structure and size[1]. Shared services through ICBs or commercial providers are common.

Does a small private clinic need a DPO?

Only if its core activities involve large-scale processing of health data. Assess scale using patient numbers, data volume, duration and reach, and record the decision.

References

  1. legislation.gov.uk (The National Archives) (2026). UK GDPR Article 37: Designation of the data protection officer (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2026). Data Protection Act 2018, section 7: Meaning of public authority and public body (opens in a new tab) ↑

  3. legislation.gov.uk (The National Archives) (2026). Freedom of Information Act 2000, Schedule 1, Part III: National Health Service (opens in a new tab) ↑

  4. Care Quality Commission (2026). State of Care 2025/26: dental (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) ↑

  6. legislation.gov.uk (The National Archives) (2026). UK GDPR Article 83: General conditions for imposing administrative fines (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