All templates

nAble Witness Automated Exception Escalation

Every few minutes during lab hours, WebRun reads the nAble Witness scanning log in nAbleIVF, finds any barcode mismatch, manual override, or skipped witnessing step, posts the exception to the lab Slack channel, and drafts an on-call text to the lab lead for review so a failed double-check is caught before the next step.

Runs on WebRun · Strict Lockdown policy
Every 10 minutes during lab hours WebRunorchestrates each step
1 nAbleIVF read the nAble Witness scan log
2 Slack post the witnessing exception
3 Twilio draft an on-call escalation text
In short

How do I automatically escalate failed IVF witnessing scans to the lab lead?

WebRun reads the nAble Witness scan log in nAbleIVF every few minutes and catches any barcode mismatch, override, or skipped witnessing step. It posts the exception to your lab Slack channel at once and drafts an on-call text to the lab lead for a supervisor to send, so a failed double-check is escalated before the procedure moves on.

  • A failed double-check reaches the lab lead in minutes, not at shift end
  • Every witnessing exception lands in Slack with its procedure and workstation
  • On-call texts are supervisor-approved before they send

Built for IVF embryology labs · lab quality leads · fertility clinic directors · reproductive lab witnessing teams

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.nableivf.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    nAbleIVF - read the nAble Witness scan log
    nableivf.com
    WebRun in nAbleIVF: read the nAble Witness scan log
    WebRun opens nAbleIVF to read the nAble Witness scan log.
    • Open nAbleIVF and read the nAble Witness scanning and witnessing log
    • Find any barcode mismatch, an overridden or bypassed double-check, or a required witnessing step marked skipped
    • Capture the procedure, the two specimen or patient identifiers involved, the workstation, and the timestamp
    • Ignore exceptions already escalated on an earlier run

    Done when Every new witnessing exception since the last run is captured with its procedure and identifiers.

  3. 2
    Slack - post the witnessing exception
    slack.com
    WebRun in Slack: post the witnessing exception
    WebRun opens Slack to post the witnessing exception.
    • Post each new exception to the lab Slack channel with the procedure, workstation, and time
    • Mark whether it was a mismatch, an override, or a skipped step
    • @-mention the on-shift embryologist so it is seen at the bench right away

    Done when Every new witnessing exception is posted in Slack with its details.

  4. 3
    Twilio - draft an on-call escalation text
    twilio.com
    WebRun in Twilio: draft an on-call escalation text
    WebRun opens Twilio to draft an on-call escalation text.
    • For a mismatch or an overridden double-check, draft a short on-call escalation text to the lab lead, do not send it yet
    • Include only the procedure, workstation, and time, with no patient name or clinical detail
    • Leave the text queued for a supervisor to review and send, so a human decides on every escalation

    Done when An on-call escalation text is drafted and queued for supervisor approval for each high-severity exception.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.nableivf.com
ScheduleRuns automatically on this cadence
Every 10 minutes during lab hours
DeliveryHow each run's result reaches you
Witnessing exceptions · Slack
OutputWhat each run produces - A Slack post for every witnessing exception plus a drafted on-call text for each mismatch or override, queued for a supervisor to send.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it text the on-call lead without anyone approving it?

No. For a mismatch or override, WebRun drafts the on-call text and queues it for a supervisor to review and send. The Slack post is instant and internal, but the outbound text is a human decision, so no escalation leaves the building on its own.

Does the alert include patient names or clinical detail?

No. The escalation carries only the procedure, workstation, and timestamp, never a patient name or diagnosis. Full identifiers stay inside nAbleIVF and Slack, keeping protected health information off the outbound text.

What witnessing events count as an exception?

A barcode mismatch between two scanned specimens, a double-check that was overridden or bypassed, or a required witnessing step marked skipped. You set which severities page the on-call lead, so routine notes stay in Slack and only true failures escalate.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.