The definition of a term is a statement expressing the essential nature of something that enables a common understanding of key terms within an improvement team.
Contents
Introduction
Definitions are important in exploring common understanding within improvement teams. They play a key role in ensuring people understand the same thing about key terms or issues. However, their role is not to standardise or set a common language, rather to enable communication through better understanding or translation.
For example, design is a word that often invokes passion and misunderstanding amongst its users. Is it a verb or a noun? Does it refer to the artefact or the process? There is no right or wrong answer here, rather it is important that the originator and recipient of a message hold a common understanding of what is said. This will require knowledge of the background and context of each individual by the other and ideally the ability to translate the meaning of the word simultaneously or, if necessary, to agree a common use. The former model of communication is always preferable as it is likely to be accompanied by a greater empathy between individuals, but the later may be essential to avoid ambiguity.
This section provides definitions for a number of terms relevant to improvement, ordered by their likely use with in the improvement process. They are here for reference and not intended to define a common language. Indeed, alternative and related terms are provided, along with some indication as to how they might be related or used together. Nonetheless, some care has been taken to try to ensure that when these terms are used within the toolkit, it is the meaning defined here that has been adopted.
Definitions may be mapped to definitions to assist in understanding their adjacency, distinction and overlap. More than one term may be used for any particular purpose and this is often encouraged when there is good reason for doing so. The mapping provides indication as to how definitions might be linked, but is not expected to exhaustively show where these terms are related in practice.
Categorised List of Definitions
Problem
Evidence
Case
Plan
Alphabetical List of Definitions
Context
Stakeholder
stakeholder — a person with an interest or concern in something
A stakeholder is a person with an interest in the project because they have something to gain or lose
Use:
- Stakeholders may be service providers or users
- Identify as many stakeholders and their needs as possible
- Carefully prioritise the needs of all the stakeholders
see also user
User
user — a person who uses or operates something
The patient is the core user of a system, but other stakeholders are also users in the delivery of services
Use:
- Users are a special category of system stakeholders
- Identify as many users and their particular needs as possible
- Carefully balance the needs of the users and other stakeholders
see also stakeholder
Trigger
trigger — the thing that caused someone to do something
The trigger is the reason why there is an improvement programme and defines the initial scope of the programme
Use:
- The trigger describes the event or action that initiated change
- Triggers may be in response to adverse events or near misses
- Triggers may be preemptive to improve a system or avoid error
see also context and scope
Context
context — the circumstances that surround something
The context includes all aspects that affect the problem and the implementation of a solution
Use:
- The context describes all factors that may influence change
- May be used to describe enablers for improvement
- May be used to capture barriers to improvement
see also trigger and scope
Scope
scope — the extent of the area that something deals with
The scope is the boundary between aspects considered as part of the problem and others that affect the problem
Use:
- A consensus view of the scope is vitally important
- Should bound the area of interest for subsequent improvement
- Often used in conjunction with system and aim
see also trigger, context, system and aim
System
system — a set of things working together to do something
A system is a set of elements that, when combined, have qualities that are not present in the elements themselves
Use:
- A system may comprise people, rules and other things
- A system may be part of or made up of other systems
- Often used in conjunction with scope and aim
see also scope and aim
Aim
aim — the intention or ambition or achieving something
The project aim represents a clear statement of intent that helps everyone align with the project objectives
Use:
- A consensus view of the aim is very helpful
- Should provide broad focus for all subsequent development
- Often used in conjunction with scope and purpose
see also scope, system, purpose and need
Purpose
purpose — the thing that something is supposed to achieve
The purpose defines the things that the particular health and care system is supposed to deliver and achieve
Use:
- A consensus view of the purpose is important
- Should provide focus for identifying potential improvements
- Often used in conjunction with aim and theme
see also aim and theme
Need
need — a strong feeling that you must have something
A need is an essential condition that a particular stakeholder believes has to be satisfied from their perspective
Use:
- Needs may relate to fundamental issues and specific desires
- All stakeholders in a system are likely to have specific needs
- Often used in conjunction with aim, purpose and theme
see also aim, purpose and theme
Theme
theme — the core idea that is apparent in something
The themes are high-level targets for improvement and capture the essence of the things the improved system must do
Use:
- A consensus view of the theme(s) is particularly important
- Should provide particular focus for all subsequent development
- Often used in conjunction with need and requirement
see also need and requirement
Problem
Requirement
requirement — a description of something you must have
A condition that has to be satisfied for the improvement to be successful, derived from an agreed set of themes
Use:
- Requirements relate to a balanced set of stakeholders’ needs
- Requirements should be reflected in subsequent evaluation
- Often used in conjunction with need and specification
see also theme and specification
Specification
specification — a detailed description of how something should be
A specification is a structured set of requirements providing a holistic view of the need for improvement
Use:
- A specification describes an agreed collection of requirements
- The specification should be reflected in subsequent verification
- Often used in conjunction with need and requirement
see also requirement
Challenge
challenge — a difficult or demanding task or situation
The challenge represents what is known or perceived to be wrong with the current system
Use:
- A consensus view of the challenge is particularly important
- Often used synonymously with the description of a problem
- Focus on a challenge may encourage a more enthusiastic response
see also problem
Problem
problem — a detailed description of a particular challenge
The problem statement represents the consensus view on the challenge that is going to be solved
Use:
- A consensus view of the problem is particularly important
- Often used synonymously with the description of a challenge
- Focus on a problem may encourage a more muted response
see also challenge
Journey
journey — an act of travelling from one place to another
A patient journey captures the things that happen to an individual as they interact with health and care services
Use:
- A description from the point of view of the person making the journey
- The journey may be described for a typical person or an individual
- Multiple journeys may be used to describe a single intervention
see also pathway
Pathway
pathway — a course of action to achieve a specified result
The clinical pathway is a description of the things that are expected to happen in provision of a health or care service
Use:
- A description from the point of view of the person defining the pathway
- The pathway may be defined for a typical person or an individual
- Multiple pathways may be used to describe a single intervention
see also journey
Persona
persona — a caricature designed to display certain attributes
A persona is a description of a person with a blend of real attributes, to assist the design of an improved system
Use:
- Personas represent notable attributes of system stakeholders
- Personas typically describe caricatures of system users
- Personas are often used in conjunction with scenarios
see also scenario
Scenario
scenario — a typical sequence or development of events
A scenario describes an instance of a particular system as a starting point for discussing targets for improvement
Use:
- Scenarios represent notable sequences of events
- Scenarios typically describe journeys of system users
- Scenarios are often used in conjunction with personas
see also persona
Solution
Idea
idea — a suggestion or plan for doing something
A suggestion for how an aspect of the system could be improved which has not yet been worked into a viable concept
Use:
- A suggestion or plan that may form part of a concept
- A good idea is likely to be realisable and meet the requirements
- Often used in conjunction with the description of a concept
see also concept and model
Concept
concept — an idea that is connected with something
A concept is a description of something that does not yet exist, but has the potential to improve the service
Use:
- An idea or combination of ideas that may solve a problem
- A viable concept is very likely to meet the requirements
- Often used in conjunction with the description of an idea or solution
see also idea, model and solution
Model
model — a simplified representation of something
A model is a simplified physical or virtual embodiment of a concept which communicates particular aspects of it
Use:
- A simple model is often adequate early in the programme
- Models may used to describe form and/of function
- Multiple models may be better than a single integrated model
see also idea, concept and solution
Solution
solution — a way of solving a particular problem
A solution is chosen from one of the many concepts considered when exploring ways to solve the problem
Use:
- A combination of elements which together solve a problem
- A viable solution demonstrably meets the requirements
- Often used in conjunction with the description of a concept
see also concept and model
Evidence
Quality
quality — the degree of excellence possessed by a thing
The quality targets are specific objectives for clinical and cost effectiveness, patient safety and patient experience
Use:
- Quality is not solely a focus on clinical and cost effectiveness
- Quality should be identifiable, measurable and targeted
- Quality should be continuously monitored
see also target
Target
target — the identity of something to be aimed at
A target is an objective for a given phase of the improvement process related to service or programme performance
Use:
- Targets should be realistically attainable and measurable
- Targets should reflect desirable levels of quality
- Targets may vary through the improvement process
see also quality
Evaluation
evaluation — showing a solution satisfies its requirements
The evaluation of the elements of a system tests whether they are likely to achieve their intended performance
Use:
- Evaluation checks performance against individual requirements
- Approaches to evaluation should reflect the requirements
- Often used in conjunction with verification and validation
see also verification and validation
Verification
verification — showing a solution meets its requirements
The verification of a system tests whether it achieves its intended performance under specified conditions
Use:
- Verification checks performance against the requirements
- Approaches to verification should reflect the requirements
- Often used in conjunction with evaluation and validation
see also evaluation and validation
Validation
validation — showing a solution is fit for its intended purpose
The validation of a system checks whether it works with real users and other stakeholders in real contexts
Use:
- Validation begins with checking requirements against the needs
- Approaches to validation should reflect prioritised needs
- Often used in conjunction with evaluation and verification
see also evaluation and verification
Case
Rationale
rationale — the reasons or a logical basis for something
The rational for an improvement concept reasons why it has the form and function that it has
Use:
- Rationale relates to the reasoning behind key decisions
- Typically expressed with relation to the change facilitator
- Often used in conjunction with definition of the case
see also case
Case
case — a set of arguments to support doing something
The case for improving a system balances the benefits against the costs of delivering the improvement
Use:
- A clear case is essential to gather the necessary support for a plan
- The case should clearly define expected outcomes and costs
- The case should be sufficient, accurate and realistic
see also rationale
Plan
Process
process — a series of actions to achieve something
An improvement process comprises activities which are chosen in response to targets to design an improved system
Use:
- A consensus view of the process is particularly important
- The process should clearly define expected actions and outcomes
- The process outcomes should be achievable using available resource
see also plan and resource
Plan
plan — a detailed proposal for doing something
An improvement plan provides a description of the activities and resources required to deliver an improvement
Use:
- A consensus view of the plan is particularly important
- The plan should clearly define expected actions and timing
- The plan should be achievable using available resource
see also process and resource
Resource
resource — the thing that enables something to happen
The resource required to deliver improvement is likely to include people, things, tools and funding
Use:
- Resource relates to the people and things that enable change
- Typically expressed within the context of the change
- Often used in conjunction with definition of the plan
see also process and plan
Feedback
We would welcome your feedback on this page:
Privacy policy. If your feedback comments warrant follow-up communication, we will send you an email using the details you have provided. Feedback comments are anonymized and then stored on our file server
Read more about how we use your personal data. Any e-mails that are sent or received are stored on our mail server for up to 24 months.