Inside the Silicon Practice Collapse That Cut Off Hundreds of NHS Surgeries

Inside the Silicon Practice Collapse That Cut Off Hundreds of NHS Surgeries

Hundreds of National Health Service general practices across England abruptly lost their public websites, online triage forms, and patient consultation portals following the financial collapse and administration of healthcare software supplier Silicon Practice. The outage severed the primary digital front door for millions of patients, forcing surgeries back onto overloaded telephone lines and paper forms overnight. While official communications framed the disruption as an isolated vendor failure, the collapse exposes a deeper structural vulnerability inside UK primary care procurement, where critical clinical infrastructure relies on undercapitalized, single-point-of-failure suppliers operating on razor-thin margins.

The lights went out without a grace period.

For practice managers arriving at their desks across England, the realization was immediate and unforgiving. Domain names stopped resolving. Custom-built patient portals returned blank error screens. Repeat prescription requests, sick note applications, and symptom-checking questionnaires vanished into a digital void. In a healthcare system where telephone queues at 8:00 AM are already a national flashpoint, losing the online triage layer meant an instant, crushing surge in inbound calls that reception teams had neither the staffing nor the switchboard capacity to absorb.

The Anatomy of a Silent Digital Blackout

To understand why the collapse of a single private company caused such widespread operational paralysis, you have to look at what Silicon Practice actually built and how deeply it was embedded in daily clinical workflows. Operating largely through its flagship FootFall platform, the firm did not merely host static brochure websites displaying opening hours and clinic addresses. Over the past decade, it constructed interactive digital front doors designed to fulfill NHS England's mandate for modern general practice access.

Patients used these portals to submit structured medical histories before a doctor ever picked up a chart. Administrative staff relied on the backend dashboards to route queries, manage routine chronic disease reviews, and publish mandatory public health notices. When Silicon Practice entered administration and ceased trading, the servers hosting those web environments and the administrative pipelines supporting them were left stranded without active engineering maintenance or guaranteed hosting continuity.

Software-as-a-Service (SaaS) in healthcare carries a brutal catch. Unlike a physical piece of medical equipment—an electrocardiogram machine or a blood pressure monitor that continues working even if the manufacturer goes bankrupt—cloud-hosted patient portals require continuous server uptime, security certificate renewals, and active database management. The moment the vendor's corporate credit cards are frozen and its engineering team is laid off, the product begins to decay in real time.

How NHS Procurement Created a Fragile Vendor Ecosystem

The failure of Silicon Practice did not happen in a vacuum. It is the predictable consequence of a decade-long push by central health authorities to digitize primary care at breakneck speed while keeping per-patient software budgets artificially low.

Following the introduction of the NHS Long Term Plan and subsequent GP contract reforms, every practice in England was required to offer online consultations and maintain a functional, accessible website. To meet these targets, Integrated Care Boards (ICBs) and Clinical Commissioning Groups (CCGs) before them turned to approved procurement frameworks—most notably the Digital Care Services (DCS) catalogue and earlier dynamic purchasing systems.

These frameworks were built to encourage competition and innovation from small and medium-sized enterprises (SMEs). On paper, opening the market to agile tech startups prevented monopolies by legacy clinical system giants like EMIS and TPP. In practice, it created a race to the bottom on pricing.

Small suppliers won regional contracts by offering low annual licensing fees per registered patient, often bundling bespoke website design, hosting, and ongoing compliance updates into a single flat rate. While customer acquisition looked strong during the pandemic-era rush to remote triage, the unit economics were punishing. Inflation drove up cloud hosting costs, cybersecurity compliance standards became vastly more expensive to maintain, and NHS support teams demanded round-the-clock account management.

When a small vendor operating on fixed-price public sector contracts hits a cash flow crunch, there is no mechanism to pass rising operational costs onto the customer mid-contract. The company absorbs the loss until its reserves run dry.

The Myth of Seamless Continuity in Healthcare IT

Public sector procurement rules theoretically account for supplier insolvency. Standard NHS framework agreements almost always include clauses requiring vendors to maintain business continuity plans, data escrow arrangements, or transition support in the event of liquidation.

Reality rarely respects contract law.

When a company collapses into administration, the legal priority of the appointed insolvency practitioners is not patient access to primary care. Their statutory duty is to realize assets and maximize returns for creditors. Retaining expensive cloud infrastructure engineers or paying delinquent Amazon Web Services and Microsoft Azure hosting bills out of an empty corporate bank account is rarely viable without immediate emergency underwriting from the state.

Furthermore, migrating hundreds of individual GP practice websites is not a simple matter of flipping a switch. Each surgery owns—or thinks it owns—its specific domain name, local clinic branding, custom forms, and localized service directories. In many cases across the Silicon Practice estate, domain registrations, DNS records, and content management configurations were tightly coupled to the vendor's proprietary infrastructure.

Untangling that web requires manual intervention for every single practice:

  • Domain ownership verification: Practices frequently discover during a crisis that their .nhs.uk or .co.uk domain registration details are tied to a defunct vendor admin email address, locking them out of making basic DNS changes.
  • Content extraction: Without active backend access, staff cannot export custom-written patient guidance, local referral pathways, or bespoke triage templates, forcing them to rebuild content from memory or cached web pages.
  • Clinical safety sign-off: Under NHS digital clinical safety standards (specifically DCB0129 and DCB0160), practices cannot simply slap together a free consumer website builder overnight. Any replacement tool handling patient queries must undergo clinical risk assessments and data protection impact assessments before going live.
  • Data protection compliance: Ensuring that any residual patient-identifiable data submitted through legacy forms is securely purged or transferred under UK GDPR rules adds another layer of legal friction before administrators can wipe servers.

The Hidden Burden on Practice Managers and Clinical Staff

Media coverage of NHS IT outages usually focuses on patient frustration, and rightly so. A parent trying to book an urgent appointment for a feverish child or a patient needing an emergency repeat prescription feels the impact immediately. Yet the internal operational toll inside GP surgeries is equally severe and far less visible.

General practices are independent small businesses contracted to the NHS, not centrally managed branches of a single corporation. When a major supplier collapses, there is no centralized NHS IT swat team that swoops in to rebuild 400 websites by Monday morning. Instead, the burden falls directly on practice managers—administrators who are already juggling payroll, Care Quality Commission (CQC) inspections, premises maintenance, and acute clinical staffing shortages.

Consider a hypothetical example of a medium-sized suburban surgery serving 12,000 patients. On a normal Monday, 40 percent of patient contact flows through its online portal. Administrative staff triage those requests asynchronously, booking routine blood tests, issuing electronic prescriptions, and reserving scarce same-day GP slots for acute cases.

When that portal goes dark, all 40 percent of those interactions collapse back onto the telephone switchboard simultaneously. Receptionists spend three times longer on each call manually typing symptom descriptions that patients previously entered themselves. GPs lose pre-consultation context, lengthening appointment times. Meanwhile, the practice manager spends hours on hold with regional ICB digital leads, trying to secure emergency funding to onboard a rival supplier whose onboarding queue is suddenly backed up for six weeks.

Why Legacy Clinical Systems Cannot Simply Absorb the Load

A common question from outside the health sector is why GP practices rely on third-party web vendors at all when they already run massive, multimillion-pound core Electronic Health Record (EHR) systems like EMIS Web or SystmOne.

The answer lies in the architectural divide between core clinical databases and patient-facing web interfaces. Legacy EHR platforms were engineered decades ago as heavy, on-premise or private-cloud clinical ledgers designed for doctors and nurses—not as consumer-friendly web applications. While both major EHR providers have built their own patient apps and online consultation modules, practices often found them rigid, expensive, or poorly integrated with local primary care network (PCN) workflows.

Third-party specialists like Silicon Practice stepped into that gap by offering customizable websites that sat on top of the core clinical system, acting as a translation layer between the public and the surgery. That modular approach gave practices design freedom, but it also introduced an extra link in the chain. When that middle layer snapped, the core clinical database inside the surgery remained intact, yet the public had no digital bridge to reach it.

Red Flags the NHS Missed Before the Crash

Corporate collapses of this scale rarely happen overnight without warning signs visible in public financial filings or industry chatter. Across the UK health tech sector, smaller software vendors have faced a brutal squeeze over the past three years.

Companies House filings for small-to-medium health tech suppliers routinely show a familiar pattern: swelling balance sheet liabilities, mounting research and development debt, and shrinking cash reserves as pandemic-era grants dried up. Unlike venture-backed startups in consumer fintech or enterprise AI, UK primary care software firms have virtually zero pricing power. Their revenue per customer is capped by national framework tariffs, while their compliance obligations grow heavier every year.

To stay on NHS approved supplier lists, vendors must maintain ISO 27001 certification, pass annual penetration tests, adhere to strict NHS England Digital Technology Assessment Criteria (DTAC), and support continuous integration updates with the NHS App. For a large corporation with thousands of clients, spreading a £250,000 annual compliance bill across the user base is trivial. For a smaller vendor supporting a few hundred practices on low-margin contracts, fixed regulatory overhead consumes capital that should be funding infrastructure resilience and engineering redundancy.

When regional commissioning bodies evaluate bids, they heavily weight upfront price and feature checklists. Far less scrutiny is applied to vendor solvency, balance sheet liquidity, or whether a supplier's hosting architecture can survive a corporate restructuring.

What Practices and Commissioners Must Change Now

The Silicon Practice shutdown serves as a stark warning for every primary care network and Integrated Care Board across the country. Relying on fragile, single-vendor infrastructure for essential public health access is an operational gamble that eventually loses.

Protecting surgeries against future vendor insolvencies requires immediate, practical shifts in how digital services are bought and governed:

  1. Decouple domain ownership from web hosting: GP practices must retain direct administrative control over their own domain names and DNS zones through independent registrars, ensuring they can redirect web traffic to a backup landing page within minutes if a hosting provider fails.
  2. Mandate automated code and content escrow: Procurement frameworks must require verified, automated escrow of website templates, static assets, and configuration files—not just a contractual promise on paper that dissolves in administration.
  3. Audit vendor financial health alongside clinical safety: Regional commissioners must treat corporate liquidity and balance sheet stability as core clinical safety metrics, recognizing that an insolvent vendor poses a direct risk to patient access.
  4. Maintain a stripped-back fallback presence: Every surgery needs a pre-approved, lightweight static backup page hosted independently of its primary triage vendor, capable of displaying emergency contact details, pharmacy signposting, and NHS 111 guidance the moment a main portal goes offline.

Until NHS digital procurement stops treating critical clinical infrastructure like disposable commodity software, primary care will remain one corporate insolvency away from another blackout.

LL

Leah Liu

Leah Liu is a meticulous researcher and eloquent writer, recognized for delivering accurate, insightful content that keeps readers coming back.