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
- The worklist API (
GET /api/worklist) queries across six distinct exception types in a single request: message exceptions (flagged, rejected, or pending verification), delivery failures (failed or retrying outbound deliveries), unmapped results (instrument codes without LOINC mappings), delta checks (failed patient-to-patient comparisons), QC violations (Westgard rule violations from the continuous stats engine), and preanalytical alerts (specimen status issues and routing stage timeouts) - Each exception type is permission-gated — operators see only the categories their role allows.
results:viewgrants message and delivery exceptions;config:mappingsadds unmapped results;qc:viewadds delta and QC entries;preanalytical:viewadds preanalytical alerts - Source-scoped users see only exceptions from instruments they are authorized to access, enforced server-side through the source-scope SQL filter
- Every item carries a severity level (critical, error, warning, info), a direct action link into the relevant resolution surface (Inspector, Trace, QC dashboard, Delta Checks, Unmapped mapper, Preanalytical page), and a human-readable title and detail description
- The
/worklistdashboard page renders all items in a filterable, searchable table with type tabs, source dropdowns, and severity-colored badges
What's Included
- PHI-safe search: Operators can search by message ID (integer), specimen ID (via preanalytical events and active orders), or patient (via HMAC token lookup — raw MRNs are never exposed in results). The search term is processed through the PHI HMAC key and matched against
patient_tokenswithout revealing the underlying MRN - Barcode scanner support: A keyboard-wedge barcode reader integration captures scanned specimen and accession identifiers directly into the search field. Barcode scanning is available on
/worklist,/addon, and/storagepages - Type filtering: Six filter tabs match the six exception types. Operators can focus on one category (e.g., only QC violations) or view all simultaneously. Tabs that the operator lacks permission for are hidden entirely
- Source filtering: A per-instrument source dropdown lets operators narrow results to a single analyzer or automation line. Sources are pulled from
/api/sources/optionsand respect source-scope permissions - Severity badges: Items are color-coded — red for critical (rejected messages, blocked delta checks, delivery errors), yellow for warnings (flagged messages, unmapped results, QC violations), blue for info (pending messages, processing preanalytical events)
- Action linking: Every item includes a direct navigation link to its resolution page — Open Inspector for message exceptions, Open Trace for delivery failures, Map Result for unmapped items, Review Delta for delta checks, Open QC for QC violations, and Open Preanalytics (or Review Specimen Fluids for routing material reviews) for preanalytical alerts
- Override routing statuses: Late-arrival routing stages and timed-out transit SLAs appear with detailed reason text showing the routing source, performing source, battery code, and stage reason
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.