MedElevator Войти в исследования
← Поиск публикаций

DOI 10.1016/j.fhj.2026.100550

Медицинская библиотека · Future healthcare journal · 2026

Creating a service system architecture for people living with multiple long-term conditions.

McKay Alison, Lara Francisco Tapia, Boughan Sharanjit, Broch Jason, Edeson David, Henderson Max, Huerta Omar, Irvine Richard, Kingsbury Sarah R, McFarlane Lindsay, Rebane Amy, Trowsdale Dan B, Conaghan Philip G

СтатьяПеревод в очереди

Аннотация

PURPOSE: To identify barriers and improvement opportunities for the effective management of care for people with multiple long-term conditions (MLTCs) and propose a service system architecture to ensure an integrated approach to achieving improved outcomes.

METHODS

A systems engineering process was used to derive stakeholder needs from multimorbidity case studies. An abductive analysis provided principles for system design. Hackathons using LEGO® SeriousPlay® helped co-create a service system architecture with patients and service providers.

RESULTS

Stakeholder needs captured through three metaphors (spaghetti, barriers, elephants in rooms) reflected concerns with current solutions; six principles for designing MLTC care services addressing service user and provider needs, mental health considerations, costs and system integration; and a service system architecture blueprint for MLTC care pathways.

CONCLUSIONS

The novel system architecture increases equality and equity and provides a framework for holistic MLTC care spanning multiple clinical specialties and disciplines.

Для цитирования: McKay Alison, Lara Francisco Tapia, Boughan Sharanjit, Broch Jason, Edeson David, Henderson Max, Huerta Omar, Irvine Richard, Kingsbury Sarah R, McFarlane Lindsay, Rebane Amy, Trowsdale Dan B, Conaghan Philip G. Creating a service system architecture for people living with multiple long-term conditions.. Future healthcare journal. 2026. DOI: 10.1016/j.fhj.2026.100550.
Подготовка и перевод публикации
Обработка статьи · этапы, ошибки и управление
Загрузка состояния…

История · было → стало

Состояние обновляется каждые 5 секунд, пока блок открыт. Процент показывается только там, где известен объём работы. Пауза останавливает продолжение этапа; текущий запрос к источнику может завершиться.

Тип публикации указан по данным источника. Уровень доказательности автоматически не присваивается.