Improving quality of care: development of a risk-adjusted perioperative morbidity model for vaginal hysterectomy

Christine A. Heisler, Giovanni D. Aletti, Amy L. Weaver, L. Joseph Melton, William A. Cliby, John B. Gebhart

Research output: Contribution to journalArticlepeer-review

9 Scopus citations

Abstract

Objective: We sought to develop and evaluate a risk-adjusted perioperative morbidity model for vaginal hysterectomy. Study Design: Medical records of women who underwent vaginal hysterectomy during 2004 and 2005 were retrospectively reviewed. Morbidity included hospital readmission, reoperation, and unplanned medical intervention or intensive care unit admission; urinary tract infections were excluded. Multivariate logistic regression identified factors associated with perioperative morbidity (adjusted for urinary tract infection). The resulting model was validated using a random 2006 sample. Results: Of 712 patients, 139 (19.5%) had morbidity associated with congestive heart failure or prior myocardial infarction, perioperative hemoglobin decrease >3.1 g/dL, preoperative hemoglobin <12.0 g/dL, and prior thrombosis (c-index = 0.68). Predicted morbidity was similar to observed rates in the validation sample. Conclusion: History of congestive heart failure or myocardial infarction, prior thrombosis, perioperative hemoglobin decrease >3.1 g/dL, or preoperative hemoglobin <12.0 g/dL were associated with increased perioperative complications. Quality improvement efforts should modify these variables to optimize outcomes.

Original languageEnglish (US)
Pages (from-to)137.e1-137.e5
JournalAmerican journal of obstetrics and gynecology
Volume202
Issue number2
DOIs
StatePublished - Feb 2010

Keywords

  • perioperative morbidity
  • risk adjustment
  • vaginal hysterectomy

ASJC Scopus subject areas

  • Obstetrics and Gynecology

Fingerprint

Dive into the research topics of 'Improving quality of care: development of a risk-adjusted perioperative morbidity model for vaginal hysterectomy'. Together they form a unique fingerprint.

Cite this