During an active admission, submit the payer notices utilization management owes, notice of admission, discharge notice, transfer notice, and file expedited or concurrent appeals on the payer’s provider portal. Your UM team produces the clinical content. The agent submits it and brings back the confirmation number and a screenshot.
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
An admission, discharge, transfer, or adverse determination fires in your UM system, Asteroid signs in to the payer portal, files the matching notice or appeal with the clinical content your team produced, and returns the confirmation number and screenshot, and any portal prompt the content does not answer stops for a UM nurse.
How it actually runs
The same shape runs on legacy Windows or Citrix UM case systems with no browser at all: a computer-use agent completes the case-creation form and uploads the PDF the way a coordinator would. Status tracking after submission is a separate workflow and is not part of this one.
A UM event with its clinical content: notice type or appeal, member, admission, and the supporting documentation
Confirmation number and screenshot on the UM case
Each notice or appeal returns the payer’s confirmation number, submission timestamp, and screenshot to your UM case record, as evidence of timely filing.
A portal question the clinical content does not answer: A required clinical field the packet does not cover, a member or admission the portal does not recognize, or an appeal type the portal will not accept stops the run with the portal’s wording. A UM nurse resolves it once. The agent never answers a clinical question on its own.
A UM notice filed late is a denial you cannot appeal, and an appeal filed without the right clinical content loses. Asteroid does not generate the clinical case. Your UM tool or your nurses produce it, and the agent puts it on the payer’s form inside the window, with proof. A portal question the content does not answer stops the run for a nurse rather than getting a guessed answer under time pressure.
At scale
The UM notice and appeal agents are in the catalogue pipeline, built payer by payer with multi-payer clearinghouse portals first, then direct payer portals. The portal login and navigation they use run today in prior authorization on payer portals and denial management. Post-claim appeals are a different portal section and a different workflow: claim status, denials, and appeals. Scope your payer mix to sequence the build; the rest of the category is in the prior authorization 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.