The Critical Difference Between Workflow Management Versus Mere 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

Workflow Management Versus Mere Workflow

Van der Aalst and van Hee [1] describe an evolution of information systems that can be profitably applied to the evolution of the EHR as well. First were collections of separate applications, each with its own database; then applications began to share a common database. Each application had its own user interface; then applications shared a common look and feel and, increasingly, context as well. Finally, workflow-related business logic moved into workflow management systems, which managed application workflow. In short, data, user interface, and now workflow have migrated or are migrating out of healthcare applications and into shared databases, user interface resources, and workflow management systems.

A workflow management system is a software application that stores and executes workflow or process definitions to create and manage workflow processes while facilitating interactions among users and applications [1, 2]. “Workflow” and “workflow management” (and by extension, “workflow systems” and “workflow management systems”) are frequently confused and this is naturally so. Users usually interact with workflow systems, not the workflow management systems used to implement them. However, it is the underlying workflow management system that allows a workflow system to be flexibly tailored to local processes and user preferences, and to be easily monitored and maintained.

A useful analogy can be made between a database management system and a workflow management system. A database usually comes with a database management system that is used to execute and manage it. The database management system creates, executes, monitors, and edits the database, but is not itself the database. During database execution, users and applications create, update, and delete data. Similarly, a workflow management system creates, executes, monitors, and edits a workflow system, but is not itself a workflow system. The main advantage to EHR users of getting both a workflow system and a workflow management system—together—is that they can further customize the EHR workflow system to reflect their clinical needs, personal preferences, and business requirements.

At this moment when the EHR can benefit so much from workflow management system technology, the EHR can also benefit from the model of how the workflow management system industry has developed during the past decade. In both cases, WfMSs then and EHRs today, there existed or exists a software application that had or has great potential to increase the effectiveness and efficiency of core processes as well as increase the satisfaction of those engaged in making those core processes happen. While there was and is great opportunity, there was and is uncertainty. There was no standard model of application functionality and no standard terminology for discussion, education, and planning. So, the Workflow Management Coalition helped to define a standard model of workflow management, the Workflow Reference Model [2] (Figure 1 represents relationships among important terminology).

This Workflow Reference Model described a common vocabulary about workflow, a workflow management architecture that was technology and vendor neutral, and key interfaces that required standardization.

business-process1

The Workflow Reference Model is reminiscent of the electronic health record reference model being defined today. So, it is natural to connect these two efforts when presenting the concept of electronic health record workflow management systems. In fact, a recent paper examining the legacy of the original reference model concludes by saying that the core legacy may be that “it has provided a common framework for people to think about Workflow and BPM (Business Process Management) and ten years of fascinating discussions!” [3] I hope and believe the same will be true of electronic health record workflow management systems, too! (By the way, there remains a residual of terminological variation, such as process definition versus workflow definition.)




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 30

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 31

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 31

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 32

For further exploration of the difference between a workflow system and a workflow management system, see my Confusing Workflow Technology With Workflow Is Like Confusing Your Database With Your Data.

Take me to the next blog post in this series! The Critical Importance of Executable Model Of EHR Workflow: Process-Aware HIT.

Leave a Reply

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