MCE — Med Control Evaluations
Lead Product Designer — Operational dashboard system for IME workflows, with three role-based experiences (Admin, Adjuster, Supervisor).
%2012.31.55.png)
Role & Setup
Lead designer on the dashboard, embedded in a full-stack engagement.
MCE is a 26-year-old Independent Medical Evaluation company running nationwide Workers' Comp, No-Fault and Liability claims. The engagement was a partnership between MCE and Rewav (full-stack agency) to replace a brittle Microsoft Access setup with a modern, HIPAA-aligned platform.
Inside that engagement I owned the dashboard layer end-to-end — the surface where the operation actually happens.
My Role
Lead Product Designer — Dashboard
Single point of accountability for dashboard UX/UI and the three role-based flows (Admin, Adjuster, Supervisor). Worked directly with MCE operations and Rewav engineering.
Build Model
Designer embedded with full-stack engineering
Rewav owned back-end, database migration and HIPAA implementation. I drove every product and design call inside the dashboard layer and paired with engineers through implementation — fast feedback cycles, focused on shipping.
What I Owned
- End-to-end ownership of the dashboard layer
- Role-based information architecture (navigation & sections tailored to Admin, Adjuster, Supervisor)
- Information-rich screens — tables, charts, donut graphs, timelines
- Design system with shared tokens (colors, spacing, type) and reusable UI components
- “Bird Eye” oversight feature
- Functionality calls & tradeoffs per role
- Pairing with engineering through implementation, not just at handoff
Honest scope: Rewav owned back-end, the Microsoft Access → WordPress migration, HIPAA compliance, and the marketing site. I owned the dashboard layer end-to-end — role-based flows, UX/UI, data viz, the “Bird Eye” feature, and the design system. Calls on permissions, functionality split, and visualization were mine.
HIPAA-aligned design · PHI-aware UX patternsThe Why
One company, one workflow, three very different jobs to be done.
MCE was running a nationwide IME operation on top of Microsoft Access and a tangle of spreadsheets. Every IME request, every addendum, every cancellation and reschedule passed through people doing fundamentally different jobs — but looking at the same flat data.
The brief was specific: build a dashboard that an Admin, an Adjuster and a Supervisor can each open and immediately see their work, with their level of authority — without three different products to maintain. Add a big-picture “Bird Eye” view for oversight, keep PHI (protected health information) visible only when it has to be, and make sure scheduling, addendums and performance live in the same interface.
Overview
What was built
An operational dashboard system replacing manual IME processing — three role-based experiences on one design system, built to scale across MCE's nationwide panel of 1,800+ board-certified physicians with HIPAA-aware patterns from day one.
In Context
From overview to case detail in one click
One shared interface, with data filtered by role. The Admin lands on counters, the donut chart, and the addendum pipeline at the top of the screen, without scrolling — then clicks through into any metric (here, the 120 IME Canceled) to a focused table with Doctor, Patient, Specialty and Scheduled Date. The dashboard is the launching pad, not the destination.
%2012.42.39.png)
Admin · My Teams Performance — clicked into the 120 IME Canceled metric. Donut chart + addendum pipeline above; case-by-case table below.
Color & Typography
A vibrant palette in a calm, operational interface
The product palette deliberately avoids the navy-and-teal cliche of medical SaaS. Cobalt anchors authority for headers and primary actions; magenta is the brand's signature accent, used for the highest-attention CTAs and the most operationally critical state (reschedules). Violet, cyan, orange and green are reserved as semantic data colors across every chart, so operators learn the language once and read it everywhere.
The Three Users
Three users, three flows, one design system
The biggest product call on this project: instead of building three separate products, I designed one shared interface, with data scoped by role, powered by a single design system. Same navigation patterns, same UI components, very different jobs to be done. Each role inherits the components and chart language — only the data scope and the permitted actions change.
Admin
Sees every team · Clicks into any case
Default scopeMy Teams Performance — every team, every adjuster, every outcome rolled up org-wide.
What I designedAn information-rich overview pairing an IME donut chart (Canceled / No Shows / Reschedule) with the addendum pipeline, appointment-volume cards, and a weekly outcome chart — every total clickable through into the case-by-case table (Doctor, Patient, Specialty, Scheduled Date, ID).
Why this shapeAdmins are accountable for the whole operation. They need the big-picture view and the one-click drill — never a separate report.
%2012.43.26.png)
Adjuster
Team-only view · Owns their work
Default scopeMy Performance Team — their team only. Same donut chart, addendums, and IMES cards, scoped to The Capables Team (or whichever team they belong to).
What I designedA focused team-level dashboard with an appointment-booking chart broken down by claimant count (1 / 2 / 3+) per week, so adjusters see workload patterns — not just totals — and can self-correct without a manager prompt.
Why this shapeAdjusters don't need org-wide noise. Scoping to their team gives them ownership without overwhelm, and exposes complexity (multi-appointment claimants) that a flat number hides.
%2012.43.52.png)
Supervisor
Manages teams · Clicks into any individual
Default scopeThe whole team, with the ability to Add new team and Search by team member to drop directly into an individual adjuster (e.g. Joan Makovich) for a 1:1 coaching read.
What I designedA two-level view: team aggregates at the top, and an individual's Record Reviews timeline below — so supervisors move from “how is the team doing?” to “why is Joan's February so much higher than March?” without changing screens.
Why this shapeCoaching needs pattern + person, side by side. Splitting them into separate pages turns a 30-second insight into a five-click investigation.
Functionality I Designed
Five dashboard surfaces that ship the operation
These are the surfaces where most of the operational work actually happens — each one solving a specific friction MCE had been carrying for years on top of Microsoft Access.
Bird Eye Feature
ProblemSupervisors and Admins couldn't see the operation as a system — only as a list of cases.
SolutionA single-screen overview combining IME volume, addendums, outcomes and team performance.
WhyOperational health is a pattern, not a row — the Bird Eye turns weeks of guesswork into a 5-second read.
Weekly IME Volume & Outcome Tracker
ProblemNo-shows, cancellations and reschedules were tracked separately and missed as a system — revenue leaked here.
SolutionA weekly IME trend chart paired with the Canceled / No Shows / Reschedule breakdown card right next to it.
WhyOutcomes only mean something next to the volume they came from. Co-locating them makes the “why are we losing appointments” conversation possible.
Addendum Pipeline
ProblemAddendum requests aged silently. Without a queue they piled up and physicians lost context.
SolutionA dedicated pipeline with closed vs. in-progress states, requested counts on the dashboard, aging visibility per role.
WhyAnything without a visible queue eventually gets forgotten. Making the pipeline a core part of the dashboard prevents quiet drift.
Specialty-Aware IME Scheduling
ProblemScheduling was a multi-tool dance — finding a board-certified specialist near the claimant took 10+ minutes per case.
SolutionInline IME scheduling from the Adjuster dashboard with specialty + geography filters — the right doctor surfaces inside the case itself.
WhyIf scheduling lives in another tab, momentum dies. Bringing it into the dashboard collapses 10 minutes into 30 seconds.
Team Performance View (Admin / Supervisor)
ProblemThere was no shared view of team performance — coaching happened from memory and gut feel.
SolutionA My Teams Performance tab with adjuster-level breakdowns, closure rates and outcome trends, scoped to the manager's team.
WhyPattern recognition needs data. A structured view replaces “I feel like Lisa is overloaded” with “Lisa has 38% more open addendums than the team average.”
Design Decisions & Tradeoffs
Three calls where the obvious answer was wrong
Every call on a healthcare ops tool is a tradeoff between visibility, safety and speed. Three places the easy answer would have hurt the operation — and what I shipped instead.
One product for all three roles, or three separate products?
Option A
One single dashboard, same view for everyone
Cheapest to build, but Adjusters drown in Admin metrics and Supervisors lose the patterns they need.
Option B
Three fully separate products
Cleanest per-role experience, but tripled the design system maintenance and fragmented training and support.
Chosen · C
One shared interface, with data scopes & permissions per role
Same navigation patterns and components. Each role sees the data and controls scoped to their authority — nothing more.
Why C: Operations teams move between roles over time. A shared interface makes promotions painless and protects the design system. Permissions do the heavy lifting — not three forked codebases.
How do we show HIPAA-sensitive data without overloading the screen?
Option A
Show everything by default
Maximum visibility, but every glance at the dashboard exposes protected health information — with the added risk of someone glancing over your shoulder in shared offices.
Option B
Hide all patient detail until explicit action
Safest on paper, but adds friction to every legitimate workflow and trains people to click through without thinking.
Chosen · C
Show details only when the role needs them
Counts, queues and trends always visible. Patient names and identifiers revealed only inside the case context the role is authorized to see.
Why C: HIPAA asks for the minimum necessary, not for hiding everything. Aggregates can live on the dashboard safely; PHI lives one click deeper, inside the case. The UI teaches the policy by design.
How do we visualize performance without gamifying healthcare work?
Option A
Leaderboards, streaks, badges
Familiar SaaS pattern. Wrong incentive for healthcare — can pressure quantity over case quality.
Option B
Hide individual performance entirely
Avoids gamification, but removes the visibility supervisors need to coach and adjusters need to self-correct.
Chosen · C
Contextual transparency, no rankings
Each user sees their own data plus their team's aggregate. Trends & outcomes shown next to volume — never as a ranked list.
Why C: The right behavior in healthcare is “the right outcome, on time” — not “the most tickets closed.” Numbers next to the team average give self-awareness and coaching context without inviting a race.
Status & Measurement
What shipped, what we're measuring, and how we'll know
The dashboard shipped into MCE's production operation as part of the broader Rewav engagement. Rather than claim metrics I don't own, here's the honest split: shipped scope, the operational bets the design makes, and the measurement plan.
Shipped · Scope Metrics
What was actually built & delivered
- 3Role-based dashboards (Admin, Adjuster, Supervisor) on one shared interface
- 12+Dashboard screens designed across roles, all information-rich
- 1Design system & shared tokens powering every screen — reusable UI components across all 3 roles
- 5Operational features shipped end-to-end (Bird Eye, weekly tracker, addendum pipeline, scheduling, team perf.)
- HIPAAPHI (protected health info) revealed only when needed, on every screen
- 26 yrsof operational know-how absorbed into the information architecture, replacing Microsoft Access
Hypotheses · Operational Bets the Design is Making
The four bets baked into the dashboard
A shared interface with role-aware data scopes will cut role-switching errors and onboarding time vs. a flat dashboard.
Signal: shorter onboarding time for new hires, fewer “wrong tab” support tickets · Measured via: training time + helpdesk logsSupervisors and Admins will open the Bird Eye daily once they trust it — replacing weekly spreadsheets pulled from the old Access setup.
Signal: daily active use of Bird Eye by supervisor cohort · Measured via: page-view tracking per roleMaking the addendum pipeline a core part of the dashboard should lower median addendum age vs. baseline.
Signal: median days addendum stays “In Progress” · Measured via: addendum status changesCo-locating IME volume and Canceled / No Shows / Reschedule on one canvas will surface lost-revenue patterns faster than separate reports.
Signal: reduced no-show rate after operational responses · Measured via: weekly outcome changesMeasurement Plan
How we'll know
- 30 dPer-role adoption read (Admin / Adjuster / Supervisor) + 5 moderated sessions
- 60 dAddendum throughput delta & outcome trend review
- 90 dFull hypothesis review, design system iteration plan, accessibility re-audit
Tools
Stack for evidence
Figma for system & flows, FigJam for role mapping & permissions, Notion for handoff and decision logs, Linear for tickets, Hotjar for adoption signals.
Client Reflection
From the MCE leadership
Rewav has truly transformed our operations. Their expertise in back-end development, website design, and HIPAA compliance has streamlined our processes, improved team collaboration, and enhanced our digital presence. The migration to a more scalable platform and the automation of IME processing have saved us valuable time. We're thrilled with the results and look forward to continuing our partnership.
Process
A senior-PD workflow on a regulated product
The premise
Healthcare operations work doesn't tolerate guesswork — every judgment call had to be human. I owned every decision touching user safety, role permissions and PHI visibility, from discovery through engineering handoff.
Discovery & Role Mapping
Ran the ops interviews, synthesized themes and surfaced the overlaps and conflicts in role responsibilities. Validated every role boundary with the team, authored the permission matrices and made the call on what each role actually sees and controls.
Wireframes & Dashboard IA
Designed layout variants per role, defined the information architecture, navigation patterns, components and every chart choice. Deliberately rejected gamification patterns that didn't belong in healthcare.
Visual Design & HIPAA-Aware Patterns
Built the visual system end to end: palette, accessible color combinations, role color meaning, interface text for sensitive states and the PHI reveal-on-demand pattern across every empty, error and sensitive state.
Engineering Handoff & QA
Wrote the handoff specs and edge-case notes, worked directly with Rewav engineering, owned QA on every shipped flow and called the tradeoffs between polish and ship date.