IKS Health
2025
Scaling Enterprise Healthcare: Unifying Multi-Product Ecosystem Through a Scalable Design System
With IKS Health's growing portfolio of healthcare products, maintaining a consistent user experience across teams became a key challenge. Similar components were being designed differently, creating inconsistencies in spacing, states, interactions, and usage patterns. We addressed this by creating a scalable, accessible design system that brought consistency to the product ecosystem while giving teams the flexibility to design and deliver faster as the platform evolved.
The Strategic Context & The Ecosystem Problem
The Multi-Product Dilemma: IKS Health tools serve clinical operators, physicians, and administrative staff simultaneously. When users switched from Pre-Op Visit to MyCareHub or Denial Prediction, mental models broke: status indicators meant different things, keyboard navigation was inconsistent, and visual hierarchies clashed.
The Cost of Inconsistency:
Clinical Risk: Alert ambiguity (e.g., critical vs. advisory warnings styled arbitrarily).
Engineering Waste: Multiple dev pods rebuilding the same data tables, filters, and modals from scratch across varied stacks (React, legacy modules, Tableau dashboards).
Time to Market: New healthcare modules took months just to wireframe and style.
Diagnostic Audit & Architectural Strategy
We didn’t start by designing components. We started by understanding the ecosystem.
Every product team had solved the same problems in its own way. Buttons looked different from product to product, tables behaved differently, and each team had its own take on common UI patterns. Before adding anything new, we needed to know what was actually working and what was causing the inconsistency.
Existing Product Screens
Component Inventory (Methodology: Component Audit)
We started by establishing a clear view of the existing component landscape across the product ecosystem. Each product team contributed its current patterns - including buttons, tables, filters, charts, steppers, navigation, and other foundational UI elements.
We analyzed these components across structure, behavior, states, accessibility, and usage to uncover duplication, inconsistencies, and opportunities for consolidation. The objective wasn’t to replace what teams had built, but to identify the strongest patterns and create a shared foundation that could scale across products without compromising product-specific needs.
Foundations
Color System / CTAs / Other UI elements
Color System
CTAs
Other UI elements
Key Learnings
Tech Feasibility Before Visual Polish
"A design system is only as good as its cross-stack implementation." Talking to engineering early—especially regarding legacy surfaces like Tableau—revealed hard interaction boundaries before patterns were codified. Designing within those constraints prevented rework and built trust across multidisciplinary engineering teams.
Accessibility in Healthcare Is Non-Negotiable
"Accessible design isn't a checklist; it's clinical safety." Designing for high-stress, fast-paced medical environments taught us that high contrast, legible data tables, and distinct status indicators directly reduce diagnostic friction and operator fatigue.
Governance Matters More Than Component Count
"Building components is easy; keeping them cohesive requires a living system." A library of 30+ components succeeded because it was backed by clear semantic token hierarchy (Global → Semantic → Surface), strict naming conventions, and shared ownership rituals between designers and developers.
"By treating the design system as an infrastructure product rather than a static UI kit, we bridged the gap between four legacy healthcare applications and modern front-end standards. The result was a scalable, accessible foundation that sped up delivery by 40% while ensuring clinicians and patients interact with a reliable, cohesive digital ecosystem."
