NHS England is deploying Microsoft 365 Copilot to more than 500,000 staff in what it describes as the largest healthcare AI rollout in the world. But as the technology embeds itself across health services, legal experts are warning that clinicians not AI developers could be held liable when it fails.

Microsoft Copilot Comes to the NHS at Scale, As Doctors Face Unresolved AI Liability Risk

NHS England announced this week that 505,000 clinicians and support staff will receive access to Microsoft 365 Copilot, an AI-powered assistant capable of drafting documents, summarising meetings, analysing data and supporting operational planning. 

The rollout, expected to complete by October 2026, follows a trial involving more than 30,000 NHS workers across 90 organisations, a trial NHS England says demonstrated average time savings of 43 minutes per working day. Across a workforce of half a million, the arithmetic is striking, millions of administrative hours recovered, potentially each month.

What is less clear is what happens when the technology gets something wrong.

A Workforce Technology Bet of Historic Scale

The Microsoft deployment is the most significant single workforce technology commitment NHS England has made in recent memory. Each NHS trust will receive a central licence allocation based on headcount typically around 2,000 licences to start covering functions from clinical administration and patient correspondence to HR, finance and board reporting. Rob Thompson, NHS England’s chief digital, data and technology officer, described the potential to save staff around two days of admin time every month as a potential turning point for patient care.

Having spent years trialling AI in contained settings, ambient scribing tools, diagnostic imaging support, predictive analytics the health service is now moving toward operational deployment at scale. The 10-Year Health Plan has set productivity and efficiency as core commitments, and AI is increasingly central to how NHS England intends to deliver on them.

The Liability Gap Nobody Has Closed

The timing of the rollout makes a report published this week by the Medical Protection Society (MPS) all the more pointed. The MPS, which represents doctors facing allegations of wrongdoing, is warning that under current UK law, clinicians not AI developers risk becoming the primary target of clinical negligence claims when AI-assisted decisions lead to patient harm.

The concern is not hypothetical. The MPS sets out scenarios in which AI misses a lung tumour on a chest X-ray, or incorrectly recommends an increased warfarin dose, resulting in serious patient harm. In both cases, the legal exposure under existing frameworks falls predominantly on the clinician who acted on the AI output, not on the technology company that built or supplied the system. The MPS is calling on the government to reclassify AI tools as products under the Consumer Protection Act 1987, which would redirect liability toward developers and manufacturers.

Dr Sarah Townley, the MPS’s deputy medical director, put it plainly, the pace of AI adoption has created a gap between what the technology can do and what the law can handle and that gap is widening. NHS Resolution is understood to be drafting guidance on AI liability, and the Department of Health and Social Care has said it will review the MPS recommendations. Neither commitment amounts to a resolution.

What This Means for Social Care

Care providers operating under Care Quality Commission inspection frameworks, working within local authority commissioning contracts, and delivering care under the obligations of the Care Act 2014, carry substantial documentation and reporting requirements. The admin load on registered managers and care coordinators is significant. Tools capable of reducing that burden drafting care plans, summarising handover notes, flagging compliance requirements would have direct operational value.

But the liability question the MPS has raised applies here too, perhaps more acutely. Social care operates with thinner legal infrastructure around technology governance than the NHS. There is no equivalent of NHS Resolution managing negligence exposure across the independent care sector. If a care worker acts on the output of an AI tool that produces an error, a missed medication interaction flagged incorrectly, a risk assessment that underestimates a client’s needs the question of who bears responsibility is, if anything, less resolved in social care than in the health service.

Governance Must Travel With the Technology

The Health Foundation has noted that public confidence in AI depends not just on the technology itself but on the oversight and safeguards that accompany it. That observation carries particular weight in care settings, where the people most affected older adults, people with disabilities, those with complex needs are among the least able to challenge errors or navigate complaints processes.

For integrated care systems seeking to extend digital transformation into community and social care settings, the NHS Copilot rollout offers a reference point both for what large-scale AI deployment can look like, and for the governance questions that remain open when it arrives. Procurement decisions, contractual liability clauses, staff training requirements and escalation protocols all need to be worked through before AI tools move from pilot to practice in any care setting.

The sector has seen enough promising technology deployments stall or cause harm through poor implementation to know that scale alone is not a measure of success.