Data protection

Data processing agreements with suppliers

When a practice needs a data processing agreement, the Article 28 clauses to check, sub-processors, breach terms and red flags in supplier contracts.

Ava research teamPublished 6 min read

On this page
  1. Do you need one?
  2. The eight obligations to check
  3. Sub-processors and breaches
  4. The tools nobody signed a contract for
  5. Reviewing a supplier, step by step
  6. What the NHS toolkit expects
  7. Questions to ask before you sign
  8. When the contract ends
  9. Example: a new online booking tool
  10. Keep it proportionate
  11. Frequently asked questions
  12. References

Key takeaways

  • Any supplier that handles patient or staff data on your behalf is a processor, and UK GDPR requires a written contract with specific terms.
  • Check eight core obligations, including acting only on your instructions, security, sub-processors, breach help and deletion at the end.
  • Tools staff adopt on their own, outside any contract, are the biggest gap: 11% of GPs use AI tools they obtained independently.
  • Keep a supplier register with the contract, the data involved and a review date for each.

Do you need one?

A practice is the controller of its patient data: it decides why and how the data is used. Suppliers that handle that data only to provide a service to you, on your instructions, are processors. Under Article 28 of UK GDPR, processing by a processor must be governed by a contract or other legal act that sets out the subject matter, duration, nature and purpose of the processing, the types of data and categories of people, and the controller's obligations and rights[1].

In a typical practice, processors include the telephony provider, the text messaging service, online consultation and booking tools, the website host, IT support, cloud storage, confidential waste contractors, CCTV maintenance companies with remote access, payroll bureaux and transcription or AI tools. The same checklist applies to a phone service such as Ava, where the practice is the controller and the supplier processes call data under a written agreement.

Not every supplier is a processor. A body that decides its own purposes for the data, such as an accountant acting under professional rules or a hospital receiving a referral, is usually a controller in its own right. The contract terms differ, so decide the role first.

The eight obligations to check

Article 28(3) lists what the contract must require of the processor[1]. Read each supplier's terms against this list rather than accepting a statement that the contract is GDPR compliant.

Article 28(3) obligations, with what to look for in supplier terms.
ObligationWhat good looks likeRed flag
Act only on documented instructions, including on international transfersProcessing limited to providing the serviceSupplier may use data to improve its products or for analytics
Staff bound by confidentialityContractual confidentiality for all staff with accessSilence on staff access
Security measuresSpecific measures or certifications describedGeneric promise of industry standard security
Sub-processors only with authorisationList provided, notice of changes, right to objectSupplier may change sub-processors freely
Help with data subject rightsDefined process and timescale for helping with requestsCharges for every request, or no process
Help with security, breaches and impact assessmentsBreach notification without undue delay and support with assessmentsNotification only when the supplier decides it is serious
Delete or return data at the endYour choice, with confirmation of deletionData kept indefinitely or only on payment
Information and auditsEvidence of compliance and audit rightsNo audit rights at all

Sub-processors and breaches

Most software suppliers rely on others: cloud hosts, messaging gateways, transcription engines, support desks. A processor must not engage another processor without your prior specific or general written authorisation, and under a general authorisation it must tell you about intended changes so you can object[1]. Ask for the current sub-processor list, where each is located, and how you will be notified of changes.

Breach terms deserve close reading. UK GDPR requires a processor to notify the controller without undue delay after becoming aware of a personal data breach[2], and you then have your own deadline to notify the regulator where required. A contract that lets the supplier wait until it has finished investigating, or that only covers breaches it considers material, leaves you exposed. Ask for notification within a defined short period, with the information you will need to make your own decision.

The tools nobody signed a contract for

The most dangerous processors are the ones the practice does not know about. The Nuffield Trust found that 13% of all GPs use AI tools provided by their practice, while 11% use tools they obtained independently[3]. A free transcription app, a personal note-taking tool or a general chatbot used to draft letters may process patient data with no contract, no impact assessment and terms that allow the provider to keep or reuse it.

Where GPs' AI tools come from (share of all GPs)Nuffield Trust and RCGP survey, 2025
Where GPs' AI tools come from (share of all GPs)Comparison. Provided by their practice: 13%; Obtained independently: 11%.13%Provided by their practiceProvided by their practice: 13%11%Obtained independentlyObtained independently: 11%Where GPs' AI tools come from (share of all GPs)Comparison. Provided by their practice: 13%; Obtained independently: 11%.13%Provided by their practiceProvided by their practice: 13%11%Obtained independentlyObtained independently: 11%

Source: Nuffield Trust, 2025[3]

Show the data
ItemValue
Provided by their practice13%
Obtained independently11%

Clinicians are not careless about this; among GPs not using AI, 82% were worried about patient privacy and data security[4]. The answer is to provide approved tools with proper contracts, explain why unapproved ones are a problem, and ask staff to tell you what they are using without fear of blame.

Reviewing a supplier, step by step

  1. Confirm the role

    Decide whether the supplier is your processor, a separate controller or a joint controller, and record the reasoning.

  2. Map the data

    Write down what personal data the supplier will handle, whose it is, whether it includes health data, and how long it will be kept.

  3. Get the terms

    Ask for the data processing agreement or the data protection terms, the security summary, the sub-processor list and the locations where data is stored.

  4. Check against Article 28

    Use the table above. Note gaps and ask for changes in writing; many suppliers have an addendum for healthcare customers.

  5. Assess the risk

    For anything involving health data at scale, new technology or AI, complete or update a data protection impact assessment before go-live.

  6. Record and review

    Add the supplier to your register with the contract, data, risk rating and a review date, and recheck at renewal or when the service changes.

What the NHS toolkit expects

For GP practices, the 2026-27 Data Security and Protection Toolkit asks whether the practice has a list of suppliers that handle personal information, with the products and services they deliver, and whether it assures that its IT system suppliers have robust cyber security arrangements[5]. A simple supplier register, kept up to date, answers both questions and makes this work visible to anyone reviewing the practice.

  • Supplier name and contact for data protection queries.
  • Service provided and the systems involved.
  • Personal data handled, including whether it is health data.
  • Role: processor, controller or joint controller.
  • Contract and processing terms, with date signed.
  • Data locations and transfer safeguards.
  • Security assurance seen, such as certification.
  • Review date and owner.

Questions to ask before you sign

Sales conversations focus on features. Bring these questions to the demo or send them in writing, and keep the answers with the contract. A supplier used to working with the NHS or private healthcare will answer them quickly; one that cannot is telling you something.

  • Will you sign a data processing agreement, and can we see it before we commit?
  • Do you or your sub-processors use our data, including recordings, transcripts or messages, to train or improve your products?
  • Where is our data stored and supported from, and which countries can your staff access it from?
  • How do you tell us about a breach, how quickly, and what information will you give?
  • How do we export our data, and how do you confirm deletion when we leave?
  • Which security certifications do you hold, and can we see the summary?
  • Who in your company can access our data, and is that access logged?

When the contract ends

Exit is where weak processing terms cause real trouble. Practices change telephony, messaging and software suppliers regularly, and each change leaves data behind: call recordings, message logs, patient records in a booking tool, backups. Before the end date, agree in writing what will be exported to you and in what format, what will be deleted, and when. Ask for confirmation of deletion, including from backups once they expire, and add it to your records. If you need some data kept, such as call recordings linked to an open complaint, agree that specifically rather than leaving everything with a supplier you no longer pay.

Example: a new online booking tool

Example: Bridge Street Physio, a fictional private clinic, chooses an online booking tool. The supplier's standard terms say it may use customer data to improve its services and that sub-processors may change without notice. The manager asks for the healthcare addendum, which limits use to providing the service, lists sub-processors with a notice period for changes, and commits to breach notification within a defined period.

Example: the manager also asks where data is stored. Some support staff are outside the UK, so the clinic checks the transfer safeguards before signing. The supplier goes on the register with a review date at renewal.

Keep it proportionate

A practice cannot negotiate bespoke terms with every global software company, and does not need to. What it can do is read the terms, choose suppliers whose standard terms meet Article 28, ask for the healthcare addendum where one exists, and walk away from tools that will not commit to the basics. Patient data is special category data[6], so the bar is higher than for ordinary business software.

Related reading: suppliers storing data outside the UK, using AI tools with patient data, IT supplier contracts, CCTV and clinical photographs held in cloud imaging systems.

Frequently asked questions

Is a data processing agreement a legal requirement?

Yes, when a supplier processes personal data on your behalf. UK GDPR Article 28 requires a contract with specific terms[1].

Does a supplier's standard terms count?

Yes, if they contain the Article 28 terms. Many suppliers put them in a data processing addendum; check it against the eight obligations.

What should a contract say about breaches?

That the supplier will tell you without undue delay, with the information you need[2]. A defined short period is better than vague wording.

Do free apps used by staff need an agreement?

If they process patient data, yes, and most free consumer tools will not offer acceptable terms. Provide approved tools instead.

References

  1. legislation.gov.uk (The National Archives) (2026). UK GDPR Article 28: Processor (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2026). UK GDPR Article 33: Notification of a personal data breach (opens in a new tab) ↑

  3. Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑

  4. Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑

  5. 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) ↑

  6. 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