Blueprint Digital NHS WalesOnce for Wales: An Antipattern
The Blueprint

Once for Wales: An Antipattern

Once for Wales is the policy framing that justifies DHCW's monopoly on digital delivery for NHS Wales. In software-engineering language, it is an antipattern — a popular structural choice that looks like the obvious answer but reliably produces the failure modes it was supposed to prevent. Denmark, Estonia, and NHS Digital England examined the same model and explicitly rejected it. Wales is the exception, not the default.

What is the 'once for Wales' policy? It is the framing that justifies DHCW's monopoly on digital delivery for NHS Wales — every system, every integration, every strategic procurement flows through one Special Health Authority. The phrase is presented as self-evident: a small country, a single body. In software-engineering terms it is an antipattern — a commonly-attempted structural choice that looks like the obvious answer but reliably produces the failure modes it was supposed to prevent. Denmark (5.9M people), Estonia (1.3M with a 200-person national agency), and NHS Digital England all examined this model and rejected it. 'Once for Wales' is a specifically Welsh arrangement — and the results speak for themselves: ~£600M cumulative funding, £0.5M of quantified value, 0/9 programmes on time, 12+ months at Level 3 enhanced monitoring escalating to Level 4.

What “Once for Wales” means

“Once for Wales” is the policy framing under which Digital Health and Care Wales (DHCW) exists as a single national Special Health Authority delivering all digital infrastructure for NHS Wales. Every system, every integration, every strategic procurement flows through one monopoly delivery body. The phrase appears in DHCW strategy documents, in Welsh Government commissioning papers, and in the public rationale for DHCW’s existence. It is presented as self-evident: a small country, a single delivery body.

It is not self-evident. It is an antipattern.

What “antipattern” means in this context

In software engineering and organisational design, an antipattern is a commonly-attempted solution to a recurring problem that looks plausible on first reading, is widely adopted on first principles, and reliably produces the failure modes it was meant to prevent. Antipatterns are not unknown mistakes — they are patterns, repeated across organisations, identifiable in advance, and documented in the literature. The distinguishing feature is that the people inside the antipattern can usually articulate why their version is “different” or “necessary in our context”, while the structural mechanism producing the failure operates regardless of intent.

Monopoly delivery bodies for national digital infrastructure are a documented antipattern across health, transport, identity, and tax. The international evidence has been clear for at least fifteen years. Wales adopted the antipattern anyway.

Why the antipattern looks plausible

The argument runs:

  • Wales has 3.16 million people, served by seven health boards.
  • A unified digital backbone benefits from network effects.
  • A single delivery body avoids duplication.
  • “Once for Wales” therefore captures economies of scale that fragmented delivery would miss.

The reasoning is plausible at first reading. It is also the reasoning that every comparator country considered and rejected. That is the diagnostic signature of an antipattern: the surface logic is internally consistent, the structural mechanism is the opposite of what the logic predicts.

Why every comparator rejected the antipattern

Denmark (5.9 million people, comparable to Wales × 2). Denmark separates standards (set by Sundhedsdatastyrelsen, the Danish Health Data Authority, on behalf of the state) from delivery (carried out by multiple regional and commercial actors operating under those standards). Sundhedsdatastyrelsen is a small agency with regulatory teeth — it does not deliver applications. The delivery layer competes; the standards layer arbitrates. Danish citizens see a single national patient record (Sundhedsplatformen / sundhed.dk) — but that record is fed by multiple delivery actors, not one.

Estonia (1.3 million people — closer to a single Welsh health board in population). Estonia operates e-Health Estonia, a national agency of approximately 200 staff. That is one-sixth of DHCW’s headcount. Like Denmark, Estonia separates the standards function (run by the agency) from delivery (which sits with health institutions and the X-Road interoperability layer). The agency is a thin standards body; the delivery is distributed.

NHS Digital England (now NHS England Transformation Directorate) — comparable scale, far higher institutional maturity. England separates national infrastructure (Spine, NHS Number, dm+d) from application delivery (which sits with trusts, primary care suppliers, and competing vendors). National standards are set centrally; delivery is plural. No equivalent of DHCW’s monopoly delivery body exists.

The pattern is consistent. Every comparator separates standards-setting from application delivery. None has a single monopoly delivery body. “Once for Wales” is not the small-country default — it is the Welsh exception, and it is the same antipattern that the comparator jurisdictions actively designed away from.

How the antipattern manifests at DHCW

The monopoly framing has three structural effects, each of which the Blueprint analysis maps to a specific feedback loop. Each is a well-documented consequence of the antipattern rather than a feature of DHCW’s specific implementation:

  1. No exit option for health boards. If a health board is dissatisfied with the delivery of a national system — say, WPAS, eMPI, or RISP — there is no alternative supplier within NHS Wales. The health board can complain; it cannot procure elsewhere. This is the mechanism that produces L2: The Credibility Death Spiral — trust erodes but cannot be priced into delivery decisions because there is no competitive signal. The same dynamic operates at the infrastructure layer. The DHCW data centre supplier — whose cooling failover failed in July 2024 and again in near-identical fashion in June 2025 — faces no competitive pressure to remediate because there is no alternative national supplier within the once-for-Wales architecture; the March 2026 PSBA outage was the third year of the same pattern at the network layer.

  2. No external benchmark for quality. When the delivery layer is one body, “what good looks like” is whatever that body produces this quarter. There is no parallel delivery against which to compare. Drift to low performance becomes invisible, because the comparator is yesterday’s DHCW rather than today’s Denmark. This is the structural mechanism behind Trap: Drift to Low Performance.

  3. Standards and delivery are not separated. DHCW sets the technical standards and delivers the systems that implement them. The standards-setter and the delivered-against party are the same organisation. Audit Wales has no independent technical-standards function to refer to. The Welsh Government has no separate standards-body to commission. The result is a closed-loop technical authority — L11: Captured Governance compounds this directly.

Replacing the antipattern with the pattern

The Blueprint’s Intervention 4: Flip the Model ends the once-for-Wales monopoly delivery model and replaces it with the architectural pattern the comparator jurisdictions converged on. Specifically:

  • Separate the standards function from the delivery function. A small Welsh national digital standards body sets technical and interoperability standards; delivery is carried out by health boards, the DHCW successor, and (where appropriate) external providers operating under those standards.
  • Embed engineering teams in health boards under clinical leadership. Removes the unbreakable monopoly between the delivery body and the receiving institutions.
  • Recruit externally on published technical criteria. Removes the loyalty-selection pipeline that the monopoly has structurally protected.

Ending “once for Wales” is not anti-cooperation. It is anti-antipattern. Denmark and Estonia are more digitally integrated than NHS Wales by every measurable outcome — and they got there by separating standards from delivery, not by concentrating both in one body.

What this page does not say

This page does not argue that DHCW should be dissolved. It argues that the antipattern — single-monopoly-delivery — is the wrong structural condition for any successor body to operate under. The next step is in Intervention 4.

The “once for Wales” framing has been load-bearing for DHCW’s existence. Removing the framing is not a presentational choice — it is a precondition for the structural reform the Blueprint proposes, and it is what the international evidence has been telling Wales for at least fifteen years.