Automated Genetic Testing Prior Authorization
Every morning, WebRun opens Progeny Clinical, finds newly ordered tests whose payer requires prior authorization, drafts the authorization packet with the clinical justification in DocuSign, and logs each request's status in a Google Sheet so your billing team always knows what is waiting, submitted, or approved.
How do I clear genetic testing prior authorization requests without losing track of any of them?
WebRun checks Progeny Clinical every morning for newly ordered tests that need payer prior authorization, drafts the packet with the clinical justification in DocuSign, and logs each request's status in a Google Sheet. Billing staff review and submit every packet themselves, so nothing goes to a payer without a human checking it, while the tracker shows what is still waiting.
- Every order needing authorization gets a drafted packet the same morning it is placed
- Billing staff see one tracker instead of checking payer portals one by one
- Requests waiting more than 5 business days are flagged automatically
Built for genetics billing teams · prior authorization coordinators · genetics practice managers · medical geneticists
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.progenygenetics.comin a real browser with your saved login - no setup, no API keys. -
1
Progeny Clinical - find orders needing prior authorization
progenygenetics.com
WebRun opens Progeny Clinical to find orders needing prior authorization. - Open Progeny Clinical and list test orders placed since the last check
- Check each order's payer against your list of payers that require prior authorization
- Pull the clinical indication and family history supporting medical necessity for each flagged order
Done when Every order requiring prior authorization is listed with its payer and clinical justification.
-
2
DocuSign - draft the authorization packet
docusign.com
WebRun opens DocuSign to draft the authorization packet. - Draft a prior authorization packet using the payer's template with the patient, test, and clinical justification pre filled
- Attach the supporting family history summary from Progeny Clinical
- Leave the packet unsent. Billing staff review and submit it to the payer themselves
Done when A drafted, unsent authorization packet exists in DocuSign for every order that needs one.
-
3
Google Sheets - log the request status
google.com
WebRun opens Google Sheets to log the request status. - Open the Prior Authorization Tracker sheet
- Add or update a row for each order with the payer, date drafted, and current status
- Flag any request that has been waiting more than 5 business days without a payer response
Done when The tracker sheet reflects every open prior authorization and how long it has been waiting.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it submit the authorization request to the payer on its own?
No. WebRun only drafts the packet in DocuSign and leaves it unsent. Your billing team reviews and submits every request to the payer themselves.
How does it know which payers require prior authorization?
You give it your payer list once during setup. It checks every new order's payer against that list and only drafts a packet when authorization is actually required.
What happens to requests that are already approved?
It reads the live order status in Progeny Clinical each morning, so any request already approved or denied is updated on the tracker and stops appearing as open.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.