| Literature DB >> 32183787 |
Fiona Lobban1, Duncan Appelbe2, Victoria Appleton3, Julie Billsborough4, Naomi Ruth Fisher3, Sheena Foster4, Bethany Gill3, David Glentworth5, Chris Harrop5, Sonia Johnson6, Steven H Jones3, Tibor Zoltan Kovacs5, Elizabeth Lewis3, Barbara Mezes3, Charlotte Morton6, Elizabeth Murray7, Puffin O'Hanlon6, Vanessa Pinfold4, Jo Rycroft-Malone8, Ronald Siddle5, Jo Smith9, Chris J Sutton10, Pietro Viglienghi5, Andrew Walker3.
Abstract
BACKGROUND: Despite the potential of digital health interventions to improve the delivery of psychoeducation to people with mental health problems and their relatives, and substantial investment in their development, there is little evidence of successful implementation into clinical practice. We report the first implementation study of a digital health intervention: Relatives Education And Coping Toolkit (REACT), into routine mental healthcare. Our main aim was to identify critical factors affecting staff uptake and use of this online self-management tool for relatives of people with psychosis or bipolar.Entities:
Keywords: Caregivers; Case series; Digital health intervention; Early intervention; Implementation science; Internet; Mental health; Psychotic disorders
Mesh:
Year: 2020 PMID: 32183787 PMCID: PMC7077000 DOI: 10.1186/s12913-020-5002-4
Source DB: PubMed Journal: BMC Health Serv Res ISSN: 1472-6963 Impact factor: 2.655
Description of features of IMPART cases relevant to study
| Wave | Case | Description |
|---|---|---|
| Wave 1 | Woods | • Urban area, very high rates of psychosis • High ethnic diversity • Two geographically distinct teams • Reported average caseload per staff of 28 • Very high staff turnover & absence • Low morale: half of one team left in the first 6 months of study |
| Moor | • Large rural area • Population predominantly white British • Early Intervention not separate service, embedded in geographically spread community teams • Lower caseloads (approximately 15, exact figures n/a) but long travel times | |
| Wave 2 | Ocean | • Urban area • Population majority white British • Three geographically distinct teams which performed quite differently • One team had very high staff turnover and high levels of sickness absence, in this team carer support was delegated to one carer lead rather than part of all CC’s work. • Caseloads high (approx. 26) |
| Seashore | • Primarily urban area • High ethnic diversity • Three teams across locality, operating quite differently and independent of each other • Low staff morale and very high turnover, in one team all CCs and team manager left over a period of three months • Trust implementing new DHI for service users at the same time as IMPART study • Caseloads described as ‘high’ but numbers not available due to period of intense change | |
| Wave 3 | Lakes | • Largely rural area • Six teams cover large geographical area, managed in pairs • First IL a senior psychiatrist who left early in project, succeeded by another psychiatrist • Led to variable engagement with IMPART study over time |
| Marsh | • Mainly urban area with rural pockets • Two separately located teams covered by one IL, one RS • Very early in project, RS role given to non-clinical staff member in R&D department |
CC Care Coordinator
IL IMPART Lead
RS REACT Supporter
R&D Research & Development
Roles and levels of access for each type of REACT user account
| Role | Description of role | Access |
|---|---|---|
| IMPART lead | Provide a link between the research team and clinical service. Provide access to key data sources. Create accounts for REACT Supporters and all clinicians | Full access to REACT trust website, with information regarding all signed-up clinicians, REACT supporters and relatives. Could not access forums and direct messages. |
| REACT supporter | Support the relative to use and get the most out of the toolkit. Moderate the REACT Group forum and respond to direct messages from relatives. Update local information on the Resource Directory | Access to all aspects of REACT toolkit including forum and direct messages, and details of relatives who have been invited. |
| Clinician | Invite relative to use REACT- both verbally and by sending them an email invite. | Sign up relatives only; could access toolkit modules. |
| Relative | End users of REACT | Access to REACT toolkit, including forum and direct messages. |
Implementation outcomes over 18 months
| Wave | Wave 1 | Wave 2 | Wave 3 | ||||
|---|---|---|---|---|---|---|---|
| Trust | Woods | Moor | Ocean | Seashore | Lakes | Marsh | Total |
| No. of clinician accounts created | 44 | 37 | 32 | 63 | 64 | 41 | 281 |
| No. of clinicians sending invites (% of clinicians who created account) | 8 (18) | 12 (54) | 4 (12) | 18 (29) | 8 (13) | 7(17) | 57 |
| Median (range) invites sent per clinician | 3 (1,11) | 3 (1,9) | 8 (4,20) | 2.5 (1,25) | 2 (1,15) | 3 (1,45) | 3 (1,45) |
| Total no. of Invites sent | 35 | 47 | 40 | 112 | 29 | 92 | 355 |
| No. of relatives invited (% of caseload) | 29 (6)a | 40 (18)a | 37 (5)a | 93 (24)a | 25 (4)b | 86 (23) c | 310 |
| No. of relatives accounts created (% of caseload) | 7 (1)a | 24 (11)a | 20 (3)a | 38 (9)a | 17 (3)b | 53 (15)c | 159 |
| No. of staff interviewed | 15 | 15 | 42 | 23 | 20 | 14 | 129 |
a Source for caseload is trust self-assessment for CCQI National Early Intervention in Psychosis Audit 2016–17
b Source for caseload is EI Access and NICE Concordance Presentation by EI Clinical Lead
c Source for caseload is EI Provider & Commissioners’ Report 2016
Key factors impacting on implementation of REACT
| NPT components | Key factors impacting on implementation | Illustrative quotes |
|---|---|---|
| Coherence | Generally good understanding of REACT. Staff could identify benefits to relatives and staff including: a) standardised information, | |
| b) available any time, any place, anywhere; | ||
| c) training for staff; | ||
| d) hitting national targets; | ||
| e) reducing staff workloads; | ||
| f) empowering self- management for relatives | ||
| g) good fit with other parts of carer services | ||
| REACT seen as research, rather than part of the clinical service. This generated some short-term behaviour but impeded long-term commitment as seen as inherently time-limited and the responsibility of the R&D team. | ||
| Challenges with delivering face to face training to all staff due to shifts, staff turnover etc. Online training manual not well used. Consequently, some staff not familiar with REACT and didn’t understand their role in offering it. | ||
| Cognitive participation | “Professional ownership” was important in determining who used REACT | |
| Staff feared negative impact on relationships with relatives in case digital support would not be as effective as face-to-face support and relatives may feel “fobbed off”; | ||
| REACT may not be appropriate for everyone – particularly older adults | ||
| REACT content static and sometimes at odds with current practice e.g. REACT provides definitions for the diagnostic terms that relatives may have come across (based on what relatives identified as useful things to include). | ||
| REACT roles allocated, but no choice and not volunteered. | ||
| Negative experiences of IT systems in all trusts, leading to negative attitudes towards IT in general. | ||
| Collective Action | Despite recognising value, REACT was difficult to prioritise. In the context of limited resources, priority was given to activity | |
| a) focussed on service user outcome, | ||
| b) linked to financial incentives | ||
| Changing and competing externally driven priorities made strategic planning for new interventions difficult | ||
| Most teams had high caseloads, low staffing levels and poor morale. | ||
| REACT not sufficiently user friendly or robust for staff | ||
| REACT did not always work on the IT equipment available to staff | ||
| Online was “out of sight, out of mind” for staff | ||
| React Supporters not confident or supported to respond to forum or direct messages online…., | ||
| Reflexive monitoring | Feedback from relatives was very important in motivating staff behaviour. | |
| Lack of feedback from relatives and low activity on forum were demotivating for staff. |
Recommendations for implementing digital health interventions
| Understanding context is key | |
| Clarify exactly how DHI fits into the broader clinical service including care pathways and auditing targets | |
| Understand, acknowledge, and where possible address important wider contextual barriers to uptake and use of DHI | |
| Clarify the organisational structure and identify relevant decision-makers across different levels of the organisation, and understand how decision making around adoption of new practices happens within each organisation | |
| Consider which elements of DHI require local adaptation (e.g. resource directories of other available services), and which require national integration (e.g. online forums) | |
| Design DHI to be compatible with the range of hardware and software currently used across the healthcare teams | |
| Identify other organisational changes that are occurring simultaneously and consider how these may affect implementation of DHI. Simultaneous implementation of other DHIs may be particularly challenging for staff | |
| Maximise initial buy-in and continued use | |
| Clearly identify originators/developers of DHI, and seek endorsement from credible parent organisations, and end users | |
| Ensure DHI is clearly identified as a clinical initiative and not identified as primarily research | |
| Explicitly identify and label DHI with the key value(s) for each stakeholder group in the organisation | |
| All relevant user groups (including staff) should have full access to the DHI, pilot the DHI, consider the pros and cons, and be part of the service decision to adopt | |
| All staff fears and concerns about DHI should be identified and addressed in organisational written policy and staff training prior to adoption | |
| Promote DHI as part of a multichannel service to avoid “out of sight out of mind” | |
| Ensure ongoing training and support for all staff | |
| Consider appointing one or more champions to coordinate organisational activity and be a point of contact for DHI providers | |
| Train staff in all relevant skills including generic IT skills, using multi-channel, flexible training that can accommodate constant turnover of staff. | |
| Provide relevant feedback and manage expectations | |
| Audit reports around DHI use need to be easily available to stakeholders in user friendly form, with clear mechanism established for addressing feedback involving DHI providers | |
| Specific short and long term targets should be set regarding uptake and use of DHI to manage staff expectations and evaluate progress |