Health care · Platform modernization

AEM & SPA modernization

Organization
Centene Corporation / HealthNet
Role
Product Design Manager, Member Portal & Design Systems
Scope
Secure Chassis · AEM SPAs
Populations
Medicaid · Medicare · PDP · Marketplace

Overview

A dominant theme across my tenure has been platform migration and modernization. Centene's member web experience was not a single product. It was Medicaid, Medicare, PDP, and Marketplace populations on different legacy stacks, each with its own navigation, compliance constraints, and release cadence.

I led design for moving those populations onto Secure Chassis and Adobe Experience Manager single-page applications (AEM SPAs). This was not a feature sprint. It was modernizing the entire member portal ecosystem while members continued to manage benefits, claims, payments, and pharmacy every day.

Centene member portal on modernized chassis

Member portal experience on the modernized platform: one chassis, multiple lines of business

Platform migration

The business committed to migrating member populations to Secure Chassis and AEM SPAs as the shared technical foundation for authenticated member experiences. That shift touched every high-traffic journey in the portal, not just net-new features.

Populations in scope

Medicaid, Medicare, PDP, and Marketplace member populations moved onto the shared chassis model, each with line-of-business rules but a common interaction and release pattern.

Parallel initiatives

Ambetter portal migration and enhancements, Marketplace and Medicare portal improvements, and compliance and vulnerability remediation ran alongside chassis work so security and regulatory obligations did not wait for a big-bang launch.

A huge portion of the team's work was modernizing the entire member portal ecosystem, not just building features on top of legacy pages.
  • Migration to Secure Chassis across major member populations
  • Movement to AEM SPAs for authenticated member experiences
  • Ambetter, Marketplace, and Medicare portal enhancements in parallel
  • Compliance and vulnerability remediation woven into release planning

What my team delivered

Design leadership here meant orchestrating hundreds of legacy screens into a governed chassis experience. My team produced the UX decisions, patterns, and migration artifacts engineering and product needed to ship incrementally without losing member trust.

  • Chassis experience modelShared navigation, layout, and interaction patterns for authenticated members across lines of business.
  • AEM SPA patternsSingle-page application flows aligned with Fondue components and synchronized design-and-code deployment.
  • Ambetter portal migrationStructured migration and enhancements as the first major downstream application of chassis modernization.
  • Medicare & Marketplace improvementsPortal upgrades for additional populations with compliance and accessibility standards built into the chassis.
  • Secure member consolidationSecure enrollment and account experiences on one Fondue-based framework instead of fragmented legacy stacks.
  • Compliance remediationDesign and engineering alignment on vulnerability and regulatory fixes without pausing member-critical releases.

Legacy to chassis mapping

Before engineering could migrate pages, design had to map what members had on legacy portals to what they would get on chassis. That work was detailed, cross-functional, and often where product decisions got made.

We documented legacy marketplace member portal pages against chassis-based targets. That included redesign and prioritization decisions for claims, payments, pharmacy, My Spending, and top-level portal navigation. Each mapping row was a member journey that either moved as-is, improved on migration, or merged into a new pattern.

Experience domains mapped

Claims, payments, pharmacy, spending summaries, and global navigation were traced from legacy implementations to chassis targets so engineering could sequence migrations and product could sign off on parity.

Design governance

Migrations adopted Fondue components where possible, enforced accessibility standards (WCAG) at the pattern level, and kept analytics instrumentation consistent across populations.

Analytics and platform mapping representing legacy-to-chassis migration planning

Legacy-to-chassis mapping across member populations

Outcome

  • Ecosystem modernizationMoved Medicaid, Medicare, PDP, and Marketplace populations toward Secure Chassis and AEM SPAs as a shared member platform.
  • Incremental deliveryLegacy-to-chassis mapping let teams ship migrations in phases without a single risky cutover.
  • Line-of-business continuityAmbetter, Marketplace, and Medicare improvements advanced in parallel with platform work.
  • Secure memberConsolidated secure experiences onto one Fondue-based framework aligned with chassis delivery.
  • Governed scale30+ designer org operated on shared patterns, accessibility gates, and design-and-code parity through Fondue.

Related: Centene design leadership · ESI pharmacy migration · Fondue design system