Skip to main content

Testing a Customizable Treatment Tool in Real Time

UCLA RadPath Portal Screenshot

UCLA’s updated RadPath cancer treatment tool organizes all the information doctors need—pathology reports, test results, diagnoses, next steps—in one easy-to-navigate, responsive hub. Now, it’s as innovative as the physicians who use it.

The Challenge

In a world of complicated, out-of-date medical technology, RadPath is an innovative tool that is integral to UCLA’s radiology and pathology departments. The hospital wanted to expand the tool’s capabilities, make it possible for their developers to create new views for different medical specialties, and ensure that physicians would be able to access the information they needed for their patients, regardless of which device they were using.

Our Approach

Because the stakes are high for a tool like this one, we needed to be sure that we were creating the most user-friendly design possible. To that end, we sat down with several physicians across multiple disciplines to hear more about what wasn’t working, and what kind of features would make their jobs easier. It was clear from their feedback that RadPath needed to be responsive, customizable by specialty, and simpler, with a better user interface, and way less scrolling. 

The Technology

The most critical piece of this project was making the user interface as easy to use as possible. For that reason, we never sent UCLA Health a photoshopped document or a PDF of what they could expect the redesigned RadPath to look like; instead, we reviewed live creative concepts, so we could be sure that our decision to, say, switch to easily navigable tabs, or pull out the elements that were causing scroll jacking, was the right one. Because we were able to put a working prototype in their hands, the team’s feedback was fast an invaluable, making the process much smoother.

We worked hard to improve the existing tool, but we also wanted to make sure that different specialties could each have their own version. When we handed over the code for the updated tool, we made it possible for the hospital’s in house developer to tailor different interfaces to meet the needs of different kinds of doctors. We also made sure that RadPath is responsive, so that a doctor walking down a hallway could check in on a pathology report just as easily as a physician sitting at a desktop. 

The Result

Because we were able to live test the tool, we were able to deliver the updated RadPath tool extremely quickly, and the hand off process between us and their in-house developer was simple. Now, UCLA can spin out as many discipline-specific versions of RadPath as it needs.