Security and PHI posture.

The strongest control is structural: PHI stays on your infrastructure because the whole platform runs there. Everything else layers on top of that fact.

Residency first

Radial is an on-premise appliance: no vendor cloud, no patient-data egress as a side effect of using the product, and full function on a disconnected network after the one-time install. Your existing institutional controls (network segmentation, backup, access governance) apply to Radial the way they apply to any internal clinical system, because that's what it is.

Authenticated access, attributed actions

Every session is authenticated against per-user accounts, and curation is attributed: confirmations, approvals, and edits record who made them. Provenance doubles as accountability — the audit trail is the same one that makes the dataset defensible.

PHI Privacy Mode

For demos, screenshots, and shoulder-surfable screens, one switch swaps names, MRNs, dates of birth, and ages for synthetic placeholders, or redacts them. Exports mask patient identifiers by default. It's the difference between showing the platform and showing a patient.

The longer conversation

Security reviews are institution-specific, and we'd rather answer yours directly than gesture at a checklist here. Bring your security and privacy teams' questions to a demo — deployment details, authentication options, and data-handling specifics are exactly what that conversation is for.