90% of NHS clinicians say they already use AI in clinical practice — the adoption number healthcare software builders can't ignore

A new survey published in August 2026 finds 90% of NHS clinicians report using AI tools in clinical practice, arriving as the NHS confirms how it will spend £10bn over three years on technology, digital and data as part of the 10 Year Health Plan.

A survey published this month found that 90% of NHS clinicians now report using AI in clinical practice — a striking number given how recent and cautious most institutional NHS AI rollouts have been. It lands alongside confirmation of how the NHS’s £10bn technology funding over the next three years will be spent, money the government says will deliver roughly half the commitments in its 10 Year Health Plan and generate £41bn in benefits over the following decade. A new AI triage tool is also rolling out through the NHS App, reaching over 200,000 patients within a year and every NHS App user by April 2028.

The gap between “90% of clinicians already use AI” and “the NHS is only just funding and formally rolling out AI systems” is the real story. It suggests most current clinical AI use is informal — individual clinicians reaching for general-purpose tools on their own initiative — running well ahead of the sanctioned, procured, audited systems that trust boards and regulators are only now building the funding and governance structures for. That gap is exactly where risk concentrates: unmanaged AI use inside clinical workflows, with none of the safeguards a procured system would carry.

So what

For healthcare organisations, this cuts two ways. It confirms clinician appetite for AI tools is not the barrier — adoption is already happening, informally, whether or not there’s a sanctioned system to channel it into. And it makes the case for moving deliberately: a narrow, well-scoped, properly governed tool — the kind recent NHS trust deployments have favoured over broad chatbot rollouts — gives clinicians a sanctioned alternative to informal tool use, with an audit trail and clinical safety case behind it. If your organisation is weighing where to start, that’s the conversation worth having before procurement decisions get made for you. More on how we approach this at healthcare software development, or get in touch to talk through a project.

← All research

More research.

GitHub's Copilot metrics now count OpenCode and Claude Code traffic: who really uses which AI coding tool

On 23 October 2026 GitHub added a per-tool breakdown to the Copilot usage metrics API, so tools such as OpenCode and Claude Code are counted even without editor telemetry. It shows how mixed the AI coding tool stack inside software teams has become.

Read ›

GitHub Copilot retires Claude Opus 5 and GPT-5.6 Terra on 16 November: the model-churn bill for buyers

GitHub has announced that Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra leave every Copilot experience on 16 November 2026. For anyone commissioning AI-assisted development, model retirement is now a monthly event to plan around.

Read ›

GitHub Copilot now benchmarks how 'agent-first' your developers are against your industry

On 22 October 2026 GitHub added opt-in industry comparisons to its Copilot impact dashboard, ranking firms by share of agent-first developers and by the merge rate of agentic pull requests. Here is how to read the numbers when you are buying software.

Read ›

Apple's new bait-and-switch rule 2.5.19: what it means for AI-built and fast-shipped apps

On 16 October 2026 Apple updated its App Review Guidelines: apps that change after approval can be removed from the App Store and the Developer Program, and AI-generated intimate imagery is now explicitly covered. Here is what founders commissioning an iOS app should check.

Read ›

GitHub Copilot agentic autofix is generally available: AI now fixes security alerts, and bills for it

GitHub made agentic autofix for code scanning alerts generally available on 15 October 2026. Copilot can now fix up to 25 security alerts in one pull request, using AI credits your supplier or your team pays for.

Read ›

GitHub AI Scan for pull requests goes GA: AI security checks for PHP, Terraform and Dockerfiles

GitHub's AI Scan for pull requests became generally available on 15 October 2026, checking languages the standard scanner misses. Findings are advisory and cannot block a merge, which matters when you buy software.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work