"Safe-by-Design" Pharmacovigilance Compliance Orchestrator

KARUN K M — Tue, 19 May 2026 08:43:16 +0000

I Built a "Safe-by-Design" Pharmacovigilance

Compliance Orchestrator That Makes Regulatory

Deadlines Impossible to Miss

The Problem Nobody Talks About

Every year, pharmaceutical companies receive FDA warning letters that cost an average of $300,000 each. Many of them share a common root cause that has nothing to do with bad science or negligent teams.

It is a shared Excel spreadsheet. A color-coded Outlook inbox. A WhatsApp group that moves too fast.

In Pharmacovigilance (PV), when a patient experiences a serious adverse drug reaction, a legal clock starts immediately. Regulators mandate reporting within 7 days for serious cases and 15 days for non-serious ones. Miss the window and you are not looking at a slap on the wrist. You are looking at federal enforcement.

The teams responsible for this are tracking 50 to 100 active cases simultaneously using tools built for scheduling meetings.

I built something better.

What I Built

The PV Case Orchestrator is a real-time compliance management application for Pharmacovigilance teams. It replaces the spreadsheet-and-email workflow with a single intelligent command center that makes every regulatory deadline and every pending action visible, urgent, and impossible to ignore.

Built entirely on MeDo for the Build with MeDo Hackathon.

The Core Innovation: Safe-by-Design Architecture

Most compliance tools alert you when something goes wrong. This one is architected so that going wrong requires actively fighting the system.

Four Human-in-the-Loop Verification Gates

Every safety-critical action in the application requires explicit human confirmation before the system proceeds:

Gate 1 — Day 0 Clock Confirmation
The regulatory clock does not start until a human explicitly confirms the date of first receipt, selects the source type, and checks a confirmation box with the text: "I confirm this is the date our organization first received this case. I understand this timestamp is immutable and will appear in regulatory submissions." The timestamp locks permanently after this point.

Gate 2 — Classification Sign-Off
The system analyzes intake text using keyword triage and returns a confidence-scored recommendation (SERIOUS, NON-SERIOUS, SUSAR, or UNABLE TO CLASSIFY). A human must actively confirm or override every recommendation before any deadline is calculated. If the confidence score falls below 60%, no recommendation is shown at all — the case is flagged CRITICAL and held until a clinician manually classifies it.

Gate 3 — Alert Acknowledgement
Critical cases trigger a full-screen red interrupt that cannot be dismissed by clicking outside it or pressing Escape. The only exit is a button labeled "I ACKNOWLEDGE THIS ALERT" which captures the user ID and timestamp and writes them permanently to the audit trail.

Gate 4 — Submission Checklist
No case can reach READY FOR SUBMISSION status unless all four checklist items are confirmed: narrative complete, causality assessed, client notified, regulatory form complete. This block is enforced at the data layer — not just in the UI.

The Auditory Interface: Calm Technology Applied

to Compliance

Alarm fatigue is documented in clinical literature as one of the leading causes of missed critical signals in high-stakes environments. Every compliance tool I have ever seen makes this worse by adding more visual notifications to an already overwhelmed screen.

I went in a different direction.

The PV Case Orchestrator implements a three-tier auditory alert system designed around the principle of Calm Technology — information should live in the periphery of attention until it genuinely needs the center of it.

Tier 1 — Routine (>5 days remaining)

Single 440Hz sine wave chime
0.8 second decay
30% volume
Fires once on case update
Cognitive message: Something happened. No action needed yet.

Tier 2 — Warning (2–5 days remaining)

Ascending two-note interval: C5 (523Hz) rising to E5 (659Hz)
Creates psychoacoustic incompleteness — the brain registers something unresolved
Maximum 3 plays per case per 24 hours (habituation prevention)
After 3 plays, switches to visual-only to break the fatigue cycle

Tier 3 — Critical / SUSAR (<2 days or SUSAR)

Descending three-note minor phrase: G5 (784Hz) → E5 (659Hz) → C5 (523Hz)
Plays three times with 3-second gaps
Fires simultaneously with full-screen visual interrupt
Visual interrupt fires whether audio is available or not — never a silent failure

On every page load, a silent AudioContext health check verifies audio is working.
If it fails, a persistent amber banner activates across all screens:
"Audio alerts inactive — visual-only mode enabled."

The FMEA: We Risk-Assessed It Before

We Built It

Before writing a single line of logic, I ran a Failure Mode and Effects Analysis on the three highest-probability risks:

Risk	Severity	Probability	Mitigation
Keyword triage misclassification	9/10	8/10	Confidence gate + mandatory human confirmation
Audio alert suppression	8/10	9/10	Multi-modal redundant alert stack
Clock integrity failure	10/10	7/10	Immutable Day 0 ledger + parallel reclassification clock

Every mitigation is baked into the architecture, not bolted on afterward.

The Tech Stack

Platform: MeDo (full-stack AI generation)
Frontend: HTML5, CSS3, JavaScript ES6+
Audio: Web Audio API — OscillatorNode, GainNode, frequency envelope engineering
Backend: MeDo Rules Engine — 13 business logic automations
Database: MeDo Backend Services — Cases table with 40+ fields including append-only audit trail
AI Layer: MeDo LLM Engine (Claude/Anthropic) — confidence-scored keyword triage, natural language intake parsing
Safety Standard: ICH E2B(R3), EU AI Act Article 14 human oversight pattern

The North Star Metric

Zero late submissions per 1,000 active cases.

Not faster workflows. Not prettier dashboards. Zero. Late. Submissions.

That is a number a Chief Compliance Officer puts on a slide to their board. That is the number this application was built to deliver.

Try It

The live application is deployed and running.

https://app-bookj4rxcx6p.appmedo.com

Built for the Build with MeDo Hackathon.

If you work in pharma, biotech, or clinical research — or if you are building safety-critical tools and want to talk about Safe-by-Design architecture — I would love to hear from you in the comments.

DEV Community: KARUN K M