Automated Craneware Missing-Charge Report
Every morning, WebRun opens Craneware, pulls every encounter flagged for a missing charge in the last 24 hours, logs the account, department, and dollar amount at risk into a Google Sheet, and posts your revenue integrity team a ranked Slack summary so nothing slips past bill drop.
How do I catch missing charges before a claim goes out?
WebRun checks Craneware every morning for encounters flagged with missing charges, logs each one into a Google Sheet with the department and dollar impact, and posts your revenue integrity team a ranked Slack summary. It never posts a charge itself, so your team catches and fixes gaps before the claim goes out, not after.
- Missing charges get caught before claims go out, not after a denial
- Revenue integrity leads open Slack to a ranked dollar-impact list every morning
- Unresolved items carry forward automatically so nothing falls off the list
Built for hospital revenue integrity teams · charge capture analysts · patient financial services · HIM coding compliance
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
www.craneware.comin a real browser with your saved login - no setup, no API keys. -
1
Craneware - find encounters with missing charges
craneware.com
WebRun opens Craneware to find encounters with missing charges. - Open Craneware and filter the charge integrity worklist to encounters flagged in the last 24 hours
- Capture the account number, department, service date, and estimated dollar impact for each
- Sort so the highest-dollar accounts needing a bill hold sit at the top
Done when Every encounter flagged for a missing charge in the last 24 hours is captured with its dollar impact.
-
2
Google Sheets - log the worklist with dollar impact
google.com
WebRun opens Google Sheets to log the worklist with dollar impact. - Log each flagged encounter as a new row in the daily missing-charge tracker
- Mark whether the account is still open or already past bill drop
- Carry forward any prior-day rows still unresolved
Done when The tracker reflects every open missing-charge encounter with its current status.
-
3
Slack - alert the team to what's at risk
slack.com
WebRun opens Slack to alert the team to what's at risk. - Post the revenue integrity channel a ranked summary of today's flagged encounters
- Put the highest-dollar accounts closest to bill drop first
- Leave posting the actual charge to your charge capture team. WebRun only flags, it never adds a charge line itself
Done when The team has today's missing-charge worklist in Slack before bill drop.
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 post the missing charges itself?
No. WebRun only flags likely missing charges and logs them to a worklist with the dollar impact. Your charge capture team reviews and posts every charge themselves, so nothing hits a claim without a human check.
How does it know a charge is missing?
It reads the same charge integrity flags Craneware already raises for the encounter, so it's using signals your team already trusts, just surfaced earlier and ranked by dollar impact.
What happens to items that don't get fixed the same day?
They carry forward into the next day's tracker as still open, so nothing quietly falls off the list before the claim goes out.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.