Adverse Event ReportingAdverse Event Reporting (Dietary Supplements)

The Dietary Supplement and Nonprescription Drug Consumer Protection Act of 2006 added mandatory serious adverse event reporting for supplements marketed in the US. The responsible person is the firm whose name appears on the label.

Labels must include a domestic address or phone number through which reports can be received.

A serious adverse event results in death, a life-threatening experience, inpatient hospitalisation, persistent or significant disability, a congenital anomaly, or requires medical or surgical intervention to prevent one of those outcomes.

Non-serious events need not be reported to FDA but should still be recorded and assessed.

Reports are submitted on MedWatch Form 3500A within 15 business days of receiving the report, with a copy of the label. New medical information received within a year must also be forwarded within 15 business days.

Track the receipt date carefully; the clock starts when anyone in the company receives the information.

Reports arrive through customer service calls, emails, social media, retailers and distributors. Every channel needs a route to the safety process.

Train front-line staff to recognise and capture adverse event information.

Records of all adverse event reports, serious or not, must be kept for six years and made available to FDA on request.

Records should include the report, follow-up, assessment and submission.

Beyond reporting, firms should assess events for patterns that could indicate a product quality issue, such as contamination or mislabelling, and link them to complaint investigations.

Reporting does not establish causation, but trends warrant investigation.

Pitfalls include reports stuck in a general inbox, retailers not forwarding contacts, incomplete follow-up and treating serious events as ordinary complaints.

Run periodic mock reports through the process.

1. Capture the complaint or event with date of awareness, reporter, product, lot and description, exactly as received.
2. Triage promptly so potential reportable events reach the people trained to assess them.
3. Assess against the applicable rules for the product type and market, and record the rationale.
4. Submit within the applicable timeline where reporting is required, and keep proof of submission.
5. Link the event to investigation, trending and CAPA where appropriate.

The date of awareness matters because reporting clocks usually start from it. Recording it at intake, rather than reconstructing it later, protects the company in an inspection.

Individual reports answer individual events. Trending by product, lot, failure mode and customer helps quality teams see patterns that no single report reveals, and supports management review.

Trends prompt human investigation. They do not by themselves establish cause or reportability.

V5 complaint and quality records can capture consumer contacts, link them to product lots and production records, and route investigations to CAPA.

V5 does not determine seriousness or submit MedWatch reports; trained staff do.

Trace how a phone call mentioning a hospital visit would move from first contact to FDA submission, and time each step.

Close any step where information could wait in an inbox.

When a retailer or distributor's name is on the label, it may be the responsible person, or it may authorise the manufacturer to submit. Agreements should state who reports and how information flows.

Information received by a retailer still needs prompt forwarding to the responsible person.

Initial reports are often incomplete. Attempt follow-up for medical details, product lot, dose and outcome, and record attempts even when unsuccessful.

Forward significant new information to FDA within the required timeframe.

Other countries have their own vigilance rules for supplements, natural health products and complementary medicines. A US process does not automatically satisfy them.

Map reporting obligations for every market where products are sold.

A consumer emails customer service saying they were hospitalised after taking a product. The agent logs it as a potential serious adverse event the same day.

The safety lead reviews, requests label and lot details, submits MedWatch 3500A within the 15-business-day window, and quality reviews the lot's production and complaint history.

1. Confirm the applicable requirement, product scope and decision owner.
2. Map the current method and the records already available.
3. Define terms, responsibilities, evidence and exception handling in the approved procedure.
4. Pilot the method on one representative process and challenge a difficult exception.
5. Train affected roles, approve the change and monitor whether the method works as intended.
6. Review after significant change and retain a transparent history of decisions.

Scale the formality to risk and complexity. A small operation still needs clear responsibilities and reconstructable evidence, while a multi-site operation also needs harmonised definitions, governance and comparison rules.

• Can a reviewer identify the source, owner, method and current approved version?
• Do summaries reconcile to original records and include unfavourable or missing evidence?
• Are exceptions visible, assessed and linked to the affected material, product or process?
• Are actions assigned, overdue items escalated and effectiveness reviewed?
• Have changes in product, supplier, equipment, method or regulation triggered reassessment?
• Does the record distinguish system support from the decision an authorised person made?

• Approved scope, definitions and responsibilities for Adverse Event Reporting (Dietary Supplements).
• Source records and identifiers that let a reviewer reconstruct the work.
• Methods, assumptions, calculations, exclusions and any data-quality limitations.
• Exceptions, investigations, decisions, approvals and resulting actions.
• Version history showing when the approach changed and why.

Records should be proportionate to the decision and usable by someone who was not present. Preserve original evidence and corrections rather than replacing it with an unexplained summary.

• Can users trace every summary value back to its source record and version?
• How are roles, permissions, signatures and corrections recorded?
• Can the workflow reflect our approved procedure without inventing a universal rule?
• What happens during an outage, and how are later entries distinguished?
• Can we test the highest-risk exception with realistic data before committing?
• Which decisions remain explicitly assigned to an authorised person?