HealthITPrep
CPHIMS guide Concepts Features Pricing FAQ
Sign in Start free
العربية

ITIL: incident vs problem vs change

By Adel Moustafa, CPHIMS® · Updated 22 October 2026

Three words the exam uses with exact meanings: what each one is, which process owns it, and how they follow each other when a hospital system fails.

In short: an incident is an unplanned interruption or loss of quality in a service, and incident management restores the service as fast as possible, often with a workaround. A problem is the cause, or possible cause, of one or more incidents, and problem management finds it and removes it. A change adds, modifies or removes anything that could affect a service, and change enablement makes sure every change, the fix included, is assessed and authorised before it goes in.
ITIL Incident Problem Change Service request One example Side by side Common mistakes Summary Sources

What is ITIL?

ITIL is the most widely used framework of good practice for IT service management: how an IT department plans, delivers and supports the services people rely on. ITIL 4 (2019), the edition most study material is based on, describes 34 practices. The exam asks above all about the ones that keep clinical systems running, and expects the precise meaning of each word.

What is an incident, and what does incident management do?

ITIL 4 defines an incident as an unplanned interruption to a service, or a reduction in the quality of a service. The EHR is down, the lab interface stops sending results, printing on a ward takes five minutes instead of five seconds.

  • The goal: restore normal service as quickly as possible and limit the harm. Not to find out why.
  • How: log the incident, set its priority by impact and urgency, use a known workaround if there is one (restart the service, switch to the backup printer, go to downtime procedures), escalate when needed, and close it once users confirm service is back.
  • Who: usually starts at the service desk, with technical teams behind it.

What is a problem, and what does problem management do?

A problem is a cause, or potential cause, of one or more incidents. Restarting the server three times this week fixed three incidents; the reason it keeps freezing is the problem.

  • The goal: reduce how often incidents happen and how much harm they do, by finding and removing their causes.
  • Problem identification: spotting problems, often from repeated or similar incidents, or before any incident from trend analysis and vendor warnings.
  • Problem control: analysing the root cause and documenting workarounds. A problem whose cause has been analysed but not yet removed is a known error.
  • Error control: deciding how to fix the known error for good; the permanent fix usually needs a change.

Problem management is slower and more analytical than incident management, and it needs data: an incident log where incidents are linked to each other is what reveals that a problem exists.

What is a change, and what does change enablement do?

A change is the addition, modification or removal of anything that could have a direct or indirect effect on services: a software update, a new interface, a server configuration, a firewall rule. ITIL 4 calls the practice change enablement; earlier editions called it change management, the name many questions still use. The change is the modification itself; change enablement is the practice that assesses, authorises and schedules it.

  • The goal: as many successful changes as possible, by assessing their risks, authorising them and managing the schedule.
  • Standard change: low risk, well understood and pre-authorised, such as adding memory to a server by a tested procedure.
  • Normal change: assessed and authorised by the right change authority before it is scheduled; for large changes this can be a change advisory board (CAB).
  • Emergency change: needed as soon as possible, often to resolve an incident; assessed and authorised quickly, but still recorded and reviewed.

Is a service request an incident?

No. A service request is a user asking for something that is a normal part of the service: resetting a password, a new account for a new nurse, access to a report, a new mouse. Nothing is broken, so it follows its own practice, service request management, usually through pre-defined steps. Logging every password reset as an incident distorts the incident figures and hides real problems.

How do they follow each other in one example?

  1. Incident: on Monday morning the EHR sign-in screen freezes for many users. The service desk restarts the application server and service returns in 20 minutes. Incident closed.
  2. More incidents: the same happens on Wednesday and on Friday, and is handled the same way.
  3. Problem: the repeats point to a common cause. Problem management opens a problem record, and the analysis finds a memory leak in a sign-in component after a recent update. The problem is now a known error: its cause is known but not yet removed, and the restart is recorded as its workaround.
  4. Change: the vendor releases a patch. Installing it on the live system is a normal change here, because of its risk: assessed, tested, authorised and scheduled for a quiet hour. A pre-authorised standard change or an emergency change would follow the path of its own type.
  5. Back to problem management: after the change, no new incidents. The problem is closed.

Incident, problem and change side by side

IncidentProblemChange
What it isAn interruption or loss of quality in a serviceThe cause, or potential cause, of one or more incidentsAdding, modifying or removing something that can affect a service
The question it answersHow do we get service back now?Why does this keep happening, and how do we stop it?How do we make this change safely?
Measured byTime to restore serviceFewer repeat incidentsChanges that succeed without causing incidents
Typical outputService restored, often by a workaroundRoot cause, known error, permanent fix proposedA fix put in place with its risk assessed

What do candidates get wrong?

  • Choosing incident management to find the root cause. Incident management restores service; the cause belongs to problem management.
  • Waiting for the root cause before restoring service. In a hospital, clinicians need the system now; restore first, then investigate.
  • Applying the permanent fix straight to the live system. The fix is a change, and it goes through change enablement by the path its type calls for (standard, normal or emergency), even when it is urgent.
  • Confusing ITIL change with organisational change management. Helping people accept a new way of working (Kotter's eight steps, Lewin's unfreeze, change, refreeze) is a leadership subject; ITIL change enablement controls changes to IT services.
  • Calling a password reset an incident. It is a service request.

Summary for revision

  • Incident: an interruption or loss of quality in a service; restore it fast, often with a workaround.
  • Problem: the cause, or potential cause, of one or more incidents; find the root cause and remove it.
  • Known error: a problem whose cause has been analysed but not yet removed.
  • Change: any addition, modification or removal that could affect a service; change enablement assesses and authorises it according to its type (standard, normal or emergency).
  • Service request: an ordinary request such as a password reset, not an incident.

Sources

  • ITIL 4 Foundation (AXELOS, 2019; ITIL is now owned by PeopleCert): the definitions of incident, problem, known error and change, and the practices of incident management, problem management, change enablement and service request management.

Related free practice questions

  • Incident management versus problem management in ITIL
  • Kotter’s model for leading change

The site files this concept under the domain Management and Leadership.

Try exam-style questions

A 20-question trial exam with an explanation for every option and a score per domain, drawn from 40 free questions. No payment method needed.

Start the trial exam

Questions about the exam: CPHIMS guide · What is CPHIMS? · Exam cost · Eligibility · Passing score · Renewal · Exam day · How long to study · Is it worth it? · What is CAHIMS?

Concepts explained: HL7 v2 vs FHIR · Capitation vs fee-for-service · Safe Harbor vs Expert Determination · Backup types, RTO and RPO · Privacy Rule vs Security Rule · CDS five rights · Lewin vs Kotter · SDLC and go-live strategies · Testing types · Earned value (SPI, CPI) · Structure, process, outcome · HIE models · Six Sigma vs Lean · Levels of interoperability · Bandwidth vs latency · EMTALA · Risk responses · RACI matrix · Build vs buy · Sunk vs opportunity cost · Data governance

The four domains: Healthcare and Technology Environments · Clinical Informatics · Healthcare Information and Systems Management · Management and Leadership

Written by Adel Moustafa, About us

Written and checked against the sources above on 22 October 2026. An independent site, not affiliated with or endorsed by HIMSS. CPHIMS® is a registered trademark of HIMSS.

CPHIMS guide Compare certifications Free practice questions Concepts explained About us Terms of Use Privacy Policy Refund Policy Contact us

© 2026 HealthITPrep. This site is not affiliated with or endorsed by HIMSS. CPHIMS is a registered trademark of HIMSS.