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
| Level | Meaning |
|---|---|
| SEV1 | Critical — production results flow is blocked or compromised across the tenant |
| SEV2 | High — a specific instrument or delivery path is down; partial impact |
| SEV3 | Medium — a feature is degraded but workarounds exist; non-blocking |
| SEV4 | Low — 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:
| Category | Covers |
|---|---|
interface_health | Edge agent connectivity, source listener status, heartbeat gaps |
message_flow | Message ingestion, parsing errors, throughput anomalies |
delivery | Outbound HL7 MLLP, FHIR R4, webhook, or File Drop delivery failures |
routing | Order routing, staged-until-arrival timeouts, routing-stage exceptions |
mapping | Unmapped instrument codes, test identity gaps, LOINC mapping issues |
rules | Auto-verification rule behavior, clinical rule work items, rerun requests |
qc_delta | QC Westgard violations, delta check blocks, exclusion audit questions |
access | User permissions, sign-in issues, team membership, directory sync |
product_defect | Unexpected dashboard behavior, API errors, data inconsistencies |
PHI Posture
Every case declares its PHI posture so support operators know what data handling rules apply:
- No PHI — the case summary, impact, and evidence references contain no protected health information. Safe for routine triage.
- PHI-safe — the case context uses pseudonymised or tokenised references (e.g., MRN HMAC tokens). Operational identifiers only.
- Audited PHI required — the case may reference raw PHI. Access requires the audited PHI Troubleshooter permission and a recorded reason.
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:
- Message traces — link to a specific parsed HL7 or ASTM message in the Trace Inspector
- Delivery logs — link to an outbound delivery attempt with status and retry history
- Instrument sources — link to the affected source configuration
- QC records — link to a specific rolling-stat QC violation
- Worklist items — link to the originating worklist exception
- Result publication profiles — link to governed result publishing configuration
- Destinations — link to the affected delivery target
Automated Case Creation
Cases can be created manually or automatically from two product surfaces:
- From Worklist — any open worklist item can create a case. Nine worklist types are supported: message exceptions, delivery failures, unmapped results, delta checks, QC violations, preanalytical alerts, routing-stage timeouts, clinical rule work items, and result comment reviews. The case inherits the worklist item's title, detail, severity, and evidence references automatically.
- From File Drop Delivery — a File Drop package delivery can create a case. The system reads the delivery log, result publication profile, and reconciliation status. Severity is auto-assigned: SEV2 for failed deliveries or rejected reconciliation, SEV3 for unverified reconciliation, SEV4 for successful deliveries needing routine review.
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
| Permission | Grants |
|---|---|
support:view | List and view internal support cases with full detail, activity log, and evidence references |
support:manage | Create, update, assign, and resolve support cases; generate support packets |
support:case:view | View customer-safe case summaries on the public status page |