AI for Patient Intake in Government

A school emails the adult social care duty inbox at ten past five on a Friday, subject line "concern about a pupil's grandmother". Six paragraphs down, past the family history and the pastoral lead's name, sits the sentence that matters: the woman has been alone since Tuesday and there is no food in the house. By the time a duty officer opens the case management system, the statutory clock has been running an hour and nobody has recorded when it started.

Statutory first contact, programme by programme

The phrase comes from healthcare, but much of this work happens in buildings that are not hospitals. Immunisation and school vaccination programmes take consent back from thousands of households in a few weeks. Sexual health and communicable disease services register people who would rather not be, and contact tracing opens an intake on somebody who contacted nobody. Reception into custody or detention includes a health screen within hours of arrival, on a person whose records sit elsewhere. Veterans and serving personnel enrolment keeps readiness records that follow a career. Adult social care and safeguarding take referrals from anyone at all, and school nursing picks up children whose parents never filled in a form.

They share the shape of the first hour: somebody who is usually not a clinician reads a stranger's account, decides what it is, and starts a legal duty running.

Entitlement is set by law, not by a price list

A private clinic asks whether somebody will pay. A public body asks whether a duty is owed. Ordinary residence, age, an eligible need, immigration status where the regulations make it relevant, a means test for a contribution: each is a test written in statute or guidance, each carries exceptions, and several cannot be answered from the referral alone.

An unresolved entitlement question is also not a reason to stop. Urgent treatment, safeguarding enquiries, screening on reception and communicable disease work all continue while entitlement is open, and the record carries both threads: what was provided, and what was still being established.

Three organisations, one person, one lawful basis

The referrer, the assessor and the provider often sit in three organisations under three different duties. The police share under one power, a school under another, a charity on consent it may not have recorded, a neighbour with nothing beyond concern. On the receiving side the basis may be a public task, a statutory duty, vital interests in an emergency, or consent that can be withdrawn next week.

So intake captures more than contact details: who sent this, under what basis, what the person was told, what they agreed to, whether they had capacity to agree, and which parts are restricted from onward sharing. Get that wrong and every later handover either stalls on an unanswerable question or happens anyway and becomes a finding in somebody's report.

The urgent detail is in the fourth paragraph

Referrals arrive as prose. A police notification written at the end of a shift, a teacher's email, a housing officer's case note, a charity web form, a daughter's phone call typed up by a contact centre agent. There is no fixed format and the chronology is often inside out: background first, the significant fact in the middle, the referrer's view at the end.

That fact is rarely flagged. No food since Tuesday. A named person who still has keys. An earlier unexplained injury mentioned in passing. Officers skim, because the queue requires it, and skimming is how a buried sentence gets missed. Add scanned handwriting, a forty page bundle in which two pages matter, and the same referral sent twice by two agencies.

The duty to assess starts at a moment somebody has to name

Most of these programmes run against defined periods. A screen within hours of reception into custody. An assessment begun within a set time of a referral being accepted. A safeguarding decision made promptly, with promptly defined locally and inspected nationally.

The clock needs a start point and there are at least three candidates: the date of the event described, the date the referral reached a shared inbox, and the date a human opened it. Somebody has to choose, record the choice and defend it. Most breaches are not caused by slow assessment. They are caused by a referral sitting unread in a mailbox nobody owned over a bank holiday.

The missing item that stalls everything

GP details. A date of birth. A current address. A consent signature. Confirmation of who holds authority to act for the person. The missing item is usually knowable in the first five minutes of reading and discovered on day six, after the case has been queued, allocated and reopened twice.

An interpreter booked at intake, not at the appointment

Spoken language, sign language, easy read, large print, braille, an advocate, the adjustment somebody needs in order to attend at all. These belong in the intake record, not in a note added after the first visit fails. Capture the need when the referral is read and the first contact works. Miss it and you spend a slot, the person is recorded as not having engaged, and the timescale runs on. Held on the record rather than in an officer's head, it also stops being asked for twice.

The same person, four programmes, no shared number

Public bodies routinely hold the same person several times over. Variant spellings and transliterations, a married name on one system and a maiden name on another, a date of birth guessed as the first of January, no national health identifier on a charity's referral, no fixed address at all. A child may be known to school nursing, community paediatrics and social care under three slightly different names.

The risk runs both ways. A wrong merge puts one person's health information into another's file, a breach and a clinical hazard at once. A wrong split hides the pattern: three low level concerns that, read together, are an escalating one.

Every field points back to a sentence somebody wrote

An agent reads the referral, however it arrived, and populates the structured intake fields, attaching to each the exact sentence it came from. The officer verifies rather than transcribes, which is faster than retyping. Where the referral does not say, the field stays empty and marked as not stated, never filled with a plausible guess.

That provenance does most of the work downstream. It makes an entry checkable in seconds and safe to correct, because you can see what the agent read and judge how it read it.

What the referral evidences, and what it only asserts

Entitlement criteria can be held as a written list and the referral checked against it. The output is not a yes or a no but three groups: criteria the referral evidences and where, criteria it asserts without evidence, and criteria it does not address. A referral may state that the person lives in the area while giving no address, or describe a care need without reaching the threshold in guidance.

The agent can also flag which missing item will stall the statutory timescale, and check the referral against existing records to say whether this is somebody already known to another programme, with matching and conflicting details set out rather than merged.

The acknowledgement and the evidence request, drafted not sent

Most intake correspondence is formulaic in structure, particular in content. An acknowledgement to the referrer. A request for the one missing item. A holding letter in the format the person asked for. An agent can draft these from the referral and the criteria list, in the service's own wording, for the officer to read, amend and send.

The decision itself does not move. Accepting, refusing or escalating a referral stays with the named officer, because a refusal carries consequences, appeal and complaint routes, and sometimes the return of the same person in a worse state. Signing it is a human act, and the name on it should belong to somebody who read the words.

Written now to be read by an inspector later

Every intake record here has several future readers: an inspector, an auditor, the person through a subject access request, a journalist through a freedom of information request, occasionally a coroner. The trail has to be legible without a technical explanation: what was received, what the agent extracted, which sentence each field came from, what the officer changed, when, and what was sent.

Two consequences. Avoid opaque scores at intake: a number nobody can explain is worse than no number. And keep third party information separable from the start, since much of a referral is somebody else's personal data and has to come out before disclosure.

Nobody can change the intake form this quarter

The form usually belongs to a case management system under a long contract, and the procurement route to altering it is measured in quarters. So build around it: read the inbox, produce the fields and the drafts, and write back through whatever interface exists, or present the set for an officer to transfer. A project that waits for a new system will not happen.

Where AI fails here

Some of this should not be automated at any confidence level. Anything indicating immediate risk to life needs a route straight to a person, not a place in a processed queue. Capacity and best interests decisions, child protection thresholds, mental health and deprivation of liberty assessments, and the reading of coercive control, where the signal is what the person avoids saying, turn on judgement that criteria on a page do not capture.

The model will also misread handwriting, local place names and dialect, and it can be fluently wrong about dates, which matters more here than almost anywhere, because the dates are the clock. It cannot see what the referrer chose not to write down, cannot hear that a caller was frightened, and will not notice when the person's account contradicts the referral. A high volume programme with a stable form, such as immunisation consent, is where this is strongest; the Friday evening referral is where it should only read, extract and draft.

Where to start

Take one programme and one intake route, with four weeks of history. Measure what you have now: time from arrival to triage decision, and how many cases stalled on one missing item. Then run the agent in shadow, producing the fields, the evidence gaps and the duplicate flags while nobody acts on the output, and compare it against what the officer recorded. Contested referrals, not clean ones, are the ones to score.

Adopt AI Partners builds this kind of intake agent inside the case management systems, inboxes and referral forms a team already works in. If the delay on your referral route is in the reading rather than the assessing, describe the situation to hello@adoptaipartners.com and we can say whether it is a sensible first candidate.