11.4 Regulatory Reporting Requirements Before and After Marketing Authorisation

Regulatory Reporting Before and After Marketing Authorisation

Quick Reference: Section 9.3 teaches the clocks — the 7-day and 15-day expedited timelines under ICH E2A and the periodic safety reports. This section teaches the architecture: the full set of reporting obligations across a product's lifecycle, who owns each one, and where the information flows. Learn the routing here and the timing there; the exam tests both.

Why this is tested

The ACRP-CP Exam Content Outline lists 2C, "Regulatory reporting requirements (e.g., pre- and post-approval, safety)" in Domain 2, and 3E, "Study reporting requirements (e.g., SAEs, deviations, INDs, IRB)" in Domain 3. Between them they ask a single question in many forms: given this event, who has to tell whom?

---

The reporting map

Exam Watchout: The site never reports a SUSAR directly to a regulatory authority. The investigator's safety obligation runs to the sponsor; the sponsor holds the pharmacovigilance database, performs the expectedness assessment against the Reference Safety Information, and reports onward. Items that place the investigator in direct expedited correspondence with an authority are testing exactly this misconception.

---

Part 1 — Reporting during development (pre-approval)

Expedited reporting of SUSARs

Annex 1 3.13.2(b) requires the sponsor, in accordance with applicable regulatory requirements and with ICH E2A, to "expedite the reporting to the regulatory authority(ies) of all suspected, unexpected and serious adverse reactions (i.e., SUSARs)."

Three tests must all be satisfied before an event becomes a SUSAR:

SERIOUS?      Meets an E2A seriousness criterion
                  │ yes
UNEXPECTED?   Nature or severity not consistent with the applicable
              product information — normally the RSI in the IB
                  │ yes
RELATED?      A reasonable possibility of a causal relationship
              with the investigational product
                  │ yes
              ───► SUSAR → sponsor expedites to authorities

Fail any one test and it is not a SUSAR. A serious, related but expected reaction is captured in the periodic safety report rather than expedited; a serious, unexpected event with no reasonable causal possibility likewise.

Expectedness is judged against the RSI

Annex 1 3.13.2(c): safety reporting to authorities "should be undertaken by assessing the expectedness of the reaction in relation to the applicable product information (e.g., the reference safety information (RSI) contained within the Investigator's Brochure or alternative documents)."

Two operational consequences that generate exam items:

1. The RSI version in force at the time of assessment governs. When the IB is updated, previously unexpected reactions may become expected and vice versa. Sites must know which IB edition is current — see section 11.3.
2. Severity is part of expectedness. An event listed in the RSI as mild is unexpected when it occurs at a severity or specificity the RSI does not describe.

Information back to the sites

Annex 1 3.13.2(d) requires SUSAR reporting to investigators and IRBs/IECs to be done "in a manner that reflects the urgency of action required", taking account of the evolving knowledge of the product's safety profile. It expressly notes that "in some regions, periodic reporting of line listings with an overall safety assessment may be appropriate."

This is why sites receive a mixture of individual safety letters and periodic line listings. Both require the same site actions: review by the investigator, submission to the IRB/IEC per its requirements, filing in the investigator site file, and consideration of whether the consent form's risk description remains accurate.

Urgent safety issues

Annex 1 3.13.2(e): urgent safety issues requiring immediate attention or action "should be reported to the IRB/IEC and/or regulatory authority(ies) and investigators without undue delay."

Note the breadth: this is not limited to individual case reports. A newly identified interaction, a manufacturing defect affecting supplied product, or an emerging pattern across sites all qualify. It pairs with 3.13.3, Managing an Immediate Hazard, and with the investigator's own immediate-hazard route in 2.5.4–2.5.5.

Alternative arrangements are allowed — but only prospectively

Annex 1 3.13.2(f) permits alternative safety reporting arrangements, for example where certain SAEs are exempt from immediate reporting because they are protocol-defined efficacy endpoints or expected disease progression in a mortality trial. The conditions are strict: such arrangements must be "prospectively agreed upon with the regulatory authority(ies) and, if applicable, the IRB/IEC, and described in the clinical trial protocol."

Exam Watchout: "The protocol says deaths due to disease progression are not reported as SAEs" is only a valid answer if the arrangement was prospectively agreed and written into the protocol. A sponsor deciding mid-trial to stop expediting a category of events, however sensible, is not covered.

Periodic reports and IB updates

Annex 1 3.13.2(a) requires the sponsor to submit "safety updates and periodic reports, including changes to the Investigator's Brochure, as required by applicable regulatory requirements." The Development Safety Update Report and its relationship to the annual reporting cycle are covered in section 9.3.

---

Part 2 — Reporting at the end of a trial, or before it

Premature termination or suspension

Both parties carry obligations, and they are examined as a pair:

The obligation candidates most often forget is the one to the participants: people who are mid-treatment must be told, and their continuing care arranged.

Clinical trial reports

Annex 1 3.17.2 requires the sponsor to ensure that clinical trial or study reports are prepared and provided to regulatory authorities as required, whether the trial completes or terminates early. A trial that stopped early still produces a report.

---

Part 3 — After marketing authorisation

Once a product is authorised, the reporting obligations do not end; they change shape. The ACRP-CP Exam Content Outline explicitly says "pre- and post-approval", so the categories are worth knowing even though the exam does not test any one country's post-marketing statute.

Exam Watchout: A Phase IV trial of an authorised product is still a clinical trial, and every GCP obligation in this guide applies to it in full — IRB/IEC approval, informed consent, the protocol, essential records, safety reporting. What changes is that the product is authorised, so Principle 7.2 becomes central: the relevant risk is the increment beyond usual medical care, not the total risk of treating the condition, and oversight is calibrated accordingly.

---

Realistic exam scenario

Scenario: On a Tuesday morning a coordinator learns that a participant enrolled in a Phase II hepatology trial was admitted overnight with acute liver failure and died. The protocol lists "elevated transaminases" as an expected reaction in the Reference Safety Information; acute liver failure is not listed. The coordinator's institution requires all in-hospital deaths to be reported to its patient safety office. The site's monitor is on annual leave. The principal investigator asks whether the site should file an expedited report with the national regulatory authority itself, since "seven days is not long and nobody is answering at the sponsor."

Evaluation:

• The event is serious (fatal), unexpected — acute liver failure is not the same as elevated transaminases, and severity is part of the expectedness judgement — and there is at least a reasonable possibility of causality in a hepatology trial. On the face of it, a SUSAR.
• The site must not report to the regulatory authority. Under Annex 1 2.7.2 the investigator's obligation runs to the sponsor, and under 3.13.2(b) the sponsor performs the expectedness assessment against the current RSI and expedites onward. A site-initiated regulatory filing bypasses the pharmacovigilance database and risks duplicate, inconsistent or incomplete reporting.
• The monitor's absence is irrelevant. Safety reporting goes to the sponsor's designated safety contact through the route named in the protocol and safety management plan, not through the monitor.
• The institutional patient safety report is a separate internal obligation that runs in parallel; it neither satisfies nor replaces the trial safety report.

Correct actions: report the SAE to the sponsor's safety contact immediately using the protocol's route; complete the SAE form with the information available rather than waiting for the full picture, and follow up; notify the IRB/IEC per its own requirements; record the event in the source documents and eCRF; file the institutional report separately; and, once the sponsor's assessment returns, review whether the consent form's risk description and the IB's Reference Safety Information need to change — and whether other participants require additional monitoring under 3.13.3.