Security model
Security built into the platform.
Occentra protects occupational health data through architectural isolation, explicit access control and secure application design. Boundaries are built into the system, not added afterwards.
Tenant isolation
Dedicated database schema per occupational health provider
Least privilege
Role-based access so users see only what they are authorised to see
Auditability
Actions recorded so governance can explain what happened
Secure defaults
Configuration and platform behaviour designed to start closed
Certification
Cyber Essentials certification
Cyber Essentials is a UK government-backed scheme covering core cyber security controls. The company behind Occentra holds this certification. The registry badge provides the certificate details.
Security principles
Boundaries first, not bolt-on controls.
Occupational health systems hold medical information, employment context and operational records. Those records serve different people for different purposes. Occentra treats those boundaries as part of the domain model, not as permissions added at the end.
- Sensitive data is only presented to authorised users
- Employers, clinicians and operational users are separated by role
- Strong tenant isolation is a core architectural principle
- The platform prefers configuration over bespoke behaviour that is harder to reason about
Multi-tenant architecture
One provider, one database schema.
Occentra is multi-tenant. Each occupational health provider runs as a tenant with a dedicated database schema. Provider data is segregated at the database layer, so one provider's records are not stored in another's schema.
Database
Provider A
schema_a
- Cases
- Assessments
- Documents
Provider B
schema_b
- Cases
- Assessments
- Documents
Provider C
schema_c
- Cases
- Assessments
- Documents
Clinical data protection
Different roles, different views of the same case.
A referral, case and report are not the same record to every participant. Employers initiate and receive what their role requires. Clinicians work with clinical detail. Operational users support the service without automatic access to medical information they do not need. Clinical form answers, triage notes, assessments and outcomes require clinical access, which operational roles do not have by default.
- Role-based access control determines what each participant can see and do
- Least privilege guides which fields and documents are presented
- Sensitive medical information remains visible only to authorised users
- Clinical form answers, triage notes, assessments and outcomes require clinical access
Case flow
Authentication and access control
Authorisation is part of the product model.
Access is organised around roles. Employers, clinicians and operational users receive capabilities appropriate to their work. Sensitive information is only presented to authorised users. Permissions are checked on the server. Hiding a control in the interface is not the access control.
Staff sign-in requires a verified email address. Two-factor authentication and passkeys are available. A provider can restrict sign-in and API access to an IP allowlist. Sign-in history is kept separately from the audit trail. Single sign-on is coming soon.
| Role | Typical visibility |
|---|---|
| Employer | Referral context, case status and released reports appropriate to their role |
| Clinician | Clinical detail, assessments and records required for care and reporting |
| Operations | Operational workflow and administration without blanket clinical access |
| Read-only auditor | Operational records, sign-in history and the audit trail, without clinical assessments, outcomes or user administration |
Audit trail
Actions recorded where governance needs them.
Occentra records actions so teams can explain what happened across configuration and case activity. Records are append-only. Clinical free text is not copied into the audit record, and a sensitive field can be marked as changed without storing the text. This supports operational review without claiming that every event is cryptographically immutable.
Configuration changes
Changes to templates, pathways and governed settings can be traced over time.
Case progression
Meaningful case events help explain how a referral moved from intake to report.
Access-relevant activity
Role changes, user activation and other authorised actions leave a record for internal review.
Documents
Upload, link, unlink and delete are recorded. File contents are not stored in the audit record.
Infrastructure and development
Secure defaults and modern application practices.
Data in transit is protected with HTTPS/TLS. The platform is built with modern web application security practices. Configuration is preferred to bespoke behaviour so security-relevant paths stay visible and maintainable. Secure-by-default design means the platform starts closed and opens access through explicit authorisation.
- Each occupational health provider has its own private document store
- Downloads go through an authorised route in the application, not a public file link
UK company
A UK occupational health software provider.
Occentra is built by Divergent Matrix Limited, a company registered in England (Company No. 14707575). The platform is designed to meet the expectations of UK occupational health providers handling sensitive employee health data.
- Divergent Matrix Limited is a UK-registered company
- Multi-tenant architecture with dedicated database schema per provider
- Role-based access control separates employers, clinicians and operational users
- Data in transit protected with HTTPS/TLS
- Two-factor authentication, passkeys and an optional IP allowlist for staff access
- Private document storage, with downloads through the application
- Audit trail for configuration, case activity and document changes
For detailed security architecture, see the sections above. For contractual data processing terms, contact us directly.
Scope
What this page explains, and what it does not.
This page explains
- How multi-tenant isolation is structured with dedicated database schemas
- How role separation shapes access to referrals, cases and reports
- How TLS, RBAC, least privilege and auditability fit the architecture
- How staff sign-in works today, including two-factor authentication, passkeys and an optional IP allowlist
- That single sign-on is coming soon
- How documents are stored privately and downloaded through the application
- How secure defaults and modern web application practices inform development
This page does not
- Replace your organisation's compliance programme or risk assessments
- Assert certifications or standards beyond those listed here
- Describe every hosting or operational control in full detail
- Guarantee absolute security of any system connected to the internet
For contractual terms and website data practices, see the Privacy Policy and Terms of Use.
Frequently asked questions
Common questions from security and IT reviews.
How are occupational health providers isolated from each other?
- Occentra is multi-tenant. Each provider has a dedicated database schema, so provider data is segregated at the database layer.
Who can see sensitive medical information?
- Sensitive data is only presented to authorised users. Clinical form answers, triage notes, assessments and outcomes require clinical access, which operational roles do not have by default. Employers, clinicians and operational users are separated by role.
Is data encrypted in transit?
- Yes. Data in transit is protected with HTTPS/TLS.
Does Occentra keep an audit trail?
- Yes. Records are append-only and cover configuration, case activity and document changes. Clinical free text is not copied into the audit record. The record is not a cryptographic ledger.
What sign-in controls are available?
- Staff sign-in requires a verified email address. Two-factor authentication and passkeys are available. A provider can restrict sign-in and API access to an IP allowlist. Sign-in history is kept separately from the audit trail. Single sign-on is coming soon.
Where are documents stored?
- Each provider has its own private document store. Downloads go through an authorised route in the application. Upload, link, unlink and delete are recorded. File contents are not copied into the audit record.
What application security practices does Occentra follow?
- Occentra is built with modern web application security practices, prefers configuration over bespoke behaviour, and aims for secure-by-default design. Permissions are checked on the server.
How do we ask deeper security questions?
- Register your interest or contact us. For website privacy questions, use the contact details on the Privacy Policy.
See how Occentra would fit your service.
Bring us a referral pathway or assessment process you run today. We will show how it can be configured, tracked and governed in Occentra.