Occentra

Blog

10 Occupational Health Data Security Mistakes and How to Avoid Them

A clinician finishes an assessment for an Employee and prepares an opinion for the employer. The clinical Case contains a history, examination notes and test results. The employer needs an answer about fitness for work and any relevant adjustments. Sending the clinical notes instead of the approved Report would disclose information the employer does not need.

Occupational health data security depends on how information moves between clinicians, administrators, Employees and Clients. Encryption and passwords matter, but so do the decisions made during an ordinary working day: who can open a record, what belongs in a Report, and who checks its recipient. The following ten mistakes provide a way to examine those decisions in your own service.

1. Giving too many people access to clinical records

A Case administrator may need to see that an assessment is booked and a Report awaits release. That does not mean they need access to the clinician's full assessment or confidential Form answers. Equally, a Client contact who submitted a Referral should not inherit clinical access because they can follow the Case status.

Define roles around actual tasks, then check permissions at record and action level. Separate clinical, administrative, employer and audit functions. Review access when people change roles and remove it promptly when they leave. Test the boundary with realistic accounts: can an administrator complete their work without opening clinical findings? The NCSC's cloud security guidance recommends granular access and periodic removal of unnecessary permissions.

2. Confusing clinical records with employer health records

The clinician's record exists to support assessment and care. An employer-facing Report communicates an appropriate occupational health opinion. They are related, but they are not interchangeable. For a management Referral about a return to work, the employer may need to know whether the Employee can perform particular duties, what restrictions apply and when to review them. A diagnosis or detailed history may sometimes be relevant, but disclosure needs a specific justification; a request for the whole Case is not enough.

Health surveillance adds another distinction. HSE guidance says employers must maintain a health record of surveillance outcomes, including relevant exposure and fitness information. The confidential medical record, which can contain notes and test results, is held in medical confidence by the occupational health professional. The employer's health record should not include confidential medical information without the worker's written consent. This is also why a retention rule for a statutory health record should not be copied blindly onto every clinical record.

Before disclosure, establish the purpose, recipient and minimum information needed. Identify the applicable UK GDPR lawful basis and special category condition, and consider professional confidentiality and the circumstances of the assessment separately. Consent to a clinical disclosure is a distinct question from the data protection basis for processing. The ICO's occupational health guidance emphasises restricted access and the duty of confidence. The GMC's guidance on employment reports explains informed consent to disclosure and why the whole record is not usually appropriate. Build the clinical record and the employer Report as separate outputs, with a deliberate review before release.

3. Sending sensitive information through uncontrolled email

Email can be an appropriate channel when its security and use fit the information. The common failure is uncontrolled distribution: an address selected from autocomplete, the wrong attachment, a broad Client distribution list, or a Report forwarded into a mailbox with no agreed owner. Once a file is sent, access may be difficult to revoke.

Choose a suitable secure channel for each disclosure. Confirm the named recipient, attachment and approved Report version before sending. Where a portal is used, check its recipient permissions and whether access can be withdrawn. Document who may release Reports and how exceptions are handled. ICO guidance on sharing workers' health information calls for a necessary, proportionate disclosure with a lawful basis and special category condition.

4. Relying on shared accounts or weak authentication

When several staff use one login, a record may show that an account opened a Case, but not who actually did it. Reused passwords, missing multifactor authentication and weak account recovery can also undermine an otherwise careful permission model. An account left active after a colleague leaves creates another avoidable route to the records.

Give each person an individual identity. Require strong authentication appropriate to the risk, use multifactor authentication, and make account recovery and leaver processes controlled events. Check that service accounts are limited to their purpose. Audit history is most useful when important actions can be attributed to the person or service that performed them.

5. Storing clinical information on unmanaged devices

Mobile clinics and work at Client sites create legitimate reasons to work away from the usual office. They also create local copies: a Report saved to a personal laptop, an assessment downloaded to a desktop folder, a file on a removable drive, or an open session on a shared computer. The central system's permissions cannot govern an unmanaged copy indefinitely.

Set rules for approved devices, local storage and deletion of working files. Use device encryption, screen locking, endpoint management and access controls appropriate to the environment. Record when offline working is genuinely necessary and how completed work returns to the controlled record. If evaluating offline occupational health software, check whether offline access is available now, and ask how local records are protected and reconciled. Our guide to offline occupational health workflows examines those trade-offs.

6. Failing to maintain an appropriate audit trail

If a Report is sent to an unexpected recipient, the provider needs to establish which version was released, by whom and when. The same applies to permission changes, document exports and significant edits to clinical information. A list of logins alone will not reconstruct a disclosure.

Decide which events matter for investigation and governance, and make logs attributable, protected against unauthorised alteration and subject to a defined retention period. Keep sensitive clinical free text out of routine audit entries where an event marker will do. Audit history should explain material actions, rather than become indiscriminate staff surveillance. Test whether an investigator can follow a representative Referral from intake through Case, assessment, approval and Report release.

7. Keeping clinical records without a clear retention policy

Records persist in places a Case closure does not touch: old systems, shared drives, email attachments, backups and downloaded files. A service may have a defensible rule for its primary clinical database while retaining duplicate copies indefinitely elsewhere.

Create a schedule by record type and purpose, identify its owner, and include transfer and disposal procedures. General clinical records and statutory health surveillance health records may have different requirements. HSE says the applicable regulations set the minimum retention for health records, giving 40 years under COSHH as one example; where no period is specified, the health record should be kept at least while the worker is employed. That is not a universal 40-year rule for all occupational health notes. The ICO's workers' health checklist calls for a documented retention policy and keeping information only as long as necessary. Account for legal, clinical and professional obligations before disposal.

8. Overlooking suppliers and integrations

An occupational health service may use separate systems for Referrals, email, documents, laboratory results, hosting and employer access. Each transfer creates a question: what information moves, who can see it, and what happens when the contract ends? A useful supplier review follows the data, not just the headline security features.

Map each flow and access boundary. Review supplier controls, subcontractors, incident responsibilities, data return and deletion. Record the actual controller and processor roles for each processing activity; the labels depend on who determines its purposes and means, not on an organisation's industry. Where a controller uses a processor, the ICO's contract guidance explains the required written terms. Ask a software supplier to demonstrate how a Client user is kept out of another Client's information and out of clinical material they are not meant to receive.

9. Assuming backups guarantee business continuity

A backup file is not a recovered occupational health service. Recovery also needs usable data, working access controls, a known sequence for restoring systems and a way to continue urgent clinical work during an outage. A backup taken too rarely may lose recent assessment work; a restore that has never been tested may fail at the point it is needed.

Set recovery point and recovery time objectives according to the service's needs. Protect backup access, check data integrity and rehearse restoration. Decide how urgent Referrals, Appointments and Reports will be handled while systems are unavailable, including how temporary records will be reconciled afterwards. The NCSC recommends planning and testing restoration, as well as maintaining secure, current backups. Ask suppliers for evidence of their recovery process, rather than assuming a stated backup frequency answers the continuity question.

10. Having no clear response to a clinical data breach

An unexpected disclosure needs immediate containment, but the team also needs to preserve evidence and establish what happened. Was an employer-facing Report sent to the wrong manager, or did the attachment include confidential assessment notes? Which Employee was affected, and who else received the information? Those details determine both the response and any notification duties.

Give staff a clear reporting route and assign responsibility for containment, investigation, risk assessment, communications and corrective action. Agree how the provider, employer and suppliers coordinate where their systems are involved. Record every personal data breach, including those that do not require notification. Under the ICO's personal data breach guidance, a personal data breach is reportable to the ICO unless it is unlikely to result in a risk to individuals' rights and freedoms. Where notification is required, it must be made without undue delay and, where feasible, within 72 hours of becoming aware of the breach. If a breach is likely to result in a high risk to individuals' rights and freedoms, affected people must also be informed without undue delay. A security alert is not automatically a reportable personal data breach.

How secure is your occupational health information?

Use these questions with a recent, representative Case, including its documents and communications:

  • Can administrative staff work on the Case without access to clinical findings they do not need?
  • Are confidential assessment notes separate from the employer-facing Report and surveillance health record?
  • Can a Client contact see only the Referrals, Cases and Reports appropriate to their role?
  • Is a Report's recipient, content and version checked before release?
  • Can individual access be changed or revoked promptly when responsibilities change?
  • Are important disclosures and permission changes attributable to individual users?
  • Are downloaded files and mobile devices governed by an enforceable policy?
  • Does the retention schedule cover email, exports, legacy systems and backups?
  • Are supplier data flows, access rights and contracts documented?
  • Has a backup been restored successfully in a test, including usable records?
  • Can staff report a suspected disclosure quickly, and has the response process been rehearsed?

A checklist exposes questions to investigate. It does not establish legal compliance by itself.

Building security into occupational health software

Software can make good information governance easier to practise. Occentra structures work around Referrals and Cases while keeping clinical access distinct from employer-facing information. Its current application uses provider-specific tenant schemas, role-based permissions checked on the server, individual authentication, and audit history for meaningful Case and configuration activity. The company behind Occentra holds Cyber Essentials certification; the security page provides the certificate details. The application controls support a reviewable workflow. Clinical disclosure, retention and incident procedures still need the provider's own governance.

When assessing any platform, use a real Case to ask who can view its clinical detail, how an approved Report reaches a Client and what history remains afterwards. Our software buyer's guide provides a wider procurement framework. You can also explore the product. Book a walkthrough to see how Occentra handles these boundaries in practice.

← Back to blog