HealthSight Advisors

Prior to joining the team, HSA’s website used to have two different experiences for clinical pharmacists (CPs) and infection preventionists (IPs). It underwent a design overhaul that combined the workflows of clinical pharmacists and IPs into one experience, with the first major release focusing on the pharmacist workflow.

This change removed relevant workflows that the IPs relied on for patient documentation on hospital acquired infections (HAIs).

I led the iterative design of the alerts and reports page, so our customers can spend less time navigating the page looking for relevant data, and instead focus on taking action with their patient list.

Legacy HSA which IP users preferred for it's clear data table that's actionable.

Updated HSA that highlighted information important for a CP and not an IP.

Due to time constraints, we opted to review post-release surveys to gauge user satisfaction and better understand which features caused the most friction. We found that users are having trouble navigating the new reports and alerts pages because:

Not all data types can be filtered for

They cannot tell which cultures have been reviewed for a patient

There is too much information that dilutes the listing

Some of the new list actions leads users to the wrong path

To get an insight on what users did like, we collaborated with customer support and our subject matter experts (SMEs).  SMEs know our application inside and out because they were IPs in a previous role.

From these interviews, we concluded that the legacy version was favorable because:

Legacy documentation icons.

Data columns were straightforward with one kind of listing per cell

Filtering was easy, with a sort function per column

There was date range filter for culture collection/results

"Purple + signs" were a signal for "needs documentation" (see image on left)

Since we had a week to conduct research, our HFE and I decided to take on an A/B testing approach where we would show users three different prototypes that address user pain points that were also discussed with our PM.

We provided tasked-based scenarios for each feature we wanted to test and compared which of the designs had the higher success rate. This was also a way for us to get user feedback on the PM's suggested designs to showcase why it's important to conduct research on the ideal solution.

For each feature below, #2 performed the best and users completed these tasks with no issues.

Filter on specimen collected date and finalized date

Date range filter existed in legacy HSA and was a necessary feature that greatly increased documentation efficiency.

1. Access through microbio column header

2. Module through calendar icon

3. As part of left filter

Patient search in report and alert results

Currently, users had to scroll endlessly to find specific patients

1. Access through patient column header

2. Search bar above data table

3. Search bar as part of left filter

Quick, visible recognition of completed documentation status

Currently, users had to open up a separate module for each patient to see if the patient needed documentation

1. icon + color for each culture under microbio

2. Upgraded legacy icons with tags on hover

3. Color to differentiate document types

Although the above designs performed well, not everything goes as planned. Design 2 was well loved by the users because it resembled the legacy icons.  However, once shipped, I saw an increase in customer support inquiries that I needed to investigate.

Proposed designs that aligned with the design system, but kept the familiarity of the legacy icons.

Since the icons I designed were new, I worked with our lead designer and requirements engineer to make sure the icons were accessible and authorized for the tool. We concluded that it was best to unify the icons by using one document symbol.

One unified icon with tags on hover.

Having such a unified icon design confused IPs because they could not differentiate document types as easily.
As a result, these icons were rolled back immediately for further revision.

We conducted another round of usability testing where we focused on addressing the documentation icon. The design on the left worked well because users can tell if a culture needs documentation and they are able to view existing documentations easily through the accession number.

Two versions of culture documentation for iteration II.