06-reference/research

health wizz status rescore

2026-05-24·research-brief·source: deep-research

Health Wizz — pivoted away from patient-data-sovereignty, re-scored 0/3

Verdict (one line)

Pivoted away. Health Wizz's 2026 product is clinical-trial-recruitment B2B SaaS for pharma sponsors and CROs (Journey Wizz platform, FHIR-via-150-EHRs integration). The original patient-as-filing-cabinet + data-broker model that earned a 1.5/3 score on the May 11 scan is gone from the live product surface — replaced by a polished pharma-trial-recruitment pitch with named metrics (60% screen-failure reduction, 3x site activation). Re-score: 0/3 on the patient-data-sovereignty + outcome-procurement wedge. Same pivot pattern as Hu-manity.co — patient-sovereignty rhetoric collapsed into a different revenue model when the sovereignty thesis couldn't generate revenue.

The question

Health Wizz status check — re-score against the 3-leg (Data-Sovereignty + Value-Based-Contract + Patient-Incentive cash) rubric from the May 11 patient-data-sovereignty competitor scan. Need to confirm whether Health Wizz is still a 2026 competitor on the wedge or whether it joins Hu-manity in the pivoted-away cautionary-tale bucket.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The May 11 scan's "clean white space" verdict gets stronger, not weaker. Two of the three 1.5/3-to-2/3 "closest competitors" (Hu-manity and Health Wizz) are now confirmed-pivoted-away in May 2026. That leaves Embleema (2/3 in form) as the only remaining serious competitor on the wedge — and the May 22 Embleema brief showed they pivoted to DoD biosecurity, not VBC + patient-sovereignty. The patient-data-sovereignty + outcome-procurement wedge is now even cleaner than the May 11 verdict claimed — all three "closest competitor" candidates have functionally abandoned the thesis.

The failure-mode pattern is now repeatable enough to name. Both Hu-manity and Health Wizz built (a) patient-anchored data-rights/sovereignty rhetoric, (b) a patient-facing app to hold the data, and (c) an aspirational data-licensing-revenue-share model. Both stalled at sub-$1M funding (Health Wizz $737K, Hu-manity $5.5M pre-seed). Both pivoted into a different B2B vertical where revenue is real (trial recruitment / cookie compliance), keeping the patient-sovereignty marketing copy as legacy branding. The pattern: patient-sovereignty + data-licensing-as-revenue does not stand alone as a commercial wedge — the operator either pivots to a B2B vertical or stalls. This is why the May 11 bet architecture requires the VBC + outcomes-tied PI legs together — without the contracted-savings flow, the patient-sovereignty leg has no sustainable revenue model.

Specific RDCO action: In the Phase-1 MVP positioning copy, cite Hu-manity and Health Wizz as the cautionary-tale duo — both as social proof that "patient app + data licensing revenue share" alone has been tried twice and failed twice, validating the structural choice to bundle DS with VBC + outcomes-PI. This becomes a defensible differentiation paragraph in the bet-architecture v2 and a candidate Sanity Check editorial angle ("the two times patient-data sovereignty got tried as a standalone business model in the last 8 years, here's where they ended up").

The pivot-pattern also informs the kill criteria for RDCO's own bet. If after 18 months the VBC + PI legs cannot generate contracted revenue and only the patient-app DS leg is operationally alive, the RDCO bet has hit the same failure mode as Hu-manity and Health Wizz — at which point the kill-or-pivot decision should NOT be "lean into the patient-app and find a different B2B vertical" (that's the trap both predecessors fell into). It should be a clean wind-down.

Open follow-ups

Sources

Vault:

Web (accessed 2026-05-24):