Notifications & Alerting

Vorian Connect monitors lab operations continuously and delivers email and SMS alerts when attention is needed — offline instruments, unmapped result backlogs, preanalytical specimen conditions, and QC violations. Per-tenant settings let each lab control which alerts fire, at what severity, and who receives them.

How It Works

What's Included

Where It Fits

The notifier is a background operational service that bridges automated monitoring and human attention. It complements the Observability dashboard — observability is for active scanning, notifications are for passive awareness. When a lab team is not watching the dashboard, the notifier ensures they still know when something needs attention.

Alert settings are managed through the Team administration surface, where site administrators configure which alert types are active for their lab, who receives them, and at what severity threshold. The notifier worker runs as a separate process alongside the gateway and reprocessor, sharing the same PostgreSQL database for tenant-scoped alert state.

Technical Details (for evaluators)

The notifier worker (package notifier) uses a polling loop with configurable interval (NOTIFIER_POLL_SECONDS, default 60s). Each poll cycle runs three processors: offline instrument enqueue, unmapped threshold checks, preanalytical delivery, and generic alert delivery. Processors use FOR UPDATE SKIP LOCKED to safely handle concurrent notifier instances without duplicate delivery.

Email delivery uses Go's net/smtp with STARTTLS support (configurable via SMTP_REQUIRE_STARTTLS). SMS delivery uses the Twilio REST API (POST /2010-04-01/Accounts/{sid}/Messages.json) with HTTP Basic authentication. SMS recipients are validated as E.164 format (+1XXXXXXXXXX) before delivery is attempted. Both channels are guarded by feature flags — if SMTP credentials or Twilio credentials are missing, the channel is silently disabled.

Alert deduplication uses a dedupe_key column (e.g., offline_instrument:{source_id}) combined with the throttle window to prevent repeat notifications. The throttle is enforced at enqueue time — the INSERT checks for an existing notification with the same dedupe key within the throttle interval and skips if one exists.

Delivery idempotency is handled through the alert_notification_deliveries table with a composite unique constraint on (notification_table, notification_id, channel, recipient). Before sending to a recipient, the worker checks whether a successful delivery already exists for that combination and skips if so.

Last updated: July 19, 2026