What is a PSUR?

Periodic Safety Update Reports (PSURs) are among the most important regulatory documents used to monitor the safety of medicinal products after marketing authorisation. They provide regulators and marketing authorisation holders with a structured mechanism for reviewing accumulated safety information, assessing the benefit‑risk profile of a product and determining whether changes to product information, risk‑minimisation activities or regulatory actions may be necessary.

For Qualified Persons Responsible for Pharmacovigilance (QPPVs), PSURs form a core component of pharmacovigilance governance. Specialist writing teams prepare the reports, but QPPVs are expected to maintain awareness of significant safety issues, signal conclusions, benefit‑risk determinations and regulatory commitments arising from aggregate safety reporting.

Table of Contents - What is a PSUR? - Why PSURs Exist - Regulatory Basis and Context (Inline References) - PSUR versus PBRER — Key Differences and Practical Convergence - The PSUR Lifecycle and Core Steps - Data Lock Point (DLP) — Management and Inspection Relevance - Downloadable DLP Log Template (Fully Worked) - Exposure Data — Importance and Estimation Approaches - Downloadable Exposure Worksheet Template (Fully Worked) - Signal Evaluation and Benefit‑Risk Assessment - Governance and Roles — Who Does What - Inspection Relevance — What Inspectors Look For - Quality Assurance, Archiving and Vendor Oversight - Role of the QPPV — Oversight and Sign‑Off - Practical Checklists, Timelines and Traceability - Conclusion

What is a PSUR?

A Periodic Safety Update Report is a regulatory document that provides a comprehensive review of the cumulative safety experience of a medicinal product over a defined reporting interval. Unlike individual adverse event reports that focus on specific cases, PSURs examine aggregated data and evaluate whether the overall understanding of the product's safety profile has changed.

The purpose of a PSUR is to answer the central question:

Does the totality of available evidence continue to support a positive benefit‑risk balance?

To answer this, PSURs integrate information from multiple sources including spontaneous adverse event reports, clinical studies, scientific literature, regulatory actions, signal evaluations and post‑authorisation safety activities.

Why PSURs Exist

Medicinal products continue to generate new information long after initial approval. New safety information may emerge through:

• Spontaneous adverse event reporting
• Scientific literature monitoring
• Clinical trials and extension studies
• Post‑authorisation safety studies (PASS)
• Epidemiological investigations
• Signal detection activities
• Regulatory authority communications
• Product quality investigations
• Risk‑minimisation effectiveness assessments

PSURs permit collective review and interpretation of these diverse sources, placing event counts in the context of product exposure and clinical benefit.

Regulatory Basis and Context (Inline References)

PSUR requirements and expectations are codified in regional law and international guidance. The following references should be used as primary guidance when designing PSUR processes and artefacts (inline citations included at the point of use):

• ICH E2C(R2) Periodic Benefit‑Risk Evaluation Report (PBRER) — primary international standard for the narrative structure and integrated benefit‑risk approach. See ICH E2C(R2) for detailed section descriptions and recommended content (ICH E2C(R2), 2016) [source: ICH E2C(R2) guideline].
• EMA Good Pharmacovigilance Practices (GVP) Module VII — EU operational guidance for PSURs, DLP management and submission pathways (EMA GVP Module VII, current revision) [source: EMA GVP Module VII].
• EU pharmacovigilance legislation — Directive 2001/83/EC and Regulation (EC) No 726/2004 specify statutory obligations for periodic reporting and MAH responsibilities; use these texts for legal deadlines and obligations.
• National regulatory guidance — local authorities may specify format, frequency and regional aggregation rules (e.g., MHRA, FDA cross‑references for PBRER where applicable). Always reconcile global PSUR planning with jurisdictional requirements.

When preparing a PSUR intended to meet multiple jurisdictions, the ICH E2C(R2) PBRER framework is the practical baseline; append jurisdiction‑specific modules or tables to meet local needs (see "PSUR versus PBRER" and "PSUR Lifecycle").

PSUR versus PBRER — Key Differences and Practical Convergence

Modern PSURs commonly adopt the PBRER structure described in ICH E2C(R2). The following comparison summarises core differences and practical implications for report preparation, and cites the relevant guidance sections:

• Focus and narrative: ICH E2C(R2) emphasises integrated benefit‑risk narrative (Sections 1–5 of the guideline). GVP Module VII maps EU expectations onto this approach for PSUR submissions.
• Exposure and methodology: ICH E2C(R2) and EMA GVP Module VII require transparent exposure methodology, assumptions and sensitivity analysis; include sources, conversion factors and uncertainty discussion.
• Signals and impact: Both guidelines expect clear documentation of signal detection, evaluation and the practical impact on benefit‑risk and labelling.
• Global applicability and appendices: Use PBRER core with jurisdictional appendices required by EU/other regulators.

Implementation note: prepare to meet PBRER content standards irrespective of the PSUR label to reduce regulatory queries and improve inspection readiness (ICH E2C(R2), EMA GVP VII).

The PSUR Lifecycle and Core Steps

Preparation of a PSUR is a cross‑functional activity requiring months of planning:

1. Planning and scheduling (master schedule aligning global cycles)
2. Determination of reporting interval (aligned to submission cycle and regulatory commitments)
3. Establishment and control of the Data Lock Point (DLP)
4. Data extraction and reconciliation (safety databases, literature, registries)
5. Exposure estimation (denominator generation) — document assumptions and sensitivity
6. Signal detection and evaluation
7. Integrated benefit‑risk assessment (PBRER narrative)
8. Drafting and quality review (medical, regulatory, QA)
9. Final sign‑off (QPPV, MAH delegate)
10. Submission and follow‑up (regulatory queries, agreed actions)

Governance touches multiple functions: pharmacovigilance, epidemiology, biostatistics, regulatory affairs, clinical development, medical affairs, quality assurance and, where applicable, commercial affiliates and suppliers.

Data Lock Point (DLP) — Management and Inspection Relevance

The Data Lock Point (DLP) is the cut‑off date for data to be included in the report. All aggregated counts, analyses and conclusions reference that date.

Regulatory and guidance context: - EMA GVP Module VII explicitly requires DLP management processes and documentation (see GVP Module VII, sections on Data Lock Points). - ICH E2C(R2) expects traceability between source data and report content; DLP is the anchor for that traceability.

Key DLP governance expectations (inspection relevance):

• The DLP must be recorded in a controlled log with rationale and change history.
• Queries and extracts must reference the DLP; line listings must show received dates relative to DLP.
• Procedures must describe handling of safety information received after DLP, including criteria for urgent submissions (e.g., reportable unexpected serious reactions that trigger expedited regulatory notification).
• Any change to an agreed DLP should be justified, documented, and approved by accountable persons (PSUR lead, QPPV delegate, regulatory affairs).
• Inspectors will expect traceability from source data to figures/tables and to the final report, all anchored to the DLP.
• DLP governance should be reflected in the Pharmacovigilance System Master File (PSMF) and relevant SOPs (cross‑reference: GVP Module I and Module VII).

Failures in DLP handling are common inspection findings: undocumented DLP, inconsistent datasets, or lack of explanation for significant post‑DLP events.

Downloadable DLP Log Template (Fully Worked)

Below is a fully worked DLP log template presented as both a readable table and a downloadable CSV block that can be copied into a spreadsheet for immediate use. Use the template to record DLP decisions, approvals, changes and post‑DLP entries. Store the completed log in the PSUR master file and PSMF.

DLP Log Template (columns explained) - DLP ID: unique identifier for the DLP entry - Product / MA number: product name and MA number or identifier - Reporting Interval: start and end dates covered - Proposed DLP date: initial proposed DLP - Approved DLP date: final approved DLP (if different) - Jurisdiction(s): EU/global/regional scope - Rationale: reason for selecting this DLP (e.g., align with EU cycle, harmonise global) - Approver name / role: who approved (PSUR lead, Head of PV, QPPV) - Approval date: date approver signed off - Change history: summary of any changes to DLP and dates - Impacted datasets: list of data sources included and note if any excluded - Post‑DLP events log ref: pointer to post‑DLP events register - Archive location / filename: where the log is stored - Version: version of DLP log entry

Worked example (single completed row shown for illustration)

Downloadable CSV (copy into a text editor and save as DLP_Log.csv):

DLP ID,Product / MA number,Reporting Interval,Proposed DLP date,Approved DLP date,Jurisdiction(s),Rationale,Approver name / role,Approval date,Change history,Impacted datasets,Post-DLP events log ref,Archive location / filename,Version
DLP-2025-001,ExampleDrug 12345,"2024-01-01 to 2024-12-31",2024-12-31,2024-12-31,"EU + RoW","Align with EU PSUR cycle; global reconciliation planned","J. Smith, PSUR Lead; A. Brown, QPPV delegate",2025-01-10,"None","Safety DB extract (v2025.01); Literature (to 2024-12-31); Sales (to 2024-12-31)","PDLPEV-2025-001","/PSURs/ExampleDrug/2025/DLP_Log_v01.csv",v1.0

Implementation details and inspection relevance: - Place the DLP log in a controlled electronic repository (with audit trail). Each entry must have approver electronic signatures or documented email approvals that are archived. - Link the DLP entry to the traceability matrix (source extraction query IDs, line listing file names and versions). - Maintain a post‑DLP events register that records date received, nature of event, initial assessment and decision (no action, expedite, follow‑up in next PSUR). Reference this register in the DLP log (see Post‑DLP events log ref). - Inspectors will request the DLP log and associated approvals; ensure that the log shows decision rationales and that it maps directly to the extracts used in the final report.

Exposure Data — Importance and Estimation Approaches

Exposure is the denominator enabling meaningful interpretation of adverse event counts. Exposure estimation must be transparent, reproducible and include uncertainty assessment.

Common data sources: - Sales units (IQVIA, IMS, national distributors) - Prescription databases (national prescription registries) - Health insurance claims - Hospital procurement records - Patient registries or PASS - Clinical trial and compassionate use databases

Common estimation approaches: - Treatment courses calculated from sales units ÷ units per course - Defined Daily Dose (DDD) approach (WHO DDD where applicable) - Patient dispensation counts (unique patients) - Patient‑years derived from average daily dose × number of units

Documentation must include assumptions (e.g., average course length, dosing), adjustments for pack size, stockpiling, parallel exports, and conversion factors. Inspectors will expect justification, sensitivity analyses and traceability to original vendor files or prescriptions (see ICH E2C(R2) and EMA GVP Module VII).

Downloadable Exposure Worksheet Template (Fully Worked)

Below is a practical exposure worksheet template with a fully worked example. It is provided as a readable table and as a downloadable CSV block ready to copy into a spreadsheet. Use the worksheet to document assumptions, sources, calculations and sensitivity analyses; retain vendor source files and reconciliation logs in the PSUR archive.

Exposure Worksheet Template (columns explained) - Worksheet ID: unique identifier - Product / MA number - Region / Country - Data source (vendor or database) - Data extraction date range - Raw units (e.g., tablets, vials, DDDs) - Conversion factor (units → courses or DDD → patient‑days) - Units per course (if applicable) - Number of courses / patients - Average duration per course (days) - Patient‑years (primary estimate) - Sensitivity bounds (low / high patient‑years) - Key assumptions (text) - Source file name / vendor report ID - Reconciled by (name / role) - Reconciliation date - Notes / uncertainties

Worked example 1 — Oral tablet (sales to patient‑years) | Worksheet ID | Product / MA number | Region | Data source | Date range | Raw units | Units per course | Number of courses | Avg duration (days) | Patient‑years | Sensitivity low/high | Key assumptions | Source file | Reconciled by | Reconciliation date | Notes | |---|---:|---|---|---:|---:|---:|---:|---:|---:|---|---|---|---|---:|---| | EXP-2025-001 | ExampleDrug 12345 | Country A | VendorSalesReport (VendorCo v1.2) | 2024-01-01 to 2024-12-31 | 120,000 tablets | 30 tablets/course | 4,000 | 30 | 4,000 × (30/365) ≈ 328 | 218 / 436 (duration 20–40 days) | Dose = 1 tab/day; one course = 30 days | VendorSales_12345_20241231.pdf | M. Patel, Epidemiologist | 2025-01-05 | Assumes no parallel export; pack size consistency confirmed |

Worked example 2 — Prescription database (chronic therapy) | Worksheet ID | Product / MA number | Region | Data source | Date range | Raw units | Units per course | Number of courses | Avg duration (days) | Patient‑years | Sensitivity low/high | Key assumptions | Source file | Reconciled by | Reconciliation date | Notes | |---|---:|---|---|---:|---:|---:|---:|---:|---:|---|---|---|---|---:|---| | EXP-2025-002 | ChronicDrug 67890 | Country B | NationalPrescriptionDB v2024 | 2024-01-01 to 2024-12-31 | 24,000 unique patients (dispensed) | n/a | 24,000 | 270 (avg days/year) | (24,000×270)/365 ≈ 17,753 | 14,000 / 20,000 (based on refill variability) | Continuous use assumption; 3 dispensations/year × 90 days | Prescriptions_67890_20241231.csv | E. Li, Epidemiologist | 2025-01-07 | Adjust for early discontinuation and stockpiling in sensitivity |

Downloadable CSV (copy into a text editor and save as Exposure_Worksheet.csv):

Worksheet ID,Product / MA number,Region,Data source,Date range,Raw units,Units per course,Number of courses,Avg duration (days),Patient-years,Sensitivity low/high,Key assumptions,Source file,Reconciled by,Reconciliation date,Notes
EXP-2025-001,ExampleDrug 12345,Country A,VendorSalesReport (VendorCo v1.2),"2024-01-01 to 2024-12-31",120000,30,4000,30,328,"218 / 436 (duration 20-40 days)","Dose = 1 tab/day; one course = 30 days","VendorSales_12345_20241231.pdf","M. Patel, Epidemiologist",2025-01-05,"Assumes no parallel export; pack size consistency confirmed"
EXP-2025-002,ChronicDrug 67890,Country B,NationalPrescriptionDB v2024,"2024-01-01 to 2024-12-31","24000 unique patients",n/a,24000,270,17753,"14000 / 20000 (refill variability)","Continuous use assumption; 3 dispensations/year × 90 days","Prescriptions_67890_20241231.csv","E. Li, Epidemiologist",2025-01-07,"Adjust for early discontinuation and stockpiling in sensitivity"

Implementation details and inspection relevance: - Save the worksheet as a controlled document with versioning. Each worksheet row must reference the vendor report filename and extraction query ID so auditors can retrieve source files. - Include calculations as live formulas in the spreadsheet (do not paste static values as the only source). Save both formula and value versions in the archive. - Provide a short Methods subsection in the PSUR that references the worksheet ID(s) and summarises assumptions and sensitivity bounds (ICH E2C(R2) expects clear exposure methodology). - Inspectors will request the worksheet and associated reconciliations to confirm your denominator calculations. Ensure reconciliations show how raw vendor units became patient‑years and that assumptions are justified.

Signal Evaluation and Benefit‑Risk Assessment

Signal discussions should be clear, structured and show how signal assessment alters the overall benefit‑risk picture. For each signal, document:

• Source of signal
• Assessment steps (case quality, plausibility, alternative explanations)
• Epidemiological evidence and exposure context
• Impact on labelling or risk‑minimisation measures
• Outcome (closed, under evaluation, confirmed, actioned)
• Linkage to benefit‑risk conclusion

Integrated benefit‑risk evaluations should summarise why the product's overall benefits continue to outweigh risks (or not), referencing clinical effectiveness, disease severity, available alternatives, frequency/seriousness of events, and risk‑mitigation effectiveness.

Inspectors often query weakly justified benefit‑risk conclusions or lack of linkage between signal outcomes and benefit‑risk decisions. Use the traceability matrix to link signal assessment minutes and decision records to the PSUR text.

Governance and Roles — Who Does What

A clear governance structure reduces inspection risk. Typical roles and responsibilities:

• PSUR Lead: project management, schedule, coordination of contributors, DLP control.
• Safety Physician / Medical Reviewer: clinical interpretation, benefit‑risk authoring.
• Epidemiologist/Biostatistician: exposure estimation, observed/expected analyses, signal quantification.
• PV Writer(s): drafting, integration of sections, data visualisation.
• Regulatory Affairs: jurisdictional submission strategy, regulatory intelligence.
• QPPV / Delegate: oversight, final sign‑off and attestation of pharmacovigilance system effectiveness.
• Quality Assurance: process audits, report quality control and archive integrity.
• Vendors/Contract Research Organisations (CROs): contracted responsibilities documented with oversight and evidence of deliverable acceptance.

Governance expectations include documented SOPs, delegation logs, training records, vendor contracts, and records of internal review meetings.

Practical governance controls to include: - RACI matrix for PSUR activities contextualised by report section (who Responsible, Accountable, Consulted, Informed). - Documented authorisation matrix for DLP decisions and post‑DLP handling. - QA gate checklists with mandatory artefacts before submission (DLP log, exposure worksheet, traceability matrix, QPPV attestation). - Internal audit plan that includes retrospective review of PSUR documentation against submitted reports.

Inspection Relevance — What Inspectors Look For

Inspectors commonly request evidence that PSUR processes operate within a robust pharmacovigilance system. Typical expectations and documents to present:

• PSUR schedule and DLP log (including approvals and changes)
• SOPs detailing PSUR preparation, DLP control, exposure estimation and PSMF cross‑references
• Data extraction queries and results, reconciliations and version history
• Line listings used for analyses and case narratives supporting signal discussions
• Exposure calculation worksheets and source invoices/reports for sales or prescription data
• Meeting minutes for signal review committees, adjudication panels and medical sign‑off
• QPPV attestation and final sign‑off records
• Vendor agreements, deliverable records and oversight evidence
• Traceability matrix linking source data → analyses → conclusions → regulatory submissions

Inspectors will probe for timeliness, data integrity, traceability and clarity of rationale for key decisions. Provide ready access to the DLP log and exposure worksheets to speed inspection activities.

Quality Assurance, Archiving and Vendor Oversight

Quality assurance must be integral. Key controls:

• Version control and secure archival of draft and final reports
• QA checklist sign‑off at predefined review gates
• Documented vendor contracts specifying deliverables, timelines and audit rights
• Regular audits of vendors and contracted service providers
• PSMF entries describing aggregate reporting processes and key personnel
• Archival retention in line with regulatory requirements and SOPs

Inspectors will review evidence of quality controls, vendor oversight and archived materials; prepare to produce both final submissions and supporting worksheets.

Role of the QPPV — Oversight and Sign‑Off

The QPPV retains overall responsibility for the pharmacovigilance system; PSUR oversight expectations include:

• Awareness of major PSUR conclusions and actions
• Confirmation that PSURs were prepared under compliant procedures
• Review of significant signals and benefit‑risk changes included in reports
• Final attestation that the pharmacovigilance system is functioning and that the report accurately reflects the safety profile

QPPV involvement should be documented through meeting minutes, sign‑off records and delegation logs. For inspection purposes, maintain an explicit QPPV sign‑off record that references the DLP ID, exposure worksheet IDs and traceability matrix.

Practical Checklists, Timelines and Traceability

Use the PSUR master file, DLP log and exposure worksheets as primary artefacts to demonstrate inspection readiness. Practical elements to include:

• PSUR master schedule with submission dates, reporting intervals and jurisdictional requirements
• DLP log entry (date, rationale, approvers, change history) — use the downloadable template
• Exposure worksheets for each region or data source with calculations and sensitivity analyses — use the downloadable template
• Traceability matrix linking report sections to worksheet IDs, data extracts and meeting minutes
• Executive one‑page DLP summary for inspectors with timeline from DLP → extraction → review → submission and signature block
• QA checklist demonstrating completion of required artefacts before submission

Traceability Matrix — Practical Tool for Inspections

Provide a simple traceability matrix linking key report components to source documents:

• Table rows: Report Section (e.g., Benefit‑Risk, Exposure, Signal X)
• Columns: Source datasets, extraction queries, line listing identifiers, meeting minutes, author/reviewer, QA check, archive location

During inspection, present the traceability matrix to rapidly demonstrate linkages.

Conclusion

PSURs—prepared in line with PBRER principles—are central to lifecycle pharmacovigilance. Making PSUR preparation inspection‑ready requires robust DLP control, transparent exposure estimation, structured signal evaluation, documented governance and traceable decision pathways. QPPVs should ensure systems, SOPs and records exist to demonstrate that PSUR conclusions are evidence‑based, reproducible and auditable.

This article adds practical, regulatory‑referenced artefacts and two fully worked, downloadable templates (DLP log and exposure worksheet) to improve navigation, inspection readiness and reproducibility. Use the templates as controlled starting points; adapt for product complexity and jurisdictional requirements, and ensure all deliverables are archived with proper version control, approvals and links to the PSUR master file and PSMF.