Epic As Platform For Clinical Decision Support. Implications For Qi And Research.
Upcoming SlideShare
Loading in...5
×
 

Epic As Platform For Clinical Decision Support. Implications For Qi And Research.

on

  • 4,211 views

 

Statistics

Views

Total Views
4,211
Slideshare-icon Views on SlideShare
4,202
Embed Views
9

Actions

Likes
1
Downloads
69
Comments
0

2 Embeds 9

http://www.slideshare.net 8
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Yiscah

Epic As Platform For Clinical Decision Support. Implications For Qi And Research. Epic As Platform For Clinical Decision Support. Implications For Qi And Research. Presentation Transcript

  • Epic Research Advisory Council Meeting April 1, 2009 Epic as a Platform Launching Decision Support Tools: Implications for Research and Population QI Yiscah Bracha, MS Minneapolis Medical Research Foundation Robert Grundmeier, MD The Children’s Hospital of Philadelphia
  • Improving Asthma Care in an Integrated Safety Net through a Commercially Available Electronic Medical Record
    • Prime contractor:  Denver Health and Hospital Association .
    • Subcontractor:  Minneapolis Medical Research Foundation. Project site: Hennepin County Medical Center, Mpls MN
    • AHRQ Contract No. HHSA290200600020, Task Order No. 5
      • Staff and contractors – Minneapolis Medical Research Foundation
      • Gail Brottman, MD (Chief, Pediatric Pulmonology, HCMC)
      • Kevin Larsen, MD (Chief Medical Informatics Officer, HCMC)
      • Yiscah Bracha, MS (Research Director, Center for Urban Health)
      • Cherylee Sherry, MPH (Project Manager, Pediatric Research & Advocacy HCMC )
      • Touch Thouk (Administrative Manager, Center for Urban Health)
      • Angeline Carlson, PhD (Principle, Data Intelligence Inc.)
      • Staff – Denver Health and Hospital Association
      • Sherry Eisert, PhD (Director, Health Services Research)
      • Michael (Josh) Durfee (Research Projects Coordinator, Health Services Research)
      • Contributors of Ideas, Information & Effort:
      • Michael Barbouche (University of Wisconsin Medical Foundation); Robert Grundmeier, MD (Children’s Hospital of Philadelphia); Michael Kahn, MD, PhD (Denver Children’s Hospital)
      • Donald Uden, PharmD (University of Minnesota), Faith Dohman, RN (Hennepin Faculty Associates), Susan Ross, RN (Minnesota Department of Health)
  • The Problem:
    • Docs practice within an information avalanche
    • Impossible for any human to keep up
  • What is a busy physician to do?
  • Be confident.
  • Be concerned.
  • Be oblivious.
  • Medical informatics to the rescue!
    • Provide decision support during care, while doc viewing pt electronic record
    • Developmental generation beyond:
      • URL to PDF of guidelines on screen (clinicians don’t go there)
      • Automatic reminders & alerts (clinicians suffer from “alert fatigue”)
  • Task-based decision support
    • Types of support
      • Which diagnostic tests to use
      • How to initiate therapy
      • How to adjust therapy over time
    • Electronic data:
      • EHR data automatically populate decision algorithms
      • Results from algorithms automatically populate patient data record
  • ASTHMA REGISTRY Asthma info for Populations Clarity Information for Populations Epic Information on Individual Patients Electronic decision support for: Asthma Decision Support & Epic: Current model Electronic decision support for: Which diagnostic imaging tech? IMAGING REGISTRY Imaging info for Populations interface engine interface engine
  • ASTHMA REGISTRY Asthma info for Populations Clarity Information for Populations Epic Information on Individual Patients Electronic decision support for: Asthma Current model and data warehousing: Electronic decision support for: Which diagnostic imaging tech? IMAGING REGISTRY Imaging info for Populations ASTHMA REGISTRY Asthma info for Populations interface engine interface engine
  • Clarity Information for Populations Epic Information on Individual Patients Electronic decision support for: Asthma Current model and data warehousing: Electronic decision support for: Which diagnostic imaging tech? interface engine interface engine IMAGING REGISTRY Imaging info for Populations ASTHMA REGISTRY Asthma info for Populations
  • Building the Warehouse: IMAGING REGISTRY Imaging info for Populations ASTHMA REGISTRY Asthma info for Populations
  • The Warehouse Dream: ASTHMA REGISTRY Asthma info for Populations HIV REGISTRY HIV info for Populations STENT REGISTRY Stent info for Populations DIABETES REGISTRY Diabetes info for Populations IMAGING REGISTRY Imaging info for Populations COLONOSCOPY REGISTRY Colonoscopy info Populations
  • ASTHMA REGISTRY Asthma info for Populations HIV REGISTRY HIV info for Populations STENT REGISTRY Stent info for Populations DIABETES REGISTRY Diabetes info for Populations IMAGING REGISTRY Imaging info for Populations COLONOSCOPY REGISTRY Colonoscopy info Populations The analytic dream:
  • Our analytic reality: ASTHMA REGISTRY Asthma info for Populations HIV REGISTRY HIV info for Populations DIABETES REGISTRY Diabetes info for Populations IMAGING REGISTRY Imaging info for Populations WHY?
  • Clarity Information for Populations Epic Information on Individual Patients Electronic decision support for: Asthma ASTHMA REGISTRY Asthma info for Populations The problem with the current model: Electronic decision support for: Which diagnostic imaging tech? IMAGING REGISTRY Imaging info for Populations interface engine interface engine
  • Clarity Information for Populations Epic Information on Individual Patients Electronic decision support for: Asthma ASTHMA REGISTRY Asthma info for Populations Electronic decision support for: Which diagnostic imaging tech? IMAGING REGISTRY Imaging info for Populations Hard to build…. Hard to maintain…. interface engine interface engine
  • Clarity Information for Populations Epic Information on Individual Patients Electronic decision support for: Asthma ASTHMA REGISTRY Asthma info for Populations So much effort focused on interface*: Electronic decision support for: Which diagnostic imaging tech? IMAGING REGISTRY Imaging info for Populations * Building complex decision support within Epic is just as much effort as interface interface engine interface engine
  • No resources for data mgmt: ASTHMA REGISTRY Asthma info for Populations HIV REGISTRY HIV info for Populations DIABETES REGISTRY Diabetes info for Populations IMAGING REGISTRY Imaging info for Populations
  • A low-cost alternative to current model:
    • Support provided by external applet
    • Applet invoked through Intranet hyperlink
    • Hyperlink opens applet in new window
    • Applet provides decision support
    • Applet saves data to its own database
    • User returns to Epic
  • Example: HIT Asthma Project
    • Java Applet, called e-AAP, provides administrative & clinical decision support*
    • Invoked from Epic:
      • Create new Asthma Action Plan (procedure order)
      • View existing Asthma Action Plan
        • from Order Results
        • from asthma detail in problem list
    • Invocation sends @ 20 encrypted live Epic data elements to applet through URL
    • New asthma data saved to SQL server database
    * Support based on NAEPP-3 Guidelines, August 2007
  • e-AAP Clinical Decision Support:
    • For new asthma patients
      • Assess severity
      • Initiate treatment given age & severity
    • For currently treated asthma patients
      • Assess control
      • Modify treatment given age, control, current treatment, pt adherence
        • Step-based treatment
        • Supports user in calculating current step
  • e-AAP Administrative Support:
    • Document severity and/or control
    • Generate printable asthma action plan
      • Patient-specific
      • Patient-friendly (tested for literacy)
      • Records all JHACO-required data
    • Document production of AAP
    • Generate:
      • Template of asthma progress note that user can paste into patient’s chart
      • List of selected meds & instructions for use
  • Launched as procedure order in Epic: Highlighted data transferred in URL. Clicking here launches applet..
  • Live data passed to Applet in URL: Web link defined by print group Launches web browser with “garbled” pt data in URL
  • Linking code required: Cache routine: Delivers hyperlink Cache global: Provides configuration
  • 1 st screen user sees: User automatically logged in; audit trail initiated; patient data transferred directly from Epic.
  • Applet generates data. Where do they go?
    • Individual patient data:
      • Saved to underlying database
      • Applet generates asthma progress note that doc can paste into record
    • Population data:
      • All Applet data stored to underlying registry
      • Clarity data extracted & merged with Applet data in registry
  • Clarity Information for Populations Epic Information for Individual Patients ASTHMA APPLET Asthma info for Individual patients ASTHMA REGISTRY Asthma info for Populations Patient & user context thru URL Individual pt data: Saved to SQL server database (registry)
  • Clarity Information for Populations Epic Information for Individual Patients ASTHMA APPLET Asthma info for Individual patients ASTHMA REGISTRY Asthma info for Populations Patient & user context thru URL Population data: Relevant data extracted from Clarity, merged with Applet data in registry
  • Clarity Information for Populations Epic Information for Individual Patients ASTHMA APPLET Asthma info for Individual patients ASTHMA REGISTRY Asthma info for Populations Patient & user context Decision Support & Epic: Alternative model
  • How are applet data retrieved?
    • Individual patient data:
      • Previously created e-AAPs easily found & reviewed from Applet.
      • If user pasted asthma progress note, available in EHR.
    • Population data:
      • Extracted from underlying registry
      • Registry populated with Applet data and relevant data from Clarity
  • To view individual pt data: To see previous AAPs, user clicks here
  • Pop-up appears: User clicks on desired PDF
  • Hyperlink opens applet:
  • Clarity Information for Populations Epic Information for Individual Patients ASTHMA APPLET Asthma info for Individual patients ASTHMA REGISTRY Asthma info for Populations Patient & user context thru URL To view population data:
  • Clarity Information for Populations Epic Information for Individual Patients ASTHMA APPLET Asthma info for Individual patients Imaging Applet Imaging info for Individual Patients ASTHMA REGISTRY Asthma info for Populations Imaging Registry Imaging info for Populations Patient & user context Patient & user context Multiple such registries possible:
  • Clarity Information for Populations Epic Information for Individual Patients ASTHMA APPLET Asthma info for Individual patients Imaging Applet Imaging info for Individual Patients ASTHMA REGISTRY Asthma info for Populations Imaging Registry HIV info for Populations Patient & user context Patient & user context ASTHMA REGISTRY Asthma info for Populations Alternate model and data warehousing:
  • EHR Data Repository Information for Populations Local EHR Information for Individual Patients ASTHMA APPLET Asthma info for Individual patients HIV APPLET HIV info for Individual Patients Patient & user context Patient & user context IMAGING REGISTRY Imaging info for Populations ASTHMA REGISTRY Asthma info for Populations Alternate model and data warehousing: Imaging Applet HIV info for Individual Patients
  • Imaging Applet HIV info for Individual Patients EHR Data Repository Information for Populations Local EHR Information for Individual Patients ASTHMA APPLET Asthma info for Individual patients Patient & user context Patient & user context No major interface to build or maintain! ASTHMA REGISTRY Asthma info for Populations Imaging Registry Imaging info for Populations interface engine interface engine
  • ASTHMA REGISTRY Asthma info for Populations HIV REGISTRY HIV info for Populations STENT REGISTRY Stent info for Populations DIABETES REGISTRY Diabetes info for Populations IMAGING REGISTRY Imaging info for Populations COLONOSCOPY REGISTRY Colonoscopy info Populations Maybe we can!
  • Questions? Project supported by the Agency for Health Research and Quality . Contract No. HHSA290200600020, Task Order No. 5 The findings and conclusions are the responsibility of the authors, not the AHRQ. Clinical informatics at HCMC: Dr. Kevin Larsen ( [email_address] ) Invoking applet from Epic: Dr. Robert Grundmeier ( [email_address] ) Asthma details about applet: Dr. Gail Brottman ( [email_address] ) Project direction & all other Qs: Yiscah Bracha, MS ( [email_address] )
  • Extra Slides
    • URL to live application demo
    • Why not build in Epic
      • Logical complexity
      • Volume of clinical material
  • Why not build it in Epic?
    • Logical complexity
      • Existence of relevant data
      • Validity of relevant data
      • User choices
      • Patient age, adherence
    • Volume of up-to-date clinical info required
      • @37k med combos in guidelines
      • Guidelines contain @ 2% of all possibilities
  • e-AAP: High-level process flow: Disease mgmt component
  • Disease management component:
  • Treatment decisions in guidelines:
  •  
  • Treatment data in Applet:
  •