Adverse Event Reporting for Retatrutide: What Clinic Owners Are Obligated to Document and Report

When a clinic administers retatrutide under an IRB-approved research protocol, adverse event reporting becomes a formal obligation — not a best practice, but a regulatory requirement. Understanding what you are obligated to document, what you are obligated to report, and to whom, is essential before you administer the first dose.

An adverse event (AE) in a research context is any untoward medical occurrence in a research subject, regardless of whether it is considered related to the investigational compound. This is a broader definition than most clinicians are accustomed to. It includes:

• Expected side effects that occur at the anticipated frequency and severity (nausea, injection site reactions, GI symptoms)
• Unexpected side effects — anything not described in the research protocol or consent document
• Medical events that occur during the study period, even if they appear unrelated to the compound
• Laboratory abnormalities that are clinically significant

The key point is that you do not get to decide in advance what is reportable. If it happens to a research subject during the study period, it needs to be documented.

Adverse events are classified by severity, and the reporting obligations differ by classification.

Non-serious adverse events are those that do not meet the criteria for serious. They are documented in the patient's research record and reported to the IRB on the schedule specified in your protocol — typically in periodic progress reports (annually or semi-annually, depending on the IRB).

Serious adverse events (SAEs) are those that result in death, are life-threatening, require hospitalization or prolonged hospitalization, result in persistent or significant disability, or are considered medically significant by the investigator. SAEs must be reported to the IRB promptly — typically within 7 to 10 calendar days of the investigator becoming aware of the event.

Unexpected serious adverse events (USAEs) — serious adverse events that are not described in the research protocol or consent document — carry the most urgent reporting obligations. These must be reported to the IRB immediately, typically within 24 to 72 hours.

For every adverse event, your documentation should include:

• The date the event occurred and the date you became aware of it
• A description of the event, including onset, duration, severity, and outcome
• The investigator's assessment of whether the event is related to the investigational compound (unrelated, possibly related, probably related, definitely related)
• Any action taken in response to the event (dose modification, discontinuation, medical treatment)
• The outcome of the event (resolved, ongoing, unknown)

This documentation belongs in the patient's research record — separate from, but cross-referenced with, their clinical chart.

Your IRB will specify the reporting requirements in your protocol approval. Read those requirements carefully and build a system for tracking adverse events from day one. Do not rely on memory or informal notes. A formal adverse event log — even a simple spreadsheet — is better than nothing.

When you submit an SAE report to the IRB, include all of the documentation elements listed above, plus any relevant medical records, laboratory results, or imaging. The IRB may request additional information or require a protocol modification in response to the report.

In addition to IRB reporting, serious adverse events involving investigational compounds may trigger FDA MedWatch reporting obligations. If you are operating under an IND (Investigational New Drug application), the IND sponsor has specific reporting obligations to the FDA. If you are operating under an IRB protocol without an IND, consult with your healthcare counsel about whether MedWatch reporting is required for your specific situation.

Adverse event reporting is not just a regulatory obligation. It is how the medical community learns about the safety profile of investigational compounds. The TRIUMPH trial data that makes retatrutide compelling was generated through rigorous adverse event reporting. When clinic owners administer investigational compounds without documenting and reporting adverse events, they are not just creating legal exposure — they are failing to contribute to the evidence base that will ultimately determine whether this compound gets approved and how it should be used.

Before you administer the first dose of retatrutide under your IRB protocol, you should have:

• A designated adverse event log for your research study
• A clear internal process for who is responsible for documenting and reporting adverse events
• Contact information for your IRB's adverse event reporting line
• A calendar reminder for periodic progress report submissions
• A clear understanding of what constitutes a serious adverse event under your protocol

This infrastructure does not need to be elaborate. It needs to be consistent and documented.