Tuesday, June 25, 2019

The Central Sensitization Inventory predict pain‐related disability for musculoskeletal disorders in the primary care setting

Abstract

Background

Central sensitization (CS) is found in patients with musculoskeletal disorders and is related to clinical symptoms, including pain‐related disability. The Central Sensitization Inventory (CSI) has been developed for patients who are at risk of symptoms related to CS, and CSI severity levels are suggested for clinical interpretation of the CSI score. However, the longitudinal relationship between CSI severity and pain‐related disability is unclear in primary care. In this study, we investigated the association between CSI severity levels and the profiles of patients with musculoskeletal disorders as well as the longitudinal relationship between CSI severity levels and pain‐related disability in primary care settings.

Methods

A total of 553 patients were assessed using CSI, EuroQol‐5 dimension (EQ5D), and Brief Pain Inventory (BPI). Of the 553 patients, 150 patients were reassessed at the 3‐month follow‐up. Patients were grouped into three severity levels according to baseline CSI score: subclinical, mild, and moderate to higher level.

Results

As the CSI severity levels increased, the clinical symptoms tended to worsen on cross‐sectional analysis (p<0.05). Pain‐related disability at the 3‐month follow‐up was significantly higher for patients with moderate to high baseline CSI severity levels than for patients with subclinical baseline CSI levels (p<0.001). Furthermore, pain‐related disability increased according to the CSI severity level, with a medium to large effect size. However, there were no differences in pain duration across the CSI severity levels.

Conclusions

CSI has clinical utility as a prediction tool regardless of pain duration in patients with musculoskeletal disorders in primary care settings.

This article is protected by copyright. All rights reserved.



from Wiley: European Journal of Pain: Table of Contents http://bit.ly/2XytR8G
via IFTTT

No comments:

Post a Comment