Automated Battery ERI Replacement Recall
Every morning, WebRun opens Octagos, finds devices that have reached elective replacement indicator or recommended replacement time on their latest transmission, drafts a generator-replacement recall email in Outlook for each patient, and posts your clinician a ranked Slack list so a battery nearing end of service is always acted on quickly.
How do I catch devices reaching battery ERI and recall them for replacement?
WebRun scans Octagos every morning and flags devices whose latest transmission reports elective replacement indicator or recommended replacement time. It drafts a generator-replacement recall email in Outlook for each patient, left unsent, and posts your clinician a ranked Slack list by battery status, so a depleting device is always reviewed and recalled quickly.
- Devices reaching ERI or RRT surface every morning, not at the next visit
- A recall email is ready for each patient without a clinician writing it
- Nothing is sent to a patient until a clinician reviews and approves it
Built for device clinics · cardiac electrophysiology practices · remote monitoring coordinators · electrophysiologists
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 - find devices at battery ERI
- Open Octagos and review the latest transmission for each monitored device
- Flag devices reporting elective replacement indicator, recommended replacement time, or a battery status at end of service
- Capture the patient initials, device manufacturer, model, and the battery status reported
- Skip devices where a replacement is already scheduled or logged
Done when Every device at ERI or RRT is listed with its battery status and device details.
-
2
Outlook - draft the replacement recall
outlook.com
WebRun opens Outlook to draft the replacement-recall email for review. - Draft a generator-replacement recall email for each affected patient, asking them to call the clinic to arrange evaluation
- Keep the message a general recall to book an appointment, with no device readings or clinical detail
- Save every email as a draft in a review folder and send nothing automatically
Done when A replacement-recall email is drafted and left unsent for every patient at ERI or RRT.
-
3
Slack - post the clinician list
slack.com
WebRun opens Slack to post the clinician list of depleting devices. - Post a ranked list to the clinician Slack channel of devices at ERI or RRT, most depleted first
- Show each patient by initials with the device and battery status
- Note that recall emails are drafted and awaiting review before anything is sent
Done when The clinician has a Slack list of devices at ERI or RRT with the drafted recalls noted.
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 email patients about replacement without me?
No. WebRun drafts each generator-replacement recall in Outlook and leaves it unsent. A clinician reviews the list and the wording, then sends each recall, so no patient is contacted about a battery status automatically.
Does the recall email share device readings?
No. Each draft is a general recall asking the patient to call the clinic to book an appointment, with no battery voltage, readings, or clinical detail, so it carries no protected health information beyond the greeting.
How does it know a device reached ERI?
It reads the battery status on each device's latest transmission in Octagos, so only devices reporting elective replacement indicator, recommended replacement time, or end of service are placed on the recall list.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.