Automated Garment Prior Auth Tracking
Every morning, WebRun opens LymphaTech to list garment orders that need prior authorization, updates a Google Sheet with each request's payer, status, and expiry date, and posts your billing team a Slack digest of authorizations still pending, newly approved, or expiring soon so nothing lapses before a garment is dispensed.
How do I track compression garment prior authorizations automatically?
WebRun lists garment orders needing prior authorization in LymphaTech each morning, updates a Google Sheet with each request's payer, status, and expiry, and posts your billing team a Slack digest grouped by expiring soon, pending, and approved. Submitting to the payer stays with your team, so no garment authorization lapses unnoticed and nothing is filed automatically.
- Authorizations about to expire are flagged before a garment lapses
- Approved requests are called out so orders move without delay
- Billing works one tracked list instead of chasing each payer portal
Built for medical billing teams · lymphedema clinics · authorization specialists · durable medical equipment providers
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.lymphatech.comin a real browser with your saved login - no setup, no API keys. -
1
LymphaTech - list orders needing authorization
lymphatech.com
WebRun lists garment orders that still need a prior authorization. - Open LymphaTech and list garment orders that require a prior authorization
- Note the patient, garment, prescribing clinician, and payer for each
- Flag any order that is ready to build but is still waiting on authorization
Done when Every garment order needing prior authorization is identified with its payer and patient.
-
2
Google Sheets - update each authorization's status and expiry
google.com
WebRun updates each authorization's status and expiry in Google Sheets. - Open the prior authorization tracker in Google Sheets
- Add or update a row per order with payer, submission date, current status, and expiry date
- Mark each as pending, approved, denied, or expiring within your alert window
- Do not add a second row for an order already in the tracker; update the existing one instead
Done when Every tracked authorization has a current status and expiry in the sheet.
-
3
Slack - post the authorization status digest
slack.com
WebRun posts billing a grouped digest of authorization statuses. - Post an authorization digest to the billing team's Slack channel
- Group by expiring soon, still pending, and newly approved and ready to order
- Put authorizations expiring within your window first so the team can act before they lapse
- Keep the digest internal. WebRun does not submit or resubmit anything to the payer on its own.
Done when The billing team has today's grouped authorization digest in Slack.
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
Does it submit prior authorizations to the payer?
No. WebRun tracks the status of each authorization and posts an internal Slack digest. Submitting or resubmitting to the payer stays with your billing team, so no filing happens without a person handling it.
How does it warn about authorizations that are about to expire?
It reads each authorization's expiry date in the tracker and flags any inside your alert window, for example the next 14 days, grouping them at the top of the digest so the garment is dispensed before it lapses.
Where does the authorization data live?
In your own Google Sheet tracker, updated each run. Nothing is shared outside your practice, and the Slack digest goes only to your internal billing channel.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.