Validation Evidence

Vorian Connect produces structured validation evidence from live analyzer traffic — enabled rule inventories, message throughput by source, destination delivery status, and per-instrument trace evidence — composited into a single exportable validation summary. Interface engineers use this evidence to document cutover readiness for CAP/CLIA validation requirements.

How It Works

What's Included

Where It Fits

Validation evidence bridges the gap between running analyzer traffic in shadow mode and proving to a lab director that the interface is production-ready. Instead of manually screenshotting dashboards and pasting counts into a Word document, an interface engineer selects a date range and source filter, clicks Export, and receives a timestamped, audited Markdown document that can go directly into the validation binder.

The evidence is PHI-safe by design — message counts and rule summaries never include patient identifiers, raw HL7 payloads, or decrypted PHI. The export is a summary of what the system did, not what it saw. This means the document can be shared with CAP/CLIA inspectors and procurement teams without redaction.

Technical Details (for evaluators)

The validation evidence system is built on two primary API endpoints. The summary endpoint (GET /api/validation/summary) accepts sourceId, from, and to query parameters and returns a JSON structure with rules (enabled rule list with names, actions, priorities, and timestamps), messages (source-by-source counts with status breakdowns), destinations (counts by mode and enabled/disabled status), and traces (per-source delivery destinations with hostnames, types, and mapping counts). The summary requires validation:view permission.

The export endpoint (POST /api/validation/export) accepts the same filter parameters as a JSON body, generates the summary, renders it to markdown via a dedicated renderer (renderValidationEvidenceMarkdown), writes a validation_export audit event using logRequiredAdminAction (failing closed with a 503 if the audit write fails), and returns the markdown as a downloadable attachment. The markdown renderer formats all values as plain text — no raw HL7, no patient identifiers, no encrypted PHI blobs.

Date parameters must be valid ISO timestamps with from before to, and sourceId must be a valid UUID when provided. Invalid parameters return clean 400 errors with operator-readable messages. Source-scope denials return structured error responses with the missing permission scope.

Last updated: May 22, 2026