Hospital esophageal cancer resection volume does not predict patient mortality risk

Benjamin D. Kozower, George J. Stukenborg

Research output: Contribution to journalArticlepeer-review

23 Scopus citations

Abstract

Background: Insurers often seek to direct esophageal cancer patients to hospitals with high volumes of esophageal resection. However, controversy exists regarding the strength and validity of evidence for the volume-outcome association. The purpose of this study was to evaluate the volume-outcome relationship for esophageal cancer resection in a large population dataset and to compare 3alternative techniques for measuring the effect of volume. Methods: Esophageal cancer resection patients were identified in the 2007 Nationwide Inpatient Sample. Hospital volume was measured using a continuous linear function, a nonlinear function using restricted cubic splines, and using quintiles of volume. The statistical significance of the relationship between hospital volume and mortality risk was assessed, and adjusted for patient age, for comorbid disease, and for correlated events within hospitals. Results: A total of 6,248 esophageal cancer resection patients from 217 hospitals were identified. All 3 models demonstrated excellent performance characteristics (C index = 0.94, Nagelkerke R 2 = 0.62). However, no significant association was demonstrated between hospital procedure volume and in-hospital mortality in any model. Important predictors of mortality included age, hypertension, weight loss, and peripheral vascular disease (p < 0.001). Conclusions: Esophageal cancer resection volume is not a significant predictor of mortality and should not be used as a proxy measure for surgical quality.

Original languageEnglish
Pages (from-to)1690-1698
Number of pages9
JournalAnnals of Thoracic Surgery
Volume93
Issue number5
DOIs
StatePublished - May 2012

Fingerprint

Dive into the research topics of 'Hospital esophageal cancer resection volume does not predict patient mortality risk'. Together they form a unique fingerprint.

Cite this