z-logo
Premium
Evaluation of the Physiological and Operative Severity Score for the Enumeration of Mortality and Morbidity (POSSUM) scoring system in elderly patients with pressure sores undergoing fasciocutaneous flap‐reconstruction
Author(s) -
MIZUMOTO Kazuo,
MORITA Eishin
Publication year - 2009
Publication title -
the journal of dermatology
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.9
H-Index - 65
eISSN - 1346-8138
pISSN - 0385-2407
DOI - 10.1111/j.1346-8138.2008.00582.x
Subject(s) - medicine , pressure sores , surgery , scoring system
The aim of the present study was to predict operative morbidity in elderly patients with deep pressure sores by using the Physiological and Operative Severity Score for the Enumeration of Mortality and Morbidity (POSSUM) scoring system. Fifteen patients over 70 years old were retrospectively reviewed who had undergone gluteus maximus fasciocutaneous flap‐reconstruction for pressure sores of the sacral region from 1 April 2005 to 31 March 2007. Complications were seen in six cases (40%) after operation. Four were wound infection, one was chest infection and another was septicemia. The subjects were divided into two groups by the presence (complicated group) or absence (non‐complicated group) of postoperative complications. Each item of physiological scores, physiological score (PS), operative severity score (OS) and predicted morbidity rate (R) were calculated and compared between two groups. As a result, hemoglobin ( P  = 0.0276), PS ( P  = 0.0023) and R ( P  = 0.0078) differed significantly between the two groups. It is noteworthy that the PS were over 25 in all of the complicated group, but in only one of nine in the non‐complicated group ( P  = 0.0014). Our study suggests that, for pressure sores in the sacral region in elderly patients, gluteus maximus fasciocutaneous flap‐reconstruction can be employed in patients whose PS are under 24 in the POSSUM scoring system.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here