NHS open-source – Misryoum reports backlash after NHS England moves taxpayer-funded code behind closed doors over AI hacking risks.
A plan to hide taxpayer-funded NHS software code from public view is triggering an escalating backlash, as concerns mount over what it could mean for cybersecurity and public trust.
NHS England says it will restrict access to both existing and future code. citing risks from AI systems that can help identify and exploit weaknesses in software.. Misryoum reports the decision clashes with the NHS service standard that encourages open-source publication so others can review. improve. and build on the work.
In this context. the controversy is less about a single piece of software and more about a broader policy choice: whether openness itself should be scaled back when AI capabilities evolve quickly.. Critics argue that pulling code into the shadows could reduce the number of independent experts who spot and report problems.
Meanwhile, an open letter has gained traction, urging NHS England to reverse course.. Misryoum notes it has drawn hundreds of signatures and support from figures associated with digital rights and public-sector technology. with signatories arguing that openness enables broader scrutiny and stronger security outcomes.
A key point raised by campaigners is that open-source code tends to be tested by a wider community, not only by the organization that originally produced it. In turn, they argue that restricting access may hinder the very people whose skills and vigilance help harden systems over time.
There is also a debate about what “risk” really means in practice.. Misryoum reports that researchers who have examined publicly available NHS-related code in the past say vulnerabilities can be found through regular auditing and the use of AI-assisted testing. suggesting that security improvements may depend more on sustained investment in cybersecurity than on limiting visibility.
Even so. NHS England frames the step as a temporary measure to “further strengthen cybersecurity” while it assesses the impact of rapid advances in AI.. Misryoum reports the organization says it will continue publishing source code where there is a clear need. but it is setting a firm deadline for pulling some projects from public access.
For patients and clinicians, the heart of the issue is confidence. Misryoum’s view is that when healthcare technology becomes harder to inspect, it can be harder for the public and external experts to verify that safety and security are keeping pace.
In the end. the decision sets up a high-stakes test of how transparency and protection should be balanced as AI tools spread.. Misryoum will be watching closely to see whether this policy shift improves security in measurable ways or instead slows down the collaborative auditing that open development can enable.