DOI 10.1093/rheumatology/keac161
Investigating characteristics of idiopathic inflammatory myopathy flares using daily symptom data collected via a smartphone app.
Аннотация
OBJECTIVE
The objective of this study was to use daily data collected via a smartphone app for characterization of patient-reported and symptom-based (using an a priori definition) flares in an adult idiopathic inflammatory myopathy (IIM) cohort.
METHODS
UK adults with an IIM answered patient-reported outcome measurements (PROMs) daily via a smartphone app during a 91-day study. Daily symptom PROMs addressed global activity, overall pain, myalgia, fatigue, and weakness (on a 0-100 visual analogue scale). Patient-reported flares were recorded via a weekly app question. Symptom-based flares were defined via an a priori definition related to increase in daily symptom data from the previous 4-day mean.
RESULTS
Twenty participants (65% female) participated. Patient-reported flares occurred on a median of 5 weeks (IQR 3, 7) per participant, out of a possible 13. The mean of each symptom score was significantly higher in flare weeks, compared with non-flare weeks (e.g. mean flare week myalgia score 34/100, vs 21/100 during non-flare week, t test P-value <0.01). Fatigue accounted for the most symptom-based flares [incidence-rate 23/100 person-days (95% CI 19, 27)], and myalgia the fewest [incidence rate 13/100 person-days (95% CI 11, 16)]. Symptom-based flares typically resolved after 3 days, although fatigue-predominant flares lasted 2 days. The majority (69%) of patient-reported flare weeks coincided with at least one symptom-based flare.
CONCLUSIONS
IIM flares are frequent and associated with increased symptom scores. This study has demonstrated the ability to identify and characterize patient-reported and symptom-based flares (based on an a priori definition), using daily app-collected data.
Предметные рубрики MeSH
Подготовка и перевод публикации
Обработка статьи · этапы, ошибки и управление
Ошибки и ограничения
История · было → стало
Состояние обновляется каждые 5 секунд, пока блок открыт. Процент показывается только там, где известен объём работы. Пауза останавливает продолжение этапа; текущий запрос к источнику может завершиться.
Тип публикации указан по данным источника. Уровень доказательности автоматически не присваивается.