Security
A layered security and governance model, described accurately
Pathlyn publishes only trust claims that are verified about Pathlyn itself. Certifications held by an upstream vendor or by one of our tenants are never inherited as Pathlyn’s own.
Verified today
What we can say about Pathlyn right now
- Each organisation’s data and staff actions are scoped to that tenant
- Staff actions emit audit events with actor, organisation, and correlation id
- Organisations present their brand on Pathlyn-hosted tenant hosts
- Role-scoped staff queues and least-privilege access
Independent certifications, uptime figures, customer counts, and a customer-owned custom domain are not claimed here until they are independently verified and approved.
Architecture
How a request is scoped, checked and recorded
Outermost control first. Every request passes each layer in order — and the record it leaves behind cannot be quietly rewritten.
Hostname-resolved tenant context
The request hostname selects the organisation before anyone signs in — a session can never select a different tenant.
Tenant and project isolation
Every organisation’s clinical and administrative data is scoped to its own tenant boundary.
Membership and role enforcement
Staff access is derived from their organisation membership and role — checked on the server, not the browser.
Multi-factor authentication
Staff and platform-admin sign-in requires a second factor.
Practitioner credential controls
A prescriber must hold a verified, unexpired credential before they can review or sign.
Staff audit events
Actions that change organisation, membership, or clinical state are recorded with actor, organisation, and correlation id.
Immutable clinical and prescription evidence
A clinical decision and a signed prescription are never edited after the fact — only superseded, on the record.
Suspension behaviour
A suspended organisation’s staff and patients cannot start new sessions until it is reactivated.
Controlled worker and integration activity
Background jobs and outbound integrations run under the same organisation scope as the request that triggered them.
Ask us about your specific security or governance question
A demo can cover the exact controls your compliance team needs to see.