IEHP Care Manager Maintenance
Internal enterprise platform managing 30,000+ care plan assignments across 35 care managers in 4 California regions — replacing fragmented manual processes with a single data-dense command centre. 62 screens. Shipped to production. Designed and built solo.
My Role
Sole Product Designer + Frontend Developer (Angular)
Duration
4 months
Year
2023
Tools
Figma · Angular · TypeScript · CSS3
Project Brief
Design and build an internal operational command centre for IEHP's care manager workforce — enabling real-time workload visibility, care plan assignment, and operational reporting across 35 care managers managing 30,000+ care plans in 4 Southern California regions.
Internal enterprise platform managing 30,000+ care plan assignments across 35 care managers in 4 California regions — replacing fragmented manual processes with a single data-dense command centre. 62 screens. Shipped to production. Designed and built solo.
The Problem
30,000 care plans. 35 managers. Managed in spreadsheets. Delayed assignments and coverage gaps were operational risks growing with scale.
IEHP's care plan assignment depended on manual coordination: spreadsheets tracked assignments, email threads handled reassignments, regional capacity was unknown until a care manager raised the alarm. At 30,940 care plans, this was beyond what manual processes could reliably handle.
No real-time workload visibility
Admins couldn't see current workload distribution across 35 care managers without manually pulling data from multiple sources.
Manual reassignment was error-prone
When a care manager went on leave, 500+ care plans needed manual reassignment — a process taking days and prone to gaps and duplicates.
No regional capacity data
Low Desert, High Desert, Riverside County, San Bernardino County — each had different capacity but no single comparative view.
No RBAC — all staff saw everything
Care managers could see data outside their scope. The system needed role-based views: admins see everything; care managers see only their workload.
UX Audit
What was broken before we redesigned
A heuristic evaluation of the existing system identified these critical issues before any design decisions were made.
Spreadsheet as operational system
30,940 care plan assignments maintained in shared spreadsheets — no audit trail, no automation, no real-time view.
Process GapNo workload visualisation
No way to see workload distribution in real time without manually counting rows across multiple files.
Visibility GapFlat permission model
Admin and care manager views were identical — both saw all regional data and all manager assignments.
RBAC GapOur approach: Design a command centre — not a CRUD interface
Designed a multi-chart dashboard (donut, bar, carousel, sparklines), care manager management, care plan assignment by type (Complex/Basic/General/Behavioral Health), regional capacity, schedule/availability, parametric report generation, and RBAC — all under two distinct role views. 3+ pre-design BRD sessions shaped the architecture before any screen was drawn.
Process & Approach
How I approached the challenge
Pre-Design BRD Sessions
3+ documented Q&A sessions with IEHP stakeholders before design began. Mapped care manager lifecycle, assignment workflows, 4-region structure, and reporting requirements — product thinking before pixels.
Multi-Chart Dashboard
KPI cards (30,940 total / 19,046 active / 35 managers / 1 on leave), donut chart (care plan types), high-workload carousel, monthly bar chart, per-manager sparklines. Each widget justified against operational need.
RBAC Role Views
Admin: full sidebar (7 modules). Care Manager: Care Manager + Schedule only. Same codebase, two information architectures.
62-Screen System
Care Manager module, Care Plan module (4 types), Region module (4 regions), Schedule/Availability, Report Generation, Printed Report output, RBAC Privileges.
Angular Implementation
Sole Angular + TypeScript + CSS frontend developer. Forms, data tables, notification system, chart widgets, report generation, and printed IEHP-branded report templates — shipped to IEHP intranet production.
Design Principles
Enterprise tooling for operational decisions, not data entry
The care plan assignment system handles real patient lives. Design had to earn that trust.
Data at a glance, decisions in context
The dashboard answers 4 operational questions on login: total load, distribution, high-risk managers, and trend over time. Every widget has exactly one job.
RBAC as information architecture
Admin and Care Manager views are distinct information architectures — not permission flags on the same interface.
Reports are a design surface
The IEHP-branded Roster Details printed report is a design deliverable as important as any dashboard screen.
Pre-design is product design
Three BRD sessions before any wireframe shaped the entire CMM architecture. The questions asked in those sessions are visible in every module.
The most important design decision in CMM was the BRD session — not the dashboard layout.
Why This Was Hard
Complexity signals
What set this project apart from standard product design work — the technical, systemic, and domain-specific challenges that demanded real depth.
30,000+ care plans in a live system
The numbers in the CMM design file are real operational data — 30,940 total, 19,046 active. Designed for production at real scale.
Multi-chart dashboard orchestration
Donut, high-workload carousel, monthly bar chart, per-manager sparklines — four visualisation patterns coordinated on one admin dashboard.
RBAC in design and engineering
Admin vs. Care Manager views required different sidebar navigation and data visibility — same codebase, two information architectures.
Printed IEHP-branded report output
CMM Roster Details report is a printed deliverable with IEHP branding — design extending beyond the UI into formal operational documents.
Pre-design BRD discovery
3+ documented Q&A sessions with IEHP stakeholders before any wireframe — care manager lifecycle, workflows, regional structure, reporting requirements all mapped first.
One person. US healthcare enterprise client. 30,000 care plans. Design and Angular development. Shipped to production.
Feature Highlights
System capabilities
Multi-Chart Admin Dashboard
KPI cards, donut (plan type distribution), high-workload carousel, monthly bar chart, per-manager sparklines — all on one screen.
Dashboard DesignRBAC Role Views
Admin: full 7-module sidebar. Care Manager: Care Manager + Schedule only. Two information architectures from one codebase.
Access Control UXAvailability & Leave Management
Care manager availability table with Start/End dates, Active/Planned/Inactive status, Approval status, and bulk multi-select.
Operations UXParametric Report Generation
Filter by care plan type, manager, region, date range → generates a printed IEHP-branded Roster Details report.
Operational DeliverablesDesign System
Tokens, typography & components
A shared token-based system built to ensure consistency across every screen and state.
Color Tokens
Type Scale
Components
User Flow
Admin operational workflow
SSO Login
IEHP intranet
CMM Dashboard
30,940 plans
Manager Mgmt
35 managers
Plan Assignment
4 plan types
Generate Report
IEHP branded PDF
Tech Stack
Tools & technologies
Design
Frontend Engineering
TypeScript
CSS3My Contribution
Solo end-to-end ownership
01
Sole Product Designer
Pre-design BRD sessions, full 62-screen Figma system, multi-chart dashboard architecture, RBAC information design, printed report design — aligned to IEHP brand.
02
Sole Frontend Developer
Angular + TypeScript + CSS implementation — forms, data tables, notification system, chart widgets, printed report templates. Shipped to IEHP intranet production.
Impact & Performance
Operational scale
30K+
Care plans in system
62
Screens designed
35
Care managers managed
4
CA regions covered
Timeline
4 months: BRD through production
Month 1
BRD Discovery + Architecture
3+ Q&A sessions with IEHP. Mapped care manager lifecycle, RBAC requirements, 4-region structure.
Month 2
Dashboard + Core Modules
Multi-chart dashboard, Care Manager module, Care Plan module (4 types), RBAC views. 62-screen Figma completed.
Month 3–4
Angular Implementation + QA
Full Angular + TypeScript build. Forms, tables, notification system, report generation, printed output. Shipped to IEHP intranet.
Outcomes
The impact we shipped
Measured results from usability testing, stakeholder reviews, and post-launch adoption tracking.
30,940
Care plans in system
62
Screens designed
35
Care managers
4
CA regions covered
"Production-shipped enterprise dashboard enabling IEHP administrators to manage care plan assignment across 30,940 care plans and 35 care managers in real time — replacing spreadsheet-based manual processes."
Learnings & Reflection
What I'd do differently
01
BRD sessions are UX research
Pre-design Q&A documents shaped the entire CMM architecture. Treating stakeholder sessions as formal product discovery — not informal briefings — produced a system that mapped exactly to operational need.
02
KPI card numbers are design decisions
What to show on the dashboard hero (30,940 total, 19,046 active, 35 managers, 1 on leave) required deliberate decisions about what an admin needs on login. The numbers themselves are the UX.
Interested in working together?
Let's talk about your project or open role.
Live Prototype