Healthcare Design Thinking and Usability Need Engineering and Workflow

[Thank you to @HealthStandards and @uuability for hosting this week's #HITsm tweetchat on Usability Gaps in Health IT and prompting this blog post!]

Usability and design thinking are currently hot topics in health IT. They should be. In fact, they should have been for a long time. However, contrarian that I am, I have a bone to pick.

dog-bone-pick-workflow

But first, my bona fides. I started out as an engineering student, where I took not just traditional engineering courses, but courses in systems and engineering design. I transferred around a lot but eventually got a masters degree in Industrial Engineering, where I focused on human factors and workflow. One of my advisors wrote the first textbook on human-centered design.

The origin of design thinking is attributed to Herbert Simon’s seminal book The Sciences of the Artificial. I attended Simon’s lectures at Carnegie Mellon years ago (here is a blog post about how his ideas influenced me). I’ve talked design with Don Norman (and written about his mixed feelings toward user-centered design).

Over the years I’ve designed (and written code for) EHR software still in use today, as well as designed or “debugged” innumerable healthcare workflows relying on workflow technology.

The bone I have to pick? Design thinking and usability engineering don’t have enough engineering or workflow substance to be the success they might otherwise become. I am not alone in this assessment (Engineering as a Driving Force Behind the Design Thinking Movement).

One does not have to have an engineering degree to design usable products and systems. However, I believe, you do have to be able to do what engineers do — it is in fact intrinsic to our self identity — build stuff! I was an industrial engineer (now called systems engineering in healthcare), so I built workflows, not cool interactive robots like my mechanical and electrical engineer cousins. However, technology and society have so evolved since then that almost anyone can build stuff today, even cool interactive robots. So much so, that now, I too, build robots, using 3D printers, microprocessors, sensors, actuators, and software.

Users need to make the systems they use. In other words, users need to become creators, or Makers in popular parlance. In healthcare and health IT, this means designing, tweaking, and improving the workflow in which they are embedded.

But engineers can’t build something out of nothing using nothing. Engineers need tools with which and platforms on which to create. This is why I am a proponent of workflow technology. If you know your workflow, and you know how to use a computer, but are not yourself a programmer, then you can design your own health IT application workflow… if … health IT applications are themselves built on workflow platforms. Today these systems have various names, process-aware information systems, business process management, and case management systems. But many other IT platforms currently diffusing into healthcare and health IT also embed the most important characteristics of a process-aware information system, some sort of representation or model of work or workflow, plus some sort of engine to interpret the model. It is often called a workflow or process orchestration engine. Similar, by analogy, to how a software language interpreter interprets lines of code, a workflow engine interprets a description of workflow, to drive health IT software application behavior.

Given the above context (bona fides, plus philosophy and tutorial) here are my answers to this week’s #HITsm questions regarding health IT usability.

Topic 1: Why is usability in healthcare so important? #HITsm

Usability is important because safe, efficient, effective, satisfying workflows are important.

Topic 2: What are some common myths about usability and UX in HealthIT? #HITsm

The number one usability myth has to do with direction of causality. Systems don’t have good workflow because they are usable. They are usable because they have good workflow.

The number two usability myth is adding usability experts to workflow-oblivious software (read, “process-unaware”) can dramatically improve usability of that software. If you can’t change the workflow you can’t make it more usable (at least not dramatically so). There’s a major health IT vendor out there that proclaims their software is usable because they employ 300 usability professionals. Wow! They need 300 usability professionals… I wonder why? Again, please consult myth number one. Usability does not create workflow. Great workflow creates usability.

The number three usability myth is great workflow can be achieved without workflow technology. In other industry when there is a problem, say, pollution, you often see technology to fix or manage the problem named after the problem, as in pollution technology. Healthcare has a workflow problem. It requires workflow technology to fix or at least manage.

Topic 3: Has the ONC “Safety-enhanced Design” requirements helped or hurt the Usability of EHRs? #HITsm

Top-down usability certification hasn’t made much difference because it cannot make much difference, without the underlying health IT software in use become much more automatic, transparent, flexible, and improvable, in a workflow sense. Usability can’t cause these things. Usability is caused by these things. Unless and until health IT moves to more process-aware workflow platforms (which, BTW, is happening, though not fast enough), these sorts of efforts are doomed to frustrate all involved.

Topic 4: What are some additional areas (gaps) in usability of EHRs? #HITsm

Lack of use of workflow thinking and workflow technology.

Topic 5: Medical mistakes are the 3rd largest killer in the USA. What can we do to stop usability issues from killing our fellow citizens?#HITsm

Adopt more workflow technology, so the underlying software can be improved through a variety of means, including usability engineering techniques. See my post on patient safety and process-aware IT.

Thank you to both @HealthStandards and @uuability for hosting this weeks #HITsm chat, and giving me this opportunity to gnaw away at some favorite ideas!

P.S. Oh, by the way, some of the leading figures in the design thinking movement agree with me!

P.S.S.


@wareFLO On Periscope!

warefloblab3

Posted in social-media | Leave a comment

2,241 Tweets from 321 Tweeps With 5,497,584 Follower Reach at Appian World 2016!

I just returned from the Appian World 2016 BPM (Business Process Management) conference in Washington DC. As usual (been to every one since 2008) it was super stupendous great. Every year there are more folks from healthcare and health IT, which is also super stupendous great. Here is a blog post I wrote about one of the healthcare presentations, Putting (Healthcare) Data to Work (using BPM) for Service, Efficiency and Compliance.

Twitter stats rose 17 percent over Appian World 2015. Here’s a bit of a drill down.

Tweets including #Appian16 OR #AppianWorld topped out in the 800s during the main two days of the Appian World 2016.

appian-tweets-total-profile

  • 2,241 Tweets
  • 321 Tweeters
  • 5,497,584 Reach (Tweeters x Followers)
  • From 152 Locations

map1

Congratulations to Appian World’s most prolific tweeters!

most-activie-users

Ha! Ayax, I beat you by one tweet! (what a great selfie!)

And there were tweets in at least 8 languages! I’m trying to find those Swedish and Finnish tweets…

top-languages1

Predicting the future is always dangerous, but I can confidently predict even more healthcare and more tweets at Appian World 2017 in Miami Beach.


@wareFLO On Periscope!

warefloblab3

Posted in social-media | Leave a comment

Putting (Healthcare) Data to Work (using BPM) for Service, Efficiency and Compliance

I just live-tweeted a general session at Appian World about using the Appian Business Process Management Platform in healthcare, specifically by AmeriHealth Caritas, a Medicaid managed care company in 19 states. Phillip Merrell (VP, IS Strategy & Shared Services) was so good I’ve archived my tweets as a sort of notes slash blog post. Most are self-explanatory, relying on tweeted slides. Several are a bit terse, more reminders to myself, so this is also an opportunity to unpack and provide some context.

Healthcare and health IT is extremely focused on collecting data. Business Process Management technology can make sure that data is good clean data, not bad dirty data. Then, BPM can be used to make that data actionable, so that good clean data can trigger all the right processes and workflows necessary to systematically improve population health.

Process management, making sure processes do what the healthcare organization needs and does so correctly every time, is integrated into the Appian BPM Platform. Instead of separate, disjoint, databases forcing users to switch from application to application to application, BPM knits together data from multiple sources into coherent workflows, across users, departments, and even organizations. This knowledge of workflow guides what is automatically presented to who and in what manner, so as to minimize user effort. Stuff, the right stuff, happens automatically.

Regarding that “workflow layer above data layer”, I’m referring to the capacity for BPM to make data come alive, and to knit together disparate health IT applications. In fact, I recently wrote two five-part series on exactly this idea! Check out the following to entry points to those 7,000 and 10,000 words series, respectively.

Anyway, Phillip’s presentation was a virtuoso display of the understanding and articulation of the forces of change leading toward more use of Business Process Management technology in healthcare!

P.S. By the way, Phillip referred to a conversation with me the night before about consolidation in healthcare: Thanks for the shout-out! :)


@wareFLO On Periscope!

warefloblab3

Posted in healthcare-BPM | Leave a comment

Ben Moore, CEO, TelmedIQ, on Why Secure Text Messaging Apps Aren’t Enough

Every year, for the past 6 years, I systematically (some say obsessively) search for examples of workflow technology at the annual HIMSS conference. Six years ago, not much. This year, lots! For example, Ben Moore (CEO, TelmedIQ) spoke about, Why Secure Text Messaging Apps Aren’t Enough, in the Mobile Health pavilion. It was a fascinating mix of information technology, human communication, and classic process improvement themes. In fact, HIMSS tagged it Process Improvement, Workflow, Change Management. The first thing that caught my eye was this quote from its description:

“Many organizations, however, are finding that secure text messaging apps fail in healthcare environments because of their inability to recognize complex communication workflow underpinning patient care coordination” (my emphasis)

Next, there’s this slide:

telmediq-hub2

I’m not going to go through TelmedIQ’s messaging architecture box-by-box, except to point out two things. First, the box in the lower right (workflow engine sighting!). And second, it bespeaks an extremely sophisticated software architecture, with lots of hooks to legacy and other health IT systems. I’d love to have a conversation with Ben someday, in which we visit each layer and component. I suspect it would illustrate just how much secure structured messaging is becoming a multi-functional platform. TelmedIQ certainly meets my definition of a Care Workflow Platform.

Here are my notes from Ben’s talk, high-lighting workflow themes:

  • HIPAA compliant communication platform that focusses on workflow and care improvement through care coordination
  • 300 customers, 80,000 end users
  • Ben’s personal story daughter born prematurely, HC communications “shocking & stunning” (pager, requesting call backs, simple tasks took astronomically longer than they should have had to)
  • Before Secure Texting, sending insecure SMS messages
  • 5 years ago industry born, mobile apps securing emulating SMS (added value, retention policy, self destruct…)
  • 600 bed hospital saved 40 nursing FTE per shift (hour and a half a day in time savings)
  • 500 percent improvement communications workflow efficiency
  • Reliability, adoption, user inclusion, structure & policy, integration
  • put policy on message, escalation, if can’t reach user, try alternatives, calling, escalation policy
  • Adoption issues, page is already embedded in workflow with 20 clinical systems
  • patient-centric workflow, EMR can share with care team
  • inclusion issue, system focusing on physicians vs nurses, must include all workflow stakeholders
  • integrate with nurse call
  • connect to all devices,
  • put structure into the messaging, requiring certain fields based on message type enhances workflow (avoid back and forth workflow, more streamlined)
  • policy, integrate with all on call platforms
  • policy more than just schedule, reroute to different physician (routing engine)
  • orchestration key to delivering useful information & be compliant with Joint Commission (re doc texting order to nurse)
  • connecting all system is key part of our strategy as a company and we’ve done over 30 different vendor integrations with out platform

Back to that workflow engine sighting…

I’ve been tracking diffusion of workflow technology into health IT for two decades. Workflow engines are the single most important component of workflow technology. It is the workflow engine that executes, or consults, a model, or representation of work or workflow, to support workflow system users in their work. That TelmedIQ relies on a workflow engine is, to my mind, evidence the TelmedIQ messaging platform can do the four things for which I tout workflow technology in healthcare:

  • Automaticity: workflows, sequences of tasks, fire automatically and save humans work
  • Transparency: the state of current and past workflow is readily visible and apparent
  • Flexibility: what triggers what tasks in what order can be changed by non-programmers
  • Improvability: transparency and flexibility leads to improvability, workflow can be systematically improved

Ben gave an excellent talk on the importance to move beyond mere “secure messaging” to structured messaging and workflows. I’m delighted to see an underpinning of workflow technology within the TelmedIQ system architecture. And I look forward to observing TelmedIQ’s future evolution toward even more automatic, transparent, flexible, and systematically improbable workflows.

P.S. Here is a video of Ben’s HIMSS16 talk. I originally live streamed it on the #HIMSS16 hashtag using Periscope and then archived it to Katch.me. Where is was viewed over a hundred times…. but then Katch shut down. But not before I saved and uploaded to Youtube!


@wareFLO On Periscope!

warefloblab3

Posted in himss16 | Leave a comment

Workflow Quotes From 10 Percent Of 460 Open EHR Workflow Analyst Positions

Preparing for this evening’s blab about EHR workflow improvement coordinators I searched for job + workflow + EHR OR EMR on Google. The following list of 460 open job positions came up. I searched the first 46 jobs for “workflow.” Here is what I found.

Clinical Analyst

Working knowledge of hospital and surgical processes and workflow

Epic Inpatient (Orders) Analyst

Perform in-depth analysis of workflows, data collection, report details, and other technical issues associated with the use of Epic software

Work with Application Managers/Directors/etc. and the entire Project Team, to collect, analyze and document business operations and workflow.

With support, create, review, and update test scripts to reflect proposed workflow solutions.

EPIC Ambulatory Analyst

Create documentation of business requirements, current and future state workflows

Application Systems Analyst, Sr.

Reviews issue logs, plans and implements workflows, upgrades, and development projects

Electronic Health Records (EHR) Analyst

The primary focus for this role is maintenance, support, workflow analysis, and systems development associated with the Software systems, specifically the Electronic Health Records System (EHRS).

Assists in developing Policies and Procedures around electronic health records and supports and documents the continued use of Foothill Family standards and workflows in the EHRS.

Creates and maintains workflow diagrams based on system functionality to assist in troubleshooting.

Identifies, recommends, and implements workflow improvements in relation to the EHRS by working with users, super users, and vendors.

Demonstrated ability to design and documents workflows.

IT Clinical Analyst

Understands the functional workflow and processes of the Departments the analyst supports and maintains system functionality and design in support of workflow efficiency and user/department productivity.

Must have ability to learn system functionality and workflow in depth

AMB CLINICAL OPERATION ANALYST

Serves as a change management resource and manages the changes in the workflow process that will need to be made with the transition to EMR.

Division EMR Analyst

The Division EMR analyst works closely with the integrated support team (HCAPS, IT&S, CSG, SSP, etc.) to provide content build, workflow analysis, optimization planning, training, and live support of clinical users on the EMR.

Mature understanding of clinical application support processes and workflow, ambulatory EMR preferred

Staff Clinical Informatics Analyst

Clinical Informatics Analyst - Staff is responsible to perform workflow and system analysis and functional design for software development / configuration activities associated with iCentra and other HIT-related initiatives

Documents and recommends workflow changes and functional requirements, specifications, and design solutions needed to support the business requirements for common and moderately complex problems.

Collaborates with key clinical and business stakeholders to determine business rules, needs, specifications, feasibility (workflow and cost), and priorities for application development / configuration / acquisition requests and projects with a basic to moderate level of complexity and according to organizational standards and processes.

Meditech Clinical Analyst

Collaborate closely with and communicate between - IT and the hospital’s clinical staff to be up-to-speed on product features and functionality in aligning daily workflows and strategic objectives.

Clinical Application Analyst

Develop forms and specialized reports in EHR to ensure timely and accurate flow of information crucial to clinical operations and workflows as well as business and billing operations, utilizing MSSQL/T-SQL, EHR software and reporting tools, SSRS and Crystal reporting.

Experience writing workflows.

OpTime Anesthesia Analyst

Routinely perform in-depth analysis of workflows, data collection, report details and other build, design and configuration issues associated with Epic use

Ensure test scripts are created, reviewed and updated to reflect proposed workflow solutions

Familiarity with anesthesia scheduling and staff workflows, resource management and regulatory requirements

Ability to conduct detailed assessment of current state workflows & develop efficient future state workflows

IT CLINICAL SYSTEMS ANALYST

Able to collect data regarding current data processing environment and documents workflows and system access

Ability to make recommendations for workflow based on system capabilities.

Serves as member of various employee committees to discuss workflow, system needs and changes

Healthcare IT Analyst (EMR)

All candidates must have an in-depth understanding of workflows, policies and procedures, patient care/clinical business objectives, regulatory requirements and industry best practices for patient care.

The Application Analyst assists hospitals in optimizing their workflow processes through building applications that are tailored to meet the hospital’s needs.

They will learn the EMR system’s capabilities and functional use and apply their knowledge of Patient Care Business workflow to assist in the implementation of a system that meets process needs.

Basic understanding of clinical workflows and terminology preferred

Create documentation of business requirements, current and future state workflows

Clinical Information Systems Analyst

clarify needs, prioritize requests, recommend workflow enhancements, and execute change and adoption management of the Cerner Millennium EMR and other healthcare information technology (HIT) initiatives (i.e. Meaningful Use, Clinical Documentation, CPOE, and HIE).

The Clinical Systems Analyst will assist in documenting current workflow processes, performing gap analysis, and identifying needed process changes to ensure compliance with the use of technology to optimize care delivery processes and effectively communicate patient care activities.

Systems Support Analyst

Assists in the development of system workflow, templates and forms

Applications Analyst III Job

Clinical background and/or knowledge of Rehab/Therapy workflow a plus.

EMR Applications Analyst

Develop a comprehensive working knowledge of the applications currently used in assigned practices, as well as the design, build and workflow associated with the EMR.

Software Product Analyst

Developing application and data workflow diagrams

Meditech Clinical Analyst

Collaborate closely with and communicate between - IT and the hospital’s clinical staff to be up-to-speed on product features and functionality in aligning daily workflows and strategic objectives.

IT Clinical Analyst

The position is visible to clinicians with significant impact on patient safety, JCAHO, HIPAA, departmental and patient workflow.

Independently facilitates design of clinical workflow in conjunction with the clinicians; workflows will focus on improved efficiencies, solving complex workflow issues and incorporating quality initiatives.

Systems Analyst

Analyzes workflows and recommends alternatives for deriving input data, considering impact on existing systems and downstream effects (i.e. using approved change management procedures).

Epic Clarity Reports Analyst

perform analysis, development, and testing of complex reports and analytics with minimal supervision; design and develop high-efficiency reporting solutions based on end-user requirements and understanding of the Epic EMR system and workflows;

Clinical Business Analyst

Prepares workflow charts and diagrams to document business and systems workflows for existing and new applications

Plans and prepares business documents, reports, memoranda, and instructional manuals as documentation of project requirements and workflows

Privacy Analyst

Ability to use various computer applications to optimize workflow and data analytics to detect, prevent and investigate privacy incidents.

IS Clinical Applications Analyst II

Design, document, and implement future-state workflows consistent with clinical best practices and system functionality in collaboration with other team members, clinical department representatives, or under the direction of IS management/project manager.

Analyzes current state workflows/needs and translates these into the system design.

Design, build, and validate the application to conform to desired workflows within assigned area.

Coordinates with principle trainers in the design development of role-based training to support the workflows implemented.

Provide tier 2 end user application support with an understanding of the Health Information Systems modules including functionality, technical architecture, workflow, routine and non-routine processing.

Technical Support Analyst I

Understanding of clinical workflow in a medical imaging environment.

EHR APPLICATIONS ANALYST

The role will be a primary member of the onsite go-live support team, reinforcing application and workflow training and assisting with issue resolution.

Training and reinforcement of standard organizational workflows, both operational and clinical.

Ability to act as a team leader for small projects or work groups, creating a collaborative and respectful team environment and improving workflows.

Clinical Informaticist

The Clinical Informaticist works closely with the medical staff to incorporate workflows into system design and keeps current on new system functionality that will improve system acceptance and usage and strengthen the clinician-patient relationship.

Clinical Systems Analyst

Manage the clinician experience with the EMR by guiding the solution design, training resources, and supporting processes to ensure the successful engagement and sustainment of the solution while considering associated workflows and how the application(s) integrate with the clinical environments.

Clinical Analyst IS Configurators

identifies opportunities where the clinical information system can be utilized to optimize workflow for clinical processes.

Clinical Informatics Support Analyst

development of clinical workflow changes as it relates to implementation, upgrade, and optimization of clinical applications

Works with nursing department, physicians and other clinical staff to review, recommend and implement workflow and technical solutions that address operational, procedural and systems related issues within and across hospital departments and physician offices.

Strategy Analyst

combine problem-solving, data-analysis, and technical skills to identify, quantify, and solve real-world healthcare workflow problems

You will directly contribute to improved financial and clinical workflow performance for providers, allowing them to focus on the business of delivering healthcare

CLINICAL INFORMATICS ANALYST

Provides analysis for department workflows & identifies EMR requirements as supported by evidence and policies and procedures.

Develops and maintains department specific workflow documentation.

Assures standardization of policies, procedures, workflows, in accordance with the organization’s approved EMR practices. Identifies, escalates and works to resolve deviations.

Manager of Clinical Software Applications and Development

Significant experience and thorough understanding of EMR systems, clinical workflows and implementation

Interface Analyst

Work with end-users and project teams to analyze and document data and workflow processes.

Clinical Data Business Systems Analyst

provides a bridge between clinical workflows and technical workflows, leverages knowledge and skills to ensure technology meets clinical needs and regulatory requirements.

EHR Application Analyst

-Understanding both the clinical and business workflows to achieve strategic outcomes for the implementation

Clinical Business Analyst

Prepares workflow charts and diagrams to document business and systems workflows for existing and new applications

Plans and prepares business documents, reports, memoranda, and instructional manuals as documentation of project requirements and workflows

EHR Application Analyst

-Understanding both the clinical and business workflows to achieve strategic outcomes for the implementation

Two years of Epic software/domain/workflow

Clinical Process Analyst

Knowledge of systems analysis methodologies, workflow process analysis, and software application systems implementation is required.

Clinical Systems Analyst

Working knowledge of hospital and surgical processes and workflow

Posted in EHR Workflow | 3 Comments