Lumere » Cost Optimization SaaS Platform

From individual device components to meaningful, system-level comparisons.

Role
Senior UX Designer

Domain
Healthcare · SaaS · Enterprise Data Systems

Skills
Product Design · Data Visualization · Information Architecture · Workflow Design · User Research · Prototyping · Stakeholder Collaboration

Overview

A hip replacement isn't a single medical product. It's a collection of components, each with its own manufacturer, specifications, and price. For hospital systems evaluating hundreds of devices, understanding the cost and clinical implications of an entire construct can be far more useful than comparing individual parts.

At Lumere, I helped redesign a healthcare SaaS experience that brought complex medical-device data into clearer, more actionable comparisons.

The work centered on the Construct Browser, a tool that allowed physicians, hospital administrators, and purchasing teams to evaluate medical-device systems using clinical performance, outcomes, and cost data.

The Problem

The data was available. The full picture was harder to see.

Medical-device purchasing involves an unusually complicated set of decisions. A single surgical procedure may involve multiple components, each with its own SKU, vendor, cost, and clinical considerations.

Physicians evaluate products based on clinical needs and experience. Purchasing teams must also consider pricing contracts, comparable alternatives, and opportunities to reduce costs without compromising care.

The existing experience needed to make these relationships easier to understand.

Users needed to compare complete constructs while retaining access to the underlying details that informed those comparisons.

The challenge was to simplify the presentation of complex information without oversimplifying the decisions it supported.

My Role

As Senior UX Designer, I led UX design for the Construct Browser, working with product, engineering, and data visualization partners to improve how medical-device information was organized and presented.

My responsibilities included:

  • Interviewing physicians and healthcare administrators to understand evaluation and purchasing workflows.

  • Mapping user needs and translating complex product structures into usable interaction patterns.

  • Designing comparisons, information hierarchies, and drill-down experiences for data-heavy interfaces.

  • Collaborating with product and engineering teams to develop and refine the experience.

  • Supporting stakeholder presentations and discussions around clinical and financial decision-making.

The work required balancing the needs of multiple audiences who approached the same information from different perspectives.

Research & Insights

Understanding what people actually needed to compare

Through user interviews, workflow analysis, and collaboration with clinical and purchasing stakeholders, I explored how medical-device evaluations were performed and where the existing experience introduced friction.

A central challenge emerged: individual product records didn't always reflect how devices were selected, evaluated, or purchased.

For example, comparing two hip replacement systems meant understanding not only the individual components but also how those components worked together and what the complete system cost.

The design needed to support two levels of understanding:

  • The complete construct: A meaningful, system-level view that could support comparisons across products and manufacturers.

  • The individual components: The detailed product, clinical, and pricing information needed to investigate differences and evaluate alternatives.

This distinction became central to the browser redesign.

Design

1. Organizing products as complete constructs

Rather than treating every component as an isolated product, I designed interfaces that grouped related components into recognizable medical-device systems.

For a hip replacement, this meant presenting the ball, stem, and socket as parts of a larger construct, while preserving access to individual component information.

This gave users a more useful starting point for comparison and helped connect the data to actual clinical and purchasing decisions.

2. Making dense data easier to compare

Working with the data visualization team, I explored ways to improve the hierarchy and presentation of clinical, product, and financial information.

The design emphasized meaningful comparisons over simply displaying more data.

Related information was grouped, important differences were given greater prominence, and detailed information remained available for users who needed to investigate further.

The goal wasn't to remove complexity. It was to make that complexity easier to navigate.

3. Bringing cost into context

Price alone doesn't tell the full story of a medical device.

The Construct Browser needed to support comparisons that considered complete system costs alongside clinical and product information.

I designed views that brought component relationships, aggregate costs, and comparative data together, helping users understand where differences existed and investigate their implications.

This supported more informed conversations between physicians and purchasing teams without reducing clinical decisions to price alone.

4. Supporting different decision-makers

Physicians, administrators, and purchasing leaders could be looking at the same products for different reasons.

The experience needed to support detailed clinical evaluation while also making comparative financial information accessible to those responsible for procurement and cost management.

Rather than creating entirely separate experiences, the design sought to make the same underlying information useful across different tasks and levels of detail.

Outcomes

The Construct Browser redesign established a clearer way to evaluate complex medical-device systems, connecting individual component details with the broader clinical and financial context.

Key accomplishments included:

  • Organized component-level product information into system-level views.

  • Improved the structure of comparisons across medical-device alternatives.

  • Made complex clinical and pricing data easier to navigate without removing important detail.

  • Supported evaluation and purchasing discussions across clinical and administrative audiences.

  • Collaborated with data visualization, product, and engineering teams to translate complex healthcare data into practical workflows.

The result was a more coherent decision-support experience for navigating hundreds of medical-device options.

Related Work » Device Request

Alongside the Construct Browser, I redesigned Lumere's physician-facing Device Request experience.

The original workflow required navigating approximately seven or eight screens, contributing to significant drop-off and incomplete requests.

I streamlined the process to approximately three steps and designed it to support mobile use, allowing physicians to submit requests more easily between procedures.

Where the Construct Browser focused on making complex information easier to evaluate, Device Request focused on removing unnecessary steps from a frequently used workflow.

Together, these projects addressed two complementary needs: helping healthcare teams make better-informed decisions and making it easier for physicians to act on them.

Artifacts

  • Construct Browser interface explorations

  • Component grouping and comparison designs

  • Data visualization and table iterations

  • Product evaluation workflows

  • Device Request before-and-after workflow

  • Mobile Device Request designs

Previous
Previous

Northwestern Medicine » Patient Self-Scheduling

Next
Next

JPMC Party Central » Landing Page & SALT Modernization