Automated Endoscope Reprocessing Gap Alerts
Every morning, WebRun opens EndoManager and ScopeCycle, reviews the reprocessing and storage log for every endoscope, flags any scope past its maximum hang time or with a skipped disinfection step, and posts a Slack alert so the team quarantines it before the first procedure.
How do I automatically flag endoscopes past their reprocessing hang time before use?
WebRun reviews endoscope reprocessing every morning. It reads each scope's cycle and storage time in EndoManager and ScopeCycle, flags any scope past its hang-time limit or missing a disinfection step, and posts a Slack alert ordered by the first cases, so at-risk scopes are quarantined and requalified before a patient is exposed.
- No scope past its hang time reaches a patient because the log is reviewed every morning
- Reprocessing exceptions surface in Slack within seconds of the daily run
- Skipped disinfection steps are caught before the first case, not during an audit
Built for endoscopy centers · GI reprocessing technicians · ambulatory surgery centers · infection preventionists
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
newcura.comin a real browser with your saved login - no setup, no API keys. -
1
EndoManager - list scopes used and their exam records
newcura.com
WebRun opens EndoManager to list scopes in rotation. - Open EndoManager and pull the list of endoscopes tied to yesterday's and today's exams
- Capture each scope serial number, last procedure, and the assigned reprocessing tech
- Note which scopes are scheduled for the first cases today
Done when Every scope in active rotation is listed with its recent exam and reprocessing owner.
-
2
ScopeCycle - check reprocessing and storage cycles
WebRun opens ScopeCycle to check reprocessing cycles. - Open ScopeCycle and read the reprocessing cycle and storage time for each scope
- Flag any scope past its maximum hang time or shelf-life limit
- Flag any scope with a skipped or failed high-level disinfection step, or a missing leak test
Done when Every scope past hang time or with an incomplete reprocessing cycle is flagged.
-
3
Slack - alert the team to quarantine at-risk scopes
slack.com
WebRun posts the quarantine alert to Slack. - Post a short alert to the endoscopy operations channel listing each at-risk scope and why it is flagged
- Put scopes assigned to the first cases at the top so they are addressed before the room turns over
- State clearly that flagged scopes should be quarantined and requalified, never used until cleared
Done when The team has a Slack list of scopes to quarantine and requalify before use.
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 change scope status or take a scope out of service on its own?
No. WebRun only reads the reprocessing log and posts an internal alert. Quarantining a scope, requalifying it, and updating its status stay with your reprocessing staff after they review the list.
What counts as a reprocessing gap?
A scope past its maximum hang time or shelf-life limit, or one with a skipped high-level disinfection step, a missing leak test, or an incomplete cycle in ScopeCycle. You set the hang-time thresholds.
How is this different from ScopeCycle's own tracking?
ScopeCycle records each cycle. WebRun reads that log every morning next to the day's case assignments and pushes the exceptions to Slack, so nobody has to open the system to notice a scope is due for requalification.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.