Portal Landscape Assessment & Rationalization

- Lead a comprehensive inventory of the current portal and digital-services estate across every constituent-facing channel, cataloguing platform, ownership, authentication model and functional overlap.
- Identify specific areas of platform fragmentation and duplicated functionality across member, provider, employer, broker and public-facing systems.
- Analyze user workflows across each portal to identify opportunities to shift high-cost, telephone-based support toward self-service digital channels.
- Produce a rationalization roadmap that sequences consolidation of redundant platforms and retirement of legacy point solutions without disrupting active users.

Target-State Portal Architecture

- Define the target-state architecture for a common, persona-based portal platform, with role-based and constituent-based access models replacing today's siloed logins.
- Design the segmentation model that determines which capabilities are served by a shared platform core and which remain constituent-specific, with clear criteria for what belongs in each.
- Produce architecture decision records, target-state diagrams and platform standards that development teams and delivery partners can build against.
- Evaluate build-versus-consolidate-versus-replace options for each existing portal technology, with a transparent point of view on which platforms extend into the target state and which are retired.

Security, Privacy & Risk Architecture

- Architect the security, privacy and risk-management control layer for the unified portal platform, with Protected Health Information handling designed in from the target-state architecture stage, not retrofitted later.
- Define a consistent identity and access model across every persona, so a member session and a provider session are governed under the same policy framework at different privilege levels.
- Work directly with security and privacy teams to align the target-state portal design with existing regulatory obligations, including HIPAA and comparable data-protection frameworks.




- Establish audit-ready access logging and data-handling standards that hold consistently across every constituent-facing surface.

Identity, SSO & Integration Architecture

- Design a unified single sign-on and identity architecture spanning every constituent portal, replacing today's fragmented, platform-specific logins with one governed identity plane.
- Architect integration patterns between the portal platform and core systems of record, including claims, eligibility, provider data and CRM platforms.
- Define API and data-exchange standards that let the portal platform surface accurate, real-time information without duplicating source-of-truth data.
- Assess existing CRM-based experience layers, including Salesforce Health Cloud implementations and any purpose-built extensions running on top of them, for their role in the target-state architecture.

Stakeholder Engagement & Requirements Definition

- Lead requirements-gathering across member, provider, employer and broker stakeholder groups to define target-state digital-experience requirements grounded in best practice, not assumption.
- Present findings, trade-offs and the recommended rationalization roadmap to technology and business leadership, building the case for investment and sequencing.
- Partner with enterprise architecture to ensure the portal target state is consistent with the broader application and technology rationalization strategy already defined for the organization.

Governance, Roadmap & Delivery Enablement

- Produce the artifacts that hand cleanly to delivery: target-state architecture, integration standards, sequencing roadmap and the business case for each phase of consolidation.




- Define success metrics for the rationalization effort, including self-service adoption, reduction in duplicate platforms and support-contact deflection.
- Establish architecture governance for the portal platform going forward, so future portal or self-service requests are evaluated against the unified standard instead of defaulting to another point solution.

Required Experience

- 7 12 years in enterprise architecture, digital experience or portal architecture roles, including at least 5 years leading portal rationalization, consolidation or platform-strategy engagements at enterprise scale.
- Demonstrated experience architecting role-based or persona-based access models across multiple distinct user constituencies on a shared platform.
- Strong background designing identity, SSO and API integration architecture across disparate systems of record.
- Experience in regulated or compliance-sensitive environments subject to data-protection frameworks such as HIPAA, and specifically architecting for Protected Health Information handling.
- Experience working effectively across a distributed, multi-time-zone team, with proven ability to build stakeholder trust and drive outcomes remotely.

Required Technical Expertise CRM & Experience Platforms

Salesforce Health Cloud (or comparable health-focused CRM), Salesforce Marketing Cloud, experience-layer applications built on a CRM platform

Identity & SSO

Enterprise SSO and federated identity design (SAML or OIDC), role-based and persona-based access models, session security architecture

Integration & APIs

API design and governance, integration with claims, eligibility and provider-data systems of record, event-driven or service-based integration patterns

Security & Privacy

PHI handling and data-protection architecture, HIPAA-aligned access control and audit logging, privacy-by-design principles

Architecture Practice

Enterprise and solution architecture methods, architecture decision records, target-state roadmapping and platform rationalization frameworks

📌 Enterprise Portal Architect -Salesforce (Chennai)
🏢 Santan Intellect
📍 Chennai