Pain and Self-reported Swollen Joints Are Main Drivers of Patient-reported Flares in Rheumatoid Arthritis: Results from a 12-month Observational Study
Bibliographic record
Abstract
OBJECTIVE: To examine prospectively self-reported flare characteristics and their longitudinal association with disease activity and patient-reported outcomes (PRO) in patients with rheumatoid arthritis (RA). METHODS: Consecutive RA patients with 28-joint count Disease Activity Score based on C-reactive protein (DAS28-CRP) < 3.2 and no swollen joints were examined at baseline, Month 6, and Month 12. Assessments included joint counts, DAS28-CRP, visual analog scale-evaluator's global assessment (EGA), and PRO. Every third month, patients completed the Flare Assessment in Rheumatoid Arthritis and RA Flare Questionnaire, and disclosed self-management strategies. Flaring and non-flaring patients were compared and longitudinal associations between self-reported flare status (yes/no) and disease activity, PRO, and treatment escalation were explored. RESULTS: Among 80 patients with RA [74% females, mean (SD) age 63 (10) yrs, disease duration 11 (7) yrs, and baseline DAS28-CRP 1.9 (0.6)], 64 (80%) reported flare at least once during 12 months. Fifty-five percent of flares lasted less than 1 week. Common self-management strategies were analgesics (50%) and restricted activities (38%). Patients who reported being in flare had consistently higher disease activity measures and PRO compared to patients without flare. In a partly adjusted model, all flare domains, patient-reported swollen and tender joint counts and disease activity measures were associated with flares. In fully adjusted analyses, present flare was independently associated with pain (OR 1.85, 95% CI 1.34-2.60), patient-reported swollen joints (OR 1.18, 95% CI 1.03-1.36), and higher EGA (OR 1.15, 95% CI 1.04-1.28). Treatment escalation was associated with present flare (p ≤ 0.001). CONCLUSION: In RA, self-reported flares were frequent, mainly managed by analgesics, substantiated by higher disease activity measures, independently associated with pain and patient-reported swollen joints, and related to treatment escalation.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.005 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".