Oncology patient support programs are usually outsourced across three vendors, scattering cancer patients’ data and leaving the sponsor accountable for a breach it can’t see coming. A different approach: run the program — secure comms, adverse-event capture, adherence — on infrastructure the sponsor owns.
A support program that leaks is oncology patients’ records in the headline, and the sponsor’s name beside them.
When a pharmaceutical company launches an oncology therapy, it doesn’t just ship a drug — it ships a promise to help patients stay on it. These patient support programs handle side-effect reporting, adherence coaching, financial navigation, and the endless questions a frightened cancer patient has. Almost always, the pharma company outsources the whole thing to a third-party vendor. And almost always, that means handing over the most sensitive data imaginable to a company it doesn’t control.
The patient support program problem
Oncology is where patient support programs matter most and cost most. The therapies are complex, the side effects are serious, and adherence is fragile precisely when it’s most important. A good program measurably improves persistence on therapy. But the standard model has a structural flaw: the manufacturer, the specialty pharmacy, and the third-party program vendor each hold a slice of the patient’s data, none of them owns the whole relationship, and the patient’s cancer information flows through systems the sponsor can neither see into nor fully secure.
When a data breach happens — and in this vendor-sprawl model it eventually does — it’s oncology patients’ records that leak, and the sponsor’s name in the headline.
A different approach: own the program
Now imagine the sponsor or specialty pharmacy running the support program on infrastructure it owns. A self-hosted, source-available platform like VBWD is built for exactly this shape of problem — with the essential caveat, stated up front, that it is infrastructure, not medicine: not a diagnostic system, not a clinical decision tool, and not a substitute for the oncology team.
What it does provide is the operational spine of a program. A secure, end-to-end-encryptable channel for patients to report side effects and ask questions, where the conversation lives on the sponsor’s own servers rather than a vendor’s. A grounded assistant that answers logistics and education questions — how to store the medication, what to do about a missed dose, where to find financial assistance — from the program’s own approved content. Access controls that gate who on the care team sees what, with a search layer engineered so patient records can’t be surfaced by a misconfigured query. And data ownership: the program’s data stays in one place the sponsor controls, instead of scattered across three vendors. Explore the architecture and the developer docs to see how the access and messaging layers fit together.
The pharmacovigilance angle
There’s a regulatory bonus hiding here. Oncology programs carry a duty to capture and report adverse events. A secure channel the sponsor owns, feeding a database the sponsor controls, is a cleaner path to reliable adverse-event capture than a fragmented vendor chain where reports can fall between systems. Owning the infrastructure makes the compliance obligation easier to meet, not harder — provided the pharmacovigilance workflow itself is built and validated properly on top of it.
The boundary
The line is non-negotiable in oncology. A program assistant handling logistics, education, and structured side-effect intake is a support tool. Triaging whether a reported symptom is a medical emergency, or advising on dose changes, is clinical work that belongs to the oncology team, full stop. Owning the platform improves security, data control, and adverse-event capture; it does not and must not replace the clinical judgement that oncology demands.
Why it matters
The current model asks pharma companies to run their most sensitive patient relationships on infrastructure they don’t own, then holds them accountable when it leaks. Self-hosted, source-available infrastructure offers the alternative: keep the program, the data, and the patient relationship under one roof you control. VBWD is free for commercial use below a defined revenue threshold, which makes owning the stack a realistic option rather than a nine-figure build. In oncology, where the data is this sensitive and the stakes this high, ownership isn’t a preference — it’s risk management.
General information for pharma and healthcare decision-makers, not medical, legal, or regulatory advice. Patient support and pharmacovigilance systems require rigorous validation, governance, and compliance review. VBWD is infrastructure, not a medical device or clinical decision system.
Explore VBWD
VBWD is a self-hosted, source-available platform for building secure, data-owned applications — used here as infrastructure, never as a medical device. Learn more:
- 🌐 Platform and docs: vbwd.cc — the plugins, the architecture, the developer docs, and pricing.
- 💻 Source on GitHub: github.com/VBWD-platform
- 🎥 See it running: demo video · 💼 LinkedIn
Free for commercial use while VBWD-attributable sales stay under the value of 6.7 BTC a year.
