Preview received June 24, 2026; formal proposal remains the next decision input for scope, migration waves, economics, and operating model.
The legacy environment is functional, but it creates operating gravity.
WHPS depends on ServiceLink, HPS, COBOL, JCL, DB2, MQ, EDI, DataPower, file transfer, payment tokenization, reporting, reconciliation, customer-service workflows, and older portal patterns. That environment is powerful, but it is heavily coupled, expensive to change, and slow to extend. It also limits the practical levers available to improve stability, resiliency, functionality, and SLA performance because many fixes are constrained by the underlying platform, data, integration, and release model.
The business consequence is a slow-to-act operating model.
New products, regulatory changes, group onboarding, broker workflows, service automation, and reporting improvements are slowed by scarce skills, long test cycles, brittle dependencies, duplicated support paths, manual reconciliation, and legacy release windows.
WHPS is running legacy modernization and AI transformation together.
The modernization track reduces dependency on mainframe, batch, DB2, file movement, and legacy portal workflows. The AI transformation track uses the AI SDLC Factory to deliver governed product work faster: GroupLink, broker/agent pathways, ReconLink, service testing, and adjacent MVPs are now proof points.
Track 01
Platform modernization
Discover, encapsulate, rebuild, reconcile, cut over, and retire legacy dependencies by domain.
Track 02
AI transformation
Use governed agents, secure delivery gates, evidence packets, and reusable platform patterns.
Today’s run-down covers the full AI transformation and modernization portfolio.
The discussion should start with overall AI transformation and modernization strategy, including the AWS proposal preview received June 24, 2026 and the formal proposal as the next decision input. Then move through Contact Center AI, broker/agent pathways, claims, VOC, GroupLink, ReconLink, and other use-case expansion opportunities using the portfolio tracker as the source of current status.
Use the high-level transformation slides to align modernization approach, sequencing, AI SDLC operating model, and decision path.
Broker/agent pathway, CMS/EDE evidence, security architecture, traceability, and investment view are ready for walkthrough.
Benefits/enrollment, Spanish flows, claims, VOC QA, transcription audit, and IVR migration remain the core expansion set.
Ops Portal schema, POST endpoint, Beacon Spyglass WSDLs, GCP Postgres warehouse, and case examples are in motion.
Use it to show the approach: modern product experience plus database, service, and integration modernization.
Two UAT items remain: EDI policy ID mismatch and recommendation verbosity. Round 2 business working session continues.
Same governed method is being applied across GroupLink, broker/agent pathways, ReconLink, service testing, and adjacent MVPs.
Enterprise UI modernization remains in assessment as a platform modernization lane, not a cosmetic refresh.
The future state is modern product experience on shared platform services.
ServiceLink Portal, broker/agent pathways, GroupLink Portal, and Contact Center AI become modern React product experiences with guided workflows, role-aware navigation, reusable components, secure APIs, real-time status, embedded evidence, and auditable service actions.
The target architecture is cloud-native, AI-native, and evidence-backed.
Product surfaces sit over shared identity, API gateway, event streams, domain services, data products, observability, security controls, evidence stores, AI governance, and a migration facade while legacy responsibility is progressively reduced.
GroupLink proves the modernization pattern is more than UI cleanup.
The prior CSR experience is dense, manual, and record-oriented. The target GroupLink experience becomes like a modern group operations console: account search, group health, onboarding timeline, census validation, billing context, renewal workspace, delegated admin, and evidence trail. The same lane moves database, service, and backend components forward so the new experience is not trapped on old constraints.
Broker/agent pathways show regulated product delivery moving at AI SDLC speed.
The pathway brings together broker access, agency attribution, enrollment workflows, documents, CRM/service routing, CMS/EDE evidence, security controls, and auditor handoff. The point is not a single portal name; it is the capability to build certification-grade healthcare workflows with evidence from the start.
SSO / MFA / RBAC
CMS / EDE evidence
Security documentation
Testing and remediation
Architecture diagrams
Demo walkthrough
The proof points show repeatable delivery, not isolated demos.
GroupLink demonstrates modernization from legacy screens into product workflows. The broker/agent pathway demonstrates secure regulated enrollment. ReconLink supports reconciliation and parity. Contact Center AI expands service intelligence. ClaimsLink and adjacent MVPs show the same method can create new product lanes.
The WHPS AI SDLC Factory is the control system for speed with compliance.
WHPS can use agentic development and multi-agent orchestration because the method is governed: intake, risk tiering, scoped workspaces, model and tool gateways, architecture review, secure coding, testing, privacy checks, AI evaluations, human approval, release evidence, telemetry, rollback, and incident response.
The lifecycle is agile, agentic, and compliant by design.
The AI SDLC path is Define and Strategize, Decompose and Plan, Architect and Design, Build and Integrate, Validate and Secure, Deploy and Release, then Monitor and Evolve. Each phase produces artifacts, not just activity.
Compliance is enforced through artifacts, approvals, and runtime evidence.
Risk tiers, AI inventory, data lineage, threat models, human-in-the-loop approvals, kill-switch readiness, red-team tests, bias and grounding checks, release packets, RACI, monitoring, and incident records make the transformation reviewable instead of rhetorical.
Mainframe exit happens through governed waves, not a big-bang rewrite.
Each wave moves through discovery, source inventory, dependency mapping, facade, contract testing, data reconciliation, dual run, parity scorecard, cutover approval, rollback readiness, and decommission. Value is counted when old jobs, feeds, access paths, licenses, contracts, and support procedures are retired.
UI/UX unification is a platform modernization lane, not visual cleanup.
PM00003094 creates a natural next lane for the AI SDLC. The minimum bar is a modernized unified experience across Medicare, Group, ACA, and Claims, but the higher-value path pairs the front end with database, service, integration, testing, and release modernization the same way GroupLink is being approached.
Phase 01
Unified experience layer
Design system, navigation, workflow consistency, accessibility, and shared product components.
Phase 02
Backend modernization lane
Domain APIs, data contracts, DB modernization, service-test evidence, and release controls.
WHPS moves from legacy dependency to AI-native healthcare platform control.
The end state is faster delivery, lower run cost, safer AI adoption, productized healthcare services, controlled migration, and a leadership-ready evidence system. The answer to every reviewer question becomes a diagram, policy, procedure, owner, and proof packet.