How to Report a GLP-1 Side Effect to MedWatch (Form 3500B Walkthrough)

If you are taking a compounded GLP-1 medication and something has gone wrong, the FDA wants to hear about it directly. The MedWatch program is the federal pathway for individual case safety reports, and for compounded drugs it is the only systematic feedback loop the agency has. This guide walks through Form 3500B step by step, including the fields that work differently for compounded products. For the broader clinical picture of recognizing and managing reactions to compounded GLP-1 medications, see the full GLP-1 adverse events guide.

Why your report matters

FDA pharmacovigilance is fundamentally a signal-detection system. The agency does not investigate every individual case. It watches the FDA Adverse Event Reporting System (FAERS) for patterns: rising frequencies of a specific reaction, clusters tied to a specific lot or pharmacy, outcomes the product label did not predict. The same pharmacovigilance principles taught in vaccine surveillance apply here, with one key distinction. Approved manufacturers operate under mandatory expedited reporting under 21 CFR 314.80. Compounded preparations from 503A pharmacies do not, which means patient and clinician submissions to MedWatch carry disproportionately more signal weight than they would for an FDA-approved drug.

The structure of an individual case safety report (ICSR) carries directly across from VST's existing modules on adverse drug reaction surveillance and pharmacovigilance: identifiable reporter, identifiable patient, suspect product, suspect reaction. Form 3500B is the consumer instrument that captures those elements for the U.S. system.

Who can file a MedWatch report

Reporting is open. You do not need clinical credentials. Any of the following can file:

  • The patient who experienced the event
  • A family member, caregiver, or legal representative
  • The prescribing physician, NP, or PA
  • The dispensing pharmacist
  • An ER or urgent care clinician who treated the event

Multiple parties can report the same event independently; the FDA deduplicates on the back end. If your prescriber tells you they have already filed, you can still file your own. Patient-perspective detail (timeline of symptoms, what stopped the reaction, what you were doing when it started) is often what triggers a deeper FAERS review.

When you should file

The threshold is lower than most patients assume. File a MedWatch report for any of the following:

  • An unexpected reaction not listed in the patient information you received
  • Any event severe enough to make you consider stopping the medication (see when to stop AND report)
  • A product-quality concern, including warm-shipped vials, broken seals, visible particulates, or a formulation that does not match what was prescribed
  • Any event meeting the FDA "serious" criteria: hospitalization, persistent or significant disability, life-threatening event, congenital anomaly, intervention to prevent permanent impairment, or death
  • Therapeutic non-response when a clear dose response would be expected, which can indicate potency loss

For help distinguishing expected GLP-1 side effects from reportable adverse events, see how to recognize what to report.

Form 3500B vs Form 3500: which to use

The FDA publishes two parallel forms that feed the same FAERS database:

  • Form 3500B is the consumer version. Plain-language fields, optional clinical sections, designed for patients and caregivers.
  • Form 3500 is the health professional version. Structured for clinical detail, lab values, and concomitant therapy coding.

Patients should file Form 3500B. The fastest path is the online portal at the FDA's MedWatch Forms page. Paper and PDF versions are also accepted by mail or fax for those without internet access.

Form 3500B walkthrough, section by section

Section A: About the patient

Age, sex, weight, race, ethnicity, and pregnancy status if applicable. Weight is particularly relevant for GLP-1 reports because dose and outcome both correlate with body weight.

Section B: About the event

Describe what happened in plain language, then list the specifics:

  • Date the event began and date it resolved (or "ongoing")
  • Outcome: hospitalization, ER visit, disability, life-threatening, death, congenital anomaly, intervention required, or "other serious"
  • Whether the event went away after stopping (positive dechallenge) and whether it returned on restarting (positive rechallenge)
  • Any tests or labs ordered and the results, if known

Use the words your clinicians used. "Acute pancreatitis confirmed by lipase" is more useful than "stomach pain."

Section C: About the product

This is the section where compounded GLP-1 reports diverge from approved-drug reports. Cover it carefully using the conventions below.

Section D: About the reporter

Your name, contact information, and relationship to the patient. Identifying information is held by the FDA for follow-up and is not posted in the public FAERS dashboard.

Compounded-medication specifics

The product fields on Form 3500B were designed for FDA-approved drugs with a single manufacturer and a National Drug Code. Compounded preparations do not fit cleanly. Use the following conventions, which are consistent with FDA guidance for reporting on compounded human drug products:

  • Product name: exactly as printed on the vial label, including any additives. For example, "compounded tirzepatide with niacinamide" or "compounded semaglutide with B12." Generic names without a brand are correct here.
  • Manufacturer: the dispensing 503A pharmacy. Not the telehealth clinic that issued the prescription. The pharmacy name is on the vial label and on your shipping documentation.
  • NDC: may be blank. Compounded preparations are not required to carry an NDC. Leave the field blank or write "compounded, no NDC" rather than copying any number from the box.
  • Lot number: from the vial label. This is the single most important field for compounded reports. Without a lot number the FDA cannot link your report to other reports against the same batch.
  • Beyond-use date (BUD): from the vial label. For sterile compounded injectables this date is set under USP General Chapter <797> and is the equivalent of an expiration date for an approved drug.
  • Dose, frequency, route: the dose strength dispensed, your weekly injection schedule, and "subcutaneous."

For more on why these fields matter so much for compounded products, see why MedWatch matters more for compounded GLP-1. Different pharmacies, different lots, and different additive profiles can all produce different reaction profiles, and the lot number is what allows the agency to find a cluster.

What happens after you submit

You will receive an electronic confirmation immediately. Save the confirmation number. From there:

  • The report enters FAERS within a few business days.
  • An FDA safety evaluator may contact you for follow-up information. Replying is optional but helpful.
  • Identifying details are stripped before public posting. Your case appears in the public FAERS Public Dashboard as a de-identified record once it is processed.
  • The agency does not act on individual reports. It acts on aggregate signals. A single report rarely changes anything; a hundred reports against a specific pharmacy or formulation can trigger an inspection, a warning letter, or a recall.
  • You will not receive a case-by-case decision letter.

MedWatch is built to find patterns, not to adjudicate your specific harm. That work happens elsewhere.

Tell your provider too. Separately.

Filing MedWatch does not replace clinical follow-up. Your prescribing provider needs to know in order to manage the event, decide on continuation, and document the reaction in your chart. Some clinicians and most pharmacies carry parallel reporting obligations under state or federal rules, and a compounding pharmacy that hears the same complaint twice can investigate the lot directly. Do both.

Anonymity and privacy

The form collects identifying information for follow-up purposes. The FDA holds reporter and patient identifiers internally and does not release them in the public dashboard. You can decline to share your name or contact information; the report will still be accepted, but the agency will not be able to follow up for clarification, which can reduce the report's usefulness. If you are reporting on someone else's behalf, you should have their permission or be their legal representative.

A real example: when a report should be filed

One canonical case from the compounded GLP-1 market: a patient paid $576 expecting compounded tirzepatide and instead received vials of MIC (methionine, inositol, choline) and methylfolate, with the refund subsequently denied. That is a Form 3500B case. Product name as printed on the vials received, dispensing pharmacy as the manufacturer, lot numbers from the vials, and an event description distinguishing the prescribed product from what was dispensed. A wrong-formulation dispense is a product-quality event regardless of whether the patient was clinically harmed.

A second pattern worth reporting: warm-shipped vials. Multiple Trustpilot complaints have documented vials arriving warm from at least one major telehealth provider despite a written cold-chain SOP. Peptide GLP-1 medications lose potency when the cold chain breaks. Photograph the package, file a MedWatch report describing the shipping failure, and request a lot replacement. Therapeutic non-response after a warm shipment is a separate reportable event from the shipping failure itself.

Provider's adverse-event response is not MedWatch

It is common to confuse two different processes that get triggered by the same complaint:

  • Provider response: the clinical and customer-service response from the telehealth clinic and pharmacy. Refund, replacement vial, dose adjustment, switch to a different formulation, escalation to the medical director. This is private, transactional, and resolves your individual case. The quality of this response varies widely across providers and is one of the criteria we use when evaluating providers ranked by adverse-event response.
  • MedWatch: the systemic feedback loop that allows the FDA to detect emerging safety patterns across all patients on a given product. Public, aggregated, and aimed at population-level safety.

Both should happen. The provider response addresses your immediate care. The MedWatch report addresses the next patient.

FAQ

How long does it take to file Form 3500B?

Most patients complete the online form in 15 to 25 minutes if they have the vial label and dates in front of them. Locate the vial first; the lot number and beyond-use date are where people most often pause to dig through packaging.

Do I need a diagnosis to file?

No. A confirmed diagnosis improves the quality of the report, but symptoms described accurately are reportable on their own. The FDA does not gatekeep on clinical certainty.

Will my report show up publicly with my name on it?

No. The public FAERS dashboard de-identifies all individual case reports. The FDA retains identifiers internally for follow-up and deduplication.

What if my GLP-1 was compounded and the vial label is missing or unclear?

Submit anyway. Note in the description that the labeling was incomplete, including which fields were missing. Incomplete or missing labels on a sterile compounded injectable are themselves a reportable product-quality concern under USP <797> expectations.

Can I report a near-miss, like receiving a wrong formulation that I caught before injecting?

Yes. Wrong-formulation dispenses, broken seals, missing labels, and shipping failures are reportable as product-quality issues whether or not the patient was harmed. These reports are particularly valuable because they identify failures upstream of any clinical event.

Does filing MedWatch help me get a refund?

No. MedWatch does not adjudicate consumer disputes. Refunds and replacements run through your provider and pharmacy; if those channels fail, complaints to the state board of pharmacy and to the BBB are the next individual-remedy step.