06-reference/research

patient data sovereignty competitor pivot v2

2026-06-27·research-brief·source: deep-research
patient-data-sovereigntycompetitor-scansanity-checkdifferentiationfailure-mode

Close-out v2: the three closest patient-data-sovereignty competitors all pivoted away — name the failure-mode, harden the moat, draft the editorial

The question

Embleema is confirmed pivoted to DoD biosecurity (May 22), Hu-manity to cookie-compliance SaaS (May 18), Health Wizz to clinical-trial-recruitment B2B (May 24). All three closest competitors on the patient-data-sovereignty wedge have pivoted away. Should the May 11 competitor-scan get a v2 close-out brief documenting the pattern as a defensible RDCO differentiation paragraph + Sanity Check editorial angle? (Context: deep-research-derivative — three re-scores in 13 days show the SAME pivot-pattern; this is now a repeatable named failure-mode. Treat as a request to produce the v2 close-out itself.)

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

Verdict: yes, formalize the v2 close-out — this brief is it. Three re-scores in 13 days converging on one mechanism is exactly the threshold for promoting a pattern from "observation" to "named failure-mode that informs the bet's kill criteria and positioning." The close-out costs little and retires four open follow-ups across the prior briefs. The one discipline to carry forward: cite Embleema as "exited the wedge" rather than over-claiming a confirmed corporate pivot, because the public framing is expansion. The pattern survives the softer wording.

(1) Defensible RDCO differentiation paragraph (drop-in for the bet-architecture v2):

Patient-data sovereignty has been attempted as a standalone business at least three times in the last eight years — Hu-manity.co (the "31st human right," 2018), Embleema (blockchain patient-consent with crypto-token payouts, 2017), and Health Wizz (the patient data "filing cabinet," 2016). All three are still alive in 2026, and none of them still sells patient-data sovereignty. Hu-manity sells cookie-consent banners; Embleema sells pharma real-world-evidence and a DoD biosurveillance contract; Health Wizz sells clinical-trial recruitment to pharma sponsors. Each kept the sovereignty rhetoric as legacy branding on a dormant app and moved the revenue to whatever B2B vertical was nearest. None raised beyond a single early round — the market declined to fund the unbundled thesis three separate times. The lesson is structural, not incidental: "the patient owns their data and gets paid for licensing it" has no durable revenue mechanism on its own, so the operator is always pulled toward selling something else to someone other than the patient. RDCO does not compete with that thesis — RDCO fixes its missing leg. We bundle data-sovereignty with a value-based payer contract (the revenue anchor) and outcome-tied cash payouts to patients (the savings-share, not a data-licensing royalty). The payout comes from a contracted medical-savings pool, not from selling the patient's data — which is precisely the leg every predecessor lacked and the reason none of them could stay.

(2) Sanity Check editorial angle. The failure-mode is a genuine, original re-frame (clears the [[feedback_no_derivative_sanity_check_pieces|no-derivative-pieces]] bar — the sources are evidence for a thesis, not a topic to summarize), and the mechanism generalizes beyond healthcare, which is the Sanity Check sweet spot. Candidate hook:

"Three startups spent eight years proving you can't sell data dignity. Here's the receipt — and the one thing they all skipped." Walk the reader through the identical arc — sovereignty manifesto → patient app → 'patients get paid for their data' → silence → a completely different B2B product with the old slogan still in the footer. The payoff isn't "data sovereignty is a scam"; it's the engineering-flavored generalization the founder's audience already feels in their bones: a noble data-architecture with no revenue mechanism attached always degrades into selling the thing you swore you wouldn't. Land it on the universal version — the difference between a principle and a business is who pays, and when the user can't pay, someone buys the user.

Timing caveat carried from the Embleema brief: publishing names the white space publicly and could tip a competitor that the field is empty. Mitigation — the editorial can run the generalized failure-mode (principle-without-revenue-mechanism) without disclosing RDCO's specific 3-leg wedge or that RDCO is entering it. Run the pattern, hold the wedge. That keeps the piece publishable pre-launch without leaking positioning.

Kill-criteria carry-forward. The pattern also hardens the bet's own kill rule (already noted in the Health Wizz brief, restated here as the close-out's durable output): if at the 18-month gate the VBC and PI legs have not produced contracted revenue and only the patient-app DS leg is alive, RDCO has hit the exact failure mode — and the correct move is a clean wind-down, not "lean into the app and find a different B2B vertical." That last move is the trap all three predecessors fell into. Naming it now makes it harder to rationalize later.

Open follow-ups

Related

Sources

Vault:

Web (accessed 2026-06-27):