| Literature DB >> 35010652 |
Mirjam Ekstedt1,2, Marie Kirsebom3, Gunilla Lindqvist3, Åsa Kneck4, Oscar Frykholm1, Maria Flink5,6, Carolina Wannheden1.
Abstract
The increasing prevalence of chronic conditions and multimorbidity poses great challenges to healthcare systems. As patients' engagement in self-managing their chronic conditions becomes increasingly important, eHealth interventions are a promising resource for the provision of adequate and timely support. However, there is inconclusive evidence about how to design eHealth services to meet the complex needs of patients. This study applied an evidence-based and theory-informed user-centered design approach in three phases to identify the needs of older adults and healthcare professionals in the collaborative management of multimorbidity (phase 1), develop an eHealth service to address these needs (phase 2), and test the feasibility and acceptance of the eHealth service in a clinical setting (phase 3). Twenty-two user needs were identified and a web-based application-ePATH (electronic Patient Activation in Treatment at Home)-with separate user interfaces for patients and healthcare professionals was developed. The feasibility study with two nurses and five patients led to a redesign and highlighted the importance of adequately addressing not only varying user needs but also the complex nature of healthcare organizations when implementing new services and processes in chronic care management.Entities:
Keywords: chronic disease; eHealth; mHealth; patient activation; person-centered care; self-management
Mesh:
Year: 2021 PMID: 35010652 PMCID: PMC8744716 DOI: 10.3390/ijerph19010391
Source DB: PubMed Journal: Int J Environ Res Public Health ISSN: 1660-4601 Impact factor: 3.390
Figure 1Overview of the three study phases and steps numbered 1–8. The arrows between and within design phases illustrate iteration in the design process. In particular, steps 6 and 8 link the three phases through iteration.
Overview of participant involvement in all design phases, steps 1–8.
| Design Steps | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ID | Participant Role | Organization and Level of Care | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
|
| ||||||||||
| 1 | Occupational therapist, Manager | ICO, home care | • | • | • | |||||
| 2 | Registered nurse, Manager | ICO, hospital care | • | • | • | |||||
| 3 | Physician, Manager | ICO, hospital care | • | • | ||||||
| 4 | Pharmacist, Manager | ICO, hospital care | • | • | ||||||
| 5 | Registered nurse, Manager | ICO, primary care | • | • | ||||||
|
| ||||||||||
| 6 | Administrator, Social worker | ICC, social service | • | • | • | |||||
| 7 | Quality developer, Registered nurse | ICO, hospital care | • | • | • | |||||
| 8 | Quality developer, Social worker | ICC, social service | • | • | ||||||
| 9 | Administrator/Coordinator | ICO, hospital care | • | |||||||
|
| ||||||||||
| 10 | Specialist nurse, cardiology | ICO, hospital care | • | • | • | • | ||||
| 11 | Physician, internal medicine | ICO, hospital care | • | |||||||
| 12 | Specialist nurse, oncology | ICO, hospital care | • | • | ||||||
| 13 | Registered nurse | ICO, hospital acute care | • | |||||||
| 14–15 | Registered nurses ( | HDC | • | |||||||
| 16–17 | Assistant nurses ( | HDC | • | |||||||
| 18–19 | District nurses ( | ICO, primary care | • | • | • | |||||
| 20–22 | District nurses ( | ICO, primary care | • | • | ||||||
|
| ||||||||||
| 23–24 | Family carers ( | HDC | • | |||||||
| 25–32 | Patients, HF/T2D/COPD ( | HDC | • | |||||||
| 33 | Patient, T2D | Personal contact | • | |||||||
| 34–35 | Patients, T2D ( | ICO, primary care | • | |||||||
| 36–38 | Patients, HF/COPD ( | ICO, primary care | • | |||||||
| 39 | Patient, prostate cancer | Personal contact | • | |||||||
ICO = integrated care organization; HDC = heart failure day care; HF = heart failure; COPD = chronic obstructive pulmonary disease; T2D = type 2 diabetes. •: indicates in which design steps participants were involved.
Identified user needs grouped into five themes. Steps 1–3 indicate in which data collection steps the needs were captured.
| Step | ||||
|---|---|---|---|---|
| Theme | User Need | 1 | 2 | 3 |
| 1. Diagnosis-specific information | 1.1 Easily accessible information | • | • | |
| 1.2 Trustworthy (evidence-based) information | • | • | • | |
| 1.3 Comprehensive information | • | • | • | |
| 1.4 Understandable information | • | • | ||
| 1.5 Information tailored to individual needs | • | • | ||
| 2. Medication management support | 2.1 Individualized medication management instructions | • | • | |
| 2.2 Medication reminders | • | • | ||
| 2.3 Access to updated medication lists | • | • | ||
| 2.4 Medication adherence and reasons for non-adherence | • | • | ||
| 2.5 Monitoring of intended and unintended effects | • | |||
| 3. Self-management support | 3.1 Monitoring of symptoms and wellbeing | • | • | • |
| 3.2 Support for providing tailored guidance | • | • | • | |
| 3.3 Reminders and motivational support | • | • | ||
| 3.4 Information exchange between patients and HCPs | • | • | ||
| 4. Care coordination support | 4.1 Clarification of roles, responsibilities and contact details | • | • | |
| 4.2 Appointment reminders for patients | • | |||
| 4.3 Overview of patients’ care plan and trajectory | • | • | • | |
| 4.4 Support for collecting patient preferences | • | |||
| * 4.5 Information exchange between providers | • | |||
| 5. Psychosocial support | 5.1 Assurance of available support | • | ||
| * 5.2 Support for connecting with other patients | • | |||
| * 5.3 Support for inviting family caregivers as users | • | • | ||
HCPs: health care professionals; •: indicates in which design steps (1-3) the user needs were identified.; *: user needs that were not addressed in phases 2 and 3 of the design process.
Figure 2Overview of ePATH architecture and modules for different users: (a) illustrates the initial design (phase 2), which enabled all users to access ePATH through a web-based application; (b) illustrates how the web-based application was complemented with a patient-facing mobile application and related functionalities for patients after redesign (phase 3).
Figure 3Screen print of the ePATH daily overview module (patient interface): The horizontal navigation panel at the top enables the patient to navigate between different modules (overview, information, self-care, about me, notes, calendar, contacts, messaging). The horizontal panel below (“Målsättningar” = Goals) enables the patient to add general goals and specific goals until the next care visit. The three vertical panels (“Dagens läkemedel” = Medications, “Dagens egenvårdsaktiviteter” = Self-care activities, “Dagens hälsoskattningar” = Health assessments) provide an overview of the planned self-care tasks for the day and enable tracking.
Figure 4Screen prints of the mPATH app: (a) shows the mPATH home page that allows users to navigate to different pages: “Registrera” = Tracking, “Läkemedel” = Medications, “Egenvårdsaktiviteter” = Self-management activities, “Hälsoskattningar“ = Health assessments, and “Meddelanden” = Messaging; (b) illustrates an example from the tracking page which lists all daily self-management tasks chronologically. If speed-tracking is possible (first two items in the list), default values are spelled out (“Läkemedel taget: Ja” = Medication taken: Yes) and users can simply click the checkbox to track the task as done; (c) illustrates the editing view where the user can edit details for individual self-management tasks.