Every complaint in V5 is triaged against your MDR/MDV decision tree, linked to the lot and DHR, routed for investigation, and closed only when CAPA effectiveness is verified. The reportability decision — and the rationale — is captured on every record, exportable to FDA or Competent Authority on demand.
Customer service logs an issue, QA hears about it three weeks later, the MDR clock has already started.
Without a structured decision tree captured on the record, two reviewers reach different conclusions on the same complaint.
If the complaint can't be traced to the batch, the operator, the supplier and the design history, the investigation is a guess.
Every channel lands in the same triage queue with SLA timers from the moment of receipt.
Structured questions, branching logic, and the rationale captured at every step. Reviewers reach the same answer because the questions are the same.
One click takes the investigator from the complaint to the manufacturing record, the operator, the supplier lot and the design history.
Trend triggers, severity triggers and reportability triggers all open CAPAs with the complaint pre-linked.
FDA eMDR, EU MIR, Health Canada — V5 holds the data; the export is a click, not a project.
Yes — the §803 decision tree is built in, the rationale is captured on the record, and eMDR-ready exports are one click. EU MIR and Health Canada formats are also supported.
Yes — web form, customer email, phone-logged, partner portal, and direct API from your CRM or service-desk tool. All land in the same triage queue.
On severity, trend or reportability triggers you define — and any reviewer can open one manually. The complaint is always pre-linked.
Complaints is part of the V5 Quality module — live in 7 days with standard onboarding, including migration of open complaint files.
Free trial, no card. Live in 7 days with guided onboarding.