Intelligent Drug Safety · Pre-Launch Waitlist
Complete adverse event reports with voice. FDA MedWatch 3500 made easy.
No spam. No phone number. One email to get you on the list.
You're on the list. ✓
One quick optional question while you're here:
What best describes you?
The Problem
Most adverse drug events go unreported. The barrier isn't awareness — it's a process designed for systems, not people.
MedWatch asks for NDC numbers, lot codes, and route of administration. Most patients can't answer these without abandoning the report entirely.
When reporting is too hard, patients give up — and the safety signal that could inform the next patient's care never reaches the FDA.
Even when patients do report, there's no structured handoff to the physician. The information exists in a PDF and goes nowhere useful.
PV teams spend hours extracting structured data from unstructured narratives, cleaning inconsistent inputs, and filling out ICSRs by hand.
When patient-reported data arrives as free text or a phone call, key fields — dechallenge, concomitant medications, outcome categories — are routinely missing.
Intake, coding, narrative drafting, and E2B submission happen in disconnected systems. Every handoff is a manual re-entry risk.
How It Works
MurmurPV is designed to replace a form with a conversation — structured against MedWatch 3500B fields, reviewed by the patient before anything is exported.
No account. No form. Plain-language questions about what happened — which drug, what symptoms, when. If a patient doesn't know an answer, that's recorded too.
MurmurPV is built to populate a structured record aligned to MedWatch 3500B fields — concomitant medications, dechallenge timelines, FDA outcome categories. A completeness check surfaces gaps before the record is finalized.
Before export, the patient reviews a plain-language summary and corrects anything that's wrong. Human review is part of the workflow, not an afterthought.
Output is a MedWatch 3500B PDF the patient can submit, plus a structured handoff record designed to support downstream physician processing — MedDRA coding, narrative drafting, E2B R3 — without re-entry.
Built for High-Stakes Data
Patient health data deserves infrastructure-level seriousness. MurmurPV is architected to meet it.
Nothing is stored on MurmurPV's servers without explicit patient consent. The session ends; the data stays with the patient. No persistent health records without a deliberate opt-in.
For organizations with data sovereignty requirements — CROs, hospitals, trial sites — MurmurPV can run entirely within your own infrastructure. Your data never leaves your stack.
The patient-facing intake tool is open source. Any organization can audit it, deploy it, or embed it without legal review friction. Transparency is the trust signal, not a logo.
Records are structured against MedWatch 3500B fields and designed to support downstream physician pipelines — MedDRA coding, ICSR generation, E2B R3 — without re-entry.
Who It's For
Something happened after starting a new medication. You want to report it — but MedWatch is a wall of regulatory jargon. MurmurPV is designed to handle the structure so you can focus on your story.
Patient reports arrive as unstructured fragments. MurmurPV is built to surface the intake layer — so what reaches your team is a structured record designed to support MedDRA coding and ICSR processing, not raw text.
MurmurPV is in active development. We're opening early access to patients, physicians, and PV teams who want to shape how it works. One email gets you on the list.
You're on the list. ✓
No spam. You'll get one confirmation email — then we'll reach out directly when early access opens.