AI for Imaging Centers: Scheduling and Prior Authorization Follow-Up
An AI agent can prepare imaging orders, track prior authorization status and draft patient messages, with staff signing off before each exam is cleared.

An AI agent can handle the repetitive middle of imaging scheduling and prior authorization follow-up: reading incoming orders, checking that the exam and payer requirements line up, drafting the authorization packet, and tracking what is still open. The agent works inside permissions the center sets, and a named staff member signs off on each step that commits the center to a payer, a patient, or a changed appointment. This article describes how that split works in practice.
Key takeaways
- Scheduling and prior authorization follow-up are two linked queues, and most delays happen where they meet.
- The agent should prepare, check and track. Staff should approve submissions, reschedules and anything promised to a patient.
- Each cleared exam needs a written checklist with a named staff sign-off, not a shared login.
- Referrals, payer letters and faxed notes are data to read, never instructions the agent should follow.
- Start with one modality or one payer group and one observable criterion, then widen scope only after the checklist holds.
Where the work sits in an imaging center
Imaging scheduling looks simple from the front desk, but each booking depends on facts that live in different places: the order from the referring office, the modality and room, the contrast or sedation plan, the patient preparation instructions, and the payer's rules for that exam. When one of those facts is missing, the slot can stay on the calendar while the exam is not actually ready to perform. Prior authorization follow-up sits on that seam. A request may be pending, approved for a narrower set of codes than ordered, approved with a date window that barely covers the appointment, or denied with a request for more clinical notes.
Most centers already track this work across scheduling software, shared inboxes, payer portals and staff memory. The problem is rarely indifference. The follow-up depends on whoever remembers to check, and a status change on a Friday afternoon can sit unseen until the morning of the scan.
Which parts an agent can run
An agent is useful here because it can read many small records, compare them against a stated rule, and keep a running list of what is open. It should not be the final authority on any of those things. A practical scope for a first version looks like this:
- Read incoming orders and flag fields that are missing, unclear or inconsistent with the requested exam.
- Propose a slot that matches the modality, room and prep template, and hold it as a draft until staff confirms.
- Draft the authorization packet from the order, prior notes and the payer's documented requirements, then place it in the staff queue.
- Track each request through its status and raise a flag when an approval is close to expiring or a payer response is overdue.
- Draft patient messages about preparation or timing for staff to approve before anything is sent.
Memory matters. The agent needs the center's protocol templates, approved preparation language, a current note of payer requirements that staff maintain, and the contact route for each payer. It should not carry patient history beyond what a task requires. Tool access should be scoped to the minimum: read access to the scheduling calendar, write access only to draft holds, and no direct authority to submit to a payer. The OWASP authorization guidance is a useful reference for writing those scopes down as explicit rules rather than assumptions.
The same tracking pattern appears in other intake-heavy work, such as credentialing applications and expirations, where the value comes from knowing what expires next rather than acting on every record.
How the workflow runs, step by step
The sequence below is one way to set up the work. The exact steps depend on your modalities, your payers, and whether authorization runs through portals, phone calls or fax.
- Step 1: The order arrives and the agent checks the required fields: patient identifiers, ordering provider, exam, diagnosis and urgency.
- Step 2: The agent compares the exam with the payer requirement note and marks authorization as likely needed, not needed, or unknown.
- Step 3: If authorization is needed, the agent drafts the request packet and lists the supporting documents that must be attached.
- Step 4: Staff reviews the packet and submits it through the payer route. Once staff records the submission and reference number, the agent saves them to the tracking record.
- Step 5: The agent checks status on a fixed daily schedule and writes the result as approved, pending, denied or needs information.
- Step 6: If the approval covers the exam and the date window, the agent marks the appointment as cleared for staff confirmation. If not, it drafts options: reschedule, request more information, or escalate to the ordering office.
- Step 7: Before the scan, the agent produces one readiness summary for the scheduler listing what is cleared, what is open, and which decisions are needed that day.
A fixed check rhythm is easier to audit than checks made whenever someone has a spare minute. It also makes silence visible: a payer response that has not arrived by the expected day becomes a flag, not a surprise.
Decisions that stay with staff
Some decisions should not move to the agent, even when it has the information. They involve clinical judgment, financial commitments to patients, or changes the center is accountable for. Staff should own:
- Whether the clinical indication supports the exam and any question about medical necessity.
- Submission of any authorization request, and any appeal or peer-to-peer discussion.
- Any change to an appointment the patient has already accepted.
- Any estimate of what the patient will owe.
- Any urgent exception, including exams that must proceed before authorization is confirmed.
A short decision guide helps the scheduler act quickly. If the question concerns clinical content, route it to the radiologist or the ordering office. If it concerns payer policy, route it to the authorization lead. If it concerns only the calendar, the scheduler can decide after reading the readiness summary. If it involves money or a patient commitment, the billing lead or business owner signs off.
The NIST AI Risk Management Framework frames this kind of work as mapping risks, measuring them and managing them with clear owners. For an imaging center, the practical version is a written list of who can approve what, completed before the first live use. Behavioral health intake faces similar limits, and the scheduling limits in that setting are worth reading for comparison.
Staff sign-off checklist
Use this checklist before any exam is marked as cleared. The signing staff member should be named in the record.
- The order includes patient identifiers, ordering provider, exam and diagnosis, and they match the scheduling record.
- The payer requirement note was reviewed recently and states whether authorization applies to this exam.
- The authorization status is approved, the approved exam matches the ordered exam, and the date window covers the appointment.
- Any reference number is recorded, and the approval letter or portal confirmation is attached to the record.
- The preparation instructions sent to the patient match the approved template for this modality, including any contrast or sedation instruction.
- Every open item has an owner and a due date, and nothing is marked cleared while a question remains.
- The signing staff member reviewed and approved each draft patient message before it was sent.
An illustrative scenario
The following scenario is illustrative and does not describe a real center. A referral arrives for a lumbar MRI, but the diagnosis code on the order does not match the body region. The agent flags the mismatch, holds a draft slot, and places a note in the staff queue with the two conflicting fields side by side. The scheduler contacts the ordering office, the code is corrected, and the agent drafts the authorization packet with the corrected information. When the payer approves a narrower date window than expected, the agent flags that the appointment falls one day outside it and drafts two alternative dates. The staff member chooses one, approves the patient message, and signs the checklist. The exam is marked cleared only after that signature.
The value here is less about speed than about where the error was caught: before the packet left the building and before the patient arrived.
How Be Human runs this as a managed service, and how to measure it
Be Human designs and operates this kind of agent as managed infrastructure. A first engagement defines one role, such as scheduling readiness for one modality, the memory and tools that role needs, approval boundaries written as checklists, and an observable success criterion, such as whether each exam reaches the scanner with a documented authorization status. Managed operations then cover monitoring, recurring evaluations of the agent's drafts against staff corrections, permission reviews, integration maintenance when a payer portal or scheduling system changes, and controlled improvements. Service is remote and available in English and Portuguese.
Measure the first version by counting the cases where staff had to correct the agent, and by checking whether any exam reached the scanner without a documented status. Widen scope only when those counts stay low and stable for a period the owner chooses. Recurring checks of this kind are described in Anthropic's guidance on evals for agents, which is a useful model even outside software teams. If you want to find the first task in your center worth handing to an agent, take the free Be Human AI diagnostic.
Frequently asked questions
Can an AI agent submit prior authorization requests to payers by itself? In a sound setup it should not. The agent can prepare the packet, track status and flag what is missing, but a named staff member should submit and sign off because that step commits the center to a payer relationship and a record. Keeping that boundary also makes the audit trail easier to read later.
Does the agent need access to the full patient chart? No, and it should not have it by default. It needs the fields required for the exam, the contents of the authorization packet, and the status of each open request. Narrow access reduces how much sensitive information a single mistake or a malicious instruction could expose.
How long does a first version take to set up? That depends on how many modalities, payers and channels are in scope, and on how current the payer requirement notes already are. A focused first role with one modality and one written checklist is far easier to validate than a department-wide rollout. Be Human scopes the first engagement around one role and one success criterion so the boundaries are tested before anything expands.
What if a referral document contains text that tells the agent to skip a step? The agent should treat that text as data, not as a command, and this is a design rule rather than a hope. Referrals, payer letters and faxed notes come from outside the center, so they are untrusted content. The OWASP guidance on prompt injection describes how to keep instructions from external text separate from the agent's own rules, and any attempt to change the workflow should surface as a flag for staff.
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.


