Health CopilotDesign-partner concept · UK

A conversation, not a product pitch

What if members could understand their whole health picture—without the plan holding it?

A privacy-first context layer that turns member-owned data into a clearer next step across the benefits you already provide.

Member-heldEvidence-labelledBenefit-connected
Explore the idea

The opportunity

Good benefits. Fragmented member context.

Health plans already provide valuable services. The missing layer is often the member's ability to connect their own signals and understand which service matters now.

Member
WearableBlood testSymptomsPast advice
?“What should I do next?”
Virtual GP
Counselling
Screening
Wellbeing
Cash-plan benefits
The problem is not a lack of services. It is the cognitive work required to choose and use them in context.

The product concept

Private Health Context

A member-controlled layer that sits beside—not inside—the insurance, claims or employer systems.

01

Connect

The member chooses wearable history, lab documents and optional notes.

02

Understand

Health Copilot creates a timeline, flags uncertainty and shows relevant evidence.

03

Act

The member gets a better question for a clinician and a clearer route to an existing benefit.

Not a risk scoreNot a diagnosisNot another claims portal

Input → private core → output

A small system around the member—not a new data lake.

Member chooses
⌁WearablesSleep · HRV · activity
▤Lab documentsTrends · reference ranges
✎Daily contextNotes · food · symptoms
◎Genetics, optionalLocal-only analysis
⌾Member-held coreEncrypted · permissioned · reversible
TimelineContextEvidence

Nothing is disclosed by default.

Member receives
Weekly clarityWhat changed · what may matter
Pre-GP briefOne page · source-linked · concise
Benefit navigationA relevant existing service, at the right moment

Example member experience

One screen that explains the week.

The first aha moment is not “AI found a disease.” It is a simple, grounded explanation of what changed and which next step is worth considering.

Working prototype exists

The concept screen is an English adaptation of the current Health Copilot workflow.

Health CopilotPrivate
Your week · 14–20 July
Recovery contextMore stable
Pattern worth noticing

On three nights after earlier meals, your sleep duration was longer and morning resting heart rate was lower.

WearableFood logModerate confidence
Suggested next step

Repeat for one more week. If fatigue continues, prepare a GP question using your recent ferritin result.

Example output

A better conversation with the right service.

The output is a preparation artefact—not a clinical conclusion.

Member-owned health context

Brief for a GP conversation

20 July 2026 · v1

Why I am booking

Persistent morning fatigue despite stable sleep schedule. I would like to understand whether follow-up blood tests are appropriate.

Context to review

  • Ferritin: 20 ng/mL on 26 MarchLab
  • Resting HR: +5 bpm versus 8-week baselineWearable
  • Fatigue logged on 9 of 14 morningsJournal

Questions, not recommendations

  1. Would repeat ferritin and full blood count be useful?
  2. Could current supplements affect interpretation?
Current Health Copilot doctor brief prototypeCurrent working prototype · source language version

Trust architecture

Designed so the partner does not need the member's data.

Privacy is not a disclaimer at the end. It is the product boundary.

Member device / private vault
Personal context
Wearable timelineLab documentsOptional local genetics
Member-held key
Member-chosen sharingA reviewed brief may go to a clinician or service—only by explicit action.
Separate partner channelAggregate learning onlyNo member-level context crosses this boundary
Design partner · aggregate channel
Sees onlyAggregate activationDe-identified service-navigation signalsConsented qualitative research
Proposed boundaryGenetics · raw data · individual reportsRisk scores · claims decisions

Conceptual privacy-by-design architecture. Final controller / processor roles, DPIA and claims language require UK legal review.

Why design together

Complement the benefit ecosystem you already have.

The goal of a first conversation is not to buy a finished solution. It is to test whether this layer performs an important member and product need.

Health Shield lens

From access to a connected member journey

Explore how a member-held brief could make virtual GP, wellbeing and cash-plan benefits easier to use in context.

Medicash lens

From screening signals to ongoing context

Explore how HealthLens, wearable inputs and existing digital services could lead to a clearer member-owned next step.

01

Which member moment is most underserved today?

02

What data boundary would earn trust?

03

Which existing benefit should the context layer support?

04

What evidence would justify a controlled test?

An invitation

Could this make your existing benefits feel more personal—without making member data less private?

We would value a 30-minute product conversation with leaders in member experience, digital health and partnerships.

Start a conversation
Boris Korolboris.korol@ai-automation.studioai-automation.studio