Writing the Signal Evaluation Section in a PBRER

The signal section of a PBRER explains the scientifically important signal activity relevant to the reporting interval and the current safety profile. It should not reproduce the operational signal tracker. Its role is to show which safety hypotheses were important, how they were evaluated, what was concluded and how those conclusions affect the later risk and benefit-risk sections.

Purpose and Regulatory Framework

The PBRER format is defined by ICH E2C(R2) and implemented for EU PSURs through Commission Implementing Regulation (EU) No 520/2012 and GVP Module VII — Periodic safety update report (Rev. 1). Signal-management principles are described in GVP Module IX — Signal management (Rev. 1), while the underlying EU signal framework was amended by Commission Implementing Regulation (EU) 2025/1466.

As of September 2026, GVP Module IX Rev. 1 remains published while EMA has stated that affected GVP guidance will be revised to align with the amended Implementing Regulation. The former MAH EudraVigilance signal-detection pilot has ended. Authors should therefore avoid copying obsolete EVDAS-monitoring obligations into a current PBRER process.

Signal Management and PBRER Reporting Are Different Systems

The operational signal-management process identifies, validates, prioritises, assesses and documents safety signals continuously. The PBRER is periodic. It takes the scientifically relevant output of that continuous process and places it in the cumulative context of the report.

This distinction matters because the PBRER should not become the place where a signal is first discovered or formally managed merely because the reporting deadline has arrived.

A well-controlled system therefore supports the flow:

signal source → validation/assessment in the signal system → documented conclusion → appropriate representation in the PBRER → risk/benefit-risk consequence.

What Is a Signal in This Context?

A safety signal is information suggesting a new potentially causal association, or a new aspect of a known association, that is judged sufficiently credible to justify further verification or assessment. It is a hypothesis, not proof of causality.

The PBRER author should distinguish:

• a potential issue or statistical alert that never met the signal threshold;
• a validated signal undergoing assessment;
• a signal whose assessment was completed during the interval;
• an issue retained for continuing surveillance after an assessment; and
• a conclusion that has become part of the characterised risk profile.

Organisation-specific status labels may differ. The scientific meaning should remain clear.

Start From the Controlled Signal Inventory

The PBRER signal section should reconcile to the organisation's controlled signal-management records. Before drafting, the team should understand:

• which signals were newly validated during the interval;
• which were already ongoing at the start of the interval;
• which assessments were completed;
• which conclusions changed the recognised safety profile;
• which significant issues remained unresolved at the DLP; and
• which regulatory actions followed completed assessments.

The aim is not to import every tracker row. It is to ensure that the report cannot omit a scientifically important signal or create a signal status inconsistent with the operational record.

Interval and Cumulative Perspective

Signal activity is interval-based, but evaluation is often cumulative. A signal opened during the current period may depend on cases accumulated over many years, while a signal opened previously may reach its conclusion during the current interval.

The writing should therefore distinguish the timing of signal-management milestones from the evidence base used for scientific assessment.

A completed assessment should not be restricted artificially to cases received during the reporting interval if cumulative evidence is relevant to the conclusion.

Writing a Completed Signal Evaluation

A completed signal discussion should make the scientific reasoning understandable without reproducing the full internal assessment report. A useful structure is:

1. define the safety question;
2. identify the main evidence sources;
3. summarise the evidence supporting the association;
4. summarise important contradictory or limiting evidence;
5. explain the interpretation; and
6. state the conclusion and consequences.

The level of detail should be proportionate to clinical importance and the effect on the product's safety profile.

Evidence Integration

Signal assessment can draw on many sources, including:

• individual case reports and case series;
• spontaneous-reporting patterns;
• clinical trials;
• observational and pharmacoepidemiological studies;
• literature;
• non-clinical or mechanistic evidence;
• class effects;
• product utilisation and exposure; and
• regulatory assessments.

The PBRER should integrate the evidence rather than list each source independently. A case series may suggest a coherent phenotype while a well-designed observational study provides important negative evidence; both belong in the reasoning.

Statistical Signal Outputs

Disproportionality and related statistical outputs can support signal detection, but they do not establish causality. Where such analyses materially contributed to an evaluation, the author should describe their relevance and limitations without presenting a threshold crossing as the scientific conclusion.

Changes in reporting can arise from stimulated reporting, increased exposure, coding changes, regulatory communications or changes in the population treated. These factors should be considered when they affect interpretation.

Case-Level Clinical Evidence

For clinically important signals, the quality of individual cases can be decisive. Relevant features may include:

• temporal relationship;
• dechallenge and rechallenge;
• alternative causes;
• dose or duration relationship;
• consistency of phenotype;
• objective diagnostic evidence; and
• biologic plausibility.

The PBRER should not reproduce every narrative. Representative clinical characteristics can be summarised where they explain the conclusion.

Ongoing Signals

An ongoing signal should be described according to what is known at the DLP. The report should avoid implying either confirmation or refutation before the assessment is complete.

Useful information can include:

• the safety question under assessment;
• why it remains unresolved;
• important evidence obtained so far;
• the main uncertainty; and
• the next scientific step where relevant.

Internal target dates and committee schedules are generally unnecessary unless they are material to understanding the status.

Signals Closed Without Confirming a Risk

A closed signal is not synonymous with “nothing happened.” A useful discussion explains why the available evidence did not support changing the current safety understanding.

Possible reasons may include:

• weak or inconsistent case evidence;
• persuasive alternative explanations;
• lack of a coherent clinical pattern;
• reassuring controlled or epidemiological evidence;
• absence of support from mechanistic or class data; or
• an observed reporting imbalance explained by surveillance or utilisation changes.

The degree of certainty should match the evidence. Some closed assessments may warrant routine continued surveillance without remaining formal signals.

Signals That Change Risk Characterisation

When a signal supports a new adverse reaction or materially changes a known risk, the signal section should make the transition visible. The later risk-evaluation section then explains the updated cumulative risk characterisation.

The same evidence should not be duplicated extensively. A useful division is:

• Signal section: how the hypothesis was assessed and what was concluded.
• Risk section: what the conclusion means for the current understanding of the risk.
• Integrated benefit-risk: what the updated risk means in the context of therapeutic benefit.

Relationship With Reference Safety Information

If a completed signal results in a change to reference safety information, the chronology should remain consistent. A signal may be scientifically concluded before the corresponding label procedure is approved or implemented.

The PBRER should distinguish the scientific conclusion from the regulatory status of the label change. This avoids presenting a company proposal as an authority-approved outcome.

Relationship With the RMP

Not every signal becomes an RMP safety concern. A completed signal may:

• support a new important identified risk;
• strengthen or weaken an important potential risk;
• improve characterisation of an existing risk;
• have no effect on the RMP because it is not sufficiently important for risk-management planning; or
• lead to a proposed RMP change subject to the applicable regulatory procedure.

The PBRER should reflect scientific consistency without treating signal closure as an automatic RMP reclassification rule.

Illustrative Example

Suppose a signal concerns acute pancreatitis. During assessment, several well-documented cases show compatible time to onset and dechallenge, but common competing causes are present in many reports. A controlled observational study shows no clear increase in risk, although the confidence interval remains wide for a rare outcome.

A weak PBRER entry would list the number of cases and conclude that the signal was closed.

A stronger discussion would explain the clinical pattern, the important confounding, the contribution and limitations of the observational evidence, and why the totality of evidence was insufficient—or sufficient—to change the product's safety profile. The later risk section would then reflect any resulting reclassification.

Potential Writing Failure Modes

The following are illustrative writing failures, not inspection findings.

Cross-Section Reconciliation

Before finalisation, reconcile the signal section with:

• the controlled signal inventory;
• Actions Taken for Safety Reasons;
• Changes to Reference Safety Information;
• Evaluation of Risks and New Information;
• the RMP where relevant;
• the Integrated Benefit-Risk Evaluation; and
• Conclusions and Actions.

A signal should not be “ongoing” in one section, “refuted” in another and an “identified risk” in a third unless the chronology explains the difference.

Practical Authoring Checklist

1. Does the section reconcile to the controlled signal inventory?
2. Are new, ongoing and completed signal activities represented accurately?
3. Is the scientific question defined clearly?
4. Are interval milestones distinguished from cumulative evidence?
5. Are supporting and contradictory data integrated?
6. Are statistical outputs interpreted rather than treated as causal proof?
7. Are important case-level features summarised where useful?
8. Is uncertainty calibrated appropriately for ongoing signals?
9. Does each completed signal have a clear conclusion?
10. Are resulting risk, RSI and RMP consequences consistent?
11. Are obsolete EudraVigilance pilot requirements absent from current-process descriptions?
12. Does the later benefit-risk evaluation reflect materially important signal conclusions?

Relationship With Other QPPV.com Articles

For signal concepts see [[what-is-a-safety-signal]]. The continuous lifecycle is covered in [[signal-management]], with specialist articles on [[signal-detection]], [[signal-validation]], [[signal-prioritisation]] and [[signal-assessment]]. For PBRER integration see [[writing-the-evaluation-of-risks-and-new-information-section-in-a-pbrer]] and [[writing-the-integrated-benefit-risk-evaluation-section-in-a-pbrer]].

Key Takeaways

The PBRER signal section reports the scientifically important output of continuous signal management; it should not duplicate the operational signal-management system.

A signal is a hypothesis requiring evaluation, and statistical alerts or case counts do not by themselves establish causality.

Completed evaluations should integrate supporting and contradictory evidence and state clearly what conclusion was reached and what changed as a result.

Signal conclusions should flow consistently into risk evaluation, reference information, the RMP where relevant and the integrated benefit-risk assessment.

References

1. International Council for Harmonisation. ICH E2C(R2): Periodic Benefit-Risk Evaluation Report (PBRER). Step 4, 15 November 2012.
2. European Medicines Agency. GVP Module VII — Periodic safety update report (Rev. 1). EMA/816292/2011 Rev. 1.
3. European Medicines Agency. GVP Module IX — Signal management (Rev. 1). EMA/827661/2011 Rev. 1.
4. European Medicines Agency. GVP Module IX Addendum I — Methodological aspects of signal detection from spontaneous reports. EMA/209012/2015.
5. European Medicines Agency. Questions and answers on Implementing Regulation (EU) 2025/1466 and conclusion of the Signal Detection in EudraVigilance Pilot by MAHs. Current 2026 version.
6. European Union. Commission Implementing Regulation (EU) No 520/2012, as amended by Commission Implementing Regulation (EU) 2025/1466.
7. European Union. Directive 2001/83/EC, as amended.
8. European Union. Regulation (EC) No 726/2004, as amended.

Regulatory Note

As of 9 September 2026, GVP Module IX Rev. 1 remains the published EMA signal-management module, while EMA states that affected GVP guidance will be revised following Implementing Regulation (EU) 2025/1466. The former MAH EudraVigilance signal-detection pilot has ended. Internal signal timelines, scoring systems, committee structures and QPPV sign-off models should not be presented as universal EU requirements.