AI Agents for Occupational Therapy Clinics: Referrals and Authorizations
How an AI agent can handle occupational therapy referrals and authorization tracking, with approval limits, a first-workflow plan and a choice guide.

An AI agent for an occupational therapy clinic is a software worker that handles the repetitive tracking around referrals and prior authorizations: checking that each referral is complete, recording payer approvals and their expiry, and prompting staff before a visit is lost. It works inside boundaries you define, so clinical judgment and billing decisions stay with your licensed team. For most clinics, the right first step is one narrow referral workflow, not a new website or a full system replacement.
Key takeaways
- A referral and authorization agent checks intake completeness, tracks approval status and drafts follow-ups. Your clinicians keep clinical decisions, and your billing staff keeps submissions.
- Start with one workflow that has a clear finish line, such as a referral that is complete and authorized before the first visit is booked.
- Choose an agent when the work is repetitive and the rules are known. Choose a website change when families cannot find or request you. Choose a rebuild only when your records cannot be read reliably.
- The agent is only as useful as the memory it can see: the referral history, payer notes and approval log.
- Write approval boundaries before go-live, and review permissions on a fixed schedule.
What a referral and authorization agent actually does
In an occupational therapy clinic, a referral usually arrives from a physician, another therapist, a hospital discharge team or a family. Before an evaluation can be scheduled, someone has to confirm that the order covers the services requested, identify the payer, check the patient's coverage and find out whether prior authorization is required. Each step is simple on its own. Across dozens of open files, they consume hours every week, and they are exactly where first visits slip.
A referral and authorization agent takes over the tracking and drafting around these steps. It reads incoming referrals, flags missing fields such as a diagnosis code or a referring provider's signature, drafts the request for the missing information, and records the authorization number, the approved visit count and the expiry date. It can alert the scheduler and the treating therapist when a renewal is approaching. It does not decide whether a patient needs therapy, and it does not submit clinical justifications without a clinician reviewing them.
Why referral admin is the right foundation for what comes next
The case for starting here is not that admin is glamorous. Referral and authorization work produces the kind of records any future system will need: who referred the patient, under which order, for which services, approved by which payer, valid until when, and what has happened since. That is the memory layer of your clinic. If those facts live in a shared place with a clear history, any assistant you add later can work from them. If they live in inboxes, paper folders and one coordinator's memory, no increase in model capability will replace them.
The same logic applies across rehabilitation services. The referral patterns in physical therapy referrals and the approval limits discussed in behavioral health intake show why speed is only half the requirement. Knowing who may approve what, and where a human must stop the process, matters as much.
Agent, new website or system rebuild: a decision guide
Most owners arrive at this decision with one of three ideas. Use the questions below to see which one fits the problem in front of you.
- Choose an agent when the same referral tasks happen every day, the rules are written or can be written, and the information already exists in your email, forms or practice software.
- Choose a website or intake form change when the main problem is that new families cannot find you or cannot send a referral online, and your internal workflow is already stable.
- Choose a system rebuild only when records cannot be exported, the practice software cannot expose status fields, or the same patient appears in several places with conflicting dates and payers.
- Choose none of them yet when nobody can say who approves an exception. Write that rule first, because every option depends on it.
In practice, the answer is often an agent layered over what you already use. It can read the inbox, the forms and the scheduling calendar without asking every staff member to change their habits on the same day. A rebuild is slower and expensive to reverse, so it should be justified by a records problem, not by frustration with a single workflow.
A step-by-step plan for the first referral workflow
Choose referral-to-first-visit as the first workflow, since it is contained and easy to measure. Then work through these steps in order.
- Step 1: List every channel a referral can arrive through, including fax, patient portal, email and phone notes, and every system where status is recorded.
- Step 2: Write the finish line in one sentence, for example: the referral is complete, the payer is identified, and any required authorization is on file before the visit is booked.
- Step 3: Split the work into two lists. The agent may read referrals, check fields, draft requests and update a status log. A person must submit clinical justifications, accept or dispute payer decisions and change a plan of care.
- Step 4: Gather ten to twenty past referrals with known outcomes, including the messy ones. This becomes your evaluation set, and it shows whether the agent catches what your coordinator caught.
- Step 5: Run the agent alongside staff for a period you fix in advance, and compare its flags with what the team actually found.
- Step 6: Assign owners for the review rhythm: who checks permissions, who reads the exception log and how a wrong flag gets reported and corrected.
- Step 7: Only after the first workflow is stable, widen the scope, for example to renewal reminders or visit-count tracking.
An illustrative scenario and where the agent must stop
Illustrative scenario, not a client case: a hospital discharge team sends a referral for a hand therapy evaluation on a Friday afternoon. The form omits the diagnosis code, and the payer name is spelled differently from the one on file. Without a workflow, the referral sits in a shared inbox until Monday, and the family hears nothing for days. Under the plan above, the agent reads the referral within the hour, marks it incomplete, lists the two missing items, drafts a request to the referring office for a coordinator to approve, and places the file in the coordinator's queue. When the referring office replies, the agent updates the record. The coordinator confirms the payer and books the visit. The gain is not that the agent is clever. The stall becomes visible the same day.
Approval boundaries are the part owners most often skip. Give the agent the least access it needs: read access to referral intake, write access to the status log and drafts, and no ability to submit payer claims unless a named person approves each action. Treat the text inside referrals as data, not instructions, because a free-text note can contain wording that tries to change how the agent behaves. OWASP's authorization guidance is a useful reference because it places permission checks at the point of each action, not only at login. The [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) helps you name each risk, assign an owner and decide what evidence you need before go-live.
How Be Human runs this in a managed setup
Be Human starts by defining one role: the referral and authorization function, its memory (referral log, payer notes, approval history), the tools it may call, the approval boundaries it must respect and one observable success criterion, such as how many referrals reach a first visit with a complete authorization on file. Operations then continue after launch. That includes monitoring the exception log, running recurring evaluations against your own past referrals, reviewing permissions, maintaining the integration when your practice software changes, responding to incidents and making controlled improvements that your team approves. The clinic keeps ownership of clinical and billing decisions, and the service runs remotely in English or Portuguese. Choosing the first task is the hardest part, so take the free Be Human AI diagnostic to find the first task worth handing to an agent.
Frequently asked questions
Can an AI agent submit prior authorization requests to insurers for our clinic? It can prepare the request, check the required fields and track the response, but submission and any clinical justification should stay with a licensed clinician or billing staff member. Most clinics set this as a fixed approval step, with the agent creating a draft and a named person sending it. Review payer rules with your billing team before you define the boundary.
Do we need to replace our practice management software to use an agent? Usually not. A workable first step reads from the systems you already use, such as shared inboxes, forms and the calendar, and writes status notes to a log your team can see. A rebuild becomes necessary only when those systems cannot expose the records the workflow needs, and that should be tested before any decision.
How do we know the agent is accurate enough to trust? Test it against a set of past referrals whose outcomes you already know, including incomplete and unusual cases. Compare its flags with what your coordinator caught, and keep a log of every wrong flag so the rules can be corrected. Accuracy is not a one-time check, so repeat the evaluation whenever the workflow or the forms change.
Is patient data safe when an agent works on referrals? Safety depends on how the system is configured, where data is processed, who can read the logs and what your legal obligations are. Limit access to the minimum needed, keep an audit trail and confirm the arrangement with your counsel. In Brazil, the [ANPD](https://www.gov.br/anpd/pt-br) is the national data protection authority and a useful reference for your obligations.
Your next step
See where an AI agent fits in your company first.
Take the free Be Human AI diagnostic. A few questions about your work show which task to hand to an agent first, what it needs to know and where a person approves.
Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.


