INFRASTRUCTURE
therefore to specify connectivity, asset and clinical-data models, open interfaces, identity, cybersecurity, resilience, test evidence, and clinical-safety obligations. The local job is to determine which tools can be operated safely, funded recurrently, and absorbed by the workforce. Current NHS clinical-risk standards themselves distinguish between the manufacturer’s safety case and the deploying organisation’s responsibilities, while a 2026 national review calls for stronger treatment of complex system interactions, cross-organisational working, and post- implementation monitoring. Third, the core should make cost, carbon, and outcomes comparable. The NHS Net Zero Building Standard already provides a whole-life-carbon method, compliance matrix, and reporting tools, and the 10 Year Capital Plan says wave 1 onwards must comply with it. The Green Book requires costs, benefits, and risks to be appraised objectively and evaluation to be planned from the outset. Hospital 2.0 should translate those disciplines into one measurement spine: capital and operational cost, energy and whole-life carbon, construction productivity, defects, safety, staff time, patient flow, and agreed clinical or experience outcomes. A common metric does not predetermine a local answer – it makes competing answers legible. Finally, the technical core should be a controlled
product, not a static PDF. Every requirement needs an owner, evidence basis, version, effective date, verification method, and route for deviation. The NAO reports that Hospital 2.0 already has technical, transformation, and digital assurance bodies, a change-control subcommittee for exemptions or deviations, and an independent technical review panel. The missing public layer is a usable release architecture: what changed, why it changed, which schemes are affected, what evidence supports it, and whether the change is mandatory, transitional, or advisory. Procurement must make that architecture enforceable.
West Middlesex Hospital modular installation.
The Hospital 2.0 Alliance notice covers design, construction, commissioning, handover, digital, and lifecycle maintenance, and describes the Alliance Agreement as the place where NHS England, Trusts, contractors, and other partners collaborate. Call-off contracts should therefore carry the current core by reference, define how later versions apply, preserve the programme’s right to reuse performance evidence, and require proposed substitutions to state their interface, safety, whole- life cost, and carbon effects. Otherwise, ‘standard’ can dissolve between the framework, the scheme contract, the specialist supplier, and the installed asset. Product- level traceability also matters after handover: the operational team needs an authoritative asset record, not simply a compliant design-stage model. The substrate is only standard if it survives procurement, installation, commissioning, and maintenance.
54 Health Estate Journal November 2026 Standardisation at this level is not central
micromanagement. It is the removal of low-value choice from high-consequence interfaces.
2. Federate the judgement Once the substrate is explicit, Trusts need an equally explicit charter for the decisions they own. ‘Local leadership’ is otherwise vulnerable to two opposite failures: national teams can drift into care-model decisions because they affect the building, while local teams can relabel avoidable technical variation as clinical uniqueness. The charter should divide decisions into four states:
n Fixed requirements apply nationally unless a formal exemption is approved.
n Bounded choices allow a Trust to select from tested options within a safe envelope.
n Local determinations are owned by the Trust and its system partners, supported by evidence.
n Escalated decisions arise where a local proposal crosses a safety, cost, carbon, interoperability, or programme threshold.
The categories should be agreed early and revisited at each business-case gateway. Care model and capacity belong in the local determination domain, although the method and assurance should be common. The Public Accounts Committee noted that the programme business case assumes an average six per cent increase in overnight beds across the schemes planned for Hospital 2.0, while detailed modelling produces materially different results between sites. It questioned how that expansion fits with the planned shift from hospital to community care and asked for scheme-level explanations of capacity, community provision, and patient flow. The programme’s demand model shows how the apparent conflict can be resolved. DHSC’s February 2026 letter to the Committee describes an NHS- owned Monte Carlo model with common national assumptions, scheme-specific inputs, and ranges that expose uncertainty. Local clinicians, operational leaders, public-health representatives, and integrated care boards help set assumptions; regional, programme, and capital- assurance teams review them; and inputs are refined through successive business cases. The model is version- controlled and records what changed and why, and what checks were completed. That is federated judgement in practice: one analytical language, local evidence, structured challenge, and traceable change. Hospital 2.0 should extend the same pattern beyond demand modelling. The Trust charter should own the care model; capacity and resilience assumptions; workforce model; community and primary-care dependencies; clinical adjacencies within nationally assured envelopes; local digital maturity; site access and logistics; decanting; enabling works; and implementation sequence. These are not cosmetic variations. They determine whether a theoretically efficient building can be staffed, commissioned, and operated safely.
Single bedrooms illustrate the boundary. Nationally,
room geometry, water safety, ventilation, digital infrastructure, emergency access, and tested equipment layouts can be standardised. Locally, the Trust must still determine observation models, staffing, escalation, cohorting, specialism-specific workflows, and how digital monitoring will be introduced. The Public Accounts Committee warned that some vulnerable patients may experience isolation, that staff may initially require more
Jim Linwood CC-BY-2.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
