Keep your price transparency file audit-ready
Every Monday, WebRun opens Craneware, compares live chargemaster pricing against your last published price transparency file, stages a refresh checklist in Google Sheets, and drafts a compliance sign-off request in Outlook before anything gets republished.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I keep my price transparency file current without missing a refresh?
WebRun checks weekly whether the pricing behind your public price transparency file has drifted from what's live in Craneware, stages a refresh checklist in Google Sheets, and drafts a compliance sign-off request in Outlook. It never republishes the public file itself, so nothing goes live on your website until compliance has reviewed and approved the change.
- Pricing drift behind the public file gets caught weekly, not at the next compliance deadline
- Every refresh goes through a compliance sign-off before it's published
- A running staleness tracker means no refresh cycle gets missed by accident
Built for compliance officers · hospital finance teams · revenue integrity teams · chargemaster coordinators
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 - check pricing behind the file for drift
craneware.com How to Automate Craneware
WebRun opens Craneware to check pricing behind the file for drift. - Open Craneware and compare the current chargemaster pricing against what's reflected in the last published price transparency file
- Capture every item whose live price has drifted from the published file beyond a small tolerance
- Note how long it's been since the file was last refreshed
Done when Every item with pricing drift is listed alongside how stale the current published file is.
-
2
Google Sheets - stage the refresh checklist
google.com How to Automate Google Sheets
WebRun opens Google Sheets to stage the refresh checklist. - Log the drifted items and the days since last refresh into the compliance tracker
- Mark the file as due for refresh once drift or staleness crosses your threshold
- Carry the tracker forward week to week so refresh history stays in one place
Done when The tracker shows the file's current staleness and every item driving the refresh.
-
3
Outlook - request compliance sign-off
microsoft.com How to Automate Outlook
WebRun opens Outlook to request compliance sign-off. - Draft an email to compliance and finance requesting their sign-off on the refreshed file
- Attach the summary of what changed since the last publish
- Leave the draft unsent. WebRun never republishes the public file itself, compliance signs off and your team publishes it
Done when A sign-off request is waiting in Outlook before the file is republished.
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 publish the updated file to your website on its own?
No. WebRun only stages the refresh checklist and drafts a compliance sign-off request in Outlook. Publishing the public file is always a deliberate step your compliance team takes after reviewing it.
How does it decide the file is stale?
By comparing live chargemaster pricing in Craneware against what the last published file shows, and by tracking how long it's been since the last refresh, both against thresholds you set.
What if nothing has drifted this week?
Nothing goes out. The tracker simply shows no items due, and no sign-off request is drafted that week.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.