Browser

How do you automate prior authorization on payer portals?

Prior authorization automation files and tracks prior auths on payer portals that have no API, the way staff do by hand. With Oya, an AI agent files one prior auth on the portal, signed in as your staff, and Oya saves it as a playbook that files the next ones with no model. On Oya Cloud and the enterprise edition this runs under a BAA.

How it works

Three steps, the same on every payer portal.

  • Run it once: an agent files the prior auth on the payer portal while a person can watch.
  • Save it as code: the run becomes a playbook, Playwright code you can read, with the member ID, CPT code, diagnosis and ordering NPI as variables.
  • Replay with no model: one SDK call or one MCP request runs it again with new inputs.

When the portal changes

The replay stops at the step that moved, the agent finishes the request from there, and its fix becomes the playbook, so the next run makes no model calls again.

Under HIPAA's controls

On Oya Cloud and the enterprise edition, the controls live in the browser.

  • We sign BAAs. Our SOC 2 Type II audit is in progress.
  • Every action, by an agent or a person, is a hash-chained audit row the database refuses to edit or delete, kept for 365 days at least.
  • Oya Cloud, or the enterprise edition in your own infrastructure (Docker, ECS, GCP or Kubernetes), so PHI can stay in your network.
  • A person can watch any session live, take over and hand it back.
  • Browsers reach only the hosts you allow.

Questions

Can AI submit prior authorizations?

Yes. An Oya agent fills in the payer portal form and submits it, signed in as your staff, and every step is a row on the audit trail. A person can watch the session and take over at any point.

Does the payer need an API?

No. Oya works the portal the way staff do, in a real browser, so it fits payers that have no API.

Can it track requests already filed?

Yes. A playbook can read a request status on the portal on a schedule, and every read lands on the audit trail.

What about portal logins and two-factor codes?

Stored passwords and TOTP seeds are sealed and never shown to the model. When a sign-in needs a person, such as a text-message code, staff can take over the session and hand it back.

How much faster is it?

Customers report 10 to 30 times the throughput of the same work by hand.

Is prior authorization automation with Oya HIPAA compliant?

On Oya Cloud and the enterprise edition, yes: Oya is HIPAA compliant and we sign BAAs. Write to [email protected].