The ICSR is the foundational document of pharmacovigilance. Every adverse event report — whether from a clinical trial, a spontaneous report from a healthcare professional, a patient, a published case report, or a regulatory authority — is processed as an ICSR. The ICSR captures the four minimum elements required for a valid case: an identifiable patient, an identifiable reporter, a suspect product, and an adverse event.

ICSRs are transmitted electronically in the ICH E2B(R3) format to regulatory databases: FDA's FAERS (FDA Adverse Event Reporting System), EMA's EudraVigilance, and the WHO's VigiBase. The electronic format is structured with specific fields for patient demographics, suspect and concomitant medications, adverse events coded in MedDRA (Medical Dictionary for Regulatory Activities), seriousness criteria, outcome, and the reporter's causality assessment.

The medical writer's contribution to the ICSR is the case narrative — a free-text summary that tells the clinical story behind the coded data. The narrative is often the most important part of the ICSR because it provides context that coded fields cannot capture: the clinical reasoning behind the diagnosis, the temporal relationship between drug exposure and event onset, relevant medical history, dechallenge/rechallenge information, and the basis for the causality assessment.

An effective ICSR narrative follows a standardised structure. The opening sentence identifies the patient (demographics, relevant medical history) and the event. The body describes the drug exposure (start date, dose, indication), the event onset (date, symptoms, diagnosis), the clinical course (investigations, treatment, dechallenge, outcome), and the causality assessment. The narrative must be factual, concise, and clinically coherent.

Key principles for narrative writing include: use MedDRA preferred terms consistently with the coded fields; specify study days or calendar dates for all events; include dechallenge (did the event improve when the drug was stopped?) and rechallenge (did the event recur when the drug was restarted?) information when available; report the reporter's verbatim description of the event alongside the coded MedDRA term; and never include the writer's own causality assessment — report only the reporter's or investigator's assessment.

The DSUR, defined by ICH E2F, is the annual safety report for an investigational drug. It serves the same purpose during clinical development that the PBRER serves for a marketed product — a comprehensive, periodic review of the safety profile. But the DSUR has unique challenges: the data come exclusively from clinical trials (there are no post-marketing reports), the comparator may be a placebo (requiring blinding considerations), and the key question is not "is the label adequate?" but "is it safe to continue exposing research subjects?"

The DSUR is submitted to all regulatory authorities where clinical trials are ongoing, typically within 60 days of the Development International Birth Date (DIBD) — the date of the first IND authorisation or clinical trial authorisation worldwide. It covers the 12-month period from the DIBD anniversary to the next DIBD anniversary.

The DSUR follows the ICH E2F structure, which includes 18 sections. The key sections include: the Executive Summary (a concise overview of the safety assessment), the current status of the development programme (which studies are ongoing, completed, or planned), cumulative subject exposure (how many subjects have been exposed and for how long), data in summary tabulations (aggregate safety data from all studies), significant findings from clinical trials (new safety findings during the reporting period), safety findings from non-interventional studies (if any), other safety information (relevant nonclinical findings, published literature), late-breaking information (significant events that occurred after the DLP but before submission), and the overall safety assessment.

The overall safety assessment is the most important section. It must address: whether any new significant safety issues have been identified during the reporting period, whether the known risks have changed in frequency or severity, whether the current IB adequately describes the safety profile, and whether the benefit-risk balance supports continuation of the ongoing clinical trials. This assessment carries weight — if the DSUR identifies a safety concern that warrants stopping a trial, the regulators will act on it.

The PBRER (formerly the PSUR — Periodic Safety Update Report) is a comprehensive, periodic review of the safety and benefit-risk profile of a marketed medicine. Defined by ICH E2C(R2), the PBRER is submitted to regulatory authorities at defined intervals (typically 6-monthly for the first 2 years, annually for the next 3 years, and every 3-5 years thereafter, depending on the jurisdiction and product).

The PBRER is one of the most complex documents a pharmacovigilance writer produces. It integrates data from multiple sources, analyses trends in the safety profile, evaluates new safety signals, assesses the benefit-risk balance, and concludes with the author's overall assessment of whether the product information remains adequate or needs updating. The PBRER is not a simple tabulation of adverse events — it is an analytical document that requires clinical judgment, epidemiological reasoning and clear scientific writing.

The PBRER follows the ICH E2C(R2) structure, which includes 19 sections. The key sections the medical writer must master are: the worldwide marketing authorisation status (where the drug is approved, what indications, what formulations), the estimated patient exposure (from sales data, prescription data, or clinical trial data), the presentation of individual case histories (a summary and analysis of cases from all sources), the safety signal evaluation (new signals identified during the period and their evaluation), the benefit evaluation (a summary of the efficacy evidence, including any new data), and the integrated benefit-risk analysis.

The data lock point (DLP) is a critical concept: it is the date up to which data are included in the PBRER. All cases received by the DLP must be included, regardless of when they occurred. Cases received after the DLP are excluded (they will appear in the next PBRER). The medical writer must ensure that all data sources are queried with the correct DLP, and that no cases are missed or double-counted.

A pharmacovigilance system is the organisational structure, processes and procedures a marketing authorisation holder (MAH) uses to fulfil its legal obligations for safety monitoring. The system must cover: adverse event collection from all sources, case processing and regulatory reporting, signal detection and evaluation, risk management, and communication of safety information. Every MAH must have a pharmacovigilance system, and it must be documented in the Pharmacovigilance System Master File.

The Pharmacovigilance System Master File (PSMF) is a detailed description of the pharmacovigilance system. Required by EU legislation (Article 104(3)(b) of Directive 2001/83/EC), the PSMF includes: the organisational structure (including the Qualified Person for Pharmacovigilance — QPPV), the sources of safety data, the computerised systems and databases used, the quality management system, the contractual arrangements for delegated activities, and the audit schedule.

The medical writer may be involved in drafting the PSMF, but more commonly contributes to the product-specific documents that sit within the pharmacovigilance system: the Risk Management Plan (RMP), the pharmacovigilance plan, and the protocols for post-authorisation safety studies (PASS).

The Risk Management Plan is a strategic document required by the EMA for all new marketing authorisation applications. It describes the medicine's safety profile, the pharmacovigilance activities planned to monitor and characterise the risks, and the risk minimisation measures designed to prevent or reduce the risks. The RMP is a living document — it is updated throughout the product's lifecycle as new safety data emerge.

The RMP has seven modules: the safety specification (important identified risks, important potential risks, and missing information), the pharmacovigilance plan (routine and additional activities to address the safety concerns), the risk minimisation plan (routine and additional measures to minimise risks), and summary tables and annexes. The writer must understand how the safety specification drives the pharmacovigilance and risk minimisation plans — each risk must have a corresponding monitoring activity and, where needed, a minimisation measure.

The US equivalent of risk minimisation is the Risk Evaluation and Mitigation Strategy (REMS), required by the FDA when the agency determines that a REMS is necessary to ensure that the benefits of a drug outweigh the risks. A REMS may include: a Medication Guide (patient information), a Communication Plan (messages to healthcare providers), Elements to Assure Safe Use (ETASU — prescriber certification, patient enrolment, pharmacy certification, special dispensing requirements), and an Implementation System.

While both RMPs and REMS address risk management, they differ in scope and structure. The RMP is required for all new EU marketing authorisations and covers the full safety specification. REMS are required only when specific risk conditions are met and focus on specific risk minimisation elements. The medical writer working in a global environment must understand both frameworks and how they interact.

Real-world evidence (RWE) — data from electronic health records, claims databases, registries, and other non-interventional sources — is playing an increasingly important role in pharmacovigilance. Traditionally, post-marketing safety surveillance relied heavily on spontaneous reporting, which suffers from well-known limitations: under-reporting, reporting bias, the inability to calculate incidence rates (because the denominator — the number of exposed patients — is unknown), and difficulty distinguishing drug effects from disease effects.

RWE addresses some of these limitations. Electronic health records provide denominator data, enabling incidence rate calculations. Claims databases provide large, population-based datasets for comparative safety analyses. Patient registries enable long-term follow-up of specific patient populations. The pharmacovigilance writer must understand how to present RWE alongside traditional spontaneous reporting data in regulatory documents — PBRERs, signal evaluations, and benefit-risk assessments.

However, RWE has its own limitations: confounding by indication, selection bias, data quality issues, and the lack of randomisation that makes causal inference more challenging than in controlled trials. The writer must present RWE with appropriate caveats and contextualise the findings within the broader evidence base.

The pharmacovigilance regulatory landscape continues to evolve. Key trends include: increased use of electronic health record data for safety surveillance, the development of sentinel-style active surveillance systems (the FDA Sentinel System being the most advanced), the move toward more structured benefit-risk assessment frameworks, and the increasing expectation that companies will use advanced analytics (including AI/ML) for signal detection.

The writer must be prepared for these changes. Understanding the methodological framework for evaluating RWE (GRACE checklist, ISPE/ISPOR guidelines), familiarity with active surveillance concepts, and awareness of emerging technologies will be essential skills for the next generation of pharmacovigilance writers.

The Medical Dictionary for Regulatory Activities (MedDRA) is the standardised terminology used globally for coding adverse events, medical history, indications and other medical concepts in regulatory documents. Every ICSR, every PBRER, every signal evaluation, and every safety section of a CSR uses MedDRA terms. Understanding MedDRA is not optional for a pharmacovigilance writer — it is a core competency.

MedDRA is organised hierarchically: System Organ Classes (SOCs) at the top (e.g., "Cardiac disorders"), followed by High Level Group Terms (HLGTs), High Level Terms (HLTs), Preferred Terms (PTs), and Lowest Level Terms (LLTs). The Preferred Term (PT) is the level most commonly used in safety reporting and document writing. The writer must use the correct PT consistently — using different PTs for the same clinical event across documents creates confusion and can mask safety signals.

MedDRA is updated biannually, and the writer must be aware of version changes. A new MedDRA version may introduce new PTs, retire old ones, or reclassify existing terms. If a PBRER uses MedDRA version 27.0 but the previous PBRER used 26.0, the writer must account for any coding changes that could create artifactual trends in the data.

For a globally marketed product, the pharmacovigilance writer may need to produce multiple periodic reports with different content, timelines and formats: the PBRER (for ICH-aligned jurisdictions), the PSUR (for jurisdictions that have not adopted ICH E2C(R2)), and in some cases, region-specific periodic reports. Coordinating these reports — ensuring consistency of data and messaging while meeting divergent requirements — is a significant logistical and quality challenge.

The writer must also manage the Reference Safety Information (RSI), also called the Company Core Safety Information (CCSI) or Company Core Data Sheet (CCDS). This is the company's core document describing the known safety profile of the product. The RSI serves as the reference against which "expectedness" is assessed — an adverse event is "unexpected" if it is not listed in the RSI at the reported specificity, severity or frequency. Changes to the RSI during a reporting period must be documented in the PBRER and communicated to all local affiliates so that expedited reporting criteria are updated globally.

Regulatory inspections of pharmacovigilance systems are conducted by the FDA (under 21 CFR Part 314.80 and Part 312.32), the EMA (under GVP Module III), and national competent authorities. Inspections can be routine (scheduled, based on a risk assessment) or triggered (prompted by a safety concern, a whistleblower report, or a pattern of late reporting). The consequences of a failed inspection range from warning letters to consent decrees, product withdrawals, and criminal penalties for responsible individuals.

Inspectors evaluate: the timeliness and completeness of adverse event reporting (are all valid ICSRs being submitted within regulatory timelines?), the quality of case processing (are narratives accurate and complete?), signal detection activities (is the company systematically looking for signals?), the PBRER/DSUR (are periodic reports submitted on time and are they analytically sound?), the PSMF (is it current and does it accurately describe the system?), and the quality management system (are SOPs in place, are they followed, and are deviations documented?).

The most common pharmacovigilance inspection findings relate to: late reporting (submitting expedited reports after the 15-day deadline), incomplete case processing (missing follow-up, incomplete narratives, incorrect MedDRA coding), inadequate signal detection (no documented process, or a process that exists on paper but is not followed), PBRER/DSUR deficiencies (missing sections, inadequate benefit-risk assessment, inconsistencies between the report and the safety database), and quality system failures (SOPs not followed, training records incomplete, audit findings not addressed).

For the medical writer, the key inspection vulnerability is documentation. Every document must have a clear audit trail: who drafted it, who reviewed it, what changes were made, and when it was finalised. Version control must be rigorous. Narratives must be consistent with the coded ICSR data. PBRERs must be consistent with the safety database. Signal evaluation reports must document the methodology, the data sources, and the rationale for the conclusion. Any discrepancy will be found — inspectors are experienced, thorough, and systematic.

Pharmacovigilance writing is a continuous cycle: individual case reports flow into the safety database, accumulate into periodic reports, generate signals that require evaluation, inform risk management decisions, and ultimately produce communications that change prescribing behaviour and protect patients. Each document in this cycle depends on the quality of the documents that preceded it. A poorly written ICSR narrative can mask a safety signal. A poorly structured PBRER can delay regulatory action. A poorly communicated risk can fail to change prescriber behaviour.

The capstone exercise asks you to work through an entire safety communication cycle: from the individual case report, through signal detection and evaluation, to the regulatory response and prescriber communication. At each stage, you will apply the principles and skills you have developed throughout this course.

Pharmacovigilance writing is not glamorous. You will not write bestsellers. Your documents will not trend on social media. But the work you do directly affects patient safety. A well-written ICSR narrative helps a signal evaluator identify a pattern. A rigorous PBRER helps regulators make evidence-based decisions. A clear DHCP letter helps a physician protect their patient from a newly identified risk. Every document in the pharmacovigilance system is a link in the chain that connects adverse event reports to patient protection.

The qualities that define an excellent pharmacovigilance writer are: precision (every term, every number, every date must be correct), timeliness (regulatory deadlines are absolute and patient safety depends on them), integrity (report what the data show, not what you wish they showed), and perspective (remember that behind every ICSR is a real patient who experienced a real adverse event). These qualities are not acquired through training alone — they are cultivated through practice, mentorship, and a genuine commitment to the purpose of pharmacovigilance: ensuring that medicines are used safely.