03Oncology AI
Planned · not yet deployedCancer intelligence needs scale that no single centre has, built from records no centre is allowed to send anywhere. Oncology AI trains across registries without moving one case out of the institution that holds it.
01The problem
What holds the data in place
Registries do not poolCannot pool
A cancer registry is built from identifiable records under a consent framework specific to the institution that collected them. Merging two of them is a legal act, not an engineering one.Rare is the whole problemNeeds scale
The subtypes that most need a model are the ones no single centre sees enough of. The signal only exists across sites.Imaging is heavy and localStays put
Whole-slide and volumetric imaging is measured in gigabytes per case, held in systems that were never designed to export.02The approach
Ingest in placeScoreTrainAttestServe
Each centre keeps its own archive and runs its own node. What crosses the boundary is a weight update and a signed record of what that centre contributed.
01PLANNED
Score in placeEvery case is evaluated on the centre’s own hardware, against its own ground truth.02PLANNED
Train across centresRounds of federated training so rare subtypes get the scale they need.03PLANNED
Attribute contributionA signed record of which centre moved the model, and by how much.04PLANNED
Serve locallyInference runs beside the scanner. The prediction never becomes an export.03What crosses
Stays in the centre
Slides and volumes
Pathology reports
Patient identifiers
Treatment records
Travels out
Model weights
Aggregate evaluation scores
Signed contribution record
04Where it applies
01
Multi-site registriesBuild one model across centres that are not permitted to share a single record.02
Tumour boardsSurface comparable prior cases from the centre’s own history, not from a public corpus.03
Trial matchingScreen against protocol criteria without moving the record to the sponsor.04
Quality assuranceA second read on every case, scored the same way at every participating site.