Automated T-Score Trend Reporting
Every morning, WebRun pulls each patient's full DXA scan history from Hologic Horizon DXA, cross-checks the chart in athenahealth for treatment changes between scans, builds a T-score trend line across every visit, and drafts a plain language summary email in Gmail for the referring physician to review and send.
How do I generate a T-score trend report across a patient's DXA scans?
WebRun pulls each patient's full scan history from Hologic Horizon DXA every morning, cross-checks athenahealth for treatment changes between visits, and builds a T-score trend line with the percent change since baseline. It drafts a plain language physician summary in Gmail, left unsent for your clinician to review and send.
- Multi-year scan history becomes one trend line instead of scattered reports
- Every T-score change is matched to a treatment reason before the physician sees it
- New baselines are logged automatically for patients on their first scan
Built for bone health clinics · endocrinologists · DXA technologists · primary care referral partners
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.hologic.comin a real browser with your saved login - no setup, no API keys. -
1
Hologic Horizon DXA - pull full scan history
hologic.com
WebRun opens Hologic Horizon DXA to pull full scan history. - Open Hologic Horizon DXA and pull every scan on file for each patient due for a trend review
- Capture the hip and spine T-score and the scan date for each visit
- Calculate the percent change in T-score between the most recent 2 scans and since baseline
Done when Every patient's full scan history is captured with T-scores and calculated change.
-
2
athenahealth - cross-check treatment changes
athenahealth.com
WebRun opens athenahealth to cross-check treatment changes. - Open athenahealth and check the medication and treatment record between each pair of scans
- Note any treatment start, stop, or switch that could explain a change in T-score
- Flag any declining trend with no treatment change noted for closer review
Done when Every T-score change is matched against the treatment record for context.
-
3
Gmail - draft the physician summary
gmail.com
WebRun opens Gmail to draft the physician summary. - Draft a plain language trend summary for the referring physician of each patient reviewed
- Include the T-score trend line, the treatment context, and whether the trend supports continuing or adjusting therapy
- Leave every draft unsent in Gmail for your clinician to review, edit, and send
Done when A drafted trend summary is waiting for clinician review for every patient due this cycle.
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 send the trend report to the referring physician automatically?
No. WebRun drafts the summary in Gmail and leaves it unsent. Your clinician reviews, edits, and sends every report to the referring physician.
How does it explain a change in T-score?
It cross-checks the treatment record in athenahealth between each pair of scans, so a change is matched against any medication start, stop, or switch rather than reported without context.
What if a patient has only had one scan?
It notes that a trend cannot be calculated yet and logs the single T-score as the new baseline for the next scan to compare against.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.