Building in the way out
The most useful capability any government department can have, Richard argues, is »the ability to change its tech without it being painful«. That means favouring modular, open source and loosely coupled systems over proprietary technology maintained by a single vendor. Treat infrastructure, applications and data as separate decisions rather than a bundle from one provider.
Take the NHS screening programme, a five-year partnership Netcompany is working on in the UK, covering all seven national adult cancer screening services. At every step, Richard explains, the system will be built with security, data, accessibility and future-proofing in mind. Developed using open source and reusable elements, the NHS will decide where it runs.
»It all comes back to choice. Whether something runs on public cloud or on premise is a secondary consideration for us,« he says. »The important thing is that we can do both.«
Richard believes that systems built for government should be owned by government, so there’s no IP lock-in. Re-use matters: »If you can reuse platforms that are scalable, robust and resilient, you are automatically reducing the risk of failure.«