MedWatch Form 3500A: Section-by-Section

FDA Form 3500A is the mandatory version of MedWatch reporting — the form manufacturers, importers, and device user facilities are legally required to file when a regulated product is associated with a death, serious injury, or, for devices, a malfunction that could cause serious harm if it recurred. It is a different legal instrument from Form 3500, the voluntary form clinicians, patients, and consumers use to report a suspected problem with no obligation attached. Filing the wrong one, or filing 3500A incompletely, is a compliance gap — not a paperwork nuance — because 3500A submissions feed directly into FDA’s post-market surveillance systems and missed or late mandatory reports carry their own regulatory exposure under 21 CFR Part 803.

This guide walks through what triggers mandatory use of 3500A, the form section by section, the fields first-time filers most often get wrong, and how 3500A’s electronic pathway differs depending on whether the reported product is a drug/biologic (which routes toward FAERS) or a medical device (which does not).

What triggers mandatory use of Form 3500A

Under 21 CFR Part 803 (Medical Device Reporting) and the parallel drug/biologic reporting rules (21 CFR 314.80 for drugs, 21 CFR 600.80 for biologics), three categories of reporter are legally required to use 3500A rather than the voluntary 3500:

Manufacturers — must report deaths and serious injuries directly to FDA, and malfunctions that would be likely to cause or contribute to a death or serious injury if the malfunction were to recur.
Importers — must report deaths and serious injuries to both FDA and the manufacturer; malfunctions are reported to the manufacturer only, not to FDA.
Device user facilities (hospitals, nursing homes, ambulatory surgical and outpatient treatment facilities) — must report deaths to both FDA and the manufacturer, and serious injuries to the manufacturer (or to FDA if the manufacturer is unknown), plus an annual summary report. Physician offices are exempt from user-facility reporting obligations.

Everyone else — a clinician, patient, or consumer who wants to flag a suspected adverse event or product problem with no regulatory obligation to do so — uses the voluntary Form 3500, not 3500A. The distinction is legal status, not severity: a mandatory reporter files 3500A even for an event a voluntary reporter might describe identically.

The reporting clock: 30-day, 5-day, and 10-workday timelines

Once a mandatory reporter becomes aware of a reportable event, the timeline depends on severity and reporter type:

30-day report — the baseline: 30 calendar days from becoming aware of a reportable death, serious injury, or malfunction.
5-day report — required when remedial action is needed to prevent an unreasonable risk of substantial harm to public health, or when FDA specifically requests it.
10-workday report — applies specifically to device user facilities reporting a death or serious injury to the manufacturer.

These clocks start running from the date the reporter becomes aware of the event, not the date the event occurred — a distinction that trips up organizations that back-date their internal clock to the incident itself rather than to discovery.

Form 3500A section by section

3500A is a single form used across product types (drugs, biologics, and devices can each be the “suspect product” in a given report), which is why it carries sections for more product categories than any one filer will normally need. The sections, in the order they appear on the form:

Section A — Patient Information

A patient identifier (not a name — FDA does not want personally identifying information here), age or date of birth, sex, and weight. This section exists to let FDA correlate reports about the same patient across multiple submissions without collecting identifying data unnecessarily.

Section B — Adverse Event or Product Problem

The outcome checkboxes (death, life-threatening, hospitalization — initial or prolonged, disability or permanent damage, congenital anomaly/birth defect, required intervention to prevent permanent impairment, or other serious/important medical event), the event and outcome dates, and a free-text narrative describing what happened. This narrative is the section reviewers most often shortchange — a thin, checkbox-only submission with no descriptive narrative is a common reason FDA follows up for more information, which slows the report rather than closing it.

Section C — Suspect Product(s)

Used when the suspect product is a drug or biologic: product name, manufacturer, NDC number or unit distribution number, dose/frequency/route of administration, therapy dates, the diagnosis or reason the product was used, and — importantly — whether the event abated after the product was stopped or the dose reduced, and whether it reappeared after reintroduction (the “dechallenge/rechallenge” fields). These two fields are frequently left blank by first-time filers even when the information is known, which weakens the causality signal FDA’s reviewers look for.

Section D — Suspect Medical Device

Used when the suspect product is a device: brand name, common device name, manufacturer, model/catalog/serial/lot number, who was operating the device (health professional, lay user/caregiver, or patient), whether the device is available for FDA evaluation, and any concomitant medical products involved. A frequent first-time-filer error is leaving the “device available for evaluation” field ambiguous rather than a clear yes/no — FDA’s device reporting guidance treats this as a material field because it determines whether a follow-up evaluation request is even worth issuing.

Section E — Initial Reporter

Name, address, and phone number of whoever first identified and reported the event, their occupation, and checkboxes for who else the event was reported to (the manufacturer, a user facility, a distributor, or FDA directly). This section is what lets FDA and the manufacturer cross-reference reports about the same incident arriving through different channels.

Section F — For Use by User Facility or Importer

Report source, the date the event was received by the facility or importer, the report type (5-day, 10-workday, 30-day, or annual baseline), the location where the event occurred, and — where available — the device’s Unique Device Identifier (UDI). Omitting the UDI when it’s available on the device label is one of the more common completeness gaps, since it isn’t always obvious to a first-time filer that the field is asking for a specific barcode-derived identifier rather than a general model number (which Section D already captures separately).

Section G — All Manufacturers

Manufacturer name, address, and contact information; report source; the date the report was received by the manufacturer; report type; the adverse event term(s) used for FDA’s coding purposes; the device’s manufacture date; whether it’s single-use; whether remedial action has been taken; whether the product is distributed outside the US; and a narrative field for additional manufacturer-level information. Manufacturers filing directly complete this section themselves; user facilities and importers routing a report through a manufacturer leave it for the manufacturer to complete on their copy.

Where the electronic pathway diverges: FAERS is not the device destination

The candidate’s own framing — how 3500A differs from “the FAERS electronic submission” — points at a real and commonly misunderstood fork. 3500A itself is a shared, multi-product form, but the electronic system a completed 3500A ultimately feeds depends entirely on which product it concerns:

Drug and biologic mandatory reports (21 CFR 314.80 / 600.80) populate FAERS, FDA’s post-market drug/biologic safety surveillance database. FAERS also receives the voluntary Form 3500 stream from clinicians, patients, and consumers — mandatory and voluntary reports sit in the same database, distinguished by report source, not by which system they arrived through.
Device mandatory reports under 21 CFR Part 803 do not go to FAERS at all. Most mandatory device reporters now file electronically through eMDR (electronic Medical Device Reporting) via FDA’s Electronic Submissions Gateway — the electronic equivalent of the paper 3500A data elements — and that pathway feeds the device-specific adverse event database (commonly known by its long-standing FDA name, MAUDE), a separate system from FAERS.

The practical consequence: a compliance team that assumes “3500A data ends up in FAERS” for a device event is wrong about where their own report lives, which matters when a facility is trying to locate its own filing history or cross-reference a device signal against public data. Search FAERS for a drug or biologic; search the device-specific database for a device. A single incident involving a combination product may require reporting into both.

FDA has also been consolidating its adverse-event systems under a broader initiative reported to unify FAERS with adjacent legacy platforms (including the vaccine-focused VAERS and device-focused systems) into a single real-time monitoring architecture — treat FAERS and MAUDE as the stable underlying legal reporting obligations regardless of front-end branding changes, and confirm current system names directly against fda.gov before citing a live dashboard URL, since this transition has been reported as fast-moving.

Common completeness errors that delay a 3500A report

Checkbox-only Section B with no narrative. The outcome checkboxes tell FDA what category of harm occurred; the narrative is what lets a reviewer actually assess it. A report with ticked boxes and no descriptive text routinely triggers a follow-up request, which adds time rather than saving it.
Blank dechallenge/rechallenge fields (Section C) when the information is actually known internally — leaving these blank instead of marking “unknown” understates the causality evidence a complete report could otherwise provide.
Ambiguous device-availability status (Section D) instead of an explicit yes/no on whether the device is available for FDA evaluation.
Missing UDI (Section F) when one is present on the device label — a small field that’s easy to skip but increasingly expected as UDI adoption has matured across device categories.
Confusing the 30-day and 5-day clocks with the date of the event itself rather than the date the reporter became aware of it — the clock starts at awareness, not occurrence.

Frequently asked questions

Who is required to file Form 3500A instead of the voluntary Form 3500?

Manufacturers, importers, and device user facilities with a legal reporting obligation under 21 CFR Part 803 (devices) or the parallel drug/biologic post-market reporting rules. Clinicians, patients, and consumers reporting voluntarily use Form 3500; physician offices are exempt from the user-facility mandatory-reporting obligation.

Does a completed Form 3500A for a device end up in FAERS?

No. FAERS is specifically the drug/biologic adverse event database. Mandatory device reports are filed electronically via eMDR and feed the device-specific adverse event database, separate from FAERS.

What’s the difference between the 30-day and 5-day reporting timelines?

30 days is the baseline timeline from becoming aware of a reportable death, serious injury, or malfunction. The 5-day timeline applies when remedial action is needed to prevent an unreasonable risk of substantial harm to public health, or when FDA specifically requests an expedited report.

Can a device user facility submit Form 3500A directly to FDA?

For serious injuries, a user facility reports to the manufacturer (or to FDA only if the manufacturer is unknown); deaths are reported to both FDA and the manufacturer, plus an annual summary report of all such events.

MedWatch Form 3500A: Section-by-Section (vs. the Voluntary 3500)

Ask about MedWatch Form 3500A: Section-by-Section (vs. the Voluntary 3500)