Over a million developers have joined DZone.

Designing Useful, Usable and Innovative EHR Systems

DZone's Guide to

Designing Useful, Usable and Innovative EHR Systems

· Big Data Zone ·
Free Resource

Jumpstart your Angular applications with Indigo.Design, a unified platform for visual design, UX prototyping, code generation, and app development.

Developed and honed over generations, the medical profession has created processes, procedures and physical artifacts that serve healthcare professionals and their patients well. Yes, there are process improvements to be had. Yes, there are inefficiencies inherent in the overlap between healthcare providers and the healthcare industry. However, improving the digital systems that support the medical profession is not the primary problem. Usability, while problematic, is not the primary problem either. The problem is the imposition of poorly designed technological solutions to replace the medical profession’s processes, procedures and physical artifacts.

The cost of designing, developing, purchasing and installing Electronic Health Record (EHR) systems, plus the price of “training” health care professionals to change their behaviors in order to adapt to their new electronic systems, amounts to many millions of dollars. In response, medical task forces, healthcare professionals and reporters are sounding the alarm that these new systems are difficult to use, decrease productivity and negatively impact the quality of patient care.

example EHR screenshot example EHR screenshot
(photo courtesy of workflow.com) (photo courtesy of emr-ehrs.com)

Usability is Not the Answer

To address these issues, the healthcare industry has focused on the need to identify, employ and measure the usability of these systems. These are laudable and necessary goals but, in the end, they are insufficient. They place the needs of users far too late in the process and do not address the primary issue—poor design. EHR systems informed by usability principles will help ensure that the user-system interaction follows accepted patterns. A rating system informed by usability principles can help healthcare institutions differentiate between systems that meet basic requirements and systems that do not. However, applying usability during the development or selection processes is insufficient to guarantee a useful system once it is deployed.

Usable and useful mean very different things. An application or feature can be considered “usable” if users can successfully and quickly complete the task for which it was created. It’s important to keep in mind that usability is, by definition, a post hoc test. Usability does not influence the gathering of requirements. It does not define the scope of the system. It does not provide a pathway to innovation.  It is absolutely possible for an application to be usable but not innovative, inspiring, beautiful, lasting or useful.

Usability is necessary for good design but it is not sufficient.

Attempting to address low adoption rates and dissatisfaction by invoking usability is akin to treating the symptoms of a disease rather than its cause. Usefulness, usability, flexibility, task support and user acceptance are the result of a formalized design process. It is the absence of this process, not the absence of an acceptable usability score that limits adoption of EHR and other healthcare systems. We must look at how healthcare systems are designed if we are to ensure that the systems we implement in our hospitals, clinics and physicians’ offices are ultimately both usable and useful.

EHRs can progress beyond ticking features off a checklist. Data can be explicitly translated into information and presented to users in ways that support their decisions and actions while freeing resources (attentional and financial) to be spent on problems previously hidden or untouched. Disparate systems can be coordinated and aligned. Processes and even entire “businesses” can be reformulated to serve user needs as well as user wants.

How? Follow a design process.

Take a look at an Indigo.Design sample application to learn more about how apps are created with design to code software.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}