INFRASTRUCTURE
Hospital 2.0: getting governance right
Hospital 2.0 will only compound value if it is precise about what must be common, what must remain locally owned, and how evidence from each scheme changes the next. A three-layer governance model can turn ‘national consistency with local leadership’ from an aspiration into an operating discipline, explains Varun Sharma, founder and CEO of pharmaceutical company NEUVIOR.
A repeatable doorset can be national. The judgement about how a frail older patient should be observed behind one is local. Confuse those two decisions and Hospital 2.0 will either surrender the economies of a programme or standardise choices that properly belong with the people accountable for care. That distinction matters now. On 30 July 2026,
the Department of Health and Social Care announced 11 long-term partnerships between NHS Trusts and construction partners under the Hospital 2.0 Alliance. The stated formula was ‘national consistency with local leadership’; Trusts retain responsibility for hospitals that reflect local needs, national standards improve quality and value, and long-term relationships support continuous improvement. It is the right ambition. It is not yet a complete allocation of decision rights. The New Hospital Programme’s first annual report describes a 46-scheme portfolio, a standardised design and delivery model, a ten-contractor alliance, and a programme intended to run through successive waves. It also describes Hospital 2.0 as substantively complete while its design products continue to be refined. The National Audit Office says the 2025 reset has placed the programme on a more stable long-term footing, but stresses that the benefits of the new design are not guaranteed and that the design will need to evolve between waves. The useful question, therefore, is not whether Hospital
2.0 should be central or local. That is a false binary. It is which decisions become safer, cheaper, and more reliable when made once; which become more dangerous when separated from local care, workforce, and community conditions; and how the programme converts variation into evidence rather than noise. The answer is a three-layer model: a national technical core, a Trust-owned decision charter, and a compulsory learning compact.
In one sentence: standardise the substrate, federate the judgement, and mandate the learning.
1. Standardise the substrate Hospital 2.0 has sound reasons to standardise. The programme is trying to replace fragmented, scheme-by- scheme development with repeatable designs, common planning assumptions, aggregated demand, and a long-term market. Its annual report says partitions, doors, mechanical and electrical systems, and façades have already been standardised. The alliance is intended
to reduce variability and waste while standardising products, processes, and data. This follows the logic of the government’s Construction Playbook: longer-term pipelines, early supply-chain involvement, outcome-based specifications, standardised components and interfaces, and whole-life value rather than a succession of isolated procurements. But a technical core must be more exact than a catalogue of standard rooms. It should define the substrate on which safe local decisions can be made. First, it should fix safety-critical requirements and interfaces: structural, fire, water, infection-prevention, ventilation, electrical, medical-gas, access, maintainability, and building-control requirements; the connections between manufactured systems; the evidence required at design, commissioning, and handover; and the circumstances in which an exemption is possible. The June 2026 response from DHSC and NHS England to the Public Accounts Committee says Hospital 2.0 is already adapting designs in response to findings from major UK inquiries, including changes to ensuite layouts and water-risk controls. That is exactly what a national core should do: absorb authoritative learning once and remove avoidable reinvention from every scheme. Second, it should define digital and information interfaces without imposing one local application stack. Hospital 2.0’s published baseline includes fibre, Wi-Fi and 5G connectivity, smart-building capabilities, predictive maintenance, asset tracking, and a hospital operations command centre. It is designed to support intelligent nurse call, sensors, and integration with electronic patient records, while leaving additional capabilities dependent on local need and digital maturity. The national job is
Queen Alexandra Hospital, Cosham, Portsmouth.
November 2026 Health Estate Journal 53
Leigh Park CC-BY-SA-4.0
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72
