Making a Complex Healthcare Ecosystem Feel Simple: A Wellness Rewards Platform for a National Health Plan
A national health plan’s wellness rewards platform: members sign in, find a deal and redeem it, while identity, marketing, member data and compliance work together behind the experience. We built it, and we run it.
The work
The Challenge: Wellness Rewards Inside Healthcare Security and Compliance
Members need to sign in securely, find offers that apply to them, receive communications that fit and use the experience in their preferred language. Behind that, the platform connects a growing ecosystem of healthcare and marketing technology: Okta for identity, Marketo for marketing, Drupal for content, AWS underneath, analytics, member eligibility data and third-party vendors, all while protecting sensitive member information.
And in healthcare, security and compliance set the rules of the build from the first decision. The job is to keep all of that complexity working behind an experience a member never has to think about.
The Strategy: A Connected Product on Drupal, Okta and AWS
We approached the platform as a connected product, not simply a website.
- Each system does what it does best. Drupal provides the content and experience layer, on AWS; integrations connect identity, marketing, member data, offers and analytics behind it, with information moving between systems in controlled, purposeful ways.
- Identity is part of the experience. Integrating with Okta handles members through the health plan’s broader authentication ecosystem: the platform knows who someone is, confirms eligibility and grants the right access, with no new credentials to manage.
- Multilingual inside one product. Members engage in the language that works for them, and the organization maintains one platform for every audience it adds.
- Security is an architectural constraint, not a final check. Authentication, authorization, data movement, integrations, infrastructure and privacy are parts of one system, maintained continuously as requirements and risks evolve.
The Outcomes: One Secure, Multilingual Member Platform
Members get an easy way to discover and use benefits beyond their coverage: sign in, find a deal, redeem it. The organization gets a platform built for a far more complicated ecosystem — secure authentication and access, controlled connections across marketing, identity and member data, centralized content and offer management, multilingual experiences and healthcare compliance met in the architecture.
The platform keeps moving by design. Vendors change, APIs change, security requirements evolve, and new campaigns, benefits and languages arrive, so Pare & Co continues to run, maintain, secure and optimize what it built. The value is the whole: every piece working together as one product, a secure, connected healthcare platform built to make a complicated ecosystem feel simple to the member.
The detail
Why it mattered
- Four jobs, one experience. A member has to sign in securely, find offers relevant to them, receive communications that fit and use all of it in their preferred language. Each of those is its own system behind the scenes, and the member should never have to know how many systems are involved.
- An ecosystem, protected. The platform connects identity, marketing, content, analytics, member eligibility data and third-party vendors while protecting sensitive member information. Every connection is another dependency, and in healthcare every dependency is a security decision.
- Compliance sets the rules of the build. In healthcare, security and compliance decide how the product works from the first architectural choice. The platform is designed so meeting them is part of how it runs, and the complexity stays invisible to the member.
How it was built
- A connected product. Drupal provides the content and experience layer, and integrations connect identity, marketing, member data, offers, analytics and other services behind it. The architecture lets each system do what it does best, with data moving between them in controlled, purposeful ways.
- Identity through Okta. Authentication on a member platform is identity work: the platform has to know who someone is, determine that they are eligible and grant appropriate access without friction. Integrating with Okta handles identity through the health plan’s broader authentication ecosystem, with no new set of credentials and no isolated member account.
- Marketing connected, responsibilities clear. Marketo connects member activity to the organization’s broader marketing ecosystem, supporting campaigns and communications. Each system keeps a clear responsibility, and the member platform stays a member platform.
- Multilingual within the same product. For a national health plan, accessibility includes language access. Members engage with wellness benefits in the language that works for them, and the capability lives inside the one underlying product, however many audiences and languages the organization adds.
How it runs
- Security as an architectural constraint. Authentication, authorization, data movement, third-party integrations, infrastructure, application security, privacy and ongoing maintenance are parts of the same system, and every new integration is designed as another controlled connection. The consequences of getting security wrong in healthcare are high, and the architecture is where that reality is answered.
- Built, then operated. Vendors change, APIs change, security requirements evolve, new campaigns and benefits launch, and languages and content need maintaining. Pare runs, maintains, secures and optimizes the platform continuously.
- Ownership that sees the whole. A product with this many interconnected pieces needs someone who understands each system and how a change in one affects everything around it. That is the job of the managed engagement.
Wellness rewards platform questions
What is a wellness rewards platform?
A member-facing product where health plan members sign in, discover discounts and benefits beyond their coverage and redeem them. Behind the experience it is a connected healthcare platform: identity, member data, marketing, content, analytics and third-party services working together under healthcare security and compliance requirements.
How does member login work on a health plan platform?
Through the health plan’s own authentication ecosystem. Integrating with Okta lets the platform know who someone is, confirm they are eligible and grant the right access, with no separate set of credentials for members to manage and identity aligned with enterprise security requirements.
Can one member platform serve multiple languages?
Yes. The platform supports multilingual experiences inside the same underlying product, so members engage with wellness benefits in the language that works for them and the organization maintains one platform for every audience it adds.
Who runs a healthcare member platform after launch?
For this health plan’s member wellness rewards platform, Pare & Co. We built it and we continue to run, maintain, secure and optimize it: vendors change, APIs change, security requirements evolve, and new campaigns, benefits and languages arrive. Long-term ownership matters when a change in one system can affect everything around it.
Client leadership
Matthew O’Bryant
Matthew O’Bryant has led member-facing platforms for health plans, where the eligibility rules underneath a simple screen are anything but.