Occupational Health Referral Management: From Referral to Case

Occupational health referral management begins with a request for occupational health input. It does not end when somebody submits a management referral form.

A management referral is the most common example. It may be described as a management referral to occupational health, an occupational health management referral or simply the referral process. Whatever the label, referral management has to preserve the request separately from the work that follows.

The request may need validation, triage or further information before the service accepts it. Once accepted, it can lead to appointments, Forms, Tasks, consultations, Reports and follow-up over a much longer period.

Those are related parts of one service, but they are not the same record:

A Referral contains the request, the reason, the management questions and the relevant context. A Case contains the operational and clinical work created once that Referral is accepted.

That distinction is the basis of effective occupational health referral management. It preserves what the referrer asked while giving the occupational health team a clear place to manage what happens next.

What is an occupational health Referral?

A Referral is a request for occupational health services concerning an Employee. The most common route is a management referral to occupational health: a manager asking for advice about fitness for work, workplace adjustments, absence or another work-and-health question within the service offered. Other referral pathways may begin with HR, an Employee or an authorised third party.

The Referral should preserve:

• Employee and employment details;
• the reason occupational health input is being requested;
• relevant absence and job context;
• the concerns the referrer wants considered;
• specific management questions;
• supporting information; and
• information about Employee awareness or consent where the pathway requires it.

There is no single form that is right for every occupational health service. The important design decision is not universal wording. It is treating the submitted Referral as a meaningful record of the request at that point in time, rather than as a placeholder for the Case that may follow.

The original Referral should not become a moving target

Suppose a manager asks: “Is this Employee medically fit to return to their current role?”

That question belongs to the Referral. During assessment, the clinician may decide that job-demand information is insufficient, request a report from another medical practitioner with the appropriate authority, arrange a further consultation or conclude that a phased return should be considered. None of that changes what the manager originally asked.

If the Referral is repeatedly edited to describe the latest position, it stops being reliable evidence of the request that started the work. A later reader may see a perfectly tidy record, but not the record that was actually submitted.

Preserving the original Referral supports practical needs:

• Clinical context. The practitioner can see why occupational health involvement began and which questions require an answer.
• Auditability. The service can distinguish information supplied at Referral from information established later.
• Review and disputes. Somebody examining the history can understand what each party knew and asked at the time.
• Reporting. Referral reasons and questions can be analysed without later Case activity silently changing the source data.
• Historical integrity. The request retains meaning after staff, templates and working arrangements have changed.

Corrections may still be legitimate. A misspelt name can be corrected, missing information can be supplied and a referrer may clarify a question. Good software records those events without quietly replacing history. Preserving a Referral means making the difference between the original submission, later additions and subsequent work visible.

What happens when a Referral is received?

Submission is an intake event, not proof that clinical work has begun.

An occupational health service may first check whether required information is present, confirm the Employee and Client relationship, validate that the requested service is covered, identify missing context, triage the request or route it to an appropriate team. It may decide that the Referral can be accepted, needs clarification or is not appropriate for the service.

Providers differ in how they perform these steps. Some have a central clinical triage function. Others allow trained operational staff to complete defined checks before practitioner review.

Referral software should accommodate those legitimate differences without making the status of the request unknowable. “Submitted”, “awaiting information”, “under review”, “accepted” and “declined” describe a Referral lifecycle. They should not be inferred from whether an Appointment happens to exist.

Teams should be able to vary questions, validation and routing where the service requires it while keeping the meaning of a Referral consistent.

From Referral to Case

Acceptance is the important boundary.

Once occupational health accepts the request and begins operational work, a Case becomes the container for that work. Depending on the pathway, it may include Tasks, Appointments, Forms, consultations, Documents, Reports, communications and follow-up. Not every Case needs every type of activity.

The two records now answer different questions:

• The Referral answers “What was requested?”
• The Case answers “What work are we doing about it?”

Consider an occupational health management referral about return to work after a prolonged absence. The original Referral holds the job context, absence information, management concerns and questions supplied by the referrer. Once accepted, the Case might contain a Task to obtain a job description, an Appointment with a clinician, a pre-consultation Form, consultation notes, a draft Report, an approval step and a follow-up review.

Changing or cancelling the Appointment affects the Case. It does not alter the original management question. Completing the pre-consultation Form does not complete the Case. Issuing a Report may answer the Referral questions, but the Case may still contain an outstanding follow-up Task.

The distinction creates a stable chain from request to outcome:

Preserve what was asked. Record separately what occupational health did because of it.

That chain is more useful than a timeline of generic updates. It lets the service see intake volume separately from active workload, measure acceptance without confusing it with Case closure and retain the reason each Case exists.

Why not use one record for everything?

For a linear workflow, one record can look simpler: one reference, one screen and one status field. The trouble appears when the Referral and the work change independently.

An “open” status might mean the manager has not completed the request, the service is waiting for missing information, triage is outstanding, an Appointment needs booking, a practitioner is drafting a Report or follow-up remains incomplete. Adding more statuses seems to solve the problem, but the list is now describing several lifecycles at once.

The ambiguity spreads:

• Does cancelling an Appointment return the Referral to an earlier status?
• If clinical review reframes the issue, should the original reason for Referral be overwritten?
• Where do operational Tasks belong before and after an Appointment?
• Does closing the Case mean the submitted Referral itself has changed?
• Can reporting distinguish requests awaiting acceptance from accepted Cases awaiting clinical work?

One generic record reduces the number of labels in the system but increases the number of meanings attached to each label. Teams then rely on notes, local convention and the knowledge of experienced administrators to explain what the status really means.

The goal is not to make the process more complicated. It is to give existing complexity clear boundaries.

A referral Form is not the Referral lifecycle

A configurable referral Form is useful. It can collect management questions, employment context, absence information, concerns and supporting details in a consistent way. Our practical guide to management referrals looks at what those questions should contain.

The Form is still the interface through which information is captured. Submission alone does not tell the occupational health service whether the Referral has been accepted, who owns the resulting Case, what work is outstanding, whether an Appointment took place, whether a Report was released or whether the Case can close.

This follows the same principle explored in our article on health surveillance Forms: Forms capture structured information. Domain workflows give that information operational meaning.

When form logic becomes the whole workflow, important work tends to disappear inside answers and submission states. A required follow-up recorded as “Yes” is data. A follow-up represented as an owned, visible Task within the Case is work.

What should occupational health referral software support?

Feature lists are less revealing than following one Referral through its exceptions. Buyers should examine whether the request and resulting work remain intelligible as both evolve.

Configuration with stable meaning

Different Clients may need different questions, service choices, supporting information and routing. They should be configurable without requiring bespoke development for every reasonable change.

Configuration needs boundaries. A Client can call a section “manager concerns” while another calls it “reason for referral”, but both can still create a Referral. Variation in the interface should not redefine the provider's operational model.

Separate, visible lifecycles

Users should be able to see the Referral's status without interpreting Case activity. Acceptance and Case creation should be explicit, linked and recorded as meaningful events.

Once the Case exists, its owner, current work and closure state should also be clear. An audit history should show that a Referral was received, further information was requested, it was accepted, a Case was created and defined work occurred. A list of field updates with timestamps is not an adequate substitute.

Case-based operational work

Appointments, Tasks, Forms, Documents and Reports should relate to the resulting Case where appropriate. This keeps an Appointment cancellation, an outstanding information request and a Report approval in their proper operational context rather than turning them into extra Referral fields.

The resulting Report should remain connected to both the Case that produced it and the original questions it is intended to address. This makes it easier to review whether the work answered the request rather than merely whether a document was generated.

Reporting that respects the distinction

Referral volume, acceptance, decline reasons and time awaiting information are intake measures. Open Cases, outstanding Tasks, upcoming Appointments and work awaiting review are operational measures.

When the records are separate but related, reporting can distinguish demand from workload. Without that distinction, a service may know it has 200 “open referrals” but not whether those are incomplete requests, untriaged submissions or Cases already receiving clinical work.

Referrers and clinicians need different views

A referring manager needs enough information to know that a Referral has been received, whether action is required from them and, where appropriate, the progress and released outcome. That does not imply access to confidential clinical material created during the Case.

The clinician needs the Referral context and original questions, then access to the clinical information necessary to do the work. These are intentionally different views of related records.

Current ICO guidance on workers' health information says access should follow a need-to-know approach. It explains that managers should receive only the information needed for their responsibilities and that access can often be limited to current or likely fitness for work. Acas guidance on occupational health assessments also addresses permission before an occupational health report is shared and the need to restrict access to those who genuinely require it.

Software should make those boundaries part of ordinary workflow, including screens, notifications, exports and Reports. Hiding clinical notes on one page is not enough if the same information appears in a manager-facing status update.

Referral management across multiple Clients

The distinction becomes especially valuable for occupational health providers. A provider may receive Referrals from different Clients, managers, locations, contractual services and intake routes. Each Client can have reasonable differences in the questions it asks and the services it purchases.

Allowing every Client's terminology to redefine the entire workflow creates a different problem. Staff training fragments, cross-Client reporting becomes difficult, integrations need special cases and changes become harder to maintain.

Configuration should accommodate legitimate variation without destroying consistent domain meaning. Clients can ask different questions while a Referral remains a request and a Case remains the work created after acceptance. That is also the useful test when a portal already creates cases for employers, as in a Meddbase alternative evaluation: whether the original request remains inspectable after triage, booking and follow-up have begun.

Consistency does not mean forcing every customer through an identical form. It allows variation to remain operable.

Referrals within a wider occupational health platform

An Employee may interact with occupational health through Referrals, Cases, Appointments, Forms, consultations, Documents, Reports, sickness absence work and health surveillance.

These records should connect where continuity is useful without being collapsed into one generic activity history. An Appointment is an event. A Form is a structured interaction. A Report communicates an authorised outcome. A Case coordinates accepted work. Each concept contributes something different.

This is the value of an explicit occupational health platform: shared Employee and Client context can reduce duplication while each workflow keeps its own lifecycle, permissions and meaning.

Questions to ask when evaluating referral management software

Ask a supplier to demonstrate a real Referral from submission to closure, including missing information, a changed Appointment and follow-up. Then ask:

• Can different Clients configure appropriate Referral questions without supplier development?
• Does the system distinguish a submitted Referral from the Case created after acceptance?
• Is the original request preserved, including later clarifications and additions?
• Can missing information be handled without silently rewriting the submission?
• Is acceptance and Case creation explicit and auditable?
• Can reporting separate Referrals awaiting action from Cases actively being worked?
• Is Case ownership clear, including Tasks that remain outstanding after an Appointment?
• Can Forms, Appointments, Documents and Reports participate in the Case without defining its status?
• Can managers see appropriate progress without gaining access to confidential clinical information?
• What prevents a Case from closing while required work remains incomplete?
• What happens to the Referral when its Case closes?
• Could somebody reviewing the record years later understand what was requested, what was added and what occupational health did?

The most revealing demonstration is rarely the happy path. Ask what the system means when the request is incomplete, the first Appointment is cancelled, a second opinion is required and the Report has been drafted but cannot yet be released.

Occentra models Referrals and Cases as separate but related concepts. The Referral retains the submitted request and its intake lifecycle. Acceptance creates the Case in which Tasks, Appointments and Forms can support the operational work. The distinction is small enough to explain in one sentence, but consequential enough to shape the whole service.

Years later, the useful record is not merely that something was “closed”. It is a history that can still answer two different questions: what did the referrer ask, and what did occupational health do about it?