RESUMEN
Background: The risk of developing a persistent reduction in renal function after postoperative acute kidney injury (pAKI) is not well-established. Objective: Perform a multi-center retrospective propensity matched study evaluating whether patients that develop pAKI have a greater decline in long-term renal function than patients that did not develop postoperative AKI. Design: Multi-center retrospective propensity matched study. Setting: Anesthesia data warehouses at three tertiary care hospitals were queried. Patients: Adult patients undergoing surgery with available preoperative and postoperative creatinine results and without baseline hemodialysis requirements. Measurements: The primary outcome was a decline in follow-up glomerular filtration rate (GFR) of 40% relative to baseline, based on follow-up outpatient visits from 0-36 months after hospital discharge. A propensity score matched sample was used in Kaplan-Meier analysis and in a piecewise Cox model to compare time to first 40% decline in GFR for patients with and without pAKI. Results: A total of 95,208 patients were included. The rate of pAKI ranged from 9.9% to 13.7%. In the piecewise Cox model, pAKI significantly increased the hazard of a 40% decline in GFR. The common effect hazard ratio was 13.35 (95% CI: 10.79 to 16.51, p<0.001) for 0-6 months, 7.07 (5.52 to 9.05, p<0.001) for 6-12 months, 6.02 (4.69 to 7.74, p<0.001) for 12-24 months, and 4.32 (2.65 to 7.05, p<0.001) for 24-36 months. Limitations: Retrospective; Patients undergoing ambulatory surgery without postoperative lab tests drawn before discharge were not captured; certain variables like postoperative urine output were not reliably available. Conclusion: Postoperative AKI significantly increases the risk of a 40% decline in GFR up to 36 months after the index surgery across three institutions.
RESUMEN
BACKGROUND: Many hospitals have replaced their legacy anesthesia information management system with an enterprise-wide electronic health record system. Integrating the anesthesia data within the context of the global hospital information infrastructure has created substantive challenges for many organizations. A process to build a perioperative data warehouse from Epic was recently published from the University of California Los Angeles (UCLA), but the generalizability of that process is unknown. We describe the implementation of their process at the University of Miami (UM). METHODS: The UCLA process was tested at UM, and performance was evaluated following the configuration of a reporting server and transfer of the required Clarity tables to that server. Modifications required for the code to execute correctly in the UM environment were identified and implemented, including the addition of locally specified elements in the database. RESULTS: The UCLA code to build the base tables in the perioperative data warehouse executed correctly after minor modifications to match the local server and database architecture at UM. The 26 stored procedures in the UCLA process all ran correctly using the default settings provided and populated the base tables. After modification of the item lists to reflect the UM implementation of Epic (eg, medications, laboratory tests, physiologic monitors, and anesthesia machine parameters), the UCLA code ran correctly and populated the base tables. The data from those tables were used successfully to populate the existing perioperative data warehouse at UM, which housed data from the legacy anesthesia information management system of the institution. The time to pull data from Epic and populate the perioperative data warehouse was 197 ± 47 minutes (standard deviation [SD]) on weekdays and 260 ± 56 minutes (SD) on weekend days, measured over 100 consecutive days. The longer times on weekends reflect the simultaneous execution of database maintenance tasks on the reporting server. The UCLA extract process has been in production at UM for the past 18 months and has been invaluable for quality assurance, business process, and research activities. CONCLUSIONS: The data schema developed at UCLA proved to be a practical and scalable method to extract information from the Epic electronic health system database into the perioperative data warehouse in use at UM. Implementing the process developed at UCLA to build a comprehensive perioperative data warehouse from Epic is an extensible process that other hospitals seeking more efficient access to their electronic health record data should consider.