Every country comparable to Wales in scale and governance made a different structural choice. None adopted a monopoly delivery body. All separated interoperability standards from application delivery. All recruited technical leadership externally against verifiable criteria.
This page documents the three most relevant comparators: Denmark (standards body + regional delivery), Estonia (interoperability layer + sovereign delivery), and NHS Digital England (competent leadership + federated procurement).
Denmark — Standards Body + Regional Delivery
Denmark has a population of around 5.9 million, roughly twice Wales’s 3.1 million, organised into five health regions with real autonomy over delivery. The national architecture is divided: a central body sets standards and maintains the interoperability backbone; regions choose and procure their own electronic health record systems.
The Danish Health Data Authority (Sundhedsdatastyrelsen) owns national data standards, the national patient index, and the statistical registers that make Danish health data one of the most complete datasets in Europe. It does not build regional EHR systems. It defines the standards those systems must meet.
The interoperability layer sits with MedCom, a publicly-funded non-profit founded in 1994, jointly owned by the Ministry of the Interior and Health, Danish Regions, and local government (KL). MedCom develops, tests, and certifies the messaging standards that allow every Danish health IT system to exchange clinical data. It does not sell software. It connects software. Denmark has ranked consistently in top-tier international interoperability comparisons for two decades — a position MedCom has held continuously since before most UK digital-health strategy documents were written.
Sundhedsplatformen is the Epic-based regional EHR covering Region Hovedstaden (Copenhagen) and Region Sjælland — approximately 2.5 million residents. Implementation began in 2016. Capital-region cost estimates reported in the Danish press cluster around DKK 2.8 billion (~£320M) over the rollout period. The go-live attracted serious public controversy; the system is now functioning and measurably improving clinical outcomes. Other regions — Midtjylland, Syddanmark, Nordjylland — made independent EHR choices. Regions have real power to choose.
The national patient portal sundhed.dk, operational since 2003, gives every Danish citizen access to their own health record, prescriptions, lab results and referrals. It is built on top of MedCom’s infrastructure — not on top of a monopoly delivery body.
The structural lesson: in Denmark, standards are separated from delivery. The national body does the interoperability work that no one else can do efficiently. Regions compete and choose on the applications that sit above it.
The Welsh comparison: Wales already has regional health boards with more operational autonomy than Danish regions had before the 2007 structural reform. The governance infrastructure to support this pattern exists. The choice to centralise delivery through a monopoly was exactly that — a choice.
Estonia — Interoperability Layer + Sovereign Delivery
Estonia has a population of around 1.3 million — roughly 40% of Wales. It is the most frequently cited digital-government case study in the world, and almost none of its architecture is a monopoly delivery model.
The foundation is X-Road (X-tee), the national data exchange layer Estonia designed and has operated since 2001. X-Road is open source, used across 99% of Estonian state services, and federates data between hundreds of public and private databases. Every EHR system in Estonia is connected via X-Road. No single vendor, and no single government body, holds the clinical data. The data is distributed across the systems that generate it; X-Road makes it look unified.
TEHIK — the Health and Welfare Information Systems Centre, about 200 staff, established in its current form in 2017 — is Estonia’s national health IT authority. It operates X-Road for health, runs the national e-Health record as a virtual record federating data from existing provider systems rather than a monolithic database, and manages the information systems that underpin Estonian social security and labour services. TEHIK covers health IT for 1.3 million people with roughly one-sixth of DHCW’s headcount.
Estonia’s e-prescription service (Digiretsept) launched in 2010. Over 99% of prescriptions in Estonia are now issued and dispensed digitally. Published costs for initial development are in the low single-digit millions of euros, with annual running costs reported in the same range.
The Nordic Institute for Interoperability Solutions (NIIS) is the joint Estonia-Finland organisation that now develops X-Road as open-source infrastructure. Finland built its national e-health service Kanta on the same X-Road stack. Iceland, Ukraine, Schleswig-Holstein, Québec and others have adopted it. Compare: DHCW’s “once for Wales” monopoly against an Estonian interoperability standard co-developed with Finland and exported across continents.
The structural lesson: Estonia’s national body owns the connective tissue, not the applications. Applications are chosen by providers. Data follows the patient because interoperability is mandatory — not because one body builds everything.
The Welsh comparison: Wales is wealthier, better-staffed, and has stronger institutional foundations than Estonia had in 2001 when X-Road launched. Estonia built world-class digital health with fewer resources and a harder starting position. The gap between Wales and Estonia is not funding or talent. It is governance.
NHS Digital England — Competent Leadership, Federated Procurement
NHS England Transformation Directorate (which absorbed NHS Digital in February 2023) covers around 56 million people. The architecture is: central standards, competitive national services, trust-level procurement.
The most important contrast is leadership recruitment. NHS Digital recruited its C-suite openly from the commercial sector. Chief Information Officer roles have been filled from Rolls-Royce and Jaguar Land Rover. The Chief Digital Officer came from the Home Office. Senior technology leaders were recruited from Credit Suisse and HSBC. Roles were advertised at market rates. Selection was against published technical criteria, run by external panels.
Compare DHCW’s recruitment model. Executive roles — CEO, CDO, Head of Software Engineering — were filled through processes that did not match this standard. The CEO role was filled by the Interim CEO of the predecessor body, NWIS — who had led NWIS through the period of its public disgrace. Career background: NHS Wales finance and health information management. No publicly documented technology programme delivery track record before appointment. The CDO is an internal promotion with 19 years at NWIS/DHCW. The Head of Software Engineering was advertised at Band 8c (£71-82k) — well below market rate for the responsibility. Selection was conducted by a small internal circle, not by open external recruitment against verifiable technical criteria. The structural pattern is documented at L7: The Competence Void.
The delivery record follows from the recruitment model. The NHS App now has tens of millions of registered users. GP Connect provides national GP-record interoperability integrated with all major GP software providers. Electronic prescribing operates at national scale. NHS Digital’s track record is not perfect — Care.data and NPfIT are documented failures — but the scale and competence of delivery is not comparable to DHCW’s 0-of-9 record on time, 83p of return per £1,000 invested.
The structural lesson: competent technical leadership, recruited externally against verifiable criteria, produces delivery. The recruitment process determines the delivery outcome. This is not correlation; it is mechanism.
The Welsh comparison: Welsh public-sector salary scales are already close to NHS Digital’s for non-executive roles. The gap is at C-suite level and in the selection process. Closing it requires political will, not additional funding.
The Pattern That Wales Rejected
Three different architectures. One consistent structural pattern:
- Competent technical leadership recruited against external, verifiable criteria
- Interoperability standards separated from application delivery
- No monopoly delivery body staffed by executives promoted from administration, finance, or long internal service
- No patronage pipeline pre-credentialing the executive cohort before the new body’s first board meeting
None of these countries built their equivalent of “once for Wales” as a delivery monopoly. The monopoly model — and the patronage pipeline that staffs it — is a specifically Welsh arrangement, designed and maintained by the same governance system this analysis critiques.
The blueprint proposes a variant of the Danish-Estonian pattern adjusted for Welsh political reality. The six interventions are the operational steps to get there.
What Wales Should Learn From Their Failures
The three jurisdictions are not flawless. Each carries documented failures that inform what reform should — and should not — attempt.
NHS Digital England. Care.data (2014, halted 2016) failed because patient consent and communication were treated as a downstream task. NPfIT (2002-2011, written off at roughly £10 billion) failed because it was attempted as a top-down monolithic build — exactly the architecture Wales is now being urged to dismantle. Both failures are directly relevant: Wales should not repeat them by sequencing transparency after delivery (Care.data) or by trying to standardise applications rather than data flows (NPfIT).
Denmark — Sundhedsplatformen go-live. The Epic-based EHR rollout in Region Hovedstaden produced documented disruption to clinical workflows in 2016-2018, with significant clinician dissatisfaction reported in the Danish press. The lesson: even well-resourced regional procurement requires deep clinical involvement in implementation, not just procurement. Welsh embedded teams under Flip the Model carry this lesson directly.
Estonia — early X-Road resistance. When X-Road launched in 2001, agency-level resistance to data-sharing standards was significant. Estonia overcame it by making interoperability mandatory in legislation, not encouraged in policy. The lesson: interoperability standards have to be statutory, not aspirational, or they fail. Welsh standards under the architectural endpoint of Flip the Model carry this lesson.
The point is not that the alternatives are perfect. It is that they have records — public, debated, learned from — to compare against. DHCW’s record is comparable in cost and time, with documented delivery far below any of them.
Risks the Alternatives Don’t Cover
Wales has structural conditions the comparator jurisdictions do not. Three are material:
- Market depth. Wales has roughly half Denmark’s population and is part of a UK procurement market dominated by NHS England’s purchasing power. Some specialist supplier negotiations require coordination with England rather than independent procurement.
- Bilingualism. Welsh-language primary care interfaces and patient-facing systems are a statutory requirement, not an option. Estonia’s largely monolingual interface is not a complete model.
- Devolved-versus-reserved policy boundaries. Several digital-health-adjacent functions (the UK-wide elements of the NHS App, GP IT systems’ UK-wide elements, identity infrastructure) sit at the intersection of devolved and reserved competence. The standards body Wales builds must interoperate with reserved-function infrastructure, not stand alone.
These constraints do not invalidate the comparator pattern. They shape implementation choices within it. The blueprint adjusts for them; the destination remains the same.