All templates

Automated Lab Results Routing for Birth Centers

Whenever a new lab result is logged in Maternity Neighborhood, WebRun identifies the assigned midwife for that client chart, posts a routing alert to the care team Slack channel with the result type and urgency tier, and logs the pending review in a Google Sheet so nothing is missed during a busy shift.

Runs on WebRun · Strict Lockdown policy
Whenever a new lab result is received in Maternity Neighborhood WebRunorchestrates each step
1 Maternity Neighborhood detect new lab result and identify assigned midwife
2 Slack post routing alert to care team
3 Google Sheets log result in pending review tracker
In short

How can I automatically route lab results to the right midwife at my birth center?

When a lab result arrives in Maternity Neighborhood, WebRun identifies the assigned midwife, classifies the result by type and urgency, and posts a routing alert to Slack within minutes. Critical results trigger an @-mention. Every result is logged in a Google Sheet pending tracker with a 4-hour follow-up flag. No PHI is included in any external message.

  • Every incoming lab result reaches the assigned midwife in Slack within minutes of arrival
  • Critical and abnormal results trigger an urgent @-mention so nothing is missed during a busy shift
  • 4-hour follow-up flag ensures no result sits unreviewed, even when the assigned midwife is on call

Built for birth centers · midwifery practices · care coordinators · freestanding birth centers

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 app.maternityneighborhood.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Maternity Neighborhood - detect new lab result and identify assigned midwife
    maternityneighborhood.com
    WebRun in Maternity Neighborhood: detect new lab result and identify assigned midwife
    WebRun opens Maternity Neighborhood to detect new lab result and identify assigned midwife.
    • Monitor Maternity Neighborhood for newly received lab results
    • When a result arrives, identify the client chart and the assigned midwife
    • Classify the result type (CBC, GBS, glucose, GDM screen, thyroid, anatomy scan, etc.) and flag any result marked critical or abnormal

    Done when The incoming result is matched to its assigned midwife and classified by type and urgency.

  3. 2
    Slack - post routing alert to care team
    slack.com
    WebRun in Slack: post routing alert to care team
    WebRun opens Slack to post routing alert to care team.
    • Post a routing alert to the care team Slack channel naming the assigned midwife and result type
    • For critical or abnormal results, use an urgent flag and @-mention the assigned midwife
    • Do not include client name, record ID, or result value in the Slack message. Use result type and urgency tier only

    Done when The assigned midwife has a Slack routing alert with result type and urgency, without PHI.

  4. 3
    Google Sheets - log result in pending review tracker
    google.com
    WebRun in Google Sheets: log result in pending review tracker
    WebRun opens Google Sheets to log result in pending review tracker.
    • Append the result to the pending review tracker Google Sheet with result type, urgency tier, assigned midwife, and a review-status field
    • Mark the row as pending until the midwife confirms review in Maternity Neighborhood
    • Flag rows that remain unreviewed for more than 4 hours with a follow-up alert

    Done when The result is logged in the pending tracker with its routing status and urgency visible.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.maternityneighborhood.com
ScheduleRuns automatically on this cadence
Whenever a new lab result is received in Maternity Neighborhood
DeliveryHow each run's result reaches you
Lab routing alert · Slack
OutputWhat each run produces - Real-time Slack routing alerts for incoming lab results by type and urgency, plus a Google Sheet pending review tracker with a 4-hour follow-up flag.
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

Does the Slack alert include the lab result value or patient name?

No. The Slack alert contains only the result type (for example, GBS screen) and urgency tier, never the result value, client name, or any PHI. All clinical detail stays inside Maternity Neighborhood.

What happens if the assigned midwife does not acknowledge the result within 4 hours?

WebRun posts a follow-up alert to the care team Slack channel and flags the row in the Google Sheet tracker so a colleague or the practice manager can ensure the result is reviewed.

Which lab result types does it classify as critical or urgent?

By default, results flagged as critical or abnormal in Maternity Neighborhood trigger an urgent Slack alert with an @-mention. You can configure additional result types to trigger urgent routing during setup.

Put this on autopilot.

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