(This is a full-text transcription of one slide from my November 5th 42-minute webinar on Ebola and EHR Workflow Engines, Editors, and Visibility. Please excuse occasional “typos” as I’ve not proofed every word. Consider watching the Youtube video or going to first slide in this transcribed series. My original post announcing the webinar includes motivating context and an outline. Thank you!)
Down here, we have the work plans, which are the workflow definitions, contain the required tests for specific conditions, so they’re not forgotten. They’re not forgotten, because when they are cued up, they don’t go away. You see them in the office view and they hang around. The patients can’t leave until they are either accomplished or dismissed for a good reason. Now we’ve come to the conceptual core of what I’m talking about. I like to talk about the power of process, the power of executable process models. In the middle here, we have models of work, models of workflow that are executable, that are mechanically consultable in order to help the users. In the middle, we have this IO model version and here we have the pick list kind of version, which is patient go to exam room, ask about meds, ask about allergies, collect some vital information.
It moves on to the physician and to the billing. You may have seen this little colorful gadget right here. This is the workflow, the red corresponds to clinical assistants and where vitals, meds, allergies and down here, blue corresponds to the physician; exam, assessment and treatment. Green here, makes sense, is billing and the happy path is all these black arrows and the exceptions are the red arrows and this model is probably only a third or a fourth as many of actual workflow task states in a sophisticated ambulatory, but I think it illustrates.
This model is something that’s in between the computer and the workflow engine, but it could be understood and executed. Over here, we have someone who isn’t a programmer who could understand that workflow and change it. This is the layer that’s missing in most traditional electronic health record documentation systems today. They are documentation systems, they are not workflow systems.
- Transcribed Slides For My 42-Minute Webinar on Ebola, EHR Workflow Engines, Editors, and Visibility
- Outline: Ebola, EHR Workflow, Workflow Tech, Workflow Engines, Editors, and Visibility
- “Poke the workflow bear” Refers To Mentioning Me On Twitter!
- Dallas Hospital Blames Flaw In Workflow For Release of Ebola Patient, Then Retracts
- Ebola Workflow, Nurse Workflow, Physician Workflow, EHR Workflow: Part 1
- EHR Workflow Is A Series Of Steps, Consuming Resources, Achieving Goals
- EHR Workflow System, Like OR Nurse, Hands Right Screen to Right Person At Right Time
- EHR Workflow Engine Executes EHR Workflow Definition, Performing Work For EHR Users
- EHR Workflow Driven By Workflow Engines Consulting Workflow Definitions Created By Non-Programmer EHR Users
- Not There Yet, But Physicians Will Design EHR Workflows Dragging And Dropping Tasks
- Classic EHR Workflow Definition Editor Looks Like Traditional Visio Flowchart
- EHR Airport Control Towers, Automobile Engines, And Aviation Cockpits: Analogies & Metaphors
- EHR Workflow Tech Enables Smart Sequences And Simultaneous Actions
- EHR Tasks Much More Visible Because Workflow Engine Tracks Task Status
- Staff Prepare For Procedures Without Being Told, EHR Workflow System Coordinates
- EHR Screen At A Time, Only Relevant Data, Tweakable Workflow, Key Tests Not Forgotten
- Healthcare Needs Executable Process Model Between Clinicians And Data
- Hospitals Need Executable Process Model Betweet Human Workflow And Computer Data
- Rebranding Business Process Management For Healthcare
- Ebola Workflow, Nurse Workflow, Physician Workflow, EHR Workflow: Part 2
- “It’s really made my life much easier and the staff love it!” 2004 HIMSS Davies EHR Winner
- Thank You! Questions About EHR Workflow Engines, Editors, and Visibility? Slide 22 and Notes
