Operator Worklist

Vorian Connect aggregates every lab exception that requires operator attention — message verification flags, delivery failures, unmapped instrument results, delta check flags, QC violations, and preanalytical alerts — into a single unified worklist. Operators can filter by exception type, search by specimen or accession, and resolve items directly from the queue.

How It Works

What's Included

Where It Fits

The operator worklist is the single-pane exception queue for lab operations. Instead of checking five different dashboards to find out what needs attention, a lab tech opens one page and sees every outstanding issue grouped by severity and type. Messages that failed auto-verification appear alongside delivery failures, unmapped instrument codes, delta check flags, and QC violations — all in one sortable, filterable view.

The worklist is designed for high-volume labs: results are capped and paginated at 150 items, all date-limited to the last 30 days, and the combined query structure avoids N+1 database round-trips. Each exception category is queried independently but merged and sorted by timestamp server-side before the response is returned.

Technical Details (for evaluators)

The worklist API is a single GET endpoint with query parameters for type (one of six enum values: message_exception, delivery_failure, unmapped_result, delta_check, qc_violation, preanalytical_alert), source (UUID), q (search term, max 120 chars), and limit (bounded 1–200, default 100). The search term is processed through the PHI HMAC function for patient lookup but falls back to direct LIKE matching against specimen IDs and message IDs when HMAC configuration is unavailable — patient-level search degrades gracefully rather than breaking entirely.

The endpoint runs all applicable category queries in sequence within a single tenant-scoped database session (via withTenant) and merges results before sorting by timestamp and slicing to the requested limit. Routing stage timeouts are included in preanalytical alerts with separate queries that surface overdue staged orders and timed-out transit SLAs. Each query includes source-scope filtering when the user has restricted instrument access, and category-level permission checks prevent unauthorized users from seeing exception types they should not access — even if they craft the query parameter manually.

Last updated: May 22, 2026