1 / 22

Health IT Hazard Manager: Design & Demo

HIT Hazard Manager. James M. Walker, MD, FACP; Principal Investigator, Geisinger Health System Andrea Hassol, MSPH; Project Director, Abt Associates September 19, 2011. Health IT Hazard Manager: Design & Demo. Hazard Control. Hazard analysis is accident analysis

ziarre
Download Presentation

Health IT Hazard Manager: Design & Demo

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HIT Hazard Manager James M. Walker, MD, FACP; Principal Investigator, Geisinger Health System Andrea Hassol, MSPH; Project Director, Abt Associates September 19, 2011 Health IT Hazard Manager: Design & Demo

  2. Hazard Control Hazard analysis is accident analysis before the accident happens. Nancy Leveson

  3. HIT Hazard Manager version 1.0 Beta Test • Background and Purpose • Hazard Manager Demo • Beta Test Sites and Procedures • Preliminary Findings • Next Steps

  4. Health It Hazard Manager Development and Alpha-Test: Geisinger Health System Beta Test Website Implementation: ECRI Patient Safety Organization; Abt Associates Beta Test Evaluation: Abt Associates; GeisingerHealth System

  5. The Contribution of HIT-related Hazards to Patient Harm No Adverse Effect Patient Harm ”Un-Forced” HIT-use Error Interaction between HIT and other healthcare systems. Care Process Compromise? Identifiable Patient Harm? Error in HIT design or implementation No Adverse Effect ”Forced”HIT- use Error HIT-Related Hazard Hazard Identified? HIT-related Hazard Near Miss Hazard Resolved? No Yes Yes No Yes Yes No No

  6. Hazard Control Near Miss No Adverse Effect Patient Harm Identifiable Patient Harm? Error in HIT design or implementation ”Un-Forced” HIT-use Error Hazard Control Interaction between HIT and other healthcare systems. HIT-Related Hazard Care Process Compromise? “Hazard Identified? No Yes Yes “Hazard Resolved? “No Adverse Effect No “Hit-related Hazard Yes Yes “”Forced” HIT-use Error No No

  7. No Adverse Effect Feeding Back Incident Reports into Hazard Control Identifiable Patient Harm? “”Un-Forced” HIT-use Error ”Forced”” HIT-use Error Hazard Resolved? HIT-related Hazard Care Process Compromise? Hazard Identified? Patient Harm No Adverse Effect Near Miss Interaction between HIT and other healthcare systems. Safety incident reports HIT-Related Hazard Error in HIT design or implementation No Yes Yes No Yes Yes No No

  8. Health It Hazard Manager Levels of Access (Security) 1. Health Care Organization: can enter, view and manage its own hazards; view hazards entered by other HCOs using the same software product (deidentified as to HCO) 2. Software Vendor: can view its customers hazards (deidentified as to HCO) 3. Policymakers, Researchers, Regulators: can view all hazards (deidentified as to HCO and vendor)

  9. Health It Hazard Manager Ontology of Hazards Discovery: when, how and who discovered the hazard; stage of discovery Causation: usability, data quality, software design, hardware, clinical decision support, implementation, user factors, other organizational factors Impact: risk and impact of care process compromise; seriousness of patient harm Corrective Action: interim and definitive fix, urgency

  10. Health It Hazard Manager Beta Test – version 1.0 7 test sites: integrated delivery systems, large and small hospitals, urban and rural • Usability • Usefulness • Ontology of hazard attributes • Automated Reports • Inter-rater Reliability 4 vendors

  11. Beta Test Preliminary Findings • An individual’s role determines what hazards they become aware of: • IT Implementation teams learn about potential hazards during testing • IT Production teams learn about hazards that may compromise care processes • Patient Safety teams learn about care process compromises that reach patients (with or without harm) • Hospitals have separate IT issues and patient incident reporting systems - are not explicitly designed for hazard identification - but can help teams identify hazards

  12. Beta Test Preliminary Findings • Failures to control hazards are often labeled “User Error”. The Hazard Manager supports more hazard control and less “blame the user”. • “Harm” is often limited to physical injury. The Hazard Manager raises awareness about psychological, financial and reputational harm. • Each causation category includes an “other specify” option to elicit additional user insights; the ontology will evolve over time to capture additional attributes of Health IT hazards.

  13. Project Schedule Beta Test data collection complete, October, 2011 Data analysis, November - December 2011 All sites project meeting, December 2011 Final Report, May 2012 Software revised, May 2012

  14. Questions? Comments? For more information: andrea_hassol@abtassoc.com

More Related