Prevention plans, for people who do not have cancer yet
The charter was amended to cover people at elevated risk but without a diagnosis. The engine now produces a Prevention Plan alongside the Treatment Plan, and the first pilots are live on the site.
Written retrospectively and published on July 19, 2026.
Until now the engine had exactly one answer for a patient with no confirmed disease: "could not resolve disease." That is correct and useless. A person with chronic hepatitis C, or a confirmed Lynch syndrome carrier, has a real and actionable cancer risk long before there is anything to stage.
CHARTER §3 is now amended to cover them — specifically, HCP-mediated prevention and early-diagnosis recommendations for at-risk asymptomatic individuals: first-degree relatives, IARC Group 1 chronic infections, and occupational exposures.
How it works
A profile with no confirmed disease but at least one fired prevention-eligible red flag now routes to Prevention Plan generation instead of that dead-end warning. Same engine, same knowledge base, same citation requirements.
Every prevention pathway ships at least two tracks — the intervention, and an observation track for declining it. That is not a stylistic choice: presenting a single binding directive would break the non-device positioning in CHARTER §15.2 C4.
What is live
32 prevention case pages, covering all seven IARC Group 1 infectious etiologies (HCV, H. pylori, HBV, HPV, HIV, EBV, HTLV-1), hereditary carrier pilots, and occupational, chronic-condition and iatrogenic exposures. They are in the gallery and the plan-builder dropdown.
What was deliberately left out
Path B — prevention advice direct to a patient, with no clinician in the loop — is parked, because it would trigger re-classification as a medical device under §15.3.
The scope document says plainly that this is a narrowing to fit the current charter rather than the intended endpoint. Worth recording while it is still inconvenient to admit.
Comments
Threads are public and indexed — please keep personal medical data out of them. Found a clinical error? Open an issue instead.
Comments are not switched on yet — the backend still needs to be configured.