OpenOnco
UA EN
← All news
July 8, 2026 site governance patients

Two doors — and why patients get a different one

The homepage now routes clinicians and patients to different places. Patients get help understanding a plan and preparing questions, not treatment recommendations — a line that has to hold for both safety and regulatory reasons.

Written retrospectively and published on July 19, 2026.

Patients were already arriving. A site about cancer treatment, indexed and public, gets read by people who have cancer — not only by the oncologists it was written for. Pretending otherwise is not a safety measure; it just means those readers get a page designed for someone else.

So the homepage now asks who you are and routes accordingly. Clinicians go to the plan builder and the knowledge base. Patients go to a free-text tumour board where they can describe a situation in ordinary language.

The line that has to hold

What patients get is help understanding a plan and preparing questions for their own oncologist. Not verdicts. Not treatment recommendations.

This is not a cosmetic distinction. A direct-to-patient clinical service would re-classify this software as a medical device under CHARTER §15.3 — with everything that implies. The education and question-preparation framing is what keeps it on the right side of that line.

Being straight about the state of the paperwork: the charter's own §2 and §15 C1 text still says "HCP-only" in places. That text has not caught up with what the site now does, and reconciling it is open work rather than something already handled.

Language now follows the reader

Shipped the same day: the site picks a language by IP. English is the default everywhere; only a Ukrainian IP flips to the /ukr/ twin, and any failed lookup falls back to English. An explicit click on the language switch is remembered and always wins over detection.

Crawlers are exempt so both language trees stay indexable, and the script never fires inside an embedded frame. The privacy disclosure for the IP lookup is on the specs page.

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.