Support Cases

Internal Vorian support case triage system. Create, track, and resolve cases linked to product evidence — message traces, delivery logs, QC violations, or worklist exceptions — with PHI-safe posture controls and a customer-facing status page.

How It Works

Support Cases provide a structured workflow for Vorian platform administrators to track issues across a tenant. Each case captures a summary, impact description, severity level, category, optional instrument source link, time range, and PHI posture. Cases carry typed evidence references that point into the product — a message trace, a delivery log entry, a QC violation, a worklist exception — so the full product context is one click away.

Cases move through a five-stage status workflow: open → waiting_on_customer or waiting_on_vorian → resolved → closed. Resolution and closure timestamps are recorded automatically via database triggers. Every status change, owner reassignment, and note is captured in an immutable activity log attached to the case.

All case mutations — creation, updates, packet exports — require a successful audit row write before the change is committed. If audit logging is unavailable, the operation fails closed with clear guidance. Tenant isolation is enforced through PostgreSQL row-level security.

Severity Levels

LevelMeaning
SEV1Critical — production results flow is blocked or compromised across the tenant
SEV2High — a specific instrument or delivery path is down; partial impact
SEV3Medium — a feature is degraded but workarounds exist; non-blocking
SEV4Low — cosmetic, informational, or future-improvement tracking

When cases are created automatically from worklist or delivery evidence, severity is derived from the underlying item: failed deliveries with exhausted retries default to SEV2, QC violations to SEV3, and informational items to SEV4.

Case Categories

Nine categories align cases to the product surface they affect:

CategoryCovers
interface_healthEdge agent connectivity, source listener status, heartbeat gaps
message_flowMessage ingestion, parsing errors, throughput anomalies
deliveryOutbound HL7 MLLP, FHIR R4, webhook, or File Drop delivery failures
routingOrder routing, staged-until-arrival timeouts, routing-stage exceptions
mappingUnmapped instrument codes, test identity gaps, LOINC mapping issues
rulesAuto-verification rule behavior, clinical rule work items, rerun requests
qc_deltaQC Westgard violations, delta check blocks, exclusion audit questions
accessUser permissions, sign-in issues, team membership, directory sync
product_defectUnexpected dashboard behavior, API errors, data inconsistencies

PHI Posture

Every case declares its PHI posture so support operators know what data handling rules apply:

Evidence References

Cases are anchored to product evidence through typed references. Each reference carries a type, an ID, a human-readable label, and an optional source ID:

Automated Case Creation

Cases can be created manually or automatically from two product surfaces:

Both paths require the support:manage permission and write an audit row before creating the case.

Support Packet Export

Each case can generate a support packet — a bundled export of all evidence linked to the case, including the full activity log, all evidence references with resolved product data, case metadata, and audit trail entries. Packets are available in JSON, CSV, TSV, and XML formats for handoff between Vorian support operators or import into external ticketing systems.

Customer-Facing Status Page

Cases marked customer_visible appear on a tenant-scoped status page at /support/status. Customers see a simplified view: case summary, severity, category, status, and a next-action indicator (Vorian, Customer, or Closed). Impact descriptions, internal notes, activity logs, and evidence references are never exposed. The status page requires the support:case:view permission — distinct from the internal support:view permission used by Vorian administrators.

Where It Fits

Support Cases bridge the gap between product observability and operational response. The Worklist surfaces exceptions — a failed delivery, a blocked delta check, a routing timeout. Support Cases turn those exceptions into tracked, audited work items with full product evidence attached. The customer status page closes the loop by giving tenant administrators visibility into what Vorian is working on for their environment.

Support Cases sit alongside the Observability dashboard and Admin Audit Log in the operations layer of Vorian Connect. They do not replace external ticketing systems — the support packet export is designed to feed into whatever system a lab already uses for issue tracking.

Permissions

PermissionGrants
support:viewList and view internal support cases with full detail, activity log, and evidence references
support:manageCreate, update, assign, and resolve support cases; generate support packets
support:case:viewView customer-safe case summaries on the public status page

Last updated: June 12, 2026