Which are all well and good, but are more akin to a 'vision' than technical design principles (especially with regard to preference of tradeoffs, data management, priority of platforms etc).
The rest of it seems to be strongly geared towards the web. It may well be that the NHS only wants to collaborate on public-facing web services, much like GOV.UK and the Government Digital Service, but this would need to be either extended or abstracted to be applicable to, say, administrative systems.
What's being withdrawn is their original CUI, linked in the article [0]. From what I can tell, this is very distinct from their new digital service manual, which seems to be replacing the old CUI.
> ...but this would need to be either extended or abstracted to be applicable to, say, administrative systems.
Based on nothing more than a rough skim of the CUI, admittedly, it seems like the original was a very web/interface-oriented design system in the first place. A focus on web components makes sense, since administrative systems can be implemented with a web-based frontend, and web design systems can be adapted to other user interfaces, because they provide a set of baseline, expected behaviours to replicate.
But still, just going by the link you have a list of principles:
https://beta.nhs.uk/service-manual/design-principles
Which are all well and good, but are more akin to a 'vision' than technical design principles (especially with regard to preference of tradeoffs, data management, priority of platforms etc).
The rest of it seems to be strongly geared towards the web. It may well be that the NHS only wants to collaborate on public-facing web services, much like GOV.UK and the Government Digital Service, but this would need to be either extended or abstracted to be applicable to, say, administrative systems.