Public Service ITSM Reference

Frameworks

Key practices for public services

The ITIL practices that matter most in government and health, with what to watch for in each.

ITIL 4 describes 34 practices. These eleven do most of the work in a public body. For each, here is the core idea and what is different in government and health.

Incident management

Restore normal service as quickly as possible and keep people informed.

Some incidents are also regulatory events: a personal data breach (72 hours to the ICO), a NIS incident at an operator of essential services, or a clinical safety incident. Build those checks into triage and major incident handling. See major incidents and reporting clocks.

Problem management

Find and remove the causes of incidents, and manage known errors.

Recurring failures in clinical or citizen-facing systems are often patient-safety or fairness risks too. Link problem records to the risk register and, for health systems, to the clinical hazard log.

Change enablement

Maximise successful changes by assessing risk, authorising changes and managing the change schedule.

In health, changes to clinical systems need clinical risk assessment under DCB0160 in England and similar practice elsewhere. Use standard (pre-approved) changes for low-risk work and keep your change authority small and fast. See change enablement with clinical safety.

Service request management

Handle pre-defined, user-initiated requests such as access, equipment and information.

Access requests are security controls. Record who approved access to systems holding personal or classified data, and review it regularly (leavers and role changes especially).

Service level management

Set clear, business-based targets and check delivery against them.

Agree targets with commissioners and users, not just IT. Under the Procurement Act 2023, larger contracts must have published key performance indicators: align service levels with them.

Information security management

Protect the information an organisation needs to conduct its business.

This is where the DSPT, the NCSC Cyber Assessment Framework, GovAssure and ISO/IEC 27001 meet ITSM. Keep one set of controls and map it to each scheme. See how the frameworks fit together.

Supplier management

Make sure suppliers and their performance are managed to support seamless services.

Most public IT is multi-supplier. Contracts are set under public procurement rules, so changing them is harder than in the private sector: get service management, security and exit requirements into the contract at the start. See supplier management.

Relationship management

Establish and nurture links with stakeholders at strategic and tactical levels.

Stakeholders include boards, clinical leads, commissioners, other public bodies, unions and the public. Plan how each is kept informed, especially during major incidents.

Knowledge management

Maintain and improve the effective, efficient and convenient use of information and knowledge.

Knowledge articles and self-service portals are covered by the accessibility regulations. In Wales, they may need to be bilingual. See knowledge and self-service.

Service continuity management

Make sure service availability and performance stay at a sufficient level after a disaster.

For systems patients or vulnerable people depend on, plan for manual workarounds and data reconciliation, not only technical recovery. See continuity and recovery.

IT asset management

Plan and manage the full lifecycle of IT assets.

Asset records underpin security (you can't patch what you don't know about), records management, freedom of information searches and secure disposal of data-bearing equipment.