Biotech / diagnostics safety routing proof C# · patient-safety and regulatory workflow depth Hosted preview planned · Embedded by engagement

Safety signals, routing gaps, and review posture that stay operator-readable.

This control plane turns synthetic pharmacovigilance exports into one review surface: case completeness, seriousness assessment, MedDRA coding, follow-up closure, aggregate reporting evidence, and named signal actions before committee decisions harden around weak packets.

Overview Signal Lane Case Routing Safety Posture Verification Docs

Proof you can run

checkable claim, exact command

tests pass

dotnet test

Runs the full xUnit suite against the analysis and render services.

same data, no server

dotnet run --project src/PharmacovigilanceSignalRouter.Api -- --demo

Prints the identical safety-posture payload the public site renders, straight to the console.

rebuild the static site

dotnet run --project src/PharmacovigilanceSignalRouter.Api -- --prerender

Regenerates every route in site/ from the same source this page is built from.

Routes and API

what's public

routes

Public proof surface

/, /signal-lane, /case-routing, /safety-posture, /verification, /docs

api

Structured payloads

/api/dashboard/summary, /api/signal-lane, /api/case-routing, /api/safety-posture, /api/verification, /api/sample

Origin

why this repo exists

pattern extension

Not a pharmacovigilance-background claim

This repo exists to show that Kinetic Gain's control-plane pattern extends cleanly into biotech and diagnostics safety operations. The primitive isn't generic "drug safety monitoring," it's incomplete case intake packets that still need seriousness rationale, MedDRA coding drift that can distort signal quality, overdue follow-up that weakens escalation, and aggregate reporting a committee can actually trust. Full origin note in the repo's docs/ORIGIN.md.