The Critical Importance of Executable Model Of EHR Workflow: Process-Aware HIT

Warning: fopen(himss16-tepr-toc.txt) [function.fopen]: failed to open stream: No such file or directory in /home/content/41/4031141/html/000websites/wareflo/wp-content/plugins/allow-php-execute/allow-php-execute.php(13) : eval()’d code on line 3

Warning: filesize() [function.filesize]: stat failed for himss16-tepr-toc.txt in /home/content/41/4031141/html/000websites/wareflo/wp-content/plugins/allow-php-execute/allow-php-execute.php(13) : eval()’d code on line 4

Warning: fread(): supplied argument is not a valid stream resource in /home/content/41/4031141/html/000websites/wareflo/wp-content/plugins/allow-php-execute/allow-php-execute.php(13) : eval()’d code on line 4

Warning: fclose(): supplied argument is not a valid stream resource in /home/content/41/4031141/html/000websites/wareflo/wp-content/plugins/allow-php-execute/allow-php-execute.php(13) : eval()’d code on line 5

At the heart of an EHR workflow management system is the workflow or process definition, which is used by a workflow engine to drive EHR behavior. For example, in Figure 2, applying the Workflow Reference Model to an ambulatory context, we see on the left a process definition. In this case, the process definition drives the se- quence of screens presented to two members of the ambulatory team, to the nurse and then to the physician: (1) Get Patient, (2) Take Vital Signs and a Chief Complaint, (3) Review Allergies, (4) Review Medications, (5) Examination, (6) Assessments, (7) Orders, (8), Evaluation and Management code generation, and (9) Billing Approval.

On the right is a process instance, sometimes referred to as a case. This is the actual patient encounter. To use an analogy, if the list on the left is a recipe, then the list on the right is the actual cake!

business-process2

Workflow management systems have workflow or process definition tools. These are graphical editors that al- low a non-programmer to define or modify EHR workflow, in effect, to program or debug EHR workflow be- havior. Figure 3 depicts one such tool. (By the way, this gives rise to a litmus test: if an EHR purports to be an EHR workflow management system, ask to see the process definition tool. While it may not look exactly like Figure 3, it should allow changes in a process definition used by the workflow engine to drive EHR behavior.) In this case, the process definition saves the user from having to navigate manually through a thicket of menus, tabs, or popup lists; the EHR presents the correct screen given the context of the user’s tasks.

Process definitions are used by the workflow engine in a similar way to rules being used by an expert system. The workflow engine reasons about who, what, why, when, where, and how in order to save the user work. Who is the user? (Dr. Jones or Dr. Smith?) What is their role in the office? (Physician, nurse, technician?) Why is the patient here? (Well child? Chronic disease management?) When is “now”, relative to what has been accomplished and what remains? Where is the user? (Exam room? Tech station?) How does this specialty accomplish its tasks?

Each step in the process definition corresponds to a specialized data presentation, acquisition, or transformation task. The process definition describes the event that triggers the presentation of the screen as well as a context that informs its content and behavior. For example, the Review of Systems screen allows the nurse to do just that, review the patient’s systems. It is triggered by the completion of the preceding screen (or by the nurse log- ging into the EHR in the exam room in the presence of the patient after all the preceding tasks in the process definition have been accomplished).

Note, however, that the process definition does not merely drive a sequence of screens with respect to a single user; rather, it drives a sequence of activities, some visible as screens, others not (printing, messaging, and so on) across a team of users occupying a variety of roles (nurse, tech, specialty provider). There are many such screenless tasks, such as printing patient materials, automatically inserting a work item into a worklist, or communication with other applications such as devices (ECG, vitals), intra-office programs (billing, patient inter- view), or communicating with the outside world (laboratory, e-prescribing).

Thus, EHR workflow management systems offer means to integrate applications with applications (such as communication from scheduling to patient charting and order entry and then on to billing, or between a medical device and the EHR), integrate applications with users (such as retrieving data from already existing systems), and integrate users with users (as in this example, in which the nurse’s tasks precede the physician’s tasks and information is forwarded from the nurse to the physician—in a more complex and realistic scenario, the physi- cian might delegate additional tasks to the nurse and monitor them.)


Warning: fopen(himss16-tepr-end.txt) [function.fopen]: failed to open stream: No such file or directory in /home/content/41/4031141/html/000websites/wareflo/wp-content/plugins/allow-php-execute/allow-php-execute.php(13) : eval()’d code on line 31

Warning: filesize() [function.filesize]: stat failed for himss16-tepr-end.txt in /home/content/41/4031141/html/000websites/wareflo/wp-content/plugins/allow-php-execute/allow-php-execute.php(13) : eval()’d code on line 32

Warning: fread(): supplied argument is not a valid stream resource in /home/content/41/4031141/html/000websites/wareflo/wp-content/plugins/allow-php-execute/allow-php-execute.php(13) : eval()’d code on line 32

Warning: fclose(): supplied argument is not a valid stream resource in /home/content/41/4031141/html/000websites/wareflo/wp-content/plugins/allow-php-execute/allow-php-execute.php(13) : eval()’d code on line 33

For more on the incredible value of executable models of healthcare workflow, see my BPM-based Population Health Management & Care Coordination: Workflow, Usability, Safety & Interoperability Perspectives.

Take me to the next blog post in this series! Different Versus Same Person Versus Time EHR Workflow: Process-Aware HIT.

Leave a Reply

Your email address will not be published. Required fields are marked *