Abstract

In 2014, ACS-NSQIP® targeted pancreatectomies to improve outcome reporting and risk calculation related to pancreatectomy. At the same time, our department began prospectively collecting data for pancreatectomy in the Enhanced Recovery After Surgery® Interactive Audit System (EIAS). The purpose of this study is to compare reported outcomes between two major auditing databases for the same patients undergoing pancreatectomy. The same 171 patients were identified in both databases. Clinical outcomes were then obtained from each database and compared to determine whether reported complication rates were statistically different between auditing databases. A combination of Wilcoxon rank sum and Pearson's chi-squared tests were used to calculate statistical significance. No significant difference was appreciated in captured demographics between EIAS and NSQIP. Significant differences in reported rates for renal dysfunction, postoperative pancreatic fistula, return to the operative room, and urinary tract infection were noted between EIAS and NSQIP. Although significant differences in reported complication rates were demonstrated between EIAS and NSQIP for pancreatectomy, much of the discrepancy is attributable to subtle differences in definitions for postoperative occurrences between the two auditing databases. It is vital for surgeons to understand the exact definition that determines the complication rate for a given database.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.