The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC.

Slides:



Advertisements
Similar presentations
Where do we go from here? We understand what RCA is and how to facilitate an RCA…..now what? We understand what RCA is and how to facilitate an RCA…..now.
Advertisements

Configuration management
The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC.
SPL/2010 Test-Driven Development (TDD) 1. SPL/
Facilitating the UCO Action Project Process – Part 4 Analyzing Data – Office of Planning & Analysis University of Central Oklahoma.
5 Why’s Overview.
A3 Training Session. Introduction…. We all are involved in… – Looking for ways to save resources – Finding ways to improve quality – Fixing problems –
A3 PROBLEM SOLVING TOOL: Date: Contact: SOLUTIONS / COUNTERMEASURES What solutions will solve the root causes? (Tools: Brainstorming and Affinity Diagram)
Title: The title should accurately describe the issue to be addressed and can never contain a proposed countermeasure. Overview Note: Remember that the.
PHD Performance Management Program Matt Gilman Spencer Soderlind Brieshon D’Agostini September 28, 2011 PDCA Training Series 2 PLAN, Part 2.
System Planning (Preliminary Investigation Overview)
1 Using Root Cause Analysis to Reduce Hospital Readmissions Jennifer Wieckowski, MSG Health Services Advisory Group of California, Inc. (HSAG-California)
ISHIKAWA DIAGRAM – Tool for quality management Marit Laos IS Project Management
Systems Analysis and Design 9th Edition
PHD Performance Management Program Matt Gilman Spencer Soderlind Brieshon D’Agostini October 19, 2011 PDCA Training Series 2 DO 1.
Problem Solving. What is Problem Solving? “higher-order cognitive process that requires the modulation and control of more routine or fundamental skills”
Root Cause Analysis Presented By: Team: Incredibles
Computers: Tools for an Information Age
Effective Problem-Solving: Getting to the Heart of the Matter © Copyright 2011– Lean Homecare Consulting Group, LLC This presentation is distributed for.
MEDICAL RECORDS MANAGEMENT IN EYE CARE SERVICES
Chapter 7: Control Charts For Attributes
Fishbone (Ishikawa) Diagram Fishbone (Ishikawa) Diagram Purpose: to identify all of the possible factors that contribute to a problem, [also called the.
Root Cause Analysis: Why? Why? Why?
Training.
How to Implement, Process and Administer the Preventive Action Process
Six Sigma By: Tim Bauman April 2, Overview What is Six Sigma? Key Concepts Methodologies Roles Examples of Six Sigma Benefits Criticisms.
WE  Cooperation WE  Cooperation  Problem Solving WE
Overview of Total Quality Tools
Chapter 27 Additional Analysis Methods. Objectives Use various tools and techniques to compare current and future states in terms of pre defined metrics.
What are the Benefits? Action AKA TPM, Total Preventative Maintenance Total Productive Maintenance Breakdowns 1 Setup / adjustment 2 Idling / minor stoppages.
Cooperation, Problem Solving, & Team Building WE
Root Cause Tutorial Page 1 More on Hazard Identification Techniques 1.Identify potential hazards that could threaten the safety of your employees,
DIRECTIONS Poster Board. Purpose You and a partner will create a poster board that demonstrates a standard from one of the three units that have been.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
Copyright © 2008 Pearson Education MathXL ® for School Teacher Training Series MathXL ® for School Overview.
Problem Solving.
Root Cause Analysis District 1 Membership
STEP 1: DEFINE THE PROBLEM Problem Statement: What is the problem? A problem is a discrepancy between a standard and the current situation. The ‘standard’
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
LORNA MARTIN CAH & SMALL RURAL LEARNING COMMUNITY APRIL 25, 2012.
PLUG IT IN 6 Project Management. 1.Project Management for Information Systems Projects 2.The Project Management Process 3.The Project Management Body.
The Essence of Lean: Connecting People, Process, and Purpose Helping Providers Elevate Performance SM © Copyright 2011– Lean Homecare.
GHA Hospital Engagement Network HAC Learning Collaborative Webinar ~ May 16, 2012 Kathy McGowan, GHA Kelley Dotson, GHA Anne Hernandez, A LLIANT | GMCF.
Improvement Model and PDSA Cycles. Organ Donation The Service Improvement Model provides a framework to test, implement and sustain change ideas to overcome.
Improvement Tools Interactive Lecture Tools Offer Assistance Understand the current state of a process Determine whether the process is in control Find.
Fishbone Diagram
Academic Strategies Unit 8 Professor Deidra Powell-Williams.
Problem Solving Skills
QI Tools to Diagnose HPV Vaccine Delivery Concerns in Your Practice
Traditional Economic Model of Quality of Conformance
EPMA- Learning from Serious Incidents STAT dosing Iain Davidson Chief Pharmacist Feb 16.
S D BELLAMY - Group Total Quality Manager - 22 August 2000 ( 5TH Revision - Health Version ) PDCA Problem Solving Guide A Guide to a Team Approach to.
MGT 561 Creative Problem Solving Osborn-Parnes Creative Problem Solving Process 1.Mess-finding 2.Fact-finding 3.Problem-finding 4.Idea-Finding 5.Solution-finding.
VISUAL AIDS May Jina Park.
3 Legged “5 Why” Root Cause Analysis
A Quick Review of the Components THE DMAIC CYCLE.
Working for healthier lungs The Whys and Whats of Care Bundles 23 November 2012.
5 Why analysis By its very nature, a Lean Six Sigma program requires a number of changes throughout the organization. That’s what we are trying to do right?
Learning Collaborative #1 March 2017
OSHE 421 Measurement of Safety Performance and Accident Investigation/Analysis Spring Semester, 2016 Instructor: Mr. Chris Kuiper, CSP
ROOT CAUSE ANALYSIS RCA
Data Driven Quality Improvement: Tools to Identify and Apply the Best Countermeasure to Facilitate Successful Change Grant M. Greenberg MD, MA, MHSA Jennifer.
PENYEBAB INSIDEN RCA2.
GETTING TO ROOT CAUSE / COUNTERMEASURES
CAUSE ANALYSIS CA
Root Cause Analysis: Why? Why? Why?
5 Why’s Overview.
CAPA, Root Cause Analysis, and Risk Management
Presentation transcript:

The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC. Pharmacy Process Improvement Series: The Five Whys – Identifying the Root Cause PlusDelta Technologies, LLC

The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC. Root Cause Analysis Tools Numerous tools available to assist with identification of root cause Fishbone (Ishikawa) charts Process mapping Failure modes effect analysis Statistical process control The 5 Whys

The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC. Process Improvement Tools The 5 Whys – Simple tool to identify root cause quickly – Originally made popular by Toyota Production System – Not a problem solving technique Problem Identify Root Cause Develop and Implement Corrective Action 5 Whys

The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC. Applying the 5 Whys Clearly state the problem – Difficult to identify root cause if problem is not clearly stated Ask “why” the problem happens and write down the answer Continue asking “why” to the previous answer until the problem’s root cause has been identified May help to visualize process (process mapping) to narrow down most likely sources for problem

The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC. The 5 Whys Benefits Allows the user or organization to: Quickly identifies those items that are symptoms of the problem versus the actual root cause of a problem Can be very effective, particularly when human factors are involved Easy to use and apply

The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC. Why 5? – The number at which most root causes are typically identified – Not always necessary or required to reach 5 Whys before a root cause is identified – May take more than 5 questions to fully explain root cause

The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC. 5 Whys – Pharmacy Example 1.Why was the patient re-admitted – Because he developed an infection postoperatively 2.Why did he develop an infection? – Because the antibiotic was not administered within one hour postoperatively 3.Why was the medication not administered within one hour postoperatively? – Because pharmacy didn’t deliver the medication on time Problem: The patient was readmitted to the hospital

The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC. 5 Whys – Pharmacy Example 4. Why did the medication not get delivered on time? – Because STAT medications are not properly identified in pharmacy workflow 5. Why are STAT meds not properly identified in pharmacy? – Pharmacy currently has no way to monitor STAT meds in real time within the order fulfillment process Root Cause

The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC. 5 Whys Failure 5 Whys will not always identify root cause If the 5 Whys fail to identify a root cause quickly, more sophisticated problem solving techniques may be necessary – Cause and Effect Analysis – Data Collection and Statistical Analysis – Affinity Diagrams – Process Capability Analysis

The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC. Operational Pearls Keep asking “why” until satisfied that there is no deeper cause that may be contributing Avoid stopping the line of questioning too early If “why” leads to multiple answers, pursue each answer separately Avoid blaming people. Faulty systems and processes are typically the culprit.

The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC. Thank You Thank you for joining us for this Pharmacy Process Improvement Webinar. Please view our other webinars on pharmacy process improvement, available at