RCM Platform Redesign:

RCM Platform Redesign:

Designing Analytics-First Workflows

Designing Analytics-First Workflows

NDA

B2B

Product Design

Time:

Time:

4 months, 2021–2022

4 months, 2021–2022

4 months, 2021–2022

Role:

Role:

Senior Design Consultant (research team of five)

Senior Design Consultant (research team of five)

Senior Design Consultant (research team of five)

Scople:

Scople:

Interaction design, information architecture, cross-functional collaboration

Interaction design, information architecture, cross-functional collaboration

Interaction design, information architecture, cross-functional collaboration

Type:

Type:

B2B Product Redesign

B2B Product Redesign

B2B Product Redesign

Overview

Overview

Mapped the platform's end-to-end workflows with three other designers, establishing the structural backbone the redesign built on.

Designed the analytics experience on top of that structure: unified operating views that pulled claims status, payment history, denial codes, and billing notes into one place.

Turning scattered revenue data into one operating picture

This piece zooms into the design work behind the redesign spec, the analytics views and workflow structure referenced in the parent case study. The through-line was data synthesis: revenue cycle work meant pulling fragmented information into one place so users could act on it, then mapping how that work moved from insights into drill-down details.

The Work

Core Workflow Visualization

Three other designers and I mapped the end-to-end experiences across the platform. I owned most of the surfaces, including claims processing, accounts receivable aging, and the financial management view, and shared coding review and billing reconciliation with the team to keep our design components consistent.

Laying out the surfaces this way is what made their fragmentation visible to me. Each was designed on its own terms, and no single view connected them.
Laying out the surfaces this way is what made their fragmentation visible to me. Each was designed on its own terms, and no single view connected them.

This is a site map laid out for financial manager experience, making the scope of the redesign legible before we designed any screen.

Laying out the surfaces this way is what made their fragmentation visible to me. Each was designed on its own terms, and no single view connected them.
Laying out the surfaces this way is what made their fragmentation visible to me. Each was designed on its own terms, and no single view connected them.

Workflow diagram traced how information moved from dashboard to data tables, so the team could see how the data is sliced along the path the user takes.

Laying out the surfaces this way is what made their fragmentation visible to me. Each was designed on its own terms, and no single view connected them.

A screen-level view of the workflow in interactive form, translating the map into the actual paths users would take.

Analytics-First Workflow Design

Research identified data synthesis as the primary friction point. To resolve issues efficiently, users had to pull together information from several sources: claims status, payment history, denial codes, and billing notes.

The redesign prioritized:

  • Unified operating views combining related data streams

  • Role-based dashboards surfacing the metrics each role needs to focused on

  • Scorecard views tracking performance across revenue types

Laying out the surfaces this way is what made their fragmentation visible to me. Each was designed on its own terms, and no single view connected them.
Laying out the surfaces this way is what made their fragmentation visible to me. Each was designed on its own terms, and no single view connected them.

A customized dashboard surfaces the key metrics that matter to each roles.

Laying out the surfaces this way is what made their fragmentation visible to me. Each was designed on its own terms, and no single view connected them.
Laying out the surfaces this way is what made their fragmentation visible to me. Each was designed on its own terms, and no single view connected them.

Widgets surface high-level data first, so users can choose where to dig deeper.

Laying out the surfaces this way is what made their fragmentation visible to me. Each was designed on its own terms, and no single view connected them.
Laying out the surfaces this way is what made their fragmentation visible to me. Each was designed on its own terms, and no single view connected them.

A timeline filter on the widet controls the view, letting users surface the specific insight they’re after.

Laying out the surfaces this way is what made their fragmentation visible to me. Each was designed on its own terms, and no single view connected them.
Laying out the surfaces this way is what made their fragmentation visible to me. Each was designed on its own terms, and no single view connected them.

Interacting with a widget drills into the underlying data table.

Designed by Ann Ash, Last updated: August 2026