Skip to content

The Wellness Intelligence System

From resident-authorized signals to a baseline your team can question.

WIS is the measurement layer beneath a wellness program. It organizes the information available to the pilot, shows what is missing, and gives leadership a consistent view for review.

How the system earns trust

Coverage before confidence.

A useful baseline does not hide thin participation or missing sources. The operating sequence makes authorization, coverage, and limitations part of the output.

  1. 01

    Authorize the inputs

    Residents choose their WIS check-ins and optional sources. Any partner-provided source, integration method, and sharing rule is selected in the signed pilot scope.

  2. 02

    Organize the signals

    WIS maps the available information across 275 modeled drivers and 8 weighted wellness dimensions. Missing data stays visible rather than being treated as certainty.

  3. 03

    Build the baseline

    The reporting view shows cohort size, reporting period, source coverage, methodology version, and material limitations alongside the available wellness pattern.

  4. 04

    Review with context

    Staff use the agreed reporting surface as wellness decision support. WIS is not diagnosis, treatment, emergency monitoring, or a substitute for professional judgment.

Illustrative product view

A baseline with its limits attached.

The interface is designed to answer two questions together: what pattern is visible, and how much evidence supports it?

Illustrative example with simulated data. This is not a live resident result.

Cohort baseline

Coverage first

Simulated data

Reporting period

30 days

Source coverage

Shown by source

Missing data

Disclosed

Physical
Emotional
Community
Environmental

Evidence boundaries

What WIS does not ask you to assume.

The pilot is designed to expose fit and limitations before a longer-term decision.

  • Aggregate or de-identified partner reporting is the default consumer-direct posture.

  • Resident-identifiable sharing requires separate authorization and a written role and data-flow analysis.

  • Simulated product views are always labeled and are never presented as resident results.

  • Data sources and optional features are scoped in writing; code availability does not make them part of every pilot.

Next step

See how this fits a senior-living pilot.

Review the operating model first, then evaluate whether your cohort, data posture, and decision timeline fit the standard pilot.