Automated CIED Billing Interval Check
Every morning, WebRun opens Octagos, reviews each patient's remote-monitoring interval and last billed date, flags the 90-day technical intervals that have completed and are now eligible to bill, logs a ready-to-bill worklist to Google Sheets, and posts your billing team a Slack digest so every reimbursable interval is captured on time.
How do I make sure every eligible CIED monitoring interval gets billed?
WebRun reviews each patient's remote-monitoring interval in Octagos every morning and flags the 90-day windows that have completed since the last billed interval and carry a received transmission. It logs a ready-to-bill worklist to Google Sheets with codes and dates, then posts billing a Slack digest of counts and expected reimbursement, so no eligible interval is missed.
- Every completed 90-day interval is captured the day it becomes eligible
- Billing sees eligible counts and expected reimbursement in Slack each morning
- Intervals near their filing deadline are worked first from a ranked list
Built for device clinic billers · cardiac electrophysiology practices · revenue cycle managers · remote monitoring 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.octagos.comin a real browser with your saved login - no setup, no API keys. -
1
Octagos - check monitoring intervals
- Open Octagos and review the remote-monitoring roster with each patient's interval start and last billed date
- Identify patients whose 90-day remote technical interval has completed since their last billed interval
- Confirm at least one transmission was received in the interval so it supports a claim
- Capture the patient initials, device manufacturer, interval dates, and the applicable interval code
Done when Every completed 90-day interval eligible to bill is listed with its dates and code.
-
2
Google Sheets - build the eligible-to-bill worklist
WebRun opens Google Sheets to build the eligible-to-bill worklist. - Open the Remote Billing Eligibility sheet
- Append one row per eligible interval with the interval dates, code, and device manufacturer
- Skip intervals already marked billed so nothing is double-listed
- Mark intervals close to the end of their filing window so they are worked first
Done when The worklist lists every eligible interval with its dates, code, and filing urgency.
-
3
Slack - post the billing digest
WebRun opens Slack to post the eligible-to-bill digest to billing. - Post a morning digest to the billing Slack channel with the count of intervals now eligible to bill
- Show the total expected reimbursement and flag any nearing the end of their filing window
- Link the full Google Sheet and leave all claim submission to the billing team
Done when Billing has a Slack digest of eligible intervals, expected reimbursement, and the worklist link.
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 submit claims automatically?
No. WebRun only identifies which intervals are eligible to bill and posts an internal worklist. Your billing team reviews the Google Sheet and submits every claim in your billing system, so nothing is filed without a human.
How does it know an interval is eligible?
It checks that a full 90-day remote technical interval has completed since the last billed interval and that at least one transmission was received in that window, so only intervals that support a claim are listed.
How does it avoid double billing an interval?
It skips any interval already marked billed and reads the last billed date in Octagos each morning, so a completed interval appears on the worklist once and drops off after it is billed.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.