Anyone who has tried to find a ward entrance, a visiting rule or the right outpatient department on a hospital website knows how quickly a simple errand turns into a search through inconsistent menus. For a trust formed by merger, the problem is doubled. Two organisations arrive with two content libraries, two service directories and two sets of assumptions about what a patient needs to know. When the new Bristol NHS Foundation Trust began operating, bringing together North Bristol and University Hospitals Bristol and Weston, it launched with a single site built on LocalNHS Drupal. It is the first English healthcare provider to do so.

The platform was developed with a digital agency and adapted from LocalGov Drupal, a framework already used by more than 60 councils in the UK and Ireland. The premise is straightforward. Publishing service information, appointment guidance and site details is a task every trust performs, and there is little reason for roughly 200 trusts to commission bespoke software for it. A feature built for one organisation can be shared with the rest at no additional cost to them.

The financial logic fits the present moment. The government has set out plans to abolish NHS England, reduce the running costs of integrated care boards and push more activity through the NHS App as the public's digital front door. Trusts are being asked to lift productivity and trim corporate overheads while waiting lists remain stubbornly high. Website procurement will not move those numbers. It does show whether the health service can identify a function that is common to all providers and stop paying for it repeatedly.

Local government is an instructive precedent. Councils faced years of austerity that left little capacity for bespoke digital projects, and pooling effort became a practical necessity. Health has not been under identical pressure, because trust budgets and procurement habits have tolerated a patchwork of suppliers and local variation. That tolerance is narrowing. Mergers add to the case, since integrating digital estates is among the least glamorous but most persistent costs of bringing organisations together.

There is also a point about how the state builds capability. Open-source code cannot be switched off by a supplier that changes its pricing, and improvements accumulate in public view. Yet shared software carries its own obligations. Someone must maintain the code, review contributions, patch security flaws and decide which features take priority. Councils have managed this through a collaborative community with volunteer effort and modest central coordination. An NHS that is reorganising its national bodies may find it harder to say who holds that responsibility for health. If the answer is nobody, the savings may prove temporary.

Patients should also keep expectations in proportion. A well-organised website reduces unnecessary calls, helps people reach the right department and lowers the administrative burden on front-line staff who field routine queries. The natural-language search built into the Bristol platform may help those with limited digital confidence, provided accessibility standards are maintained in practice. But a site cannot compensate for slow access to care, and trust leaders should resist presenting it as evidence of transformation.

For NHS leaders, the practical question is whether to join such a model early or wait for evidence. Early adopters gain influence over the roadmap and carry the risk of immature features. Late adopters inherit a tested product and have little say in its direction. Policymakers have a different task. If national bodies want trusts to share infrastructure, they need to fund stewardship and publish clear expectations on interoperability, security and content standards. Suppliers in health technology should expect closer scrutiny of any product that duplicates what a shared platform already offers.

The deeper test lies beyond websites. Patient records, scheduling tools and procurement frameworks all involve functions that most trusts perform in similar ways. Bristol's launch offers a low-stakes trial of whether the NHS can coordinate around common components without losing local accountability. If it works, the approach will carry weight in harder arenas. If it stalls on maintenance and governance, it will show how much shared infrastructure depends on institutions that currently lack the capacity to sustain it.

‍