13.07.2015 Views

Surgical management of chronic inguinal pain syndromes - Liespijn

Surgical management of chronic inguinal pain syndromes - Liespijn

Surgical management of chronic inguinal pain syndromes - Liespijn

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

n (%)Previous visits to a physician because <strong>of</strong> persisting <strong>pain</strong>*General Practioner 32 (4.6)Gynaecologist 15 (2.2)General surgeon 5 (0.7)Other (Speciality consulted physician unknown) 3 (0.4)Frequency <strong>of</strong> <strong>pain</strong> medication intake*Yes, occasionally 16 (2.3)Yes, regularly 5 (0.7)Cyclic <strong>pain</strong>* 56 (8.1)Bulge noticed* 130 (18.8)Numbness* 199 (28.8)Functional impairmentNone 628 (91.0)Mild 45 (6.5)Moderate 16 (2.3)Severe 1 (0.1)Figure 3 Pain frequency in patients following a Pfannenstiel incision (n = 689, one patient missing).Table 2 Chronic <strong>pain</strong> characteristics reported by patients that responded to the questionnaire (n= 690).*Pain located at the Pfannenstiel incisionUnivariate modelMultivariate modelOR (95% CI) p OR (95% CI) pAge 1.0 (1.0-1.0) 0.079 -Follow up duration 0.99 (0.99-1.0) 0.036 -Emergency CD* 1.53 (1.07-2.20) 0.021 1.56 (1.01-2.40) 0.020*No <strong>of</strong> Pfannenstiel incisionsN = 2 1.60 (1.07-2.39) 0.020 1.27 (0.82-1.97) 0.291N > 2 2.95 (1.62-5.37) 0.000 2.92 (1.44-5.93) 0.003Numbness 3.19 (2.25-4.51) 0.000 3.01 (2.05-4.40) 0.000Scar length 1.06 (1.01-1.11) 0.029 -Table 3 Logistic regression analysis <strong>of</strong> risk factors predicting <strong>chronic</strong> <strong>pain</strong> development following a Pfannenstiel incision (n=690).*Emergency CD in multivariate analysis among CD patients.Figure 4 Pain intensity in patients following a Pfannenstiel incision (n=690).40 Chapter 3The Pfannenstiel approach as a source <strong>of</strong> <strong>chronic</strong> <strong>pain</strong> 41

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!