For vendors.
Your product needs population-scale answers; building the data layer that produces them is years of work that isn't your product. Radial is that layer, offered in whatever shape your product needs.
Three ways to ship it
The platform inside your product
Radial runs as a component of your deployment, including on-prem alongside your own install.
Your UI, our engine
Curated cases, dose data, and DICOM operations through the versioned REST contract.
Or white-label: the analytics under your brand, scoped as part of the OEM engagement. All three shapes share the property that matters: your customers' data stays in your product and their institution, not in a third party's cloud.
Independence, structurally
Oncurate has no treatment-delivery, planning, or OIS business. Building on Radial doesn't put your roadmap on a competitor's platform, and it doesn't route your customers' data through a rival's infrastructure: a structural fact worth more than any partnership clause.
What you're not rebuilding
Under the contract is the part that takes years, and it is more than an importer.
Ingest. DICOM-RT from any system that exports it (i.e., CT, MR, and PET with RTSTRUCT, RTPLAN, and RTDOSE), a staged import lifecycle, and duplicate and conflict reconciliation.
Standardization. Structure names mapped to TG-263 by a deterministic model that learns per deployment from confirmations. High-confidence names confirm automatically and are recorded like hand confirmations; everything below confidence is queued for review with the reason it matched.
Numbers you can stand behind. DVH, OVH, and DTH from an engine with public lineage, checked against known-answer reference cases, and readers that refuse to guess when a record is incomplete or ambiguous (e.g., doses that may already be summed).
The layers your product needs next. The columnar cohort store and graphical query, protocol scorecards and limit sheets, ambient monitoring, the versioned public API, and FHIR R4 in both directions (inbound clinical records and an outbound mCODE Radiotherapy Course Summary), at pilot stage.
What ownership costs
The first 80% takes a month: a loader for clean single-vendor exports and a DVH calculator (ours is open source, so start there). The rest is a standing commitment rather than a project, and it is the part that keeps an engineer permanently on plumbing instead of on your product:
- every TPS version and every DICOM dialect your customers export
- every archive a new customer brings, with its own naming conventions
- dose semantics, duplicate handling, and the cases that must be refused rather than guessed
- validation against reference cases, security patches, and API documentation
That commitment is what the contract carries, from the team that has already met the long tail.
The design-partner offer
The API contract is young and deliberately still shapeable. An early vendor doesn't adapt to our decisions; they sit at the table where the decisions get made, while breaking changes are cheap and the surface can bend toward their product.