Automated Tebra Gestational Screening Due Tracker
Every morning, WebRun opens Tebra, finds prenatal patients entering critical gestational screening windows such as first-trimester combined screening, glucose tolerance testing, and GBS culture, checks whether the relevant order is already placed, and posts a due-now digest to Slack for the care team to review and order any outstanding tests.
How can I automatically track which prenatal patients are due for gestational screenings?
WebRun checks Tebra each morning for prenatal patients entering key gestational screening windows and confirms whether the relevant lab or imaging order has been placed. It posts a due-now digest to Slack grouped by screening type so your care team can order outstanding tests before the gestational window closes and guideline adherence is at risk.
- Care team sees every gestational screening due that day in Slack without manual chart review
- Overdue screening windows are flagged immediately so no patient misses a time-sensitive test
- Providers spend less time auditing prenatal charts and more time seeing patients
Built for OBGYN practices · obstetrics clinics · midwifery practices · women's health centers with prenatal care
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.tebra.comin a real browser with your saved login - no setup, no API keys. -
1
Tebra - identify prenatal patients entering screening windows
tebra.com
WebRun opens Tebra to identify prenatal patients entering screening windows. - Open Tebra and calculate each active prenatal patient's current gestational age from their last menstrual period or estimated due date
- Flag patients entering key windows: 10 to 13 weeks (first-trimester screen), 15 to 20 weeks (quad screen / anatomy scan), 24 to 28 weeks (glucose tolerance test), 35 to 37 weeks (GBS culture)
- Check whether the relevant lab or imaging order has already been placed for each flagged patient
- Do not place any orders - flag only for care team review
Done when All prenatal patients in a screening window with no standing order are identified and grouped by screening type.
-
2
Slack - post gestational screening due-now digest
slack.com
WebRun opens Slack to post gestational screening due-now digest. - Post a due-now digest to the clinical team Slack channel grouped by screening type
- List each patient by initials, gestational age range, and the screening test due
- Flag any patient already past the upper boundary of a screening window as Overdue
Done when The care team has today's gestational screening due list in Slack with window urgency and overdue flags.
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 place lab or imaging orders automatically?
No. WebRun identifies which patients need an order placed and posts the list to Slack for a provider or clinical staff to review. All ordering is done by a licensed provider in Tebra to maintain clinical oversight and patient safety.
Which gestational screening windows does it track?
WebRun tracks the four main prenatal screening windows: first-trimester combined screen at 10 to 13 weeks, quad screen or anatomy scan at 15 to 20 weeks, glucose tolerance test at 24 to 28 weeks, and GBS culture at 35 to 37 weeks. Additional windows can be added at setup.
What if a patient declined a recommended screening?
If a declined screening is documented in Tebra as a patient refusal, WebRun will not flag that patient for that test. Staff should document refusals in Tebra so the tracker stays accurate and does not generate unnecessary flags.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.