2006 EHR WfMS Tutorial Slides 15-22: EMR EHR Usability Principles and Workflow: Introduction

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

These slides are from 2006, but this text is a mixture speaker notes from the 2004-2006 presentation plus more recent presentations, white papers, book chapters and blogs.

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:

“I am a fan of five EHR workflow usability principles:

  • Naturalness—is there a natural fit between EHR workflow and task work-flow?
  • Consistency—do similar activities have similar workflows?
  • Relevance—does the EHR not show you too much data or too many options?
  • Support—can you see, at a glance, all pending tasks and related information?
  • Flexibility—can you fix unnatural, inconsistent, irrelevant, unsupportive workflow?

I’ll quote from my 2004 MedInfo short paper here….

‘EHR workflow management systems are more usable than EHRs without work-flow management capability. Consider these usability principles: naturalness, consistency, relevance, supportiveness, and flexibility. EHR WfMSs more natural-ly match the task structure of a physician’s office through execution of workflow definitions. They more consistently reinforce user expectations. Over time this leads to highly automated and interleaved team behavior. On a screen-by-screen basis, users encounter more relevant data and order entry options. An EHR WfMS tracks pending tasks–which patients are waiting where, how long, for what, and who is responsible–and this data can be used to support a continually up-dated shared mental model among users. Finally, to the degree to which an EHR WfMS is not natural, consistent, relevant, and supportive, the underlying flexibil-ity of the WfMS can be used to mold workflow system behavior until it becomes natural, consistent, relevant, and supportive.’

[By the way, I wrote the ghost-wrote the referenced 2003 Advance for Health Information Management Executives article]

Let’s deal with these five workflow usability principles one by one. In each case we’ll nod toward cognitive science, but not drive into weedy details.”

wfms-usability-ehr-048

Five EMR EHR Workflow Usability Principles

  • Naturalness
  • Consistency
  • Relevance
  • Supportiveness
  • Flexibility

wfms-usability-ehr-0441

Past Emphasis
System Usability less emphasis than Info Value

wfms-usability-ehr-045

Current Emphasis
System Usability equal emphasis to Info Value

wfms-usability-ehr-046

Traditional Usability
Usability is the effectiveness, efficiency and satisfaction with which specific users achieve specific goals in specific contexts (based on ISO 9241-11 definition)

wfms-usability-ehr-047

Workflow Usability
Usability is the effectiveness, efficiency, and satisfaction with which teams of users achieve collections of goals in complex environments.

wfms-usability-ehr-049

Principles to Increase Usability

  • Naturalness
  • Consistency
  • Relevance
  • Supportiveness
  • Flexibility

increase

  • Learnability
  • Throughput
  • Satisfaction
  • (Patient Safety)

wfms-usability-ehr-050

Usability Examples

Bicycle MS Office EMR EHR UI EMR EHR Workflow
Naturalness
Consistency
Relevance
Supportiveness
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 135

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 136

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 136

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 137

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 147

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 148

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 148

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 149

Leave a Reply

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