Automated Dolbey Uncoded Chart Backlog Digest
Every night, WebRun opens Dolbey, counts how many charts are sitting uncoded by service line and by age bucket, logs the totals in Google Sheets, and posts the coding manager a Slack digest showing exactly where the backlog is growing.
How do I track and reduce the uncoded chart backlog?
WebRun keeps your uncoded chart backlog visible before it becomes a crisis. Every night it opens Dolbey, counts charts still waiting to be coded by service line and age, logs the totals in Google Sheets, and posts the coding manager a Slack digest showing exactly where the pile is growing, so staffing decisions happen before the backlog does real damage.
- Coding managers see backlog growth before it becomes a crisis
- Every service line's backlog is tracked by age, night over night
- Staffing decisions get made from real numbers, not gut feel
Built for coding managers · HIM directors · medical coding teams · hospital HIM departments
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.dolbey.comin a real browser with your saved login - no setup, no API keys. -
1
Dolbey - count uncoded charts by age
dolbey.com
WebRun opens Dolbey to count uncoded charts by age. - Open the Dolbey coding worklist and filter to charts not yet coded
- Group the count by service line and by age bucket, 0 to 2, 3 to 5, and 6 plus days
- Note any service line whose backlog grew from the day before
Done when Every uncoded chart is counted and grouped by service line and age.
-
2
Google Sheets - log backlog totals
google.com
WebRun opens Google Sheets to log backlog totals. - Append tonight's counts as a new row on the backlog tracker
- Keep a running column for each service line so trend lines stay intact
- Highlight any service line that grew for two nights running
Done when The backlog tracker shows tonight's totals alongside the trend.
-
3
Slack - digest the backlog to the manager
slack.com
WebRun opens Slack to digest the backlog to the manager. - Post a digest to the coding manager with tonight's totals by service line
- Lead with whichever service line has the oldest or fastest growing pile
- Include the total uncoded count so tomorrow's staffing plan is easy to set
Done when The coding manager has tonight's backlog digest in Slack before morning huddle.
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 the digest name individual patients?
No. It only reports counts by service line and age bucket, never patient names or chart contents, so the digest is safe to share in a team channel.
Will it reassign coders on its own?
No. WebRun only reports where the backlog is growing. Reassigning coders or shifting staffing stays a decision for the coding manager.
How far back does the trend go?
Each night's totals are appended to the same tracker, so the coding manager can see whether a service line's backlog is shrinking or growing over time.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.