Topic 9.1 — Working with Local & National Governments

In one sentence: Digital health and care leaders succeed inside the public system not by resisting its rules on funding, assurance, and accountability but by learning them well enough to move fast within them and shape them over time.

Why this matters in health and care#

Almost every pound you spend and every service you run is bounded by the machinery of government. National bodies set the mandate, the standards, and the money; local government owns social care and public health; and Parliament, ministers, and the public hold all of it to account. A digital leader who treats this machinery as an obstacle to be circumvented will burn credibility and get blocked; one who treats it as the terrain will get funded, assured, and adopted.

The stakes are distinctive in health and care. You are spending public money on services that must be safe, equitable, and defensible in front of a select committee, an auditor, or a coroner. Funding arrives on political cycles that rarely match delivery cycles. Standards are not optional preferences but conditions of approval. And the same transparency that makes government trustworthy — Freedom of Information, published spend, public board papers — means your decisions will be read by people who were not in the room.

Getting this right protects patients and public money at once. A well-made business case wins investment that survives scrutiny; a service that passes assessment is one the public can trust; alignment to national strategy means your work is amplified rather than overridden at the next reorganization. The discipline of working with government is what turns a good idea into a funded, assured, sustained service.

Core concepts#

The national bodies and what they control. Learn who holds which lever. NHS England sets the operational mandate, funding flows, and many digital standards. The Department of Health and Social Care (DHSC) sets policy and sponsors legislation. The devolved governments — in Scotland, Wales, and Northern Ireland — run their own health systems with their own bodies (NHS Scotland, NHS Wales, HSC in Northern Ireland). The UK Health Security Agency (UKHSA) owns health protection. NICE appraises clinical and cost-effectiveness and sets the Evidence Standards Framework for digital health technologies. The MHRA regulates medical devices, including software as a medical device. The Care Quality Commission (CQC) inspects and registers providers. Each is a gate or an enabler depending on how early you engage it.

Policy, legislation, and mandates. Government works through hierarchy: legislation (e.g. the Health and Care Act 2022) enables, national strategy directs, and annual planning guidance and the NHS mandate turn direction into obligations with deadlines. Knowing where your work sits in this chain tells you whether you are complying, contributing, or freelancing.

Funding cycles and the business case. Public spending is appraised through HM Treasury's Green Book using the Five Case Model — strategic, economic, commercial, financial, and management cases — progressing through a Strategic Outline Case, Outline Business Case, and Full Business Case. Money is split between capital (assets) and revenue (running costs), governed by different rules and rarely interchangeable, and is released in cycles set by Spending Reviews and annual budgets rather than by project readiness.

Assurance and standards. Digital spending passes through controls. The Government Digital Service (GDS) spend controls and the Service Standard require services above thresholds to pass service assessments at alpha, beta, and live. In health specifically, the NHS Service Standard, the Digital Technology Assessment Criteria (DTAC), the Clinical Risk Management standards (DCB0129/DCB0160), and NICE's evidence standards form the assurance stack. These are not bureaucracy for its own sake; they are how the system decides your service is safe and worth the money.

Transparency and accountability. Public bodies operate in the open: Freedom of Information requests, published spend over £25,000, public board papers, National Audit Office and Public Accounts Committee scrutiny, and the Nolan Principles of public life. Assume anything you write may be read publicly, and let that raise your standard rather than your defensiveness.

Best practices#

1. Map the accountability chain before you plan the work. Identify which national body owns the mandate, the standard, and the money for your area, and where your work sits in the chain from legislation to planning guidance. Knowing whether you are complying with a mandate or proposing something novel changes who you must convince and how.

2. Write the business case in the government's own language. Use HM Treasury's Green Book Five Case Model and progress through Strategic Outline, Outline, and Full Business Cases; be explicit about capital versus revenue and about benefits that are measurable and monetized where possible. A case that assessors recognize structurally is a case they can approve; a brilliant idea in the wrong format stalls.

3. Engage assurance early and treat it as design input. Book pre-assessment conversations with GDS/service assessors, DTAC, and clinical safety (DCB0129/DCB0160) before you build, not after. Assessment findings are cheap when they arrive in discovery and ruinous when they arrive at go-live (see Topic 9.0 — Collaborating with Partner Organizations on IG engaged early).

4. Align explicitly to national strategy and standards. Show how your work delivers the NHS mandate, planning guidance, and open-standards requirements, and cite them by name. Alignment is protection: work that visibly advances the national direction survives leadership changes and budget rounds; work that ignores it is the first thing cut.

5. Plan delivery around funding cycles, not against them. Sequence work so that value lands within the financial year money is released, and never assume multi-year revenue that has not been secured through a Spending Review or budget. Design increments that each stand alone, so a funding pause degrades scope gracefully rather than stranding a half-built platform.

6. Do policy engagement properly and transparently. Engage with officials and ministers through the proper channels, register interests, and follow the rules on lobbying and transparency; bring evidence, not just advocacy. Done openly, policy engagement is a legitimate and valuable way to shape the system; done in the shadows it destroys the trust your work depends on.

7. Design for transparency from the start. Assume board papers, spend, and decision records will be public, and write them to a standard you would defend in front of the Public Accounts Committee. Publishing your reasoning, your data-quality limits, and your risks openly builds the credibility that closed decision-making erodes.

8. Respect the political cycle without being captured by it. Elections, ministerial changes, and reorganizations reset priorities on a rhythm that ignores delivery timelines. Keep the mission steady, translate it into whatever the current priority language is, and protect the delivery team from every change of political weather.

Questions to discuss with your team#

1. Where does our work actually sit in the chain from legislation to planning guidance, and are we complying, contributing, or freelancing? Government works through a hierarchy — legislation enables, national strategy directs, and the NHS mandate and annual planning guidance turn direction into dated obligations — and knowing your position in that chain tells you who you must convince and how much latitude you have. Teams often cannot answer this cleanly, which is dangerous because work that visibly advances the national direction survives leadership changes and budget rounds, while work that cuts across the mandate is the first thing overridden at the next reorganization. The tension worth debating is between alignment as genuine protection and alignment as box-ticking theatre: it is entirely possible to cite the planning guidance on paper while freelancing in practice, and a large organization can get away with that until an audit says otherwise. Concrete angles include naming which national body owns the mandate, the standard, and the money for your specific area (and the correct devolved system if you are outside England), identifying whether you are delivering an existing obligation or proposing something genuinely novel, and being honest about the parts of your programme that no mandate actually requires. A good answer maps the accountability chain for this initiative specifically rather than gesturing at national strategy in the abstract, distinguishes the work that is mandated from the work that is discretionary, and shows the alignment concretely enough that an assessor or auditor would recognize it — not merely asserts it in a slide.

2. How do we design delivery so that a funding pause, a Spending Review, or an election does not strand a half-built platform? Public money arrives on political cycles set by Spending Reviews and annual budgets, split between capital and revenue that are governed by different rules and rarely interchangeable, and released on a rhythm that almost never matches delivery cycles. The recurring failure is to assume multi-year revenue that was never actually secured and to build something whose value only materializes after the money it depends on has evaporated. The trade-off to debate is between the efficiency and coherence of one big build and the resilience of standalone increments that each land within a funded period — the former is cheaper if nothing goes wrong and ruinous if the funding weather changes, which in government it reliably does. Worth examining concretely: have you separated the one-off capital build from the recurring revenue for support, and secured the revenue line explicitly rather than hoping for it; can your programme degrade scope gracefully if a general election pauses new spending, so the first increment still demonstrates value; and are you depending on a single enthusiastic official whose priorities reset at the next reshuffle? A strong answer sequences the work so each release stands alone and delivers something real within the money already committed, treats unsecured future revenue as a risk rather than a plan, and anchors the mission to the published national mandate so it outlives any individual sponsor.

3. Are we treating assurance and transparency as things to fear and defer, or as design inputs and sources of credibility? The assurance stack — service assessment, DTAC, clinical safety under DCB0129/DCB0160, and the relevant NICE evidence tier — is how the system decides your service is safe and worth the money, and it is radically cheaper when engaged in discovery than when it surfaces findings at go-live and forces expensive rework. In parallel, public bodies operate in the open: Freedom of Information requests, published spend, public board papers, and National Audit Office and Public Accounts Committee scrutiny mean your decisions will be read by people who were not in the room. The instinct on both fronts is defensive — to treat assurance as a hurdle to clear late and transparency as a threat to manage — and the discussion should confront how much that instinct is quietly shaping the team's behaviour. Concrete angles include whether you have booked pre-assessment conversations with service assessors and clinical-safety leads before building rather than after, whether the NICE evidence tier is agreed up front so the evaluation is designed to meet it, and whether your board papers and spend records are written to a standard you would willingly defend in front of the Public Accounts Committee. An honest answer recognizes that assessment findings are cheap in discovery and ruinous at launch, that publishing your reasoning, data-quality limits, and risks openly builds credibility that closed decision-making erodes, and that both assurance and transparency should raise the team's standard rather than its defensiveness.

4. Are we engaging the correct national system for our geography, or quietly defaulting to England's bodies and rules? Health and care is devolved, and Scotland, Wales, and Northern Ireland run their own systems with their own bodies, standards, and funding routes rather than NHS England, so a plan that names the wrong machinery is not merely imprecise but unworkable. The failure is easy to make and easy to miss: teams steeped in NHS England guidance, the English Service Standard, and DTAC assume those apply everywhere, and the assumption survives until a Scottish board or a Welsh commissioner asks which of their standards you have met. The tension is that much good practice genuinely does transfer — the Green Book, clinical-safety discipline, the habit of engaging assurance early — while the institutions, evidence expectations, and approval gates do not, so the discussion has to separate the portable method from the geography-specific apparatus. Concrete angles include naming the correct national body that owns the mandate, the standard, and the money for each jurisdiction you serve, checking whether a service designed for one nation can even be deployed in another without re-assurance, and being explicit about cross-border data flows and information-governance differences. A good answer identifies the right national system for every geography in scope, distinguishes the transferable discipline from the jurisdiction-specific gates, and refuses to treat "the NHS" as a single undifferentiated buyer.

5. Are we engaging with policy and ministers through the proper channels, with evidence rather than advocacy, and to a standard we would be content to see published? Shaping the system is legitimate and often necessary — the rules, standards, and priorities are made by people you can reach — but the line between influencing policy openly and lobbying in the shadows is exactly the line that governs whether that engagement builds trust or destroys it. Public life runs on the Nolan Principles and on transparency rules, registers of interest, and lobbying disclosure, and a digital leader who forgets that a meeting note or a Freedom of Information request can surface the whole exchange is one bad email from a credibility crisis. The tension worth debating is between the genuine value of getting into the room early to shape a standard before it hardens and the risk of being seen — rightly or wrongly — to have secured advantage through access rather than merit. Concrete angles include whether you engage officials and ministers through the proper channels rather than back doors, whether you bring evidence and honest limitations rather than one-sided advocacy, whether interests are registered and the rules on lobbying followed, and whether every exchange would read well if published. An honest answer treats openness as the source of the influence rather than a constraint on it, brings evidence that acknowledges what you do not yet know, and holds every contact to a standard the team would defend in front of the Committee on Standards in Public Life.

6. How do we hold the mission steady across elections, reshuffles, and reorganizations without either ignoring the political weather or being captured by it? Government resets priorities and vocabulary on a political rhythm — elections, ministerial changes, and structural reorganizations — that pays no attention to delivery timelines, and a team can be whipsawed into rewriting its strategy with every reshuffle or, at the opposite extreme, into ignoring the shift until its funding and cover quietly evaporate. The skill is neither rigidity nor weathervaning but translation: keeping the underlying clinical or public-value mission constant while re-expressing it in whatever the current priority language happens to be, so the work is recognized as delivering today's agenda without actually changing what it does. The trade-off to debate is how much to bend the framing and the roadmap toward a new minister's emphasis before you are no longer delivering your original mission at all, and who on the team is responsible for absorbing that political turbulence so delivery engineers do not feel it. Concrete angles include whether the mission is anchored to a published, durable national mandate rather than to a single sponsor's preference, whether you have a deliberate way to re-translate the same work into new priority language, and whether the delivery team is shielded from every change of political weather. A strong answer keeps the mission and the increments steady, retranslates the narrative deliberately rather than reflexively, protects the team from churn, and can tell the difference between adapting the framing and abandoning the purpose.

In practice: a health & care example#

A fictional ICB wants to fund a regional digital service that lets people manage long-term conditions from home. The temptation is to procure a product and announce it. Instead the team maps the terrain first: NHS England owns the digital standards and much of the money, NICE's Evidence Standards Framework will judge the clinical claim, DTAC and DCB0129 clinical safety are conditions of deployment, and the county council co-funds because social care benefits.

The business case is written to the Green Book Five Case Model, moving from a Strategic Outline Case to a Full Business Case, and it separates the one-off capital build from the recurring revenue for support — securing the revenue line explicitly rather than assuming it. Benefits are monetized where possible and stated qualitatively where not, so assessors trust the numbers.

Assurance is engaged in discovery. An early conversation with service assessors reshapes the onboarding journey; the DTAC and clinical-safety work runs alongside the build; the NICE evidence tier is agreed up front so the evaluation is designed to meet it. The team aligns the pitch to the current planning guidance and cites it by name, which protects the programme when a ministerial reshuffle changes the departmental emphasis.

When a general election pauses new spending, the increment-by-increment design means the first release — remote monitoring for one condition — still lands within the funded year and demonstrates value. The public board papers, published in full, and an early National Audit Office-style self-review turn the transparency that leaders often fear into a source of credibility that helps unlock the next tranche.

Sector lenses#

Startup#

A digital-health startup meets government as a supplier and a hopeful, not a rule-setter, and its survival depends on decoding assurance before the runway runs out. Treat DTAC, clinical safety (DCB0129/DCB0160), and the relevant NICE evidence tier as product requirements from day one, because a failed assessment late in a pilot can be fatal where an enterprise would merely reschedule. Learn to read the Green Book Five Case Model so a bid speaks the buyer's language, and target funding routes built for small firms — NHS innovation accelerators, SBRI competitions, framework agreements — rather than waiting on a Spending Review the company cannot influence. Guard against building for one enthusiastic official whose priorities reset at the next reshuffle; anchor to the published national mandate so the product outlives its first sponsor.

Small business#

An established small provider — a GP practice, a community pharmacy, a care home, a domiciliary-care agency, or a single-site clinic — meets government not as a hopeful supplier but as a regulated operator that must satisfy CQC registration, DTAC-aligned procurement, and clinical-safety expectations with no dedicated digital or compliance team to lean on. The same duties that a large trust discharges through a governance department land on a practice manager or an owner already running the service day to day, so the practical task is to find the lightest defensible route to compliance rather than to build bespoke assurance from scratch. Lean on the standards and templates others have already assured — buy from DTAC-passed suppliers and NHS frameworks so the heavy assessment is inherited rather than repeated, and reuse published clinical-safety cases where they apply. Cash is tight and ongoing, so favour revenue-funded tools with predictable running costs over capital-heavy builds, and be realistic that a Spending Review or national programme timeline is something you respond to, not something you can shape. The discipline is to meet the same duties as the big organizations proportionately, using national infrastructure and shared standards to close the resource gap.

Enterprise#

A large NHS trust, ICS, or established supplier has the scale to run the full apparatus — a proper Full Business Case, capital/revenue separation, and assurance engaged in discovery — but also the inertia that lets assurance slip to go-live and force costly rework. Its advantage is a standing relationship with NHS England, the MHRA, and service assessors, so pre-assessment conversations should be routine, not exceptional. It can absorb a paused Spending Review by sequencing standalone increments across financial years, and it has the governance maturity to publish board papers to a Public Accounts Committee standard by default. The risk is bureaucratic self-justification: aligning to the national mandate on paper while freelancing in practice, which the enterprise is large enough to get away with until an audit says otherwise.

Government#

A national or local public body is the machinery itself — it writes the mandate, sets the standards, holds the Green Book, and releases the money through the Spending Review — so its task is less to comply than to make compliance coherent for everyone downstream. It must keep NHS England, DHSC, the devolved systems, NICE, the MHRA, and the CQC aligned rather than contradictory, so a supplier is not assured by one arm and blocked by another. Accountability is at its most exposed here: decisions face the National Audit Office, select committees, Freedom of Information, and the Nolan Principles, so transparency is a statutory posture, not a choice. Its hardest discipline is holding a steady mission across elections and reorganizations while the political language around it changes with every ministerial cycle.

Common failure modes#

• A business case in the wrong shape. A strong idea framed outside the Five Case Model that assessors cannot approve. Fix: write to the Green Book structure and distinguish capital from revenue.
• Assurance discovered at the end. Service assessment, DTAC, or clinical safety findings arrive at go-live and force expensive rework. Fix: engage assurance in discovery as a design input.
• Assuming multi-year revenue that was never secured. A platform built on funding that evaporates at the year-end. Fix: secure revenue explicitly and design standalone increments.
• Ignoring the devolved context. Applying England's bodies and rules to Scotland, Wales, or Northern Ireland. Fix: identify the correct national system for your geography.
• Freelancing past the national mandate. Building something that cuts across national strategy and gets overridden. Fix: align explicitly and cite the mandate and standards.
• Fearing transparency instead of using it. Treating FOI and public papers as threats and communicating defensively. Fix: write to a publishable standard and publish your reasoning.
• Being whipsawed by the political cycle. Rewriting the strategy with every reshuffle. Fix: keep the mission steady, retranslate the language, and protect the team.

Maturity model#

Checklist#

• The owning national body for your mandate, standards, and funding is identified (including the correct devolved system).
• Your work is located in the chain from legislation to planning guidance, and alignment is shown, not just claimed.
• The business case follows HM Treasury's Green Book Five Case Model, with capital and revenue distinguished.
• Recurring revenue is secured explicitly, not assumed across future years.
• Service assessment, DTAC, and clinical safety (DCB0129/DCB0160) are engaged in discovery.
• The NICE evidence tier is agreed up front and the evaluation is designed to meet it.
• Delivery is sequenced into standalone increments that each land within a funded period.
• Policy and ministerial engagement follows the proper channels and transparency rules, with evidence to hand.
• Board papers, spend, and decisions are written to a publishable, FOI-ready standard.
• The plan is resilient to elections and reorganizations; the mission is protected while the language adapts.

Key sources#

• HM Treasury — The Green Book: appraisal and evaluation in central government and the Five Case Model business-case guidance (GOV.UK).
• GOV.UK Service Manual and the Government Service Standard; GDS spend controls (GOV.UK).
• NHS England — NHS Service Standard, planning guidance, and the NHS mandate; digital and interoperability standards.
• NICE — Evidence Standards Framework for Digital Health Technologies.
• DTAC — Digital Technology Assessment Criteria (NHS England).
• NHS Digital / NHS England — Clinical Risk Management standards DCB0129 and DCB0160.
• MHRA — medical devices and Software as a Medical Device guidance; Care Quality Commission registration and inspection.
• Health and Care Act 2022 (legislation.gov.uk); Committee on Standards in Public Life — the Nolan Principles; Freedom of Information Act 2000.

References#

1. NHS England — Wikipedia — https://en.wikipedia.org/wiki/NHS_England
2. Department of Health and Social Care — Wikipedia — https://en.wikipedia.org/wiki/Department_of_Health_and_Social_Care
3. Devolution in the United Kingdom — Wikipedia — https://en.wikipedia.org/wiki/Devolution_in_the_United_Kingdom
4. UK Health Security Agency — Wikipedia — https://en.wikipedia.org/wiki/UK_Health_Security_Agency
5. National Institute for Health and Care Excellence (NICE) — Wikipedia — https://en.wikipedia.org/wiki/National_Institute_for_Health_and_Care_Excellence
6. Evidence Standards Framework for Digital Health Technologies — NICE — https://www.nice.org.uk/about/what-we-do/our-programmes/evidence-standards-framework-for-digital-health-technologies
7. Medicines and Healthcare products Regulatory Agency — Wikipedia — https://en.wikipedia.org/wiki/Medicines_and_Healthcare_products_Regulatory_Agency
8. Medical device — Wikipedia — https://en.wikipedia.org/wiki/Medical_device
9. Care Quality Commission — Wikipedia — https://en.wikipedia.org/wiki/Care_Quality_Commission
10. Health and Care Act 2022 — Wikipedia — https://en.wikipedia.org/wiki/Health_and_Care_Act_2022
11. HM Treasury — Wikipedia — https://en.wikipedia.org/wiki/HM_Treasury
12. The Green Book: appraisal and evaluation in central government — HM Treasury (GOV.UK) — https://www.gov.uk/government/publications/the-green-book-appraisal-and-evaluation-in-central-government
13. Spending Review — Wikipedia — https://en.wikipedia.org/wiki/Spending_Review
14. Government Digital Service — Wikipedia — https://en.wikipedia.org/wiki/Government_Digital_Service
15. Government Service Standard and Service Manual — GOV.UK — https://www.gov.uk/service-manual/service-standard
16. Digital Technology Assessment Criteria (DTAC) — NHS England — https://www.nhsx.nhs.uk/key-tools-and-info/digital-technology-assessment-criteria-dtac/
17. Freedom of Information Act 2000 — Wikipedia — https://en.wikipedia.org/wiki/Freedom_of_Information_Act_2000
18. National Audit Office (United Kingdom) — Wikipedia — https://en.wikipedia.org/wiki/National_Audit_Office_(United_Kingdom)
19. Public Accounts Committee (United Kingdom) — Wikipedia — https://en.wikipedia.org/wiki/Public_Accounts_Committee_(United_Kingdom)
20. Committee on Standards in Public Life (the Nolan Principles) — Wikipedia — https://en.wikipedia.org/wiki/Committee_on_Standards_in_Public_Life