Complete and track medication prior authorizations on electronic prior-auth portals, from the PBM’s question set through to determination. The prescription is already at the pharmacy; this workflow exists to stop the PA from being the reason it sits 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 medication PA enters the queue, Asteroid works the ePA portal's question set strictly from the chart material you provide, and the reference ID and determination land back in your PA queue, and any question the documents don't answer stops for the prescriber's team instead of being improvised.
How it actually runs
A denial, a step-therapy or formulary-alternative counteroffer, or a clinical question beyond the provided chart goes to the prescriber’s team immediately, with the PBM’s actual language attached.
A medication, patient, prescriber, payer, and the available clinical data enter the PA queue
Determination back in your PA queue
The ePA reference ID, the questions and evidence used, the current status, and the payer's response in its exact wording write back to your queue.
Question beyond the chart: The exact question returns by name with the PBM's language attached; the prescriber's team answers it once. Clinical and prescribing judgment never automates.
A medication PA delays the only person with no ability to work the queue: the patient at the counter. For the practice it’s one of forty routine tasks, so it waits, and the waiting is invisible until the pharmacy calls. Run as agents, the PBM’s question set is answered the hour it appears, because the agent has no other thirty-nine tasks. The PA is the whole job.
At scale
ePA-portal agents are built per PBM rather than cloned from a one-click template. What’s already live is the same discipline on payer portals and clearinghouse-style portals. Bring your PBM mix to scoping to start the build; the rest of the family is in the prior authorization workflow library.
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.