ADOPT AI PARTNERS
Insights / manufacturing

AI for Patient Intake in Manufacturing

20 October 2026  ·  8 minute read  ·  Adopt AI Partners
discussion in a modern office
Photo via Unsplash

A contract welder signs in at the gate on a Monday, badge printed, induction complete, and walks onto a line where hearing protection has been mandatory for as long as anyone can remember. His last hearing test was arranged by an agency, for a different employer, at a site nobody here has heard of. The plant does not know that and could not read his health record if it had one.

A manufacturer with a patient list

A factory is not a clinic and it still runs patient intake. The function is occupational health; the patient is the workforce.

The intake events are specific. Pre-placement health screening and fitness for work assessment, before somebody goes near a machine or takes on a safety critical task. Statutory health surveillance programmes that recur on a calendar: hearing checks for noise exposed roles, lung function testing where there is dust or a respiratory sensitiser, hand arm vibration assessment for tool users, skin checks where hands meet process chemicals. Return to work and workplace adjustment assessment after absence or injury. And screening for safety critical roles, including drug and alcohol programmes.

Each is a referral in, an assessment, an outcome out: intake, with every failure mode of a hospital front desk plus one no hospital has.

Clearance pending, and the task already under way

A new starter completes a health questionnaire. It goes to an occupational health provider, who decides whether the person can safely do the job as described, with or without adjustments. In theory that happens before the first shift. In practice it comes back half finished, the provider asks what the role actually involves, somebody emails a recruitment advert, and the assessment waits.

Meanwhile the line is short handed, so the person starts pending clearance, on the task that required clearance. Everyone knows this is wrong, and nobody has a better option at six in the morning.

Safety critical roles and testing programmes

Driving inside the yard, operating a crane, entering a confined space, working at height: each carries its own medical standards, recurring checks and often a drug and alcohol programme. The record must be exact about what was tested, when and under which policy.

industrial robot arm on a factory line
Photo via Unsplash

Surveillance programmes recur whether anyone remembers them

Health surveillance is not a one off. It is a baseline assessment, then reassessment at an interval set by the hazard, for as long as the exposure continues, plus an exit assessment.

Every one of those appointments is a small intake: a questionnaire, exposure context the clinician needs, previous results held by the provider rather than by you, and a date to be offered, booked, attended and recorded. Multiply it by several hazards and every exposed role on a rotating shift, and the load is permanent.

A confidential record with a wall through the middle

The intake record here is clinical and confidential. It belongs to the occupational health clinician, and the employer is not entitled to its contents: not the questionnaire answers, not the diagnosis, not the audiometry trace, not what the person disclosed about medication or mental health.

That wall is a legal boundary, not a configuration preference. You cannot widen it with a data sharing agreement or an admin role in a system. Any sensible design accepts that there is a middle of this process an agent must never be inside.

The fitness line, and nothing either side of it

What the plant needs out of an assessment is small. One outcome: fit, fit with stated adjustments, or unfit for this task. Plus a recall date, and sometimes a review date. That is what a supervisor acts on and what a scheduler needs to put the right person on the right machine.

So an agent has two honest places to work, both outside the wall: the referral going in, which the employer writes and owns, and the outcome coming out, a short non clinical statement the employer is entitled to receive and must act on.

An agent that ingests clinical notes to summarise them for management is the wrong build, and the easy build, which is why people reach for it. Build the two sides and leave the middle alone.

tall shelving units in a distribution warehouse
Photo via Unsplash

Nothing the clinician asks for lives in one system

A good referral is the difference between a useful assessment and a wasted appointment. It needs the role and its real task demands, the exposures, the relevant substance and hazard data, the shift pattern and any adjustments already in place.

None of that sits in one system. It is spread across risk assessments, the substance register and its safety data sheets, exposure monitoring reports, the shift rota, the authorisation matrix and a note a supervisor wrote after the last absence. Assembling it is reading and typing, which is why referrals go out thin.

An agent can assemble that pack, quote the source document for each field, and mark anything the records do not state as not stated, never as a guess. A human signs it before it leaves.

The task description a clinician can actually use

Not the advert. Weights lifted and how often, reach and posture, time standing, whether a respirator is worn and for how long, vibration tool use across a shift, night working, lone working. A clinician judging fitness for a task needs the task, described physically.

Exposure decides who is due, and job titles mislead

Eligibility for health surveillance is driven by exposure, not by job title. A schedule built from an HR roster is built from titles, which is where most go wrong.

Titles lie. A role with no noise exposure recorded against it can spend most of a shift next to a press. A fitter whose title says nothing about dust climbs inside a hopper every quarter. Working out who is due means reading exposure assessments, the substance register and real shift and task records, not a list of job families.

The register and the recall list have never been read together

Here is the villain. People miss their recall because nobody reconciled the exposure register against the surveillance schedule, and the gap surfaces years later, at an inspection or in a civil claim, when the question is whether you can show that this person, with this exposure, was offered an appointment and seen at the right interval.

That is a reconciliation problem, which is precisely the shape of work an agent does well. Run the exposure data against the surveillance record and produce a difference list: exposed and never enrolled, enrolled and overdue, enrolled against an exposure that ended, left the role with no exit assessment, offered an appointment with no recorded outcome. Not one of those findings needs a clinical fact. All are visible from outside the wall.

Labour that rotates through the exposure and off the payroll

Agency workers, contractor crews and labour suppliers rotate through the same noise, dust and tools. The obligation follows the exposure, not the payroll, so the people most likely to be missed are those never on your HR system at all.

The evidence for them sits in gate logs, permit to work records, contractor induction files and whatever the supplier says it holds. An agent can reconcile presence and task against surveillance evidence supplier by supplier, and draft the request for what is missing.

Coming back after absence, and the adjustment that has to be negotiated

Return to work assessment has the same two sided shape. In goes a referral with the role, the task demands and the absence context. Out comes a fitness line, usually with adjustments.

Then the adjustment has to survive a production plan. Somebody has to tell the planner this person cannot work nights for a while, tell the supervisor what the lifting limit is without disclosing why, and remember that it lapses. Adjustments quietly become permanent, or quietly disappear when the shift pattern changes. An agent can hold one as a live record with an owner and a review date, and raise it when that date approaches or the person is rostered against it.

The question that arrives years later, at a claim

Claims and inspections ask the same question long after everyone involved has moved on. Was this person exposed, was surveillance offered at the right interval, were they seen, were the results communicated, and did the employer act on what the programme reported at group level.

That record either exists or it does not. An agent helps by writing intake and outcome records a stranger can follow years later: dates, intervals, the exposure basis for enrolment, what was offered, what was declined, and what the plant did about it. An offer refused and recorded is defensible. An offer never made is not.

Where AI fails here

Clinical judgement is not available to a model. Fitness for work is a clinician's decision. An agent that outputs a suggested fitness status, even as a draft, is building a decision somebody will eventually accept without reading.

The confidentiality wall is a legal boundary. A design that quietly gives the agent read access to clinical notes because it would improve the summary is not a tuning choice, it is a breach waiting to be found.

Free text triage carries real risk. A questionnaire answer can hint at something that needs a clinician the same day, and an agent routing that text stands between a person and urgent care. If free text is read at all, the only safe rule is escalate broadly to a clinician and accept the false alarms.

Adjustments are negotiated, not computed. What a person can do, what the line can accommodate and what a supervisor will sustain is a three way conversation. A model can hold the record of it and nothing more.

Drug and alcohol decisions carry employment law consequences. Testing, results handling and anything following an adverse result stay with named humans and your policy, no agent in the chain.

And exposure data is often wrong at source. Registers go stale, monitoring is years old, task records do not reflect what people do. An agent reconciling against a bad register produces confident nonsense at speed. The output is a question list for a human, never a conclusion.

Where to start

Pick one site and one hazard, usually noise, and run a single reconciliation: exposure records against the surveillance schedule, including agency and contractor presence. Output a difference list with a named reason for each row, and have an occupational health adviser work through it. You will learn more about your data quality in one run than in a year of reports.

Then add referral assembly for the next intake cycle, with a human signing each pack. Then outcome routing: the fitness line, the adjustment and the recall date, delivered to the people who schedule and supervise, clinical middle untouched.

If you want a second opinion on where the wall should sit in your build, Adopt AI Partners will look at it with you: hello@adoptaipartners.com.

Tell us what your teams keep redoing

One conversation is enough to say whether there is a system worth building, and what would make it fail.

Describe your process