Home/Security
Patient data,handled like it matters.
OncoBoard holds the clinical detail a tumour board needs and nothing that names the patient. This page sets out what is stored, who can change it, where it travels and what your organisation keeps control of.
Fields for a patient's full name
Password hashing with a per-user salt
Before a session expires
Clinical actions written to the audit log
De-identified by design.
A case is identified by its MRN and the patient's initials. The case record has no field for a full name, date of birth or address, so there is nowhere to type one.
- Stored: MRN, initials, age, sex, board, urgency and status.
- Stored: TNM, AJCC stage group, ECOG, pathology, IHC, NGS variants, labs, treatment history and trial matches.
- Stored: saved measurements, votes, minutes, case chat and the audit log.
- Not sent to the server: uploaded DICOM files. They are parsed in the clinician's browser.
- MRN
- ONC-2026-4102
- Patient
- R.K. · 64
- Board
- Thoracic
- Urgency
- Priority
- Staging
- T2b N2 M0 · IIIA
- ECOG
- 1
- NGS · Tier I-A
- EGFR p.Leu858Arg
- Status
- In Review
DICOM headers can carry a name. Uploaded series stay in the browser and only the measurements you save reach the server. The viewer still shows header tags, so upload de-identified exports from PACS.
Every clinician signs in as themselves.
Accounts carry the clinician's specialty, title, institution and whether they chair the board. Votes, sign-offs and measurements are tied to that account, so the record shows who said what.
- Password storage
- scrypt · 16-byte random salt per user · 64-byte key
- Password check
- Constant-time comparison
- Session token
- 256-bit random bearer token
- Session lifetime
- 12 hours · revoked at sign-out
- Signed-in only
- Every write and every AI request
- Roles
- Six specialties · chair flag
- Chair
- No
- Token
- 9f3c…a71e · 64 hex
- Expires
- in 11 h 42 m
- Can vote
- Yes
Who did what, and when.
Each clinical change writes an audit entry with the clinician, their specialty, the action, the record it touched and the time. Your IT team reads it in the Audit & Database view.
AI governance
The AI can draft.
It cannot decide.
OncoBoard's four assistants use the Google Gemini API. These are the limits they work inside.
Called on request
The server calls the model only when a clinician presses an assistant button. Nothing runs in the background, and without an API key configured nothing is sent at all.
What leaves the server
Case synthesis and case questions send the de-identified case context. A slice read sends a rendered image of the current slice, not the DICOM file. Minutes send the votes and recent case discussion.
Labelled and disclaimed
Every output is headed "AI Decision Support" and ends with a disclaimer, wherever it appears.
Cannot act on the record
Assistants cannot vote, sign off or edit a case. A clinician reads the draft and does each of those.
On the audit log
Synthesis, slice reads and drafted minutes are written to the audit log with the clinician who asked.
Your key, your choice
AI runs on an API key your organisation configures on the server. Leave it unset and the rest of OncoBoard works as normal.
Architecture
One server.
One database.
OncoBoard is a React 19 web app, a Node.js and Express server with a WebSocket hub, and a MySQL database. The recommended deployment serves it over HTTPS and WSS.
Shared responsibilities
What we provide.
What stays with you.
Security is split between the software and the organisation that runs it. This is where the line sits.
| Area | OncoBoard provides | Your organisation provides |
|---|---|---|
| Hosting | A Node.js app with a MySQL schema that runs on standard hosting | The server, database and network it runs on, or approval of the host |
| Encryption in transit | An app and WebSocket service that run behind HTTPS and WSS | The TLS certificate and the HTTPS endpoint |
| Backups | All case data in one MySQL database | Backup schedule, retention and tested restores |
| User accounts | Clinician accounts with specialty, title, institution and chair flag | Who gets an account, and removing leavers |
| Sessions | Random bearer tokens that expire after 12 hours | Device policy for shared reading-room workstations |
| De-identification | No field for a full name, date of birth or address | De-identified DICOM exports and identifier-free free text |
| AI | On-request calls, labelled output, no write access to the record | The decision to use AI and the API key under your own agreement |
| Audit | An audit entry for every clinical change and AI draft | Who reviews the log, and how often |
| Governance | A walkthrough of this page with your team | DPIA, clinical safety sign-off and local operating procedures |
Information governance
Bring your questionnaire.
Send your security or DPIA questionnaire with your demo request. We will go through it with your information governance lead in the session.
Questions
Asked by
governance teams.
Where is patient data stored?
Does OncoBoard store patient names?
Is any data sent to an AI provider?
Can clinicians type identifiers into free text?
What does the audit log record, and what doesn't it?
Which certifications does OncoBoard hold?
Walk your IG lead through it.
Thirty minutes with this page, your questionnaire and a de-identified sample case.