Automated Craneware Daily Charge Lag Digest
Every morning, WebRun opens Craneware, calculates yesterday's average charge lag for every department against its own 30-day baseline, and posts your revenue integrity team a ranked Slack digest with the worst-slipping departments at the top.
How do I track charge lag by department every day?
WebRun measures how long it takes each department's charges to post after service in Craneware, comparing yesterday's average lag against that department's own recent baseline. Every morning it posts your revenue integrity team a ranked Slack digest, worst department first, so a worsening trend gets noticed within a day instead of showing up at month-end.
- Worsening charge lag surfaces within a day instead of at month-end close
- Every department is measured against its own baseline, not one blanket target
- The channel stays focused on outliers, not a wall of routine numbers
Built for revenue integrity teams · department charge coordinators · health system revenue cycle directors · HIM leadership
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 - measure charge lag by department
craneware.com
WebRun opens Craneware to measure charge lag by department. - Open Craneware and pull yesterday's charges with their service date and post date
- Calculate the lag in days between service and posting for each department
- Compare each department's average lag to its 30-day baseline
Done when Every department has yesterday's average charge lag calculated against its baseline.
-
2
Slack - post the ranked digest
slack.com
WebRun opens Slack to post the ranked digest. - Post the revenue integrity channel a ranked digest of department charge lag, worst first
- Call out any department whose lag jumped meaningfully above its baseline
- Include yesterday's system-wide average for context
Done when The team has this morning's charge lag digest ranked by department.
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
What counts as charge lag?
The number of days between when a service was rendered and when its charge posted in Craneware. It's calculated per department and compared to that department's own 30-day baseline, not a single hospital-wide number.
Does it flag individual charges or just departments?
Departments. It's built to show you where the trend is worsening so you know where to look, not to replace a detailed missing-charge worklist.
Can it alert on a threshold instead of every day?
Yes. The daily digest is the default, but you can set a threshold instead, so the channel only posts when a department's lag actually crosses a limit you choose.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.