The study sample included 52 QI projects across five boroughs of London, UK served by the NHS provider organisation (Table 1). Thirty projects were conceived by community mental health teams and the remaining (n=22) by inpatient care teams. Of the three themes of Quality Priorities,[13: patient safety, clinical effectiveness, and patient experience] improving clinical effectiveness was the most common focus in project aims (29 / 52). A small handful focused on multiple priorities at once (6 community mental health and 7 inpatient care projects).
Table 1. Study sample of 52 quality improvement projects in South London and Maudsley NHS Foundation Trust (2016 – 2018)
|
Community Mental Health
n = 24 (6)*
|
Inpatient
n = 15 (7)*
|
Borough
|
|
|
Croydon
|
8
|
10
|
Lambeth
|
7
|
4
|
Lewisham
|
7
|
4
|
Southwark
|
7
|
3
|
Wandsworth
|
1
|
1
|
Patient Safety
|
|
|
Reduce use of restrictive interventions on service users
|
1 (2)
|
0 (3)
|
Safer staffing
|
0
|
1 (1)
|
Risk assessments
|
1 (1)
|
1 (1)
|
Clinical Effectiveness
|
|
|
Physical healthcare screening
|
4 (1)
|
4 (3)
|
Care planning
|
10 (5)
|
6 (3)
|
Developing electronic systems to improve care delivery
|
3 (1)
|
2 (1)
|
Patient Experience
|
|
|
Reducing number of acute out-of-area treatments
|
3 (2)
|
0 (2)
|
Carer’s assessment and associated care plan
|
1 (3)
|
0 (1)
|
Quality of environment and food
|
1 (1)
|
1 (2)
|
* numbers in parentheses refers to number of projects that included multiple Quality Priorities in project aims
Project outcomes
In terms of project outcomes (Table 2), 18 of 52 projects (35%) reported a change in routine practice (adoption). However, only 10 of them reported formal project closure with aims achieved. Out of 7 of 52 projects (13%) that triggered similar projects in other sites (spread), only 3 reported formal project closure with aims achieved. A plausible explanation for these findings could be that some projects were organisation-wide initiatives that were adopted or spread across service sites regardless of the project outcome at specific sites. In light of this divergence between “work-as-imagined” and “work-as-done”,[10] we decided to retain a more stringent definition by labelling projects as successful (n=10) only if they led to adoption after achieving their aims at formal closure. This offered a more interpretable benchmark for making comparisons with the remaining 42 projects.
Table 2. Project outcomes
|
|
Adopted
(n = 18)
|
Spread
(n = 7)
|
Formal closure (n = 23)
|
Aims achieved (n = 12)
|
10
|
3
|
|
Aims not achieved (n = 11)
|
3
|
2
|
|
|
|
|
Terminated (n = 29)
|
Aims achieved (n = 4)
|
4
|
1
|
|
Aims not achieved (n = 25)
|
1
|
1
|
+ Project Status: Closed, Terminated at xP (Plan), xD (Do), xS (Study), xA (Act)
Adopted = Change idea adopted, Spread = Triggered similar projects
Costs and benefits
Among the 10 successful projects, half required six or more months (median = 6.0) for completion. Those that were not successful after formal closure (n = 13) showed large variation. Half were completed in under three months (median = 2.8) but some took up to 12 months (Figure 1). Among projects that did not reach formal closure, those that terminated at the Planning stage of PDSA (n = 18, median = 1.8 months) showed a shorter life span than those that terminated in more advanced stages (n = 11, median = 6.0 months). Meetings with the resident QI team staff took place typically on a monthly basis for successful projects (median = 1.1 meetings monthly), a slightly higher rate than for all others (median = 0.6 – 0.9 meetings monthly). Monthly correspondence between project and resident QI team staff (email/phone) shows a similar picture, with slightly higher activity levels in successful projects (median = 7.5 vs 3.8 – 4.8 monthly email/phone).
Retrospective estimates were requested for the number of service users and staff who directly benefitted from the undertaken QI projects. This proved problematic as indications were available for only a handful of projects (8 / 10 successful projects vs 11 / 42 for all others). Similarly, when inquired about whether it was possible to quantify improvement in terms of cost savings, more than half of the projects reported “not known”.
Among the 10 successful projects, seven disseminated publications of their findings (2 locally, 4 beyond local site/service, 1 not known). Among the remaining 42, five did so (2 locally, 2 beyond local site/service, 1 not known). For most projects, survey responses indicated “not known” in both respects. Two of the successful project teams went on to develop two new projects, whereas six in the latter group developed 10 new projects.
Contextual factors
We examined a range of factors that might be associated with QI project outcomes (Table 3). Seven (out of 30) QI projects in community mental health settings led to a change in routine practice. These odds were halved (Odds ratio, OR = 0.5, 95% CI: 0.1 – 2.3) for projects in inpatient care settings where three (out of 22) led to adoption, but the differences in odds did not attain statistical significance. The odds of adoption were twice higher for QI projects that required funding (OR = 2.1, 95% CI: 0.4 – 10.4), but statistical significance was not attained as well. Among the five projects for which funding was actually available, none achieved adoption (consequently, we could not calculate an OR for comparing odds). The odds of adoption were five times lower (OR = 0.2, 95% CI: >0.1 – 0.9) if it was the team’s first attempt at carrying out a QI project. These odds were five times higher if protected time for QI activities was officially sanctioned for the project (OR = 5.2, 95% CI: 1.2 – 23.4).
Table 3. Logistic regression models for association between project outcome of adoption (dependent variable) and contextual, input, and process factors (independent variables).
|
n1
|
n2
|
Odds Ratio
|
95% CI
|
|
|
|
|
|
Contextual factors
|
|
|
|
|
|
|
|
|
|
Inpatient
|
22
|
3
|
0.5
|
0.1 – 2.3
|
First QI project +
|
27
|
2
|
0.2
|
>0.1 – 0.9
|
Time officially sanctioned +
|
20
|
7
|
5.2
|
1.2 – 23.4
|
Funding available
|
5
|
0
|
#
|
#
|
Funding required
|
10
|
3
|
2.1
|
0.4 – 10.4
|
|
|
|
|
|
Input factors
|
|
|
|
|
|
|
|
|
|
Made budget plan
|
5
|
1
|
1.1
|
0.1 – 10.6
|
Project lead: non-clinical staff
|
8
|
1
|
0.6
|
0.1 – 5.1
|
Project lead: non-managerial staff
|
18
|
3
|
0.8
|
0.2 – 3.4
|
Team size
|
-
|
-
|
1.4
|
0.7 – 2.7
|
Staff turnover
|
22
|
4
|
0.9
|
0.2 – 3.6
|
|
|
|
|
|
Process factors
|
|
|
|
|
|
|
|
|
|
Engaged team leader
|
28
|
6
|
1.4
|
0.3 – 5.5
|
Engaged stakeholders
|
14
|
5
|
3.7
|
0.9 – 15.5
|
Engaged service users ++
|
10
|
5
|
7.4
|
1.6 – 34.9
|
|
|
|
|
|
No. of outcome measures +
|
-
|
-
|
3.2
|
1.1 – 9.8
|
No. of primary drivers +
|
-
|
-
|
2.7
|
1.3 – 5.9
|
No. of secondary drivers +
|
-
|
-
|
1.5
|
1.1 – 1.9
|
|
|
|
|
|
Aims quantified
|
35
|
10
|
#
|
#
|
Primary drivers tagged with measures ++
|
13
|
6
|
7.5
|
1.7 – 33.7
|
Secondary drivers tagged with measures +
|
11
|
5
|
6.0
|
1.3 – 27.2
|
Balancing measures ++
|
10
|
5
|
7.4
|
1.6 – 34.9
|
|
|
|
|
|
No. of PDSA completed +
|
-
|
-
|
1.5
|
1.1 – 2.2
|
PDSA that completed >1 cycle ++
|
13
|
6
|
7.5
|
1.7 – 33.7
|
PDSA with documentation ++
|
13
|
9
|
85.5
|
8.5 – 860.2
|
|
|
|
|
|
Data collected before implementing change idea ++
|
9
|
5
|
9.5
|
1.9 – 47.6
|
Median value of random variation in outcome measures +
|
12
|
5
|
5.0
|
1.1 – 22.0
|
Median value of random variation in process measures
|
4
|
4
|
#
|
#
|
Median value of random variation in balancing measures
|
2
|
2
|
#
|
#
|
Data collected after implementing change idea ++
|
13
|
6
|
7.5
|
1.7 – 33.7
|
n1: total number of projects that satisfy the condition described by the independent variable
n2: total number of projects (in n1) that led to a change in routine practice (adoption).
# independent variables for which odds of project outcome could not be calculated
+ independent variables that show statistically significant odds ratio
++ independent variables for which conservative estimates (lower bound of 95%CI) show at least a moderate effect size (OR > 1.5, or in opposite direction: OR < 0.7)
Input factors
The odds of adoption increased slightly (OR = 1.4, 95% CI: 0.7 – 2.7) with team size but decreased if the project was led by non-clinical staff (OR = 0.6, 95% CI: 0.1 – 5.1) or non-managerial staff (OR = 0.8, 95% CI: 0.2 – 3.4). They were similar between QI projects that did or did not make a budget plan (OR = 1.1, 95% CI: 0.1 – 10.6). Staff turnover appeared slightly detrimental to the odds of adoption (OR = 0.9, 95% CI: 0.2 – 3.6). However, none of these differences in input factors attained statistical significance.
Process factors
The odds of adoption were higher if the project team engaged their team leader, stakeholders (e.g., staff members not in project team), and service users. Only service user engagement showed a statistically reliable impact, with a large effect size (OR = 7.4, 95% CI: 1.6 – 34.9).
The odds of adoption increased moderately with the number of outcome measures attached to the aim statement of the driver diagram produced by the project team (OR = 3.7, 95% CI: 1.1 – 9.8). This was also the case for the number of primary (OR = 2.7, 95% CI: 1.3 – 5.9) and secondary drivers (OR = 1.5, 95% CI: 1.1 – 1.9) in these diagrams.
Among 35 projects that quantified their target outcomes in the aims statement, 10 led to adoption. In the remaining 17 that did not quantify their target outcomes in the aims statement, none achieved adoption (consequently, we could not calculate an OR for comparing odds). The odds of adoption were much higher if measures were tagged to the primary and secondary drivers (OR = 7.5, 95% CI: 1.7 – 33.7 and OR = 6.0, 95% CI: 1.3 – 27.2 respectively). Projects that included balancing measures also had much higher odds of adoption (OR = 7.4, 95% CI: 1.6 – 34.9).
The odds of adoption increased slightly with the number of PDSAs carried out (OR = 1.5, 95% CI: 1.1 – 2.2). However, when the comparisons focused simply on whether projects did or did not report PDSA with more than one cycle, the odds were much higher (OR = 7.5, 95% CI: 1.7 – 33.7) if they did. The odds were even higher for projects that had PDSA documentation (OR = 85.5, 95% CI: 8.5 – 860.2). Despite the wide confidence interval, the lower bound interval estimate suggests that this latter aspect of PDSA had a major impact on project outcome.
Projects that collected data before implementing change ideas showed much higher odds of adoption (OR = 9.5, 95% CI: 1.9 – 47.6). This also applies to projects that established the median value of random variation in outcome measures (OR = 5.0, 95% CI: 1.1 – 22.0). We could not calculate OR for comparing odds for projects that established the median value of random variation in process and balancing measures because all that did so achieved adoption. Projects that collected data after implementing a change idea also show much higher odds of adoption (OR = 7.5, 95% CI: 1.7 – 33.7).