Complaint Investigation Tool
AI-powered regulatory assessment for medical device complaint records — MDR reportability, risk scoring, investigation requirements, CAPA triggers, and an actionable investigation plan. Built for quality teams that need clear answers fast.
Prepared by
Matt Collins · ParanoiaIQ
Date
April 2026
Regulatory Coverage
21 CFR Part 803 · ISO 13485:2016 · ISO 14971:2019
▶ Tool Preview — Complaint Investigation
Overview
Seven regulatory tools. One complaint. 30 seconds.
The Complaint Investigation Tool runs a complete regulatory assessment every time a complaint is submitted. No checklists, no manual lookups. The tool applies the same framework a seasoned regulatory professional would apply — and surfaces the decision with the supporting rationale.
1
MDR Reportability
Evaluates reportable vs. needs-review vs. not reportable under 21 CFR 803.50, with specific basis for the determination.
21 CFR 803.50
2
Deadline Calculation
Calculates the 30-day (or 5-day) filing deadline from date of awareness, with days-remaining alert and overdue flag.
21 CFR 803.50(b)
3
Risk Score
Probability × Severity scoring on a 5×5 matrix. Classifies risk level and adjusts for service life, recurrence potential, and patient harm.
ISO 14971:2019
4
Investigation Required?
Determines whether a formal investigation is required (vs. complaint closure without investigation) with regulatory basis.
ISO 13485 §8.2.2
5
Trending Signal Check
Checks complaint history against 30-day and 12-month frequency to detect trending signals requiring escalation.
ISO 13485 §8.4
6
CAPA Assessment
Determines whether CAPA is required based on risk level, trending, recurrence pattern, and regulatory triggers.
ISO 13485 §8.5.2
7
Investigation Plan
Generates a prioritized, step-by-step investigation plan with task owner assignments and regulatory references for each step.
Complaint SOP / MDR
Step 1 of 3
Manual entry — complete the complaint record
Enter the complaint details directly or paste a raw narrative and let the AI extract the structured fields. The form mirrors the fields required for MDR evaluation and ISO 13485 complaint handling records.
ParanoiaIQ — Complaint Investigation
Tool UI — Manual Entry Form
Complaint Investigation
AI Extract
Manual Entry
CSV
Authentication
Anthropic API Key *
••••••••••••••••
Complaint Record
Complaint ID
CMP-2026-0412
Date Received *
2026-04-10
Product Name *
TitanSpine Lumbar Fusion System
Catalog / Model
TLF-4022
Lot / Serial
LOT-2023-0881
Device Context (optional)
Time in Service (yrs)
8.5
Labeled Service Life
10
Complaint History
Similar — 30 days
3
Similar — 12 months
11
Run Investigation →
🔬
No investigation running
Fill in complaint details and click Run Investigation to get a full regulatory assessment.
Form collects: Complaint Record · Device Context (service life for end-of-life analysis) · Complaint History (trending inputs) · Clinical & Device (outcome, malfunction, event description). Fields drive 7 regulatory tools in sequence.
Step 1 (alternate) — AI-assisted entry
Paste a raw complaint narrative — the AI fills the form
When complaint text arrives as a paragraph — from a phone call, email, or MDR narrative — paste it directly. The AI extraction engine reads it and pre-fills all structured fields with confidence ratings. Reviewer confirms before running the investigation.
ParanoiaIQ — Complaint Investigation · AI Extract
Tool UI — AI Extraction Results
Complaint Investigation
AI Extract
Manual Entry
CSV
API Key
••••••••••••••••
Paste Complaint Text
Surgeon reports TLF-4022 lumbar cage found cracked along superior endplate during revision surgery. 58-year-old male, 8.5 yrs post-implant. Worsening radiculopathy. Device retrieved...
Extract Fields with AI
Extracted — Review Before Running
Patient Outcome
Serious Injury
Malfunction
Yes
Product
TitanSpine Lumbar
Reporter
Clinician
Is Implant
Yes
Fails Spec
!
→ Use These Fields
How AI Extraction Works
Claude reads the raw complaint narrative and extracts every field needed for the regulatory investigation — patient outcome, malfunction flag, product details, reporter type, implant status, and a condensed event description.
Confidence Ratings
✓ CONFIDENT — clear in text
~ VERIFY — plausible
! CHECK — uncertain
Note: "Fails Specification" is never auto-checked. It requires investigation to confirm — the tool flags it as uncertain and leaves it for the reviewer to determine after physical analysis.
Paste any complaint narrative — MDR report, phone call notes, email from distributor. AI extracts and confidence-rates every field. Reviewer can edit anything before running the full investigation.
Step 2 — Investigation Results
Complete regulatory output — rendered below
The following is a real example of the investigation output format. All seven tools run in sequence and return structured results, rendered as an actionable report. This is what Greg would see after hitting "Run Investigation."
|
Complaint Investigation — CMP-2026-0412 · TitanSpine Lumbar Fusion System
MDR · ISO 13485 · ISO 14971
⚠ Immediate Actions Required
MDR deadline: Submit MedWatch 3500A by May 10, 2026 — 30 days from date of awareness (Apr 10, 2026). 13 days remaining.
Trending signal detected: 11 similar complaints in 12 months for this model. Trending evaluation required per ISO 13485 §8.2.1.
CAPA required — urgent: Risk score 20/25 (HIGH). Pattern of structural failures in same model warrants systemic corrective action.
MDR Status
MDR REPORTABLE
⚑ Investigation Required
▲ CAPA Required · Urgent
⏱ Deadline: May 10, 2026
Risk Score: 20 / HIGH
MDR Reportability
21 CFR 803.50
MDR REPORTABLE
  • Implantable device — serious injury from structural failure
  • Device malfunction with recurrence potential causing serious injury
  • Clinician-reported revision surgery required
  • 30-day report type applies (not 5-day)
Reporting Deadline
21 CFR 803.50(b)(1)
May 10, 2026
13 days remaining
Awareness date: Apr 10, 2026 · +30 days
⚑ Urgent — less than 15 days to file
Risk Score
ISO 14971:2019 §6
Probability × Severity
5
10
15
20
25
4
8
12
16
20
3
6
9
12
15
2
4
6
8
10
1
2
3
4
5
16
HIGH
Probability: 4 / 5
Severity: 4 / 5
85% of service life consumed → mid-range end-of-life classification
Investigation Required?
ISO 13485:2016 §8.2.2
REQUIRED
  • MDR-reportable event mandates documented investigation
  • Implant structural failure — failure mode must be characterized
  • Risk score ≥ 10 triggers investigation requirement
Trending Analysis
ISO 13485:2016 §8.2.1 / §8.4
SIGNAL DETECTED
  • 11 similar complaints in 12 months — statistically elevated
  • 3 in last 30 days — potential emerging cluster
  • Trend evaluation for TLF-4022 structural failures required
CAPA Assessment
ISO 13485:2016 §8.5.2
CAPA REQUIRED — URGENT
  • Risk score 16 (HIGH) — systemic corrective action indicated
  • Trending signal confirms pattern, not isolated event
  • Implant structural failure — potential field safety implications
Generated Investigation Plan
1
Retrieve and document implant — request explant from surgeon
Owner: Complaint Handling Engineer 21 CFR 803.55 ISO 13485 §8.2.2
2
Confirm MDR reportability and initiate MedWatch 3500A — deadline May 10, 2026
Owner: Regulatory Affairs 21 CFR 803.50
3
Physical failure analysis — characterize fracture mode, location, and potential manufacturing root cause
Owner: Materials / R&D Engineering ISO 13485 §8.5.2
4
Review all TLF-4022 complaints over 24 months — confirm trending signal and scope of pattern
Owner: QA / Data Analyst ISO 13485 §8.4
5
Pull manufacturing records for LOT-2023-0881 — review inspection results, NCMRs, process deviations
Owner: Manufacturing QA ISO 13485 §8.3
6
Open CAPA — document scope, root cause hypothesis, and containment actions for similar in-field devices
Owner: CAPA Owner / QA Manager ISO 13485 §8.5.2
7
Evaluate field safety — determine if corrective field action (recall, safety notice) is warranted based on failure analysis findings
Owner: Regulatory / QA Management 21 CFR Part 806 ISO 14971 §9

Investigation Summary

This complaint involves a structural failure of a TitanSpine Lumbar Fusion System (TLF-4022) retrieved during revision surgery from a 58-year-old male patient 8.5 years post-implant. The device exhibited cracking along the superior endplate, associated with worsening radiculopathy requiring surgical intervention. The patient outcome is classified as serious injury.

MDR Reportability

This event meets the definition of an MDR-reportable event under 21 CFR 803.50(a)(2). A marketed implantable device malfunctioned, the malfunction contributed directly to serious patient injury (revision surgery), and if the malfunction were to recur, it would likely cause or contribute to serious injury or death. The 30-day reporting deadline is May 10, 2026. Filing should not be delayed pending completion of failure analysis — the regulatory clock runs from the date of awareness.

Risk Assessment

Risk was scored at 16/25 (HIGH) using ISO 14971:2019 §6 criteria. Severity is rated 4/5 — serious injury with required surgical intervention in an implantable device. Probability is rated 4/5 — 11 similar complaints in 12 months indicates a non-isolated, recurrent failure mode. The device was 8.5 years into a 10-year labeled service life (85% consumed), which is classified as approaching end-of-life rather than premature failure — relevant context for root cause framing but does not diminish the risk classification.

Trending Signal

The combination of 3 complaints in 30 days and 11 in 12 months for this specific model constitutes a statistically meaningful signal requiring formal trending evaluation. This is not an isolated complaint — it is a data point in an emerging pattern. A trending analysis covering all TLF-4022 structural failure complaints over 24 months should be initiated in parallel with the individual complaint investigation.

CAPA Requirement

A formal CAPA is required. A HIGH risk score, confirmed trending signal, and implant structural failure mode satisfy the threshold for systemic corrective action under ISO 13485:2016 §8.5.2. The CAPA scope should encompass: root cause of the structural failure mode, review of manufacturing process parameters for this lot and adjacent lots, and evaluation of whether a field safety corrective action is warranted.

ParanoiaIQ — What This Means
MDR Reportable. 30-day clock is running from date of awareness.
This complaint triggered an MDR reportable determination. The 30-day deadline is firm — it runs from the date your organization became aware of the event, not from the completion of investigation. FDA does not require the investigation to be complete before filing; it requires you to submit what you know. Filing late — or failing to file — is a primary driver of FDA warning letters in complaint handling.
If FDA reviews this complaint record later, the question they will ask is not "did you investigate?" It is: "When did you know, and when did you report?" The investigation record has to answer that question credibly.
Option 1 — Handle Internally
Proceed with internal RA/QA team. Requires: MDR competency, complaint handling SOP in place, CAPA system with documented systemic corrective action. Timeline: 2–4 weeks to compliant closure, assuming resources are available now.
→ Discuss This Complaint
mcollins@paranoiaiq.com · Response within 24 hours
Regulatory Coverage
What the tool evaluates against
Every output is traceable to a specific regulatory requirement. The tool does not give generic guidance — it applies the specific section and decision logic.
Tool Regulation / Standard Decision Logic Output Type
MDR Reportability 21 CFR Part 803.50(a) Evaluates death, serious injury, malfunction with recurrence potential for marketed devices Automated
Deadline Calculation 21 CFR 803.50(b)(1)/(2) 30-day default; 5-day for devices that may have caused or contributed to death Calculated
Risk Scoring ISO 14971:2019 §6.3 / §6.4 5×5 P×S matrix; adjusts for service life (end-of-life vs premature), recurrence potential Automated
Investigation Required ISO 13485:2016 §8.2.2 MDR-reportable events, implants, risk score ≥ defined threshold, and malfunction events require investigation Automated
Trending Analysis ISO 13485:2016 §8.2.1 / §8.4 30-day and 12-month complaint frequency check; rate per units distributed when available Calculated
CAPA Assessment ISO 13485:2016 §8.5.2 Required when: risk HIGH or CRITICAL, trending signal confirmed, or systemic failure mode identified Automated
Investigation Plan Complaint SOP / MDR / ISO 13485 Generates prioritized, role-assigned steps with specific regulatory references for each action Generated