Workflow Analysis in Healthcare Lauren Gray, BSN RN October 7, 2015.

Slides:



Advertisements
Similar presentations
1 Using Root Cause Analysis to Reduce Hospital Readmissions Jennifer Wieckowski, MSG Health Services Advisory Group of California, Inc. (HSAG-California)
Advertisements

McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 15 Creating Collaborative Partnerships.
Hospital Information System (HIS) Stakeholder Consultation
Overview of Nursing Informatics
7 Chapter Management, Leadership, and the Internal Organization
SESSION 10 MANAGING KNOWLEDGE FOR THE DIGITAL FIRM.
Unit Five – Transforming Organizations
® Problem Solving for Root Cause Analysis An overview for CLARION Case Competition 2009 Presented by: Sandra Potthoff, Ph.D. Director of Program in Healthcare.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
Contextual Design. Purpose for us An example A term often used, with varying levels of precision.
Creating Collaborative Partnerships
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Slide 1 1 Critical Thinking and Nursing Judgment NPN 105 Joyce Smith RN, BSN.
Vision of how informatics enables a transformed health system Joyce Sensmeier MS, RN-BC, CPHIMS, FHIMSS, FAAN Vice President, Informatics, HIMSS President,
© 2009 Public Health Informatics Institute Multi-State Learning Collaborative September 17, 2009.
Engineering Design Process ETP 2005 – Brian Vance This material is based upon work supported by the National Science Foundation under Grant No
CHAA Examination Preparation Future Development – Session II Pages University of Mississippi Medical Center.
Use of OCAN in Crisis Intervention Webinar October, 2014.
Component 10 – Fundamentals of Workflow Process Analysis and Redesign Unit 10 – Process Change Implementation and Evaluation This material was developed.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Quality Directions Australia Improving clinical risk management systems: Root Cause Analysis.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 12.
Research in Computing สมชาย ประสิทธิ์จูตระกูล. Success Factors in Computing Research Research Computing Knowledge Scientific MethodAnalytical Skill Funding.
Quality Improvement Workflow Design Lecture a
Chapter 7: Project Human Resource Management IT Project Management, Third Edition Chapter 9 1.
© Joint Commission Resources Module 4 Re-Engineering Patient Discharge: The Hospital Launch! Faculty from Joint Commission Resources Deborah M. Nadzam,
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Allison Bloodworth, Senior User Interaction Designer, Educational Technology Services, University of California - Berkeley October 22, 2015 User Needs.
Component 2: The Culture of Health Care Unit 9: Sociotechnical Aspects: Clinicians and Technology Lecture 1 This material was developed by Oregon Health.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 6 Duplication.
On-Time Prevention Program for Long Term Care: Clinical Decision Support On-Time Prevention Program for Long Term Care: Clinical Decision Support William.
Design of Work for Patient Safety Pascale Carayon, Ph.D. Procter & Gamble Bascom Professor in Total Quality Department of Industrial and Systems Engineering.
Human Computer Interaction
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
To branch, or not to branch, that is the e-learning question With Dan Richards, Interactive Advantage Corp. To be, or not to be, that is the question:
Unit 7.2: Work Process Flow Chart Safe Workflow Design 1Component 12/Unit #7 Health IT Workforce Curriculum Version 1.0/Fall 2010.
CRITICAL THINKING AND THE NURSING PROCESS Entry Into Professional Nursing NRS 101.
Fundamentals of Workflow Analysis and Process Redesign Unit Process Change Implementation and Evaluation.
New Supervisors’ Guide To Effective Supervision
Software Engineering Principles Practical Advice and Steps for Managing Your Project.
Learning Outcomes Discuss current trends and issues in health care and nursing. Describe the essential elements of quality and safety in nursing and their.
Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation ISE
Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification.
IT-465 Introduction to Lean part Two. IT-465 Lean Manufacturing2 Introduction Waste Walks and Spaghetti Charts Outcomes Understand what a waste walk is.
Ethnographic Interviews: Interviewing and Observing Users Project: Investigating Sakai 3 Capabilities to Support Learning Activities Jacqueline Mai 10/20/09.
Unit 8a: The Implementation Team HIT Implementation Planning for Quality and Safety This material was developed by Johns Hopkins University, funded by.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 15 Creating Collaborative Partnerships.
TECHNICAL WRITING 2013 UNIT 3: DESIGNING FOR CHANGE PART 2.
The Culture of Healthcare Healthcare Processes and Decision Making Lecture a This material (Comp2_Unit4a) was developed by Oregon Health & Science University,
Patricia Alafaireet Patricia E. Alafaireet, PhD Director of Applied Health Informatics University of Missouri-School of Medicine Department of Health.
Presentation By: Leaniza F. Igot-Scheir, RN Clinical Nursing Information System First Sem Chapter 20: Practice Applications Chapter 20 by Joyce.
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
WHAT IS PROBLEM-BASED LEARNING? What is PBL? Problem Based Learning (PBL) is a teaching method utilizing case studies and group interaction. Students.
High Impact Leadership –Safety First Understanding The System, its Influence on Patient Safety and The Leadership Framework to Manage it Successfully David.
User-centered approaches to interaction design By Haiying Deng Yan Zhu.
MIS Project Management Instructor: Sihem Smida Project Man agent 3Future Managers1.
Linda Searle Leach, PhD RN, NEA-BC, CNL, UCLA School of Nursing
Chapter 33 Introduction to the Nursing Process
Fundamentals of Workflow Analysis and Process Redesign
Problem Solving Sheet Guidelines
Fundamentals of Information Systems, Sixth Edition
How does a Requirements Package Vary from Project to Project?
Purpose for Curriculum Mapping
Chapter 16 Nursing Informatics: Improving Workflow and Meaningful Use
NUR 482 Enthusiastic Studysnaptutorial.com
Background & Motivation
Chapter 1 Introducing Quality Improvement
Informatics 121 Software Design I
Introduction to Quality Improvement Methods
Presentation transcript:

Workflow Analysis in Healthcare Lauren Gray, BSN RN October 7, 2015

Objectives Workflow analysis terminology Common approaches to workflow analysis Workflow analysis tools Applicability to Health/Clinical/Nursing Informatics

Workflow Terms Current State Future State Inter-organizational workflow: Includes processes occurring across organizations such as hospitals and ambulatory clinics Intra-organizational workflow: Can include the flow of workers, patients, and information across space and time in a department as well as the interdependencies of tasks carried out Individual workflow: aka, “cognitive”. Refers to a person’s flow of thoughts related to a task. (Karsh, 2009)

Common Approaches Information/Computer Science – Petri-nets use workflow management systems to gather data re: events and model the work (organizational) – Contextual Design 3 phases: Contextual Inquiry, Work Modeling, Consolidation Purpose is to uncover 4 aspects of work that are relevant to design: Motive behind th etasks, patterns used in carrying out tasks, structure in place that enables task accomplishment, conceptual distinctions between aspects of work. (organizational & individual)

Common Approaches Computer-Supported Cooperative Work – Begun by technology developers in an effort to understand the activities of groups engaged in collaborative work activities – Guided by two theories Activity Theory: human beings engage in purposeful interactions (activities) that are goal-directed and context- specific Coordination Theory: task-interdependencies among workers that result in harmonious goal-achievement – Useful for examining workflow within and across organizations. It would not be useful for understanding individual workflow.

Common Approaches Computer-Supported Cooperative Work – Begun by technology developers in an effort to understand the activities of groups engaged in collaborative work activities – Guided by two theories Activity Theory: human beings engage in purposeful interactions (activities) that are goal-directed and context- specific Coordination Theory: task-interdependencies among workers that result in harmonious goal-achievement – Useful for examining workflow within and across organizations. It would not be useful for understanding individual workflow.

Common Approaches Cognitive Science: interested in understanding human thought processes including knowledge attainment, memory and problem solving Organizational Science: aimed at clarifying internal structures within organizations for the purpose of influencing change and directing process re-design.

Common Approaches Computer-Supported Cooperative Work – Begun by technology developers in an effort to understand the activities of groups engaged in collaborative work activities – Guided by two theories Activity Theory: human beings engage in purposeful interactions (activities) that are goal-directed and context- specific Coordination Theory: task-interdependencies among workers that result in harmonious goal-achievement – Useful for examining workflow within and across organizations. It would not be useful for understanding individual workflow.

How Do You Choose? On the requirements and goals of the project On the setting On the people doing the work Any analysis is better than no analysis

Why workflow analysis? Where are we? Where do we want to be? What do we need to do to get there? How do we know if we’re successful? Reinforce training Mangers & users will use as reference

Tips Multidisciplinary teams Staff who actually does the work Don’t rely on the vendor Assign responsibility (Project Manager, Data Steward, other point person)

Example: Analysis Make the workflow fail! – FMEA (Failure Modes Effects Analysis) – Root Cause Analysis – Spaghetti diagrams Evaluate how to address each failure

Example: Analysis Make the workflow fail! – FMEA (Failure Modes Effects Analysis) – Root Cause Analysis – Spaghetti diagrams Evaluate how to address each failure

Example: Analysis Make the workflow fail! – FMEA (Failure Modes Effects Analysis) – Root Cause Analysis – Spaghetti diagrams Evaluate how to address each failure

Example: Current State Describe workflow – Multiple people – Find variations Watch the workflow Document the workflow – Exhaustively! Be annoying! – Visio, markers & paper, Word/Pages, mind mapping software – Screen capture: SnagIt, Snipping tool

Example: Analysis Make the workflow fail! – FMEA (Failure Modes Effects Analysis) – Root Cause Analysis – Spaghetti diagrams Evaluate how to address each failure

Example: Future State Document new workflows including the fixes & changes Run through the Current State steps to test them out

Good Questions to Ask What IS the process? Are there important patient care processes that do not involve seeing a patient? What are the steps involved? What are the variations to these processes? Are there acceptable reasons for process variations by clinic site? Who completes the process? How long does it take? Where are the bottlenecks? Is there repetition in the work? Is there potential for confusion or misunderstanding?

Can be relatively simple…

Or can make you feel crazy… (and this one is the “High Level” version…)

Why document like a crazy person? Shows where sequence is critical Shows bottlenecks & interruptions Identifies opportunities & waste Helps create solutions to issues Takes advantage of automation provided by the EHR

What happens if we don’t do good workflow analysis?

Questions?

References California Healthcare Foundation (2011). Workflow analysis: EHR deployment techniques Karsh BT. In: Clinical practice improvement and redisign: How change in workflow can be supported by clinicial decision support.Quality AfHRa, editor. Rockville, Md: p. 42. Duffy, J. (2013). Get organized: Document your workflow., May 13, Sheehan, B., & Bakken, S. (2012). Approaches to Workflow Analysis in Healthcare Settings. NI 2012: Proceedings of the 11th International Congress on Nursing Informatics, 2012, 371.