Writing the Actions Taken for Safety Reasons Section in a PBRER

The Actions Taken for Safety Reasons section records significant measures taken during the reporting interval because of safety concerns. Its purpose is to show how safety information has already influenced regulatory or company action and to establish context for the scientific evaluations that appear later in the PBRER.

Regulatory Basis and Purpose

The section is part of the PBRER structure described in ICH E2C(R2) and is implemented in the EU through the PSUR framework in GVP Module VII.

The section is primarily contextual. It should tell the assessor:

• what important safety-related action occurred;
• when it occurred;
• where it applied;
• whether it was company-initiated or authority-driven where relevant; and
• which safety issue gave rise to the action.

It should not reproduce the complete scientific assessment supporting the action. That evidence belongs in the appropriate signal, risk and benefit-risk sections.

What Belongs in This Section

An item generally belongs here when an action was taken because of safety information and the action is significant enough to affect understanding or management of the medicinal product.

Examples may include:

• restriction of an indication or patient population;
• addition or strengthening of a contraindication, warning or precaution;
• an important safety-related product-information change;
• introduction or major modification of a risk-minimisation measure;
• distribution of an important safety communication such as a DHPC;
• suspension, revocation or withdrawal for safety reasons;
• an important safety-related change to study or monitoring arrangements; or
• other significant regulatory or company action intended to reduce risk.

The exact inclusion decision depends on significance and context rather than on a rigid catalogue.

What Usually Does Not Belong

The section should not become a list of every regulatory or operational event during the interval.

Items usually outside scope include:

• commercial withdrawal unrelated to safety;
• routine administrative variations;
• organisational restructuring;
• manufacturing or supply changes with no safety consequence;
• ordinary procedural updates; and
• regulatory reviews that have not yet resulted in an implemented safety action.

A useful test is: what safety concern caused this action? If no meaningful safety rationale exists, another PBRER section is usually more appropriate.

Action Versus Ongoing Review

Authors should distinguish an implemented action from an ongoing regulatory or scientific review.

For example, initiation of a referral or authority request for data may be important, but it is not automatically an action taken for safety reasons in the sense intended by this section. If the review results in a temporary restriction, product-information change or communication during the interval, that implemented measure belongs here.

Where the status remains unresolved at the data lock point, describe the current position accurately and avoid presenting a proposal as an agreed regulatory outcome.

Relationship With Later PBRER Sections

This section introduces regulatory consequences; later sections explain the science.

A safety action mentioned here should be consistent with:

• the signal evaluation;
• evaluation of risks and new information;
• characterisation of important risks;
• risk-minimisation discussion;
• integrated benefit-risk evaluation; and
• conclusions and actions.

Consistency does not mean repetition. The same issue should develop through the report: action here, evidence and interpretation later, integrated consequence at the end.

Organising the Section

The section should help the assessor understand major safety developments quickly. A purely chronological list can work for a very simple reporting interval, but grouping related actions by safety issue is often clearer when one concern led to several measures.

For example, one signal may result in:

• strengthened warnings;
• a DHPC;
• revised monitoring recommendations; and
• additional educational material.

These are better presented as one connected regulatory response than as four unrelated entries.

Unrelated actions should remain separate so the report does not imply a common scientific cause where none exists.

Information to Include for Each Important Action

A concise action description should normally allow the reader to understand:

• the safety issue;
• the action taken;
• the date or relevant timing;
• the jurisdiction or geographic scope;
• the initiator or regulatory context when important; and
• the current status at the data lock point.

The amount of detail should be proportionate. A temporary suspension affecting a major indication needs more explanation than a minor wording refinement arising from the same established risk.

Regional Differences

Different authorities may act differently on the same evidence. One country may introduce a contraindication while another requests further analysis, or implementation dates may differ.

The PBRER should describe these differences factually. It should not imply that differing regulatory decisions are inconsistent merely because they are not identical.

Where regional variation is important to interpretation, explain the scope and known reason briefly and carry the scientific implications into the later risk and benefit-risk discussion.

Company-Initiated Actions

An MAH may take precautionary action before a competent authority completes its review. Such actions can belong in this section when they are significant and safety-driven.

The wording should make the regulatory status clear. Distinguish:

• a company proposal;
• a company-implemented precautionary measure;
• an authority-requested action;
• an authority-approved action; and
• a legally binding regulatory decision.

This prevents the report from presenting internal intent as regulatory agreement.

Temporary Measures

Temporary measures require careful wording because their status may change after the reporting interval. A temporary restriction, suspension or enhanced monitoring measure should be described as temporary if that is its actual status at the data lock point.

The report should also make clear whether further review is ongoing and avoid predicting the final regulatory outcome.

Product-Information Changes

Safety-related changes to product information commonly belong in this section when they are significant. Examples include new or strengthened contraindications, warnings, precautions, monitoring recommendations or adverse-reaction information.

Do not reproduce the revised wording in full unless necessary to understand the action. The section should summarise the clinical significance and point the reader toward the later scientific evaluation.

Risk-Minimisation Measures

New or substantially changed additional risk-minimisation measures may also belong here. The description should focus on:

• the important risk addressed;
• the measure introduced or changed;
• the relevant population or setting; and
• the geographic scope.

Detailed evaluation of effectiveness belongs in the appropriate later section or RMP context, not in this introductory regulatory-history section.

Safety Communications

Important communications such as DHPCs can be safety actions, particularly where they form part of a broader risk-management response. The report should describe the safety issue, communication objective and scope without turning the section into a distribution log.

Marketing-Authorisation Measures

Suspension, revocation, withdrawal, restriction of indication or narrowing of the treated population for safety reasons are usually important enough to require clear description.

Commercial withdrawal should not be misclassified as a safety action merely because safety information existed elsewhere in the product history.

Illustrative Writing Example

Consider a hypothetical reporting interval in which evaluation of hepatotoxicity led to strengthened product information and a DHPC in several EU countries.

A weak entry would read:

The label was updated and a DHPC was sent because of liver cases.

A stronger entry would explain that, during the reporting interval, evaluation of cumulative hepatic injury reports resulted in strengthening of the warning and monitoring recommendations in the applicable product information and distribution of a DHPC in specified jurisdictions. The detailed evidence and risk characterisation would then be discussed in the later signal and risk sections.

The stronger version gives the assessor the regulatory context without prematurely reproducing the assessment.

Common Writing Failure Modes

The following are illustrative writing failures, not inspection findings.

Practical Review Checklist

1. Was each included action genuinely taken for safety reasons?
2. Is the action significant enough to merit inclusion?
3. Is the date or timing clear?
4. Is geographic scope described where relevant?
5. Is company versus authority status accurate?
6. Are temporary and permanent measures distinguished?
7. Are ongoing reviews separated from implemented actions?
8. Is the scientific rationale summarised without duplicating later assessment?
9. Are related actions grouped logically?
10. Are important regional differences explained objectively?
11. Does every major action reconcile with signal, risk and benefit-risk sections?
12. Are proposed actions distinguished from actions already implemented or agreed?

Relationship With Other QPPV.com PBRER Articles

This article addresses one PBRER section only. For the overall scientific architecture see [[understanding-the-structure-of-a-pbrer]]. For the broader regulatory framework see [[pbrer-guide]]. Detailed authoring across the complete report is covered in [[how-to-write-a-pbrer]].

Key Takeaways

The Actions Taken for Safety Reasons section provides regulatory context for the reporting interval; it is not a complete safety assessment.

Include significant actions that were actually taken because of safety concerns, and exclude routine administrative or commercial events unless safety was the reason for the action.

Distinguish implemented action from ongoing review, and distinguish company proposals from agreed or imposed regulatory decisions.

Group related actions when they arise from the same safety concern, but preserve regional differences where these matter.

The section should connect naturally to later signal, risk and integrated benefit-risk discussions without duplicating them.

References

1. International Council for Harmonisation. ICH E2C(R2): Periodic Benefit-Risk Evaluation Report (PBRER). Step 4, 15 November 2012.
2. International Council for Harmonisation. ICH E2C(R2) Questions and Answers. Updated 31 March 2014.
3. European Medicines Agency. GVP Module VII — Periodic safety update report (Rev. 1). EMA/816292/2011 Rev. 1.
4. European Medicines Agency. Periodic safety update reports (PSURs). Current EMA procedural guidance.
5. European Union. Commission Implementing Regulation (EU) No 520/2012, as amended.
6. European Union. Directive 2001/83/EC, as amended.
7. European Union. Regulation (EC) No 726/2004, as amended.

Regulatory Note

This article explains the ICH E2C(R2) PBRER section on actions taken during the reporting interval for safety reasons and its EU PSUR implementation. It does not create additional reporting categories beyond the applicable ICH/GVP framework. As of 9 September 2026, GVP Module VII Rev. 1 remains the published EMA module; current procedural guidance should be checked for submission-specific requirements.