Documentation
How Teloma works, in depth
Concepts, every module, every workflow, the safety model, and the technical layer.40 pages, organized by what you're trying to do.
Start with your role
Role
Patient
Track your journey, prep for visits, share on your terms.
Role
Caregiver
Log on behalf of someone who granted you access.
Role
Clinician
Read a patient's organized, patient-reported record.
Role
Researcher
Work with consented, de-identified data and public sources.
Role
Admin
Operate the platform, run connectors, monitor the audit log.
Concepts
What Teloma is
The product in one page — what it does, who it's for, and what it deliberately doesn't do.
Read →
Cancer, treated as an observability problem
The mental model behind the app — why this maps cleanly to logs, metrics, events, and outcomes.
Read →
Cancer-agnostic by design
Why fields are open — and what to do when your cancer type isn't on a drop-down.
Read →
Privacy and consent — the short version
How sharing works: by default nothing leaves you; everything else is opt-in and revocable.
Read →
Patient modules
Dashboard
Your home screen — a quick read on where things stand right now.
Read →
Profile
Demographics and account basics. Edit once, used everywhere.
Read →
Diagnosis & biomarkers
Cancer type, subtype, histology, stage, grade, biomarkers — and what's optional vs. important.
Read →
Treatments and cycles
Every treatment line, with cycles, response, side effects, and reasons stopped.
Read →
Medications
Patient-entered medication list — free text, no dosing guidance.
Read →
Symptoms
How you feel, day to day — severity, quality-of-life impact, and urgent flags.
Read →
Labs
Numeric results over time — names, values, units, and reference ranges.
Read →
Imaging
Scans you've had, with the radiologist's impression, the modality, and a viewable image where uploaded.
Read →
Document vault
Upload pathology, genomics, and imaging reports — kept private, downloadable, and linked to events.
Read →
Timeline
Every domain event in one chronological view — written automatically by the API.
Read →
Appointments
Visits coming up and visits that happened — provider, date, location, and notes.
Read →
Questions for the doctor
A running list of things to ask. Mark answered, keep the rest queued for the next visit.
Read →
Clinician summary
A one-page restatement of your record for a visit — generated, deterministic, downloadable as PDF.
Read →
Sharing & access
Caregiver
Clinician
Research
Research Assistant
Calanthe narrates the rule-based Tumor-State assessment — with hard guardrails.
Read →
Tumor-State Explorer
A transparent, rule-based, nine-axis profile — with explainability and a missing-data list.
Read →
Public Cancer Data Bank
A metadata-first registry of open oncology datasets — sources, datasets, drugs, combinations, trials, and ingestion jobs.
Read →
Admin
Workflows
First-visit setup
What to fill in on day one so the rest of the record makes sense.
Read →
Logging a symptom
The 20-second loop most patients run most days.
Read →
Prepping for a visit
What to do the day before so you walk in organized.
Read →
Granting a clinician access
Give a named clinician read access to your record — by email.
Read →
Granting a caregiver access
Add a partner or family member, with read-only or read/write scope.
Read →
Researcher — using the Data Bank
Find the right public source for a question, then drill into datasets and trials.
Read →
Safety & limits
Technical
Architecture
Two services over Postgres + object storage. Where each concern lives.
Read →
Auth & RBAC
Roles, access grants, the resolve_patient dependency, and how DENY gets audited.
Read →
Data model
What the tables are, what they hold, and the few invariants you need to know.
Read →
Data Bank connectors
How the three live connectors talk to public services — and where their results land.
Read →
Runbook — local dev
Start everything, reseed, and run the AI host.
Read →
Looking for the quick-reference cards instead? See the Help Center. Source docs (architecture, data model, runbook) also live in the docs/ folder of the repo.