Automated Donor Density Change Tracking
Every morning, WebRun opens TrichoSuite, reads each patient's most recent donor-zone density measurement, compares it to their previous scans, logs the change to a Google Sheet, and posts a Slack flag when a donor area shows a meaningful density drop that a clinician should review.
How do I track donor-zone density changes between scans automatically?
Every morning WebRun reads each patient's newest donor-zone density scan in TrichoSuite, compares it to their earlier scans, and logs the change and percentage to a Google Sheet. When a donor area drops past your threshold, it posts a Slack flag with the values for a clinician to review, so donor decline is caught early.
- Donor density decline is caught between scans, not at the next surgery
- Every patient's density trend is logged with a percentage change
- Clinicians are flagged only when a drop crosses your threshold
Built for hair transplant surgeons · trichologists · hair restoration clinics · clinical teams
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
trichosuite.com/en-USin a real browser with your saved login - no setup, no API keys. -
1
TrichoSuite - read donor density scans
trichosuite.com
WebRun opens TrichoSuite to read donor density scans. - Open TrichoSuite and find patients with a new donor-zone density scan since the last run
- Read the donor density measurement and follicle count for the latest scan
- Pull the prior donor density value for the same zone for comparison
Done when Each patient with a new scan has a current and prior donor density value.
-
2
Google Sheets - log the density change
google.com
WebRun opens Google Sheets to log the density change. - Open the Donor Density Trend sheet
- Append a row per patient with scan date, current density, prior density, and the change
- Calculate the percentage change and mark direction as stable, up, or down
- Update rather than duplicate a patient already logged for this scan date
Done when The trend sheet reflects today's density changes with percentage and direction.
-
3
Slack - flag meaningful drops
slack.com
WebRun opens Slack to flag meaningful drops. - Post a Slack flag to the clinical channel for any patient whose donor density dropped past your threshold
- Include patient initials, the current and prior values, and the percentage change
- Link to the trend sheet so a clinician can review the full history
Done when Clinicians have a Slack flag for every meaningful donor density drop.
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 share patient identities outside the clinic?
No. The Slack flags and trend sheet use patient initials only and stay inside your private clinic workspace. No identifying donor scan detail leaves the clinic.
What counts as a meaningful density drop?
You set the threshold, for example a percentage decline in donor density between scans. Only patients whose change crosses that threshold are flagged, so clinicians are not alerted on normal variation.
Does it contact the patient about the change?
No. This workflow only logs the trend and flags clinicians internally. Any decision to contact the patient or adjust their plan is left entirely to your clinical team.
Related templates
Instagram›Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.