Submit and track prior authorizations on the utilization-management portals payers delegate them to. When the payer’s answer is “that service goes through our UM vendor,” the authorization leaves the payer’s portal entirely, and this is the workflow that follows it there.
Go-live in as little as 30 minBrowser agentCustomer portal login
We map your process, volume, and exception paths, then recommend a practical first scope.
Building internally? Read the docs →
How Asteroid runs this workflow
A PA request the payer has delegated arrives, Asteroid submits it on the UM vendor's portal and re-checks the pend on schedule, and a normalized submission-and-status record lands back in your queue. A peer-to-peer request or unanswerable question goes to a person immediately.
How it actually runs
A peer-to-peer review request, a demand for more information, or anything the portal disputes goes to a person immediately, with the reviewer’s actual ask attached.
A PA request is ready for a utilization-management platform
A normalized record in your PA queue
The tracking number, review status, portal messages in their exact wording, and the evidence used land as one normalized submission-and-status record, with pends re-checked on schedule.
No confident match or open question: The case returns with the reviewer's actual ask attached (a peer-to-peer request, a demand for more information, or a question the inputs don't cover), and clinical staff resolve it once.
UM portals are where authorizations sit the longest, because clinical review happens there, and “pending” is where scheduling quietly dies. Staff re-checking pended auths is a person being used as a polling loop. Run as agents, every pended authorization gets re-checked on cadence, and your team gets the changes, not the checking.
At scale
These UM-portal agents are in the catalogue pipeline. The same submission discipline already runs in production on clearinghouse-style portals and payers’ own provider portals; see the prior authorization workflow library for the full set. If delegated services dominate your PA queue, scoping a build against your UM mix is the fastest path to running.
Questions
Disclaimer
Third-party names, including government agencies and registries, are used only to identify systems commonly involved in healthcare operations workflows. Asteroid is not affiliated with, endorsed by, sponsored by, or certified by those third parties unless expressly stated. Workflow availability depends on customer authorization, account permissions, configuration, and applicable system terms.