Automated Remote Transmission Tracking
Every morning, WebRun opens Octagos, reads each enrolled patient's scheduled remote-transmission cadence, works out who is due this week and who is already overdue, logs a due-and-overdue list to Google Sheets, and posts your monitoring coordinator a Slack digest so every patient stays on their remote schedule.
How do I track which patients are due for a remote CIED transmission?
WebRun reads each patient's remote-monitoring schedule in Octagos every morning and compares it against their last received transmission. It logs a due-and-overdue list to Google Sheets, sorted with the most overdue first, and posts your coordinator a Slack digest of the counts, so every patient stays inside their monitoring cadence.
- Overdue patients surface every morning before they drift off schedule
- The coordinator sees due and overdue counts in Slack within seconds
- A patient who slips repeatedly stands out in the running tracker
Built for remote monitoring coordinators · device clinics · cardiac electrophysiology practices · allied professionals
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 - read remote-transmission schedules
- Open Octagos and go to the remote-monitoring roster
- Read each patient's scheduled transmission cadence and the date of their last received transmission
- Work out who is due within the next seven days and who is already past their scheduled date
- Capture the patient initials, device manufacturer, last transmission date, and next due date
Done when Every enrolled patient is classified as on schedule, due soon, or overdue with their dates.
-
2
Google Sheets - build the due and overdue list
google.com
WebRun opens Google Sheets to build the due and overdue list. - Open the Remote Transmission Tracker sheet
- Append or update one row per patient with last transmission date, next due date, and status
- Sort so overdue patients sit at the top, then those due this week
- Keep prior days so a patient slipping repeatedly stands out
Done when The tracker lists every patient by status with their last and next transmission dates.
-
3
Slack - post the coordinator digest
slack.com
WebRun opens Slack to post the remote-transmission digest to the coordinator. - Post a morning digest to the monitoring Slack channel with counts of overdue and due-this-week patients
- List the most overdue patients first by initials and device
- Link the full Google Sheet for the coordinator to work through
Done when The coordinator has a Slack digest of overdue and due-soon counts linked to the tracker.
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 contact patients who are overdue?
No. WebRun only builds an internal tracker and posts a Slack digest for your coordinator. Any reminder or outreach to an overdue patient is drafted and sent by your team, never by WebRun on its own.
How does it decide a patient is overdue?
It compares each patient's scheduled transmission cadence in Octagos against the date of their last received transmission, so anyone past their next due date is marked overdue and sorted to the top of the list.
Does patient information leave Octagos?
The tracker and Slack digest reference patients by initials and device manufacturer only, so no protected health information beyond those initials appears in the internal list.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.