Check a medical device's FDA safety history in 10 minutes: MAUDE, Recalls, and Warning Letters.
Use this when a founder, CEO, or first RA/QA hire is about to say "we checked the safety history" in front of an investor, partner, or consultant and needs that sentence to rest on dated sources rather than memory. The goal is not to judge safety. The goal is to collect dated source records and turn them into candidate review questions.
The fear in that moment is simple: someone will ask which FDA sources were checked, the team will realize the answer is stuck in browser history and Slack notes, and a preventable evidence gap will make the whole market-entry story feel uncertain.
For founders, manufacturers, RA/QA teams, and regulatory consultants. For RA/QA or consultant review.
This is not regulatory, legal, or compliance advice. Public safety-history research does not determine safety, effectiveness, reportability, compliance status, or market eligibility.
The 10-minute workflow
The pressure point is usually not research time. It is the moment someone asks, "What did you actually check, and when did you check it?" These three steps create a source trail you can hand to RA/QA instead of a verbal summary.
MAUDE: scan the narrative
Search the brand, manufacturer, generic name, and product code. Capture event type, date received, device problem terms, and the narrative limitation.
Open sourceRecall Database: check corrections and removals
Search by product description, firm, and product code. Capture recall class, reason, action, and whether the record is exact or adjacent.
Open sourceWarning Letters: read firm-level patterns
Search the manufacturer and product category. Capture quality-system or labeling findings as candidate review points, not conclusions about your device.
Open sourceScreenshot checklist
Capture the query fields and date range before submitting.
Capture the result row with source name, date, and record ID.
Capture the detail page section that supports your review note.
Store screenshots beside the source URL and access date. A screenshot is not a substitute for the source, but it helps preserve exactly what the team reviewed.
Convert findings into Product ID Map questions
The useful output is a short review queue: which failure modes appear repeatedly, which recall reasons seem adjacent, which warning-letter findings may matter to design controls or labeling, and which records are out of scope. Put those questions into a Product ID Map before the first paid consultant call, so the team is not paying senior review time to reconstruct a search that could have been logged in advance.
Frequently asked questions
Are MAUDE reports proof that a device is unsafe?
No. MAUDE reports are adverse-event reports, not adjudicated incidence rates. Read them for narrative failure modes and recurring scenarios, then preserve the source, query, date, and limitation.
Should I search recalls by brand name or product code?
Use both. Brand names can miss older or adjacent records, while product-code searches can over-include. A useful safety-history scan records the query path and explains why each result is in or out of scope.
Does this replace a Product ID Map?
No. This tutorial is a fast public-source check. A Product ID Map adds product-specific scoping, source ledger discipline, related 510(k) and product-code evidence, and review questions for RA/QA or a qualified consultant.
This is not regulatory, legal, or compliance advice. TrueMedDevice does not determine FDA classification, submission pathway, predicate status, substantial equivalence, compliance, safety, or effectiveness. We prepare a source-backed evidence pack from public FDA sources so qualified RA/QA professionals or regulatory consultants can review and decide.