2006 EHR WfMS Tutorial Slides 48-55: EMR EHR Usability Principles and Workflow: Flexibility

Warning: fopen(chuck-as-2004-tut.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 chuck-as-2004-tut.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

From Chapter 7: Natural Language Processing, Business Process Management, and Adaptive Case Management in Healthcare in How Knowledge Workers Get Things Done: Real-World Adaptive Case Management:

Business process management suites and adaptive case management systems are nothing if not flexible, compared to non-process-aware information systems. That said, BPM and ACM vendors frequently debate how to characterize flexibility and whose product is more (or less) flexible. For example, so-called traditional BPM systems are claimed to be flexible in the sense that processes are flexibly designed before execution. In adaptive case management systems, processes are more ad-hoc, flexibly directed and redirected during process execution. “Doing-by-design” versus “design-by-doing” captures the flavor of this debate. In any case, BPM and ACM systems have way more flexible workflows than most EHR and HIT systems. The importance? What if an EHR or HIT system is not natural, consistent, supportive and relevant? Then it needs to be flexible enough to allow users to create natural, consistent, supportive and relevant workflow. In other words, “Avoid frozen EHR workflow!”

wfms-usability-ehr-076

Flexibility

  • “capable of being changed”
  • “able to adjust to different conditions”
  • “easily shaped”
  • “designs that can adapt when external conditions change”

wfms-usability-ehr-077

The analogy to flexible customization of bicycle apparatus should be obvious. One does not need to go back to the bicycle manufacturing or assembly plant to adjust the position of a bicycle seat.

wfms-usability-ehr-078

Similarly, one does not need to go back to the C programmer to flexibly customize many aspects of a word processor.

wfms-usability-ehr-079

EHR Flexibility

  • Does EHR accommodate user differences: requirements, competence, preference?
  • Is it customizable at many levels: specialty, location, clinic, individual?
  • Can a user easily “program” the EHR without being a programmer?

wfms-usability-ehr-080

EHR Flexibility

  • Degree EHR can accommodate user requirements, competence, and preferences?
  • Unnatural, inconsistent, irrelevant, and unsupportive behaviors…
  • …need to be flexibly changed to become natural, consistent, relevant and supportive.
  • “Flexibly changed” means without requiring a programmer to change the code, a tester to look for bugs, a release to schedule, downtime, and a trainer to demonstrate the new feature

[add material about flexibility at design-time versus flexibility at run-time and the traditional BPM vs intelligent BPM/dynamic case management/adaptive case management debate]

wfms-usability-ehr-081

The next screen shot was animated. I grabbed individual intermediate animations from the 2004 tutorial below. The following comes from my speaker’s notes.

wfms-usability-ehr-031

Here is a visual aid. You can think of an electronic health record as having an inventory of activities. Some of these activities are screens–entering or reviewing data or entering orders. These screens are like a pack of cards. You can select a subset of these screens and screenless activities such as the printing of educational material into a process definition. This process definition then is executed by the workflow engine during an encounter.

024-1-process-definition-animation

Animation Step 1

025-2-process-definition-animation

Animation Step 2

026-3-process-definition-animation

Animation Step 3

027-4-process-definition-animation

Animation Step 4

028-5-process-definition-animation

Animation Step 5

029-6-process-definition-animation

Animation Step 6

030-7-process-definition-animation

Animation Step 7

Warning: fopen(chuck-as-2004-tut.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 110

Warning: filesize() [function.filesize]: stat failed for chuck-as-2004-tut.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 111

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 111

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 112

Related links:

EHR/EMR Usability: Natural, Consistent, Relevant, Supportive, Flexible Workflow

Warning: fopen(chuck-2004-2006-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 122

Warning: filesize() [function.filesize]: stat failed for chuck-2004-2006-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 123

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 123

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 124

Leave a Reply

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