- Recently, in the world of healthcare IT, there has been an increased focus on the usability and design of EHR systems:
• The handling of the first Ebola case at Texas Health Presbyterian was originally thought to be due to a communication breakdown caused by a flaw in their EHR system.
• The American Medical Association recently declared the need for an “Action Plan” to improve EHR systems, citing “clunky menus” and “cluttered screens.”
• A 2013 large-scale survey of medical doctors found that “the current state of EHR technology significantly worsened professional satisfaction.”
How can “users” find their way back into the “user experience”?
Paths to a New UI
On November 2, 2012, the New York Times launched 512 paths, a visualization of all possible scenarios related to the 2012 election. Combining data and simulations from polls, the visualization would allow the user to see every “path” that lead to an election result manipulating each battleground state. Needless to say it went way beyond Tim Russert’s famous whiteboard. This expression of possible election paths embodies what we need in healthcare— the simplification of hundreds of data points, the simulation of interventions and critical events and the interactivity to allow a user full understanding of the outcome.
Instead of poll and Electoral College data, consider the implications of slicing and dicing the data representing a patient population. Each path would represent trips to emergency rooms urgent care and primary care, or preventative care measures. Each path could be affected by outreach, education or other medical interventions. Isn’t that the promise of EHR data and healthcare data analytics?
Over the last three years, user interfaces have been revolutionized to be more intuitive and powerful, as well as more accessible and universal. And perhaps most importantly, they’re free.
In the final installment of our series on analytics, we’d like to address the user interface, particularly addressing future developments and implications through a discussion of a few tools that have the potential to significantly improve the user experience.
AngularJS is one of the latest model-view-controller (MVC) frameworks that are powering dynamic web interfaces. Consider MVC as an architecture in which you can simply design the thing you’re describing (model), what it looks like (view), and what happens when the user interacts with it (controller), and then lets the framework handle all the work of actually creating the pages, forms, and transitions.
Angular also simplifies the process of loading, filtering and analyzing data across multiple factors. Imagine a typical longitudinal patient report, with CPT codes, DRGs, HCCs, rendering facilities, places of service, ICD-9 codes, PCP assignments, and more. Now imagine 10,000, 100,000, or 1M such rows. With Angular, one module can cross-analyze all of these datasets, each using different quantitative techniques and complex visualizations.
Most importantly, the user experience is preserved even as the process scales up in size. Since the Angular framework seamlessly loads data in the background, latency is reduced, allowing the developer to focus on prioritizing elements according to the desired user experience, rather than at the whim of the network connection or browser.
Harken back to the 512 paths visual from the top of the page. It’s a truly beautiful figure, both in terms of the use of visual cues, as well as a highly effective use of interactive elements to engage the user.
And it is facilitated by the d3.js visualization library.
The power of d3.js lies both in an accessible application programming interface (API) that even users unfamiliar with graphical concepts can pick up, as well as with its’ devoted user base that continues to develop and document new uses for the language. With each visualization, whether for a school project or front page figure, the user base becomes ever more enabled to develop sophisticated, interactive figures.
For these reasons, d3.js offers a great deal to those developing user interfaces in the healthcare space. For example, consider the following visual display:
Here we see each patient of a provider’s panel plotted along with their total cost of care and number of events where they interacted with the health system. Interactively, users can compare the outcomes of one patient panel against others (or the organization mean), and most importantly, drill down to the exact patient that contributes this cost.
Although the visualization doesn’t model every path outcome, it is getting close, and, more importantly, it does so in a way that can be adapted to user needs, rather than the opposite.
There are other mechanisms for developing beautiful visuals, some more powerful and perhaps better supported. The key is that anyone who has an idea of how to better visualize healthcare information should be able to take a hand at it. Tools like d3.js make this possible.
Focusing on User Experience
In the last few years, extremely powerful, fast, intuitive and beautiful interfaces have become more and more commonplace.
There is no good reason why users in the healthcare domain – physicians, nurses, medical assistants, administrative staff, leadership, and, yes, patients – shouldn’t have the same expectations. If Facebook still looked like it did when it was thefacebook, there would be far fewer Likes.
The user interface and user experience (UX) is a big reason why very few users are ‘Liking’ most healthcare business platform tools. When a patient is in a provider’s office receiving medical care, the most technologically intuitive interface shouldn’t be their iPhone, but rather the technology at their provider’s fingertips supporting the documentation of their care. That same technology should also be at the ready to help their care team, as well as all of us interested in improving patient care, to make more effective use of patients’ healthcare information in the delivery of their care.