There is a particular kind of hubris that only very large institutions can afford. In 2003, the Blair government announced what it described as the most ambitious civilian IT programme in world history: a plan to give every NHS patient in England a single, unified electronic health record, accessible by any clinician, anywhere, at any time. The budget was £6.2 billion. The timescale was a decade. The ambition was, genuinely, extraordinary. What followed became one of the most studied, most scrutinised, and most expensive cautionary tales in the history of British public administration. This is the story of the NHS national programme for IT history — NPfIT — told as it deserves to be: as a proper historical reckoning.
What Was NPfIT and Where Did It Come From?
The National Programme for IT was formally launched in 2003 under the stewardship of Richard Granger, a former Andersen Consulting executive who was appointed as the NHS’s first Director General of IT. Granger was known for his directness, and the contracts he negotiated were famously tough on suppliers. The Department of Health, under Secretary of State John Reid, sold the programme to Parliament and the public as a once-in-a-generation modernisation effort. The NHS was still largely paper-based at this point. Patient records travelled by post. Referrals were typed and faxed. The ambition to change all of that was not, in itself, unreasonable.
The programme was divided into regional clusters, with large IT companies awarded contracts to deliver systems to specific parts of England. BT took the north, Accenture and then CSC took the Midlands and East, and iSoft and Fujitsu shared responsibilities in the South. A separate contract for London went to BT. A central component called the Summary Care Record would hold basic information on every patient in England — medications, allergies, adverse reactions — and a more detailed system called the Care Records Service would handle the full clinical picture. Lorenzo, iSoft’s flagship patient records platform, was supposed to be the engine of much of this. It would prove to be one of the programme’s most persistent headaches.
Why the NHS National Programme for IT Started Unravelling
The problems did not announce themselves all at once. They accumulated. Accenture walked away from its contracts in 2006, absorbing a reported £450 million write-off rather than continue. Fujitsu followed in 2008, leaving its southern England contracts undelivered. The Lorenzo system, which iSoft had promised would be deployed across thousands of GP practices and hospital trusts, missed deadline after deadline. Trusts that had been told they would receive new systems within two or three years were still waiting a decade later.
Part of the difficulty was structural. The contracts had been negotiated centrally, with central government deciding which systems NHS trusts would use, rather than letting local organisations choose technology that fitted their existing workflows. Clinicians, many of whom had not been meaningfully consulted during the design phase, found themselves faced with systems that did not match how they actually worked. Resistance grew. Implementation stalled. And the costs kept rising.
By 2006, the National Audit Office had begun its first formal examination of the programme. The Public Accounts Committee, never particularly gentle with government IT projects, started asking increasingly pointed questions. The Health Select Committee weighed in. Academic researchers, most notably those at University College London’s Centre for Health Informatics and Multiprofessional Education, published damning independent assessments. The British Medical Journal ran a steady stream of critical commentary. The consensus among people who understood healthcare technology was hardening: this was a programme that had been designed around political ambition rather than clinical reality.
The Scale of the Money Involved
One of the persistent difficulties in telling this story is that the true cost of NPfIT is genuinely contested. The original budget of £6.2 billion grew. The National Audit Office’s 2011 report, published shortly after the programme was formally wound down by the coalition government, estimated that the total spend had reached approximately £9.8 billion, of which around £6.4 billion had already been paid out. A portion of that money had produced working systems: the NHS Spine, the electronic prescription service, and the Summary Care Record all functioned and are still in use today. But the flagship patient records component, the part that was supposed to transform how clinicians accessed information about their patients, was largely a failure. You can read the National Audit Office’s detailed accounting of this at the NAO’s official website.
The money figure alone, though, does not quite capture the opportunity cost. For nearly a decade, the NHS’s digital transformation effort was consumed by a single, failing programme. Local innovation was suppressed. Trusts that had developed their own effective systems were sometimes told to abandon them in favour of central solutions that never arrived.
Who Was Accountable When It All Fell Apart?
In September 2011, the coalition government’s Health Secretary, Andrew Lansley, announced that NPfIT would be formally dismantled. The remaining central contracts were wound down. NHS trusts would be free to procure their own systems, within a looser national framework. It was, in effect, an admission that the entire approach had been misconceived.
Accountability, as is so often the case with large public sector failures, proved elusive. Richard Granger had left the NHS in 2008. The commercial suppliers pointed to constantly shifting requirements from the NHS itself. The NHS pointed to suppliers who had overpromised. Politicians who had championed the programme were by then in opposition or out of office altogether. The National Audit Office’s reports were forensic but their findings produced no prosecutions, no significant financial penalties on individuals, and very few public apologies.
What the programme did produce was a substantial body of academic and governmental analysis examining precisely why large public sector IT projects fail. Professor Jeremy Wyatt, Professor Trisha Greenhalgh, and others published research that has since become required reading for anyone involved in health technology procurement. The failures of NPfIT seeded a generation of scholarship on the gap between technical ambition and organisational reality.
What the NHS National Programme for IT History Changed About UK Tech Procurement
The legacy of NPfIT is complicated but real. The NHS Spine, the infrastructure backbone of the programme, still underpins NHS digital services. The electronic prescription service processes millions of prescriptions every year. The Summary Care Record, however imperfect, exists and is used. These are not nothing. But the larger lesson the programme left behind was about how not to commission technology at scale.
In the years since NPfIT was wound down, UK government IT procurement has shifted — slowly and imperfectly — towards smaller, more iterative contracts. The Government Digital Service, established in 2011 and originally part of the Cabinet Office, was built explicitly on a different philosophy: agile development, user-centred design, and a preference for smaller, reversible decisions over monolithic long-term contracts. The NHS national programme for IT history NPfIT is cited, in hushed tones, in almost every serious discussion of government digital transformation that has taken place since.
Whether those lessons have truly been absorbed is a question the history of subsequent UK public sector IT projects does not entirely answer with confidence. But the story of NPfIT remains one of the most important chapters in the history of British digital ambition — a reminder that scale without understanding, and speed without consultation, tend to produce not transformation but wreckage.
Frequently Asked Questions
What was the NHS National Programme for IT (NPfIT)?
NPfIT was a Blair-era government initiative launched in 2003 to create a unified electronic health record system for every NHS patient in England. It was one of the largest civilian IT projects ever attempted, originally budgeted at £6.2 billion, and was formally wound down in 2011 after widespread failures.
How much did NPfIT actually cost the taxpayer?
The National Audit Office estimated in 2011 that approximately £9.8 billion had been committed to the programme, with around £6.4 billion already spent. Some components, including the NHS Spine and the electronic prescription service, were delivered and remain in use, but the core patient records system was largely undelivered.
Why did the NHS NPfIT project fail?
Multiple factors contributed to its failure: contracts were negotiated centrally without adequate clinical consultation, suppliers overpromised on delivery timescales, requirements shifted constantly, and the project was too large and too rigid to adapt. NHS trusts were given little choice over which systems they used, leading to widespread resistance on the ground.
Which companies were involved in NPfIT and what happened to them?
Major suppliers included BT, Accenture, CSC, Fujitsu, and iSoft. Accenture walked away in 2006, absorbing a reported £450 million loss, and Fujitsu exited in 2008. CSC eventually reached a settlement with the NHS in 2012. The experience damaged the reputations of several suppliers in the public sector market.
What changed in UK government IT procurement after NPfIT?
The programme’s failure directly influenced the creation of the Government Digital Service in 2011, which championed agile development, smaller contracts, and user-centred design. UK procurement guidelines shifted away from large monolithic contracts towards iterative, modular approaches, though critics argue the full lessons have not always been applied consistently.