Safety Specification

Introduction

The Safety Specification is the scientific foundation of the Risk Management Plan (RMP). It describes the current understanding of a medicinal product's safety profile and identifies the risks and uncertainties that require ongoing management.

Every important pharmacovigilance activity and every risk minimisation measure within an RMP should be traceable to the Safety Specification. If a risk is not considered important enough to appear in the Safety Specification, it is unlikely to justify additional risk management activities.

The purpose of the Safety Specification is therefore not merely to describe adverse reactions. Its purpose is to identify the safety concerns that are important for the ongoing evaluation and management of the product's benefit-risk balance.

Why the Safety Specification Exists

At the time of marketing authorisation, knowledge of a product's safety profile is incomplete.

Clinical trials provide important information but have limitations:

• Limited patient numbers
• Restricted study durations
• Selected patient populations
• Controlled treatment conditions

Important uncertainties frequently remain after approval.

The Safety Specification identifies these uncertainties and determines which risks require further monitoring, investigation or risk minimisation.

The Role of the Safety Specification Within the RMP

The Safety Specification sits at the centre of the RMP.

A simplified model is:

Safety Specification
        ↓
Safety Concerns
        ↓
Pharmacovigilance Plan
        ↓
Risk Minimisation Plan

The Safety Specification drives the remainder of the document.

Changes to safety concerns frequently trigger changes to pharmacovigilance activities and risk minimisation measures.

Objectives of the Safety Specification

The Safety Specification seeks to:

• Describe known risks
• Identify potential risks
• Identify missing information
• Characterise safety uncertainties
• Support benefit-risk evaluation
• Justify risk management activities

The objective is not to create a comprehensive list of all adverse reactions.

Rather, the objective is to identify issues that are important for ongoing risk management.

Sources of Information

The Safety Specification draws information from multiple sources.

These may include:

• Non-clinical studies
• Clinical trial data
• Post-marketing experience
• Signal management activities
• Epidemiological studies
• Scientific literature
• Regulatory assessments

The resulting assessment should reflect the totality of available evidence.

Historical Development

Historically, RMPs often contained extensive lists of safety issues.

Over time, regulatory expectations evolved toward a more focused approach.

Modern RMPs emphasise:

• Important risks
• Important uncertainties
• Scientifically justified concerns

The emphasis is increasingly on relevance rather than volume.

Components of the Safety Specification

The Safety Specification generally evaluates:

• Non-clinical safety findings
• Clinical trial safety data
• Post-authorisation experience
• Safety concerns
• Missing information

The most important output is the identification of safety concerns.

Safety Concerns

Safety concerns represent issues that are important for risk management purposes.

Three categories are used:

Important Identified Risks

Risks for which sufficient evidence supports a causal relationship with the product and which are important for ongoing risk management.

Important Potential Risks

Risks for which evidence suggests a possible association but uncertainty remains.

Missing Information

Important gaps in knowledge relevant to understanding product safety.

These categories form the core of the Safety Specification.

What Makes a Risk Important?

Not every adverse reaction qualifies as an important risk.

Importance is generally determined by factors such as:

• Clinical seriousness
• Frequency
• Public health impact
• Preventability
• Effect on benefit-risk balance

A common misunderstanding is that all listed adverse reactions should appear within the Safety Specification.

This is not the case.

Only risks important for risk management purposes should be included.

Important Identified Risks

An Important Identified Risk is a risk for which sufficient evidence supports an association with the product.

Examples may include:

• Serious hepatotoxicity
• Severe hypersensitivity reactions
• Major cardiovascular events
• Significant drug interactions

The designation requires both evidence and importance.

A causal relationship alone is insufficient.

Important Potential Risks

An Important Potential Risk exists when available information suggests a possible association but available evidence remains insufficient for confirmation.

Examples may arise from:

• Signal assessments
• Class effects
• Non-clinical findings
• Early clinical observations

Potential risks frequently require additional pharmacovigilance activities.

Missing Information

Missing Information represents areas where knowledge is insufficient.

Examples may include:

• Pregnancy exposure
• Paediatric use
• Long-term exposure
• Severe organ impairment

Missing Information should be clinically relevant and capable of influencing understanding of product safety.

Relationship to Signal Management

Signal management is one of the principal drivers of Safety Specification updates.

Signals may result in:

• New identified risks
• New potential risks
• Reclassification of risks
• Resolution of uncertainties

Consequently, the Safety Specification should not be viewed as a static section.

It evolves continuously throughout the product lifecycle.

Relationship to Benefit-Risk Evaluation

The Safety Specification contributes directly to benefit-risk evaluation.

The importance of a safety concern depends upon:

• Severity
• Frequency
• Reversibility
• Treatability
• Therapeutic context

The same adverse reaction may have different significance depending upon the product and indication.

For this reason, risk characterisation should always occur within a benefit-risk framework.

Relationship to Additional Pharmacovigilance Activities

Additional pharmacovigilance activities should be linked to specific safety concerns.

Examples include:

• PASS studies
• Registries
• Enhanced monitoring programmes

A useful regulatory principle is:

Every activity should address a safety concern.

Activities without a clear rationale are difficult to justify.

Relationship to Additional Risk Minimisation Measures

Additional risk minimisation measures should also be linked to safety concerns.

Examples include:

• Educational materials
• Pregnancy prevention programmes
• Controlled access systems

The Safety Specification provides the scientific justification for these interventions.

Removal of Safety Concerns

Safety concerns may be removed when evidence demonstrates that they are no longer important for risk management purposes.

Removal decisions should be supported by:

• Scientific evidence
• Regulatory justification
• Updated benefit-risk evaluation

The absence of recent reports alone is rarely sufficient.

Common Mistakes

Several recurring problems occur when developing Safety Specifications.

Excessive Numbers of Risks

Large lists of risks reduce focus and dilute risk management efforts.

Inclusion of Routine Adverse Reactions

Not all adverse reactions require inclusion as safety concerns.

Weak Justification

Risks are included without clear scientific rationale.

Failure to Remove Obsolete Concerns

Outdated risks remain indefinitely.

Poor Linkage to Activities

Additional activities are not linked to defined safety concerns.

These issues frequently attract regulatory scrutiny.

Inspection Considerations

Inspectors may review:

• Safety concern justification
• Linkage between risks and activities
• Signal-to-RMP integration
• Governance processes
• Lifecycle management

A recurring inspection theme is whether safety concerns remain scientifically justified.

Role of the QPPV

The QPPV should understand:

• Major safety concerns
• Important uncertainties
• New safety concerns
• Significant changes to the Safety Specification

The QPPV is often expected to explain how safety concerns influence broader pharmacovigilance and risk management activities.

Characteristics of a Well-Written Safety Specification

A mature Safety Specification generally demonstrates:

• Scientific justification
• Focus on important concerns
• Clear risk characterisation
• Appropriate linkage to activities
• Effective lifecycle management
• Consistency with benefit-risk evaluation

The objective is not to create the longest possible list of risks.

The objective is to identify the risks that genuinely require active management.

Key Takeaways

The Safety Specification is the scientific foundation of the RMP.

It identifies important risks and uncertainties that require ongoing management.

The three core categories are Important Identified Risks, Important Potential Risks and Missing Information.

All major pharmacovigilance activities and risk minimisation measures should be linked to safety concerns described within the Safety Specification.

A well-developed Safety Specification supports effective risk management, benefit-risk evaluation and lifecycle management throughout the product's market presence.

References

1. EMA Good Pharmacovigilance Practices (GVP) Module V – Risk Management Systems.
2. EMA Risk Management Plan Template.
3. Commission Implementing Regulation (EU) No 520/2012.
4. Regulation (EC) No 726/2004.
5. Directive 2001/83/EC.
6. ICH E2E Pharmacovigilance Planning.
7. EMA Guidance on Safety Concerns and Risk Management Planning.