Reprocessing Engine

When auto-verification rules change — a new reference range, an updated delta threshold, a corrected LOINC mapping — Vorian Connect can re-run verification on historical messages in bulk. The reprocessing engine handles this asynchronously with per-job versioning, one-click rollback, and configurable worker concurrency.

How It Works

What's Included

Where It Fits

The reprocessing engine is separate from the live message pipeline. Reprocess jobs never block new message ingestion — they use their own durable job table and worker pool. This means a lab can reprocess 100,000 historical messages while the edge agent continues to receive and auto-verify new results from analyzers without any impact on throughput.

Reprocessing is typically triggered after significant rule changes: deploying a new auto-verification rule, updating LOINC mappings, adjusting delta thresholds, or recovering from an incorrect rule that auto-verified results that should have been flagged.

Technical Details (for evaluators)

The reprocess CLI accepts -statuses (comma-separated verification statuses to target), -from and -to (date range in YYYY-MM-DD format), and -limit (maximum messages to process). Jobs are tracked in reprocess_jobs with status transitions: pending → running → completed (or failed).

Each history entry in reprocess_history records the old verification status, old notes, new status, new notes, and the job ID that produced the change. This creates a full audit trail of every verification decision change — useful for compliance reviews and debugging rule behaviour.

The worker pool uses a buffered Go channel as a semaphore to limit concurrent processing. When the channel is full, new jobs wait — no unbounded goroutine creation, no resource exhaustion under load.

Last updated: September 3, 2026