Rigorous workflows should be easier,
not dumbed down.
RadFox is being built by engineers who take clinical seriousness as a baseline, not a constraint. This is how we think about the work.
How we build.
Usability is not the opposite of rigor.
Software can make rigorous work faster and more reliable without stripping away the judgment that trained clinical staff bring. The best clinical tools raise ceilings — they don’t lower them.
In practice: every AI-assisted step in RadFox is transparent, reviewable, and overrideable. Clinicians stay in the loop because that’s where expertise lives.
Workflow is a clinical artifact.
How a case moves through a team — who owns it, who reviews it, what’s been decided — is as much a clinical artifact as any image or number. RadFox treats workflow state as a first-class object, because that’s how real programs operate.
In practice: case routing, review states, and sign-off are structured, auditable, and visible to the whole team.
Every computed number has a provenance.
A dose estimate is the end of a long chain — reconstruction, segmentation, integration, biological assumptions. RadFox carries that chain with the number, so clinical teams can inspect, compare, and trust what they’re looking at.
In practice: dose metrics are inspectable back to the voxel; assumptions and method parameters are always accessible.
Built for the heterogeneity of the real world.
Real programs run across multiple scanners, protocols, sites, and cycles. A platform that only works on one reference configuration isn’t clinical software — it’s a demo. RadFox is built for the world as it actually is.
In practice: multi-vendor DICOM ingestion, protocol harmonization, site-aware metadata — these are defaults, not add-ons.
Partnership over vendor.
Software that shapes how clinical care is delivered should be built in close partnership with the teams delivering that care. We’re building with — not for — cancer centers, physics groups, and radiopharma developers.
In practice: design partners shape what RadFox becomes. Decisions are made with clinical teams in the room.
We treat clinical seriousness as a baseline, not a constraint. The medicine deserves the software to match.— RadFox operating principle №0
Shape what this becomes.
Design partners get deep influence on how RadFox is designed, what workflows it prioritizes, and how it integrates with existing clinical infrastructure.