What public safety signals should I check before a medical device market-entry submission?
Before a medical device market-entry submission or licence-application discussion, a product-family public safety-history scan surfaces the failure modes, recall patterns, warning-letter findings, safety advisories, and incident-report themes the regulator has already seen for similar devices. As of 2026-05-23, the U.S. and Canadian public sources fall into two clearly separated tracks: for U.S./FDA, MAUDE, FDA Recalls, FDA Warning Letters, FDA Safety Communications, and FDA Import Alerts; for Canada / Health Canada, Recalls and Safety Alerts, Public Advisories, Foreign Risk Notifications, and Medical Device Incident Reports under the Canada Vigilance program. The output is a set of candidate review points for RA/QA, design controls, risk management, labelling, cybersecurity, and PMS planning — never a safety conclusion, a compliance conclusion, or an approval likelihood. Final risk acceptance, classification, pathway, and licence-outcome decisions belong to your RA/QA team or qualified consultant in consultation with the relevant regulator.
For founders, manufacturers, RA/QA teams, and regulatory consultants. For RA/QA or consultant review.
This is not regulatory, legal, or compliance advice. TrueMedDevice does not determine FDA classification, submission pathway, predicate status, substantial equivalence, Health Canada device class, MDL/MDEL eligibility, licence outcome, compliance, safety, effectiveness, risk acceptability, market eligibility, or approval likelihood. We organize public-source safety-history evidence so qualified RA/QA professionals or regulatory consultants can review and decide.
Why scan public safety history before a submission discussion
A product-family safety-history scan is the cheapest, fastest way to learn what the regulator has already seen go wrong in your category — before you draft your risk file, before you scope your verification plan, and before you spend paid consultant hours. Failure modes that appear repeatedly in recalls or Warning Letters tend to be the exact failure modes the reviewer will probe at submission and the exact patterns the inspector will probe during an audit.
The output is not a safety conclusion. It is a set of candidate review points that RA/QA, risk-management, regulatory, design controls, labelling, cybersecurity, and PMS owners can fold into their plans. The public sources are open to anyone; the value is in the scoping, the categorization, and the source-cited organization that lets RA/QA confirm or revise each candidate point quickly.
U.S. / FDA public safety signals
The FDA public surfaces below cover voluntary adverse events, recall actions, enforcement actions, public advisories, and import controls. A product-family scan typically pulls signals from at least three of the five.
- FDA MAUDE (Manufacturer and User Facility Device Experience)
Voluntary adverse-event reports. Read narratively — failure modes, common scenarios. Counts are not incidence rates.
- FDA Recalls
Voluntary and FDA-classified recall actions (Class I, II, III by FDA's severity scale). Records corrective action history per product code and per applicant.
- FDA Warning Letters
Enforcement actions against firms — surface recurring inspection findings, quality-system issues, and labelling issues for the product category.
- FDA Safety Communications
Public advisories tied to specific device categories or product types. Often signal emerging concerns the regulator wants attention on.
- FDA Import Alerts
Detention-without-physical-examination flags. Useful when researching foreign-manufacturer risk patterns relevant to the candidate device.
For the broader U.S. preparation context — intended use, candidate product code, candidate predicate shortlist, forms / fees / eSTAR / standards — see the U.S. market-entry research guide.
Canada / Health Canada public safety signals
Health Canada operates the Canada Vigilance program. The public surfaces below cover recalls, safety alerts, advisories, foreign risk notifications, and incident-reporting summaries. Severity classification, access patterns, and reporting conventions differ from FDA — the Canadian scan is a separate output, not a translation of the U.S. one.
- Health Canada Recalls and Safety Alerts Database
Public-facing recall and safety-alert records covering Canadian-marketed medical devices.
- Health Canada Public Advisories
Public statements about specific products, device categories, or emerging safety concerns under SOR/98-282.
- Health Canada Foreign Risk Notifications
Notifications about foreign regulator actions on the same or similar devices — useful comparator context.
- Medical Device Incident Reporting summaries
Post-market incident summaries published under the Canada Vigilance program.
For the broader Canada licence pathway research context — intended purpose, candidate device class, MDL/MDEL applicability, MDALL similar-licensed-device shortlist, MDSAP and standards — see the Health Canada medical device licence research guide.
How to scope a product-family scan
A useful scan is bounded. The four boundaries that matter most in practice:
- Product category — FDA product code, Health Canada class, and the device-type description that captures the candidate similar-device set.
- Time window — typically the last five to ten years for recalls and Warning Letters, last three to five years for MAUDE and incident reports. Older entries are referenced selectively.
- Severity threshold — for MAUDE / incident reports, restrict to event types relevant to the candidate failure modes; for recalls, capture Class I / II at minimum.
- Comparator set — direct similar devices and indirect similar devices on the same product code or device class, plus any candidate predicate or candidate similar-licensed device under research.
Source-backed evidence at every step: each cited record links back to a public FDA, Health Canada, or MDALL URL with access date.
Scoped + dated absence statements — the discipline
The most common writing error in this kind of scan is the absolute negative. "Manufacturer X has no compliance issues" is not a defensible statement. "No open FDA Warning Letters found for manufacturer X in the FDA Warning Letter database, query window 2020-01-01 through 2026-05-23" is. Every absence claim names the source, the query, the window, and the access date — so that any reader can re-walk and confirm.
The discipline is the same on both jurisdictions. Health Canada absence claims cite the relevant Canadian source (Recalls and Safety Alerts database, Public Advisories, Medical Device Incident Reports), the query window, and the access date.
What this surfaces — candidate review points
A scoped, source-cited scan typically surfaces candidate review points across these RA/QA dimensions:
- •Design controls and labelling issues most often cited in recalls and Warning Letters for the product family
- •ISO 14971 risk-management gaps suggested by the failure-mode pattern in MAUDE and incident reports
- •Cybersecurity-related advisories relevant to connected medical devices in the category
- •Sterility and biocompatibility concerns surfaced for the materials and processes the candidate device shares
- •Usability and human-factors issues recurring in the product category
- •Post-market surveillance (PMS) plan inputs suggested by the public adverse-event pattern
What this scan does NOT determine
The scan is research preparation. Every item below remains a judgment call for your RA/QA team or qualified consultant in consultation with the relevant regulator:
- →Safety of any specific device
- →Risk acceptability for any specific device design
- →Market eligibility, classification, or licence outcome in any jurisdiction
- →Substantial equivalence to any predicate or similar-licensed comparator
- →Compliance with any specific FDA, Health Canada, or recognized-standards obligation
- →Approval, clearance, or licence likelihood for the candidate device
This is not regulatory, legal, or compliance advice. TrueMedDevice does not determine FDA classification, submission pathway, predicate status, substantial equivalence, Health Canada device class, MDL/MDEL eligibility, licence outcome, compliance, safety, or effectiveness. We organize public-source evidence so qualified RA/QA professionals or regulatory consultants can review and decide.
Related research
- U.S. Market-Entry Research Guide — the broader U.S. preparation context
- Health Canada Medical Device Licence Research Guide — the broader Canada preparation context
- U.S. / FDA Market-Entry Product Evidence Pack — service version of the U.S. workflow
- Canada / Health Canada Market-Entry Product Evidence Pack — service version of the Canada workflow
- Request a Product ID intake — start the safety-history scan on your device
Frequently asked questions
What is a product-family safety-history scan?
A product-family safety-history scan is a structured public-source review of recalls, adverse-event reports, safety advisories, warning letters, and incident reports for the broader category of medical devices similar to your candidate device — not just one specific competitor. The point is to surface failure modes, labelling issues, and recurring inspection findings as candidate review points for RA/QA, risk-management, and PMS planning. It is not a determination of safety, risk acceptability, or market eligibility.
Why do this before talking to a regulatory consultant?
Consultant time is expensive. A safety-history scan run before the first paid call gives the consultant a concrete starting point: which failure modes the product family has historically faced, which inspection findings have been repeat issues, and which standards or guidance the regulator has been emphasizing. The conversation shifts from "let me explain my device" to "here are the candidate review points — which matter most for my product?". Final risk acceptance, classification, pathway, licence outcome, and submission strategy decisions remain with qualified RA/QA professionals.
Are MAUDE counts the same as failure rates?
No. FDA MAUDE (Manufacturer and User Facility Device Experience) records voluntary adverse-event reports. Reports are not verified, are not adjudicated, and do not give a denominator. Comparing raw counts across devices can be misleading because reporter attention varies. The right discipline is to read MAUDE narratively — failure modes, common scenarios, recurring complaints — and to record absence statements as scoped and dated ("no MAUDE reports found for product code X above severity threshold Y, in window Z, as of <date>").
What's the Canadian equivalent of MAUDE and FDA Recalls?
Health Canada publishes a Recalls and Safety Alerts database, Public Advisories, Foreign Risk Notifications, and a Medical Device Incident Reporting summary. The Canada Vigilance program runs the post-market reporting framework. These sources collectively cover similar territory to FDA MAUDE + FDA Recalls + FDA Safety Communications, but the structure, severity classification, and access patterns differ. The Canada Market-Entry Product Evidence Pack uses these sources for the Canadian safety-history scan.
Does this replace a risk-management or PMS plan?
No. ISO 14971 risk management and post-market surveillance (PMS) planning are RA/QA deliverables that depend on internal device knowledge, the manufacturer's quality system, and standards conformance evidence. A public safety-history scan is an input to those activities — it surfaces candidate review points the RA/QA team and qualified consultants can incorporate into the formal risk file and PMS plan. It is not a risk-acceptability determination and does not substitute for ISO 14971 documentation or for a regulator's safety conclusion.