Serious Adverse Event (SAE) is any unintended incident associated with a medical device that directly or indirectly resulted in, or could have led to, death, serious deterioration in health, or a serious public health threat. Under EU MDR 2017/745 and FDA 21 CFR Part 803, confirmed SAEs trigger mandatory reporting to regulatory authorities within strict, jurisdiction-specific timelines.
What is a Serious Adverse Event (SAE)?
An SAE in the medical device industry is a reportable incident that meets at least one of these criteria: it caused or contributed to a death, it caused or might have caused serious deterioration in the health of a patient, user, or other person, or it constituted a serious public health threat.
Terminology varies by framework. EU MDR 2017/745 Article 2(64) uses the phrase “serious incident” and extends the definition to malfunctions that might have led to harm, not just events that already did. FDA reporting obligations fall under 21 CFR Part 803; mandatory reports submitted under this regulation are commonly called Medical Device Reports (MDRs). In clinical trial contexts, SAE definitions follow ICH E6, which additionally includes hospitalization and permanent disability.
Why Serious Adverse Event (SAE) matters in medical device development
Missed or late SAE reports carry real regulatory consequences. FDA can issue Warning Letters, pursue injunctions, or initiate recalls. European competent authorities can restrict a device’s market access or suspend CE certification.
ISO 14971 requires manufacturers to update their risk estimates when post-market information reveals new hazards. SAEs are the primary source of that information. When SAE data shows risk levels exceeding pre-market assumptions, the manufacturer must act: modify the device, update labeling, or issue a Field Safety Corrective Action (FSCA). For Class II and Class III devices, accumulating SAE signals can also drive revisions to the Post-Market Clinical Follow-Up (PMCF) plan and feed into the Periodic Safety Update Report (PSUR) or Post-Market Surveillance Report (PMSR).
The Serious Adverse Event (SAE) reporting process
SAE management follows a defined sequence:
Detection and intake
SAEs surface through complaint forms, clinical study submissions, field reports, and post-market surveillance (PMS) signal reviews. The Quality Management System (QMS), certified under ISO 13485, must document procedures for routing all incoming events through a single intake system.
Seriousness and causality assessment
The manufacturer determines whether the event crosses the SAE threshold and whether the device caused or contributed to the outcome. Both conclusions require documented rationale, not just assertions.
Regulatory notification
Timelines are strict. Under EU MDR 2017/745 Article 87, most serious incidents must reach the relevant competent authority within 15 calendar days of awareness. Events involving imminent risk of death or serious harm require an initial report within 2 calendar days. FDA 21 CFR Part 803 sets a 30-day standard window and a 5-day requirement when immediate action is needed to prevent serious harm.
Root cause analysis and CAPA
Every SAE drives a documented investigation and a Corrective and Preventive Action (CAPA). Findings may lead to a PMCF amendment, a design change, or an FSCA.
Trend monitoring
EU MDR Article 88 requires manufacturers to report statistically significant increases in adverse events. Events below the SAE threshold individually can become reportable when they cluster into a pattern.
Common challenges and best practices
The most common failure point is intake leakage. SAEs arriving through sales emails or distributor calls frequently bypass the formal complaint system. QMS procedures must explicitly route all incoming device-related communications through documented intake, and field-facing staff need regular training on what constitutes a complaint.
Causality assessments are often over-optimistic. Manufacturers sometimes classify events as unrelated to the device without completing a thorough investigation. Regulatory bodies audit these determinations, and a thin “not device-related” rationale is a recurring finding in FDA 483 observations and EU competent authority inspections.
Timeline compliance requires more than goodwill. A 2-day or 5-day reporting clock opens when awareness is established, not when the investigation concludes. Submitting interim reports to competent authorities while the investigation continues is standard practice and expected by regulators.
A cross-functional review committee with defined QA, RA, and clinical roles, a consistent cadence, and an escalation path tied to the PMS plan and PSUR or PMSR schedule is the clearest sign of a mature vigilance system.
How SJML helps with Serious Adverse Event (SAE)
SJML’s Quality Assurance and Regulatory Affairs (QARA) team manages the adverse event lifecycle as part of its Compliance-as-a-Service offering: complaint intake, seriousness and causality assessment, mandatory regulatory reporting, root cause analysis, CAPA management, and trend monitoring. The team operates across EU MDR 2017/745, FDA 21 CFR Part 803, and MDSAP-aligned frameworks, integrating SAE data into clients’ PMS plans, PSUR and PMSR cycles, and PMCF programs. This applies to early-stage companies building their first vigilance process and to established OEMs managing multi-jurisdiction reporting obligations.
Frequently asked questions
An SAE is any unintended incident that caused or could have caused death, serious deterioration in health, or a serious public health threat. EU MDR 2017/745 Article 2(64) and FDA 21 CFR Part 803 establish these criteria. Manufacturers must document the assessment with supporting rationale, not simply state a conclusion.
A near miss involves potential harm that did not occur. EU MDR 2017/745 requires manufacturers to evaluate near misses and determine whether they reach the serious incident threshold. Under Article 88, a pattern of near misses can become reportable as a trend even if no single event qualifies as an SAE on its own.
Under EU MDR 2017/745 Article 87, most serious incidents must be reported to the relevant competent authority within 15 calendar days of becoming aware. Events involving imminent risk of death or serious harm require a 2-calendar-day initial notification. FDA 21 CFR Part 803 sets a 30-day standard window and a 5-day requirement for events posing immediate public health risk.
No. Each complaint must be assessed individually against the SAE threshold and for device causality. The QMS must document the rationale for both reportable and non-reportable conclusions. Regulators audit non-reporting decisions as closely as submitted MDRs or vigilance reports, and unsupported conclusions are a common inspection finding.
The manufacturer must complete a root cause investigation, implement and verify a CAPA, and determine whether an FSCA or Field Safety Notice (FSN) is warranted. The event and its resolution must appear in the next PSUR or PMSR. Serious Adverse Event (SAE): Competent authorities or the FDA may request additional information at any point.
Related terms
- Post-Market Surveillance (PMS)
- Field Safety Corrective Action (FSCA)
- Corrective and Preventive Action (CAPA)
- Vigilance Reporting
- ISO 14971 Risk Management
