A recent clampdown by NHS Digital on staff sharing software code has ignited a debate within the UK's digital community and raised questions about the future of open-source collaboration in public services. The updated policy, which requires NHS staff to seek explicit permission before sharing any code developed during their work, has been met with significant backlash from developers and open-source advocates, many of whom are employed within the NHS itself.
Critics argue that this restrictive approach stifles innovation, discourages collaboration, and runs counter to the spirit of transparency that many believe should underpin public sector technology development. Historically, the open-source model, where software code is freely available for inspection, modification, and distribution, has fostered a vibrant ecosystem of shared knowledge and collective improvement. For the NHS, an organisation heavily reliant on technology for patient care and administrative functions, such an approach could potentially hinder the development of bespoke solutions and the sharing of best practices across different trusts.
This internal NHS policy shift comes at a time when a separate, but related, movement is gaining momentum: a petition calling for the entire UK Civil Service to adopt Free and Open Source Software (FOSS) by default. Proponents of FOSS argue that it offers numerous advantages, including enhanced security through community scrutiny, greater flexibility and customisation, and significant cost savings by reducing reliance on proprietary software licenses. They contend that a 'FOSS by default' approach would not only benefit the public purse but also foster a more resilient and transparent digital infrastructure for government services.
The tension between these two trends highlights a broader philosophical divide within the public sector regarding software development and intellectual property. While some argue for tighter control over code to ensure security and compliance, others champion the collaborative and transparent nature of open source as a more effective and accountable model for public services. The potential implications for UK businesses and consumers are significant; a more open approach could foster a stronger domestic tech ecosystem, while a restrictive one might limit opportunities for external collaboration and innovation.
For UK businesses, particularly those in the technology sector, a move towards FOSS by default in the Civil Service could open up new avenues for contracts and partnerships, as government departments would be encouraged to work with a broader range of suppliers. Conversely, a closed approach might favour established proprietary software vendors. Consumers could benefit from more robust, secure, and cost-effective public services if FOSS principles lead to more efficient and transparent government IT systems.
The debate extends to regulatory frameworks. While the UK Information Commissioner's Office (ICO) primarily focuses on data privacy, the principles of transparency and public benefit underpinning open source align with broader governmental goals. The EU AI Act, while not directly applicable to code sharing policies, underscores a global trend towards greater scrutiny and accountability in software systems, where open source can play a role in demonstrating transparency and auditability. Expert commentary often points to the long-term strategic advantages of open source for national digital resilience, citing examples where public sector bodies have successfully leveraged FOSS for critical infrastructure. However, risks such as ensuring adequate support and managing diverse community contributions also need careful consideration.
Source: NHS Digital, UK Government Petitions