Automated LongevityEHR Wearable Anomaly Alerts
Every morning, WebRun opens LongevityEHR, reads each member's latest wearable data, compares resting heart rate, HRV, and sleep metrics against that member's normal range, logs every anomaly to a Google Sheets tracker, and sends your clinical team an urgent Telegram alert so a concerning reading gets a same day look.
How do I get alerted when a member's wearable data looks abnormal?
Every morning, WebRun opens LongevityEHR and checks each member's overnight wearable data, comparing resting heart rate, HRV, and sleep score against their own 30 day baseline. Any meaningful deviation is logged to Google Sheets and sent as an urgent Telegram alert to your clinical team, so a concerning reading gets a same day look instead of waiting for the next visit.
- Concerning wearable readings get a same day look instead of waiting for the next visit
- Every alert is compared against the member's own baseline, not a generic threshold
- New anomalies are distinguished from ones still open, so patterns are easy to spot
Built for longevity clinics · concierge medicine practices · remote patient monitoring teams · clinical directors
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
app.longevityehr.comin a real browser with your saved login - no setup, no API keys. -
1
LongevityEHR - check wearable data against each member's normal range
longevityehr.com
WebRun opens LongevityEHR to check wearable data against each member's normal range. - Open LongevityEHR and pull each active member's wearable data synced overnight
- Compare resting heart rate, HRV, and sleep score against that member's own 30 day baseline
- Flag any reading that falls outside the member's normal range by a meaningful margin
Done when Every member's overnight wearable data has been checked against their baseline.
-
2
Google Sheets - log every flagged anomaly
google.com
WebRun opens Google Sheets to log every flagged anomaly. - Open the wearable anomaly tracker
- Append a row for each flagged member with the metric, their baseline, and today's reading
- Mark whether this is a new anomaly or one still open from a prior day
Done when The tracker reflects every flagged anomaly from today's sync.
-
3
Telegram - alert the clinical team
telegram.org
WebRun opens Telegram to alert the clinical team. - Send an alert to the clinical team channel listing today's flagged members
- Lead with the most significant deviations from baseline
- Note that this is a data flag only and does not replace a clinician's judgment
Done when Your clinical team has today's wearable anomaly alert in Telegram.
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 this alert the member directly if something looks off?
No. The alert goes only to your internal clinical team in Telegram. A clinician decides whether and how to reach out to the member. WebRun never contacts a member about a wearable reading on its own.
What counts as an anomaly?
A reading, such as resting heart rate, HRV, or sleep score, that falls meaningfully outside that specific member's own 30 day baseline, not a fixed threshold applied to everyone.
Can it tell the difference between a one off bad night and a real trend?
It flags every deviation as it happens and marks whether the anomaly is new or still open from a prior day, so your team can see at a glance whether it is a one time blip or a pattern.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.