An organisational analysis of the implementation of telecare and telehealth: the whole systems demonstrator

<p>Abstract</p> <p>Background</p> <p>To investigate organisational factors influencing the implementation challenges of redesigning services for people with long term conditions in three locations in England, using remote care (telehealth and telecare).</p> <p>Methods</p> <p>Case-studies of three sites forming the UK Department of Health’s Whole Systems Demonstrator (WSD) Programme. Qualitative research techniques were used to obtain data from various sources, including semi-structured interviews, observation of meetings over the course programme and prior to its launch, and document review. Participants were managers and practitioners involved in the implementation of remote care services.</p> <p>Results</p> <p>The implementation of remote care was nested within a large pragmatic cluster randomised controlled trial (RCT), which formed a core element of the WSD programme. To produce robust benefits evidence, many aspect of the trial design could not be easily adapted to local circumstances. While remote care was successfully rolled-out, wider implementation lessons and levels of organisational learning across the sites were hindered by the requirements of the RCT.</p> <p>Conclusions</p> <p>The implementation of a complex innovation such as remote care requires it to organically evolve, be responsive and adaptable to the local health and social care system, driven by support from front-line staff and management. This need for evolution was not always aligned with the imperative to gather robust benefits evidence. This tension needs to be resolved if government ambitions for the evidence-based scaling-up of remote care are to be realised.</p>

Abstract licence: CC BY-NC-ND

• Electronic Consultation in Primary Care Between Providers and Patients: Systematic Review · 2019

• Personalized Telehealth in the Future: A Global Research Agenda · 2016

A person counts once a day per paper. We keep no cookie and no address: a reader is a hash that changes every day. Any month under five reads shows no number.