Key takeaways
- For direct care, GP practices rely on public task under Article 6 and the health or social care condition under Article 9, not on UK GDPR consent.
- As public authorities for their NHS work, practices must appoint a data protection officer and cannot use legitimate interests for their public tasks.
- Breaching the core principles, lawful basis, special category rules or patients' rights sits in the higher fine tier of up to £17.5 million or 4% of turnover.
- UK GDPR works alongside the common law duty of confidentiality and the Caldicott Principles; you need to satisfy all three.
Why GP practices are a special case
A GP practice holds some of the most sensitive information anyone will ever share: diagnoses, medicines, mental health, sexual health, family circumstances and safeguarding concerns. Most of it is special category data. Under UK GDPR, processing data concerning health is prohibited unless one of the specific conditions in Article 9 applies[1]. Everything a practice does with patient information has to fit through that gate.
GP practices are also treated as public authorities for their NHS work. That status changes three things compared with a private business: which lawful bases are available, whether a data protection officer is mandatory and how the practice answers requests under freedom of information law. Partners who have run a private business before often assume the same rules apply. They do not.
Lawful bases for direct care
Every use of personal data needs a lawful basis under Article 6, and every use of health data also needs an Article 9 condition. For providing care, the usual pairing is Article 6(1)(e), processing necessary for a task carried out in the public interest or in the exercise of official authority, and Article 9(2)(h), processing necessary for the provision of health or social care.
Two points catch practices out. First, legitimate interests is not available: UK GDPR says it does not apply to processing carried out by public authorities in the performance of their tasks[2]. Second, UK GDPR consent is rarely the right basis for care. Consent must be freely given and can be withdrawn, which does not fit a clinical record the practice is required to keep. The consent that matters for direct care is the implied consent of the common law duty of confidentiality, which is a separate test.
| Activity | Article 6 basis | Article 9 condition | Watch out for |
|---|---|---|---|
| Consultations, records, referrals | 6(1)(e) public task | 9(2)(h) health or social care | Common law confidentiality: implied consent for direct care |
| Statutory returns and legal requests | 6(1)(c) legal obligation | 9(2)(h) or 9(2)(i) public health, as applicable | Check the specific legal gateway |
| Safeguarding referrals | 6(1)(e) or 6(1)(c) | 9(2)(h) or substantial public interest conditions | Record the reasoning at the time |
| Insurance or employer reports | 6(1)(a) consent or 6(1)(e) | 9(2)(a) explicit consent | Patient's written authorisation |
| Staff payroll and HR | 6(1)(b) contract or 6(1)(c) | 9(2)(b) employment, for health data | Separate staff privacy notice |
| Research disclosures | Depends on the study | Usually explicit consent or research condition | National data opt-out may apply |
What is at stake
UK GDPR has two fine tiers. Breaches of the controller and processor obligations in Articles 25 to 39, such as security, records and breach notification, can attract fines of up to £8.7 million or 2% of worldwide annual turnover, whichever is higher[3]. Breaches of the core principles, the lawful basis rules, the Article 9 conditions and patients' rights sit in the higher tier: up to £17.5 million or 4%[3].
Source: legislation.gov.uk (The National Archives), 2026[3]
Show the data
| Item | Value |
|---|---|
| Controller obligations (Articles 25-39) | £8,700,000 |
| Principles, lawful basis, Article 9 and rights | £17,500,000 |
Fines at those levels are rare for small organisations, and the regulator uses reprimands and enforcement notices far more often. The practical risk for a practice is less about the maximum and more about reputation, CQC scrutiny and the time a serious incident consumes. Clinicians feel it too: 82% of GPs not using AI tools said patient privacy and data security worried them[4].
The duties that matter most
- Appoint a data protection officer. Article 37 makes this mandatory where processing is carried out by a public authority or body[5]. Many practices use a shared DPO service through their integrated care board or a commercial provider.
- Keep a record of processing activities: what you hold, why, who receives it and how long you keep it.
- Publish a clear privacy notice for patients and a separate one for staff, and review both when anything changes.
- Answer patients' rights requests on time, especially subject access requests, which have a short statutory deadline and are covered in our separate guide.
- Secure the data: access controls, smartcards, encryption, training and an annual Data Security and Protection Toolkit submission.
- Report notifiable personal data breaches to the regulator without undue delay and, where feasible, within 72 hours of becoming aware[6], and record every breach whether reported or not.
- Complete a data protection impact assessment before introducing new technology that is likely to create high risk.
- Put contracts in place with every supplier that processes patient data for you, from the clinical system to the phone provider.
Confidentiality and the Caldicott Principles
UK GDPR is only one layer. The common law duty of confidentiality applies to everything a patient tells the practice in confidence, and health and care organisations in England also follow the eight Caldicott Principles[7]. They cover justifying every use, using the minimum necessary, restricting access on a need-to-know basis and making sure everyone understands their responsibilities.
One Caldicott Principle is often forgotten in busy practices: the duty to share information for individual care is as important as the duty to protect confidentiality. Refusing to share with another clinician caring for the patient can itself cause harm.
A practice can be fully compliant with UK GDPR and still breach confidentiality, for example by disclosing to a relative without the patient's agreement. The reverse is also true. Train staff on both, using real examples from the front desk: the spouse who rings for results, the employer who asks whether someone attended, the police officer at reception.
New technology raises the stakes
Online consultation tools, cloud telephony, ambient voice tools and AI assistants all process patient data in new ways. Before introducing any of them, ask four questions: is the supplier a processor under a written contract, where is the data stored, what is recorded or transcribed and for how long, and does a data protection impact assessment need updating? Involve the DPO early rather than after the contract is signed.
Watch for tools staff adopt on their own. A clinician pasting a referral letter into a free online tool, or a receptionist using a personal messaging app to contact a patient, creates a processing activity the practice has not assessed. Clear rules on approved tools prevent most of these incidents.
Common mistakes in practice
Most data protection problems in general practice are not dramatic. They are small, repeated habits that nobody has questioned. Look for these when you next review your arrangements.
- Asking patients to 'consent to GDPR' on registration forms. It confuses the lawful basis and implies patients can withdraw permission for their own record.
- Privacy notices that still describe systems the practice stopped using years ago, or that omit the phone system, the website forms and text messaging.
- Shared logins on reception computers, which make it impossible to tell who looked at a record.
- Treating a request from a relative, solicitor or insurer as routine without checking the patient's authority.
- Keeping old paper records, call recordings or exported reports with no retention decision.
- Supplier contracts that were signed by a previous partner and never checked for data protection terms.
None of these needs a large project to fix. A short review led by the practice manager and the DPO, with one change agreed per meeting, clears most of them within a few months. Write each decision down: if the regulator or CQC ever asks, a dated note explaining why the practice chose a basis or a retention period is far more persuasive than a recollection.
Example: an annual data protection calendar
Example (fictional): a 9,000-patient practice built its data protection work into a simple calendar. In January the DPO reviews the record of processing and supplier contracts. In March the privacy notices are checked against any new systems. Staff training is completed in the spring, well ahead of the annual Data Security and Protection Toolkit deadline. In September the practice runs a short audit of access logs and smartcard use, and in November it reviews breaches and near misses from the year.
Each item has an owner, usually the practice manager or the information governance lead, and is reported to the partners' meeting. The calendar turns a large body of law into a few predictable tasks.
Self-check for partners and managers
- We know who our data protection officer is and how to contact them.
- Our record of processing lists every system, including phones, websites and messaging.
- Our privacy notice names our lawful bases and explains patients' rights in plain language.
- Every supplier that processes patient data has a written contract.
- Staff know how to spot and report a breach the same day.
- We have assessed every new tool introduced in the last year.
If any item is a no, start there. Our guides to data protection officers and the data protection fee cover two of the most common questions practices ask next.
Frequently asked questions
Do GP practices need consent under UK GDPR to hold patient records?
No. For direct care, practices usually rely on public task under Article 6(1)(e) and the health or social care condition under Article 9(2)(h). The common law duty of confidentiality, which is separate, relies on implied consent for direct care.
Must a GP practice have a data protection officer?
Yes. Article 37 requires a DPO where processing is carried out by a public authority or body[5], and GP practices are public authorities for their NHS work. A shared DPO service is common and acceptable.
Can a GP practice rely on legitimate interests?
Not for processing carried out in the performance of its public tasks[2]. It may be possible for some activities outside those tasks, which the DPO should assess.
How quickly must a breach be reported?
Notifiable breaches must be reported without undue delay and, where feasible, within 72 hours of becoming aware of them[6].
References
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 9: Processing of special categories of personal data (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 6: Lawfulness of processing (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 83: General conditions for imposing administrative fines (opens in a new tab) ↑
Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 37: Designation of the data protection officer (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 33: Notification of a personal data breach (opens in a new tab) ↑
GOV.UK (National Data Guardian) (2026). The Caldicott Principles (opens in a new tab) ↑