For who

Built with the people who own the question.

AURORA works with the individual who understands the investigation, selected by knowledge of the scientific operation rather than title, institutional prestige or enthusiasm for automation. Four groups meet that description in glioma research, each in a different way.

For each: what you bring, what AURORA provides, what you keep when the work is done, and what is deliberately not on offer.

01 · of 04

Researchers and clinicians

You hold a glioma question and the observations to investigate it. AURORA turns the question into a specification the tooling can carry, without taking the question away from you.

You bring
  • A research question stated in your own words
  • Observations that stay in your authorised environment
  • The judgement about what the answer means
AURORA provides
  • A scientific task specification: target, population, unit, pairing, baseline, permitted transforms, output meaning
  • Methods that return a valid analysis, a narrower interpretation or an uncertainty bound
  • A local research agent that compiles evidence, certifies what it left out, and asks before it invents
  • Evaluation at protocol, integration, scientific and user level
You keep
  • The accepted target and its versions
  • Every method with its stated assumptions
  • Artifacts that cite their own provenance
  • A protocol the next project can pick up
Not on offer

No grants, no hosted data, no clinical output for an individual patient.

02 · of 04

Engineers and agent developers

You want your work to outlive the project it was built for. AURORA publishes a contract worth conforming to, with the reference cases and evaluators that let a stranger check you did.

You bring
  • An implementation, in any language, of one part of the contract
  • A disagreement with the design, filed in public
  • A replication of a headline result at a site that had no part in it
AURORA provides
  • The task envelope: research target, assumptions, input meanings, evidence requirements
  • Reference interactions for delegation, clarification, artifact return, cancellation and stale results
  • Protocol, semantic and user-level acceptance cases, written before code
  • 212 documented tools with an evidence dossier each
You keep
  • An independently implemented peer that substitutes without changing the scientific contract
  • Your own repository, your own licence choices within Apache-2.0 compatibility
  • Credit at the established scope of what you built
Not on offer

No proprietary SDK, no vendor lock-in, no central service you must route through.

03 · of 04

Institutions, registries and networks

Your observations do not leave your perimeter. AURORA runs inside it, speaks to the systems care already runs on, and is handed on as a specification with running code.

You bring
  • A cohort described publicly and queried where it lives
  • An authorised environment and the people who govern it
  • A named team willing to be named when a result is published
AURORA provides
  • Deployment inside your perimeter, with federation between sites that never pools raw data
  • Connectors for Epic, Oracle Health, MEDITECH, athenahealth, InterSystems, Carequality, CommonWell and Redox
  • A hash-chained audit ledger and a governance chokepoint for every emitted artifact
  • Regulatory posture stated plainly: research use only, no device claims
You keep
  • Control of every observation and every export
  • The right to withdraw a module when its performance degrades
  • Documentation another institution could deploy from
Not on offer

No data hosting, no data brokerage, no clinical decision support.

04 · of 04

Patients and families

Glioma, written for the people living with it. Free to read, with no jargon left unexplained and nothing that diagnoses or triages.

You bring
  • Nothing is required. No account, no data, no cost.
AURORA provides
  • 50 plain-language glioma guides, from diagnosis to living with treatment
  • 265 glioma terms defined, each with its own page
  • A printable glioma booklet to take to appointments
You keep
  • Reading comfort settings that stay on your device
  • A record of what you have read, never uploaded
Not on offer

Not a diagnosis, not a triage tool, not a substitute for the team treating you.

How a collaboration begins

Four steps, each with a visible result.

No onboarding, no platform account. The first artifact is a written specification you can disagree with; the last is a publication at exactly the scope the work has earned.

1

A question, verbatim

You state the comparison you want to make. It is recorded in your words and never reinterpreted for you.

2

A specification

Together we write the scientific task: target quantity, population, observational unit, pairing, baseline, permitted transforms, and what the output means.

3

A bounded contribution

One supported interaction, one genuine computation, one controlled revision. Recovery cases before more agents.

4

Publication at established scope

The contract, procedures, reference cases and components are published for exactly what they have been shown to do, and no more.