AI agents for operations leaders in healthcare in the United States

US healthcare operations leaders can use AI agents to assemble prior authorisation requests, work claim denials, triage referral and records inboxes, verify eligibility and prepare good faith estimates. Clinical decisions, appeals arguing medical necessity, and disclosures of protected health information outside routine flows stay with people. HIPAA, state privacy and health laws, and Colorado's AI act for consequential decisions apply.

What do US healthcare operations leaders spend their time on?

Prior authorisation. Many procedures, drugs and imaging studies need payer approval before they happen. Each payer has its own criteria, forms and portals, and staff spend hours gathering clinical documentation, submitting requests and chasing decisions. Delays push back care and frustrate clinicians and patients.

Denials. Claims are denied for eligibility, coding, missing authorisation, timely filing and medical necessity. Revenue cycle teams sort denials by cause, correct and resubmit what they can, and appeal the rest within payer deadlines. Denial rates and days in accounts receivable are the numbers leaders watch.

Inboxes. Referrals, records requests, payer correspondence and results arrive through shared inboxes, faxes converted to documents, portals and phone messages. Sorting them to the right team, quickly, is a constant job.

Where can AI agents help?

• Prior authorisation assembly (depth 2). The agent identifies whether the service needs authorisation under the patient's plan, gathers the required clinical documentation from the record, completes the payer's form and drafts the submission for an authorisation specialist.
• Denial work queues (depth 2 and 3). The agent classifies each denial by cause, corrects and resubmits technical denials such as wrong patient details or codes within limits, and drafts appeals for medical necessity denials.
• Inbox triage (depth 2 and 3). The agent reads incoming referrals, records requests and payer letters, indexes them to the patient, and routes them. Our playbook on triaging a shared operations mailbox with an AI agent covers the method.
• Eligibility and benefits checks (depth 3). Before visits, the agent checks coverage, deductibles and authorisation status, and flags problems to registration.
• Good faith estimates (depth 2). For uninsured and self-pay patients, the agent drafts the estimate from the scheduled services and fee schedule for a financial counsellor to issue.

Technical denials and medical necessity denials are different capabilities. Fixing a transposed member ID is routine and checkable. Arguing that care was necessary is a clinical case. The agent resubmits the first at depth 3; the second is drafted for a clinician and appeals specialist.

What stays with people, and why?

Clinical decisions, including whether to proceed without authorisation in urgent cases, stay with clinicians.

Appeals arguing medical necessity stay with clinicians and appeals specialists. They need clinical reasoning and are often reviewed by the payer's own clinicians.

Disclosures of protected health information outside routine treatment, payment and operations flows, such as to attorneys, employers or in response to subpoenas, stay with the privacy office. Patient complaints and billing disputes stay with people.

Which rules apply in the United States?

HIPAA governs protected health information held by covered entities and their business associates. The privacy rule limits uses and disclosures and requires the minimum necessary information for payment and operations. The security rule requires administrative, physical and technical safeguards. An agent's supplier that handles protected health information is a business associate and needs a business associate agreement. Breaches must be notified.

States add their own health privacy and medical records laws, and state privacy laws such as California's CCPA as amended by the CPRA apply to some data outside HIPAA. Colorado has passed an AI act aimed at high-risk systems that make consequential decisions, including those affecting access to health care services; providers there should check whether any agent is in scope. Federal rules require good faith estimates for uninsured and self-pay patients. There is no single federal AI law. The NIST AI Risk Management Framework offers a voluntary structure for governing these systems.

This is an explanation of the rules, not legal advice; confirm how they apply to you with counsel.

How do you start in the first 90 days?

Weeks 1 to 4: sign the business associate agreement with the agent's supplier and complete the security review. Start inbox triage at depth 2, routing only.

Weeks 5 to 8: shadow denial classification and technical resubmissions. Compare with the revenue cycle team's work on every denial, and track resubmission acceptance.

Weeks 9 to 13: certify technical resubmissions at depth 3 and inbox routing at depth 3. Begin prior authorisation assembly in shadow for one service line. Update runbooks so every held item has a named owner; see writing runbooks for AI agent operations. Follow deploying AI agents: train, shadow, certify, widen. For a public waiting-list system, see our brief on operations agents in UK healthcare.

Where Pryme fits

In Pryme, a payer's eligibility response is signed evidence and a referral faxed by an outside practice is external. The authorisation agent shows which documents support each criterion. Its role scope covers assembly; submission and appeals are held for a named specialist, and every verdict is filed so you can show the payer and auditors what happened.