Development and Use of Ambulatory Adverse Event Trigger Tools (Text Ve Slide Presentation from the AHRQ 2009 Annual ConferencSlide presentation from the AHRQ 2009 conference. On September 14, 2009, Amy K. Rosen, PhD made this presentation at the 2009 Annual Conference. Select to access the PowerPoint® presentation (776 KB) (Plugin Software Help).Slide 1 Development and Use of Ambulatory Adverse Event Trigger ToolsAmy K. Rosen, PhDAHRQ ConferenceSept. 14, 2009Boston University School of Public Health, Boston, MA,VA Center for Healthcare Quality, Outcomes, and Economic Research (CHQOER), Bedford MAakrosen@bu.edu Slide 2 AcknowledgementsSponsored by AHRQ Contract No. HHSA290200600012, Task Order Officer Amy Helwig, MDPI Amy Rosen, PhDCo-PI Jonathan Nebeker, MD, MSCo-Investigators: Stephan Gaehde, MDHaytham Kaafarani, MD, MPHBrenna Long, MAHillary Mull, MPPBrian Nordberg, BSSteve Pickard, MSPeter Rivard, PhDLucy Savitz, PhD, MBAChris Shanahan, MD, MPHStephanie Shimada, PhD Slide 3 Project Goal and SettingsGoal: Develop adverse event (AEs) triggers for the outpatient setting Outpatient surgeryOutpatient adverse drug events (ADEs)Three sites for patient data: Boston Medical Center (BMC)Intermountain HealthcareVeterans Health Administration (VA) Slide 4 BackgroundTriggers are algorithms that use electronic patient data to identify patterns consistent with a possible adverse event e.g. , the combination of a lab value threshold and an active prescriptionGlobal vs. AE specific trigger: Flags the chart for the suspicion of occurrence of any AE or the occurrence of a specific AEInterventionist triggers: Mostly ADEsGives providers a chance to respond and avoid alert overload Slide 5 MethodsLiterature ReviewClinicalInputFocus GroupsClinical Advisory PanelModifiedDelphi PanelFinal List of TriggersDocument existing triggersEstablish prevalence of outpatient AEsEstablish primary causes of outpatient AEs Slide 6 MethodsLiterature ReviewClinicalInputFocus GroupsClinical Advisory PanelModifiedDelphi PanelFinal List of TriggersDocument existing triggersEstablish prevalence of outpatient AEsEstablish primary causes of outpatient AEsReview epidemiological basis for AEsInput clinical knowledge and data needed into trigger rules Slide 7 MethodsLiterature ReviewClinicalInputFocus GroupsClinical Advisory PanelModifiedDelphi PanelFinal List of TriggersDocument existing triggersEstablish prevalence of outpatient AEsEstablish primary causes of outpatient AEsResearch data limitationsDetermine priority areas for trigger developmentDevelop methods to critique triggersReview epidemiological basis for AEsInput clinical knowledge and data needed into trigger rules Slide 8 MethodsLiterature ReviewClinicalInputFocus GroupsClinical Advisory PanelModifiedDelphi PanelFinal List of TriggersDocument existing triggersEstablish prevalence of outpatient AEsEstablish primary causes of outpatient AEsResearch data limitationsDetermine priority areas for trigger developmentDevelop methods to critique triggersReview epidemiological basis for AEsInput clinical knowledge and data needed into trigger rulesRefine rules/trigger logicRefine priority areas priority areas for trigger development Slide 9 MethodsLiterature ReviewClinicalInputFocus GroupsClinical Advisory PanelModifiedDelphi PanelFinal List of TriggersDocument existing triggersEstablish prevalence of outpatient AEsEstablish primary causes of outpatient AEsResearch data limitationsDetermine priority areas for trigger developmentDevelop methods to critique triggersReview epidemiological basis for AEsInput clinical knowledge and data needed into trigger rulesRefine rules/trigger logicRefine priority areas priority areas for trigger developmentRate priority of AE causesRate priority of AEsRate triggers based on system- and patient-level perspectives Slide 10 MethodsObtained de-indentified clinical data from each site.Boston Medical CtrIntermountainVA (VISN 19)Combined the data fields from each site into a SQL database.Trigger DatabaseMock EMRCreated a mock electronic medical record (EMR) interface to enable case classification. Slide 11 Global Trigger Tools—Outpatient SurgeryTrigger NameDescriptionEmergency Department (ED)ED visits within 21 days of an outpatient surgery are likely to include visits due to complications from surgeryRe-AdmitHospital admissions within 30 days of an outpatient surgery may be due to complications from surgeryProcedure (Proc)Reoperation within 30 days and certain procedures on the same day as a scheduled same-day surgery are indicative that a complication may have occurredLength of stay (LOS)There is a higher probability of complications in same-day surgeries that result in a longer-than-planned stay in the hospitalSlide 12 AE-Specific Trigger Tools—Outpatient SurgeryTrigger NameDescriptionPulmonary Embolism/Deep Vein Thrombosis (PE/DVT)Detect cases of PE/DVT that result within 30 days of an outpatient surgery.Surgical Site Infection (SSI) 1Detect cases of surgical site infection that occur as a complication of outpatient surgery by looking for cases requiring wound care.Hematocrit (Hema)Detect the occurrence of postoperative hematoma/hemorrhage by looking for evidence of postoperative blood loss in same-day surgeries (otherwise expected to have minimal blood loss).Slide 13 Surgery Trigger Logic: ProcedureFire if: Same-day surgeryANDprocedure (interventional radiological OR urological OR cardiac OR gastroenterological)OR re-operation ≤ 30 daysSlide 14 AE-Specific Trigger Tools—ADETrigger NameDescriptionWarfarin (Warf)Detect rapid or excessive anticoagulation to prevent bleed by looking for over- anticoagulation and no evidence of rechecking within reasonable window.Potassium reducer (K-low)Detect hypokalemia to prevent further decline and arrhythmia by looking for dropping potassium without evidence of adjustments to medication.Potassium raiser (K-high)Detect hyperkalemia to prevent further increase and arrhythmia by looking for rising potassium without evidence of adjustments to medication.Slide 15 AE-Specific Trigger Tools—ADE (cont'd)Trigger NameDescriptionChange in renal clearance (Creat)Detect decreased renal function to prevent reactions from other drugs that are renally cleared by looking for a decrease in creatinine clearance to a concerning level that occurs soon after starting a drug that might decrease creatinine, after confirming that the new drug has not been decreased.Bone Marrow Toxin (BMT)Detect early signs of myelosuppression to prevent more severe cases by looking for a decrease in cells after non-cancer drug without evidence that the drug has been decreased in response.HypnoticDetect impairment in consciousness and cognition to improve quality of life by looking for patients on psychotropic drugs with a subsequent decline in consciousness or cognition.Slide 16 ADE Trigger Logic: Change in Renal ClearanceFire if: Subsequent increase in creatinine > 33% and dose > than dose prior to creatinine measurement (This is the reference creatinine level) ANDNOT (trimethoprim started in interval between 1 day prior to creatinine measurement and after reference creatinine level) ANDNOT (all GFR reducers and renal toxins discontinued or expired > 3 months prior to triggering value)Remove trigger if response taken within window: Renal toxin discontinued or GFR reducer dose reduced 0-6 days after firing criteria satisfied ORCreatinine resulted 0-6 days after firing criteria satisfiedSlide 17 Data Challenges—Accessing DataPolitical/Logistical Barriers Gaining permission to access the data Developed de-identification algorithmChallenge meeting HIPAA complianceAdministrative barriers to obtaining accessEncrypting/ ensuring safe transfer of data between sitesSafe storage of data from multiple institutionsIT Resources Availability of personnel for data pullsComputing infrastructures Pulling notes too resource intensiveSlide 18 Data Challenges—Data Elements"IT Black Box" Researchers reliant on IT staff's programming, no way to ascertain completeness of dataInconsistencies in coding across institutions Same information, different coding: Gender: M/F vs 1/2/3Units of measure: metric vs US vs missingICD-9-CM codes stored with or without periodsICD-9-CM procedure codes were unavailable for some proceduresLab titles inconsistent across settingsLack of documentation re: coding practicesNumeric results within text dataSlide 19 Data Challenges—Data Elements (cont'd)Missing data Loss of information from text de-identification algorithm Fuzzy pattern and word matching removed some key clinical terms from clinical notesDe-identification made notes difficult to readRemoval of dates resulted in loss of information about clinical orderMissing National Drug Codes (NDCs) in pharmacy dataFree text vs. standardized daily dosage information TAKE ONE-HALF TABLET BY MOUTH EVERY DAY FOR 2 WEEKS, THEN TAKE � ONE-HALF TABLET TWO (2) TIMES A DAY FOR 2 WEEKS, THEN TAKE ONE TABLET � TWO (2) TIMES A DAY FOR 2 WEEKS, THEN TAKE TWO TABLETS TWO (2) TIMES A � DAY FOR 2 WEEKS, THEN TAKE THREE TABLETS TWO (2) TIMES A DAY FOR 2 � WEEKS, THEN TAKE FOUR TABLETS TWO (2) TIMES A DAY INCREASE DOSE � GRADUALLY. � WHEN GOING FROM 25 TO 50 MG START WITH INCREASING THE AM � DOSE FOR 2WEEKS, THEN THE AM AND PM DOSE. � DO THIS WHEN INCREASING � FROM 50 TO 75 AND 75 TO 100. � IF QUESTIONS PLEASE CALL.Lack of units in lab dataSlide 20 Next StepsCase classification RNs classifying surgery AE trigger-flagged casesPharmacists classifying ADE trigger-flagged casesCalculate positive predictive value (PPV) for each triggerConduct a second round of focus groups at each institutionHold phone call with trigger experts to review logic and discuss resultsSlide 21 Dissemination to DateTriggers and Targeted Injury Detection Systems (TIDS)Expert Panel Meeting , Rockville, MD. June 2008. See proceedings at http://www.ahrq.gov/QUAL/triggers/Mull HJ & Nebeker, JR. Informatics Tools for the Development of Triggers for Outpatient Adverse Drug Events. AMIA Annual Symposium Proceedings. Nov 2008, 6:505-9.Kaafarani H, Rosen AK, et al. What is a Trigger Tool to a Surgeon: Designing Trigger Tools for Surveillance of Adverse Events in Ambulatory Surgery. Massachusetts Chapter of the American College of Surgeons 55th Annual Meeting, Boston, MA. Dec 2008.Kaafarani H, Rosen AK, et al. Development of Trigger Tools for Surveillance of Adverse Events in Ambulatory Surgery. VA HSR&D QUERI National Meeting, Phoenix, AZ. Dec 2008.Kaafarani H, Rosen AK, et al. Developing Trigger Tools for Surveillance of Adverse Events in Same-Day Surgery: A Literature-Based, End-User Inspired & Expert-Evaluated Methodology. VA HSR&D Annual Meeting, Baltimore, MD. Feb 2009.Shimada S, Rivard P, et al. Priorities & Preferences of Potential Ambulatory Trigger Tool Users. AcademyHealth Annual Research Meeting, Chicago, IL. June 2009.Kaafarani H, Rosen AK, et al. Developing Trigger Tools for Surveillance of Adverse Events in Same-Day Surgery: A Literature-Based, End-User Inspired and Expert-Evaluated Methodology. AHRQ Annual Meeting, Bethesda, MD. Sept 2009.Kaafarani H, Rosen AK, et al. Development of Trigger Tools for Surveillance of Adverse Events in Ambulatory Surgery. Quality and Safety in Health Care. (forthcoming) Current as of December 2009 Internet Citation: Development and Use of Ambulatory Adverse Event Trigger Tools (Text Ve: Slide Presentation from the AHRQ 2009 Annual Conferenc. December 2009. Agency for Healthcare Research and Quality, Rockville, MD. http://www.ahrq.gov/news/events/conference/2009/rosen/index.html