Thursday, February 16, 2017

Skin conductance as a pain assessment tool during chest tube removal: An observational study

Abstract

Background

Skin conductance variability to assess pain has shown varying results. Skin conductance responses per second (SCR) during a standardized painful stimulus in awake adults may give further understanding of the method's validity. The purpose of this study was to validate the SCR with the visual analogue scale (VAS) for pain (P-VAS) and anxiety (A-VAS) during chest tube removal (CTR).

Methods

Ninety-five patients receiving epidural or non-epidural treatment, scheduled for CTR, were studied. Pain or anxiety was considered when VAS > 30 mm; the SCR cut-off value reflecting pain was ≥0.2 SCR.

Results

SCR values could not be recorded in eight cases before CTR, six cases during CTR and seven cases after CTR. CTR induced increases in SCR, P-VAS and A-VAS (p < 0.001). Seventy-seven percent of all pairs of P-VAS and SCR values were well-classified; P-VAS ≤ 30 mm and SCR < 0.2 or P-VAS > 30 mm and SCR ≥ 0.2. SCR obtained before CTR differentiates between patients with and without pain during CTR in all patients (p = 0.04) and in the subgroup of non-anxious patients (p = 0.02), but not in the subgroup of anxious patients. SCR obtained during CTR had similar values in patients with and without pain in all patients and in the subgroup of anxious patients, but in the subgroup of non-anxious patients SCR during CTR differentiates patients with and without pain (p = 0.009).

Conclusions

SCR increases during painful procedures. Preprocedural SCR may help predict reported pain in patients exposed to painful procedures. SCR during CTR differentiates between patients with and without pain only in non-anxious patients.

Significance

Preprocedural SCR may help predict reported pain in patients exposed to painful procedures. Procedural SCR accuracy improves in a subgroup of non-anxious patients. P-VAS is influenced by anxiety different from SCR.



from European Journal of Pain http://ift.tt/2lnQrgD
via IFTTT

No comments:

Post a Comment