Literature Monitoring

Screening must cover both high-impact international journals and local peer-reviewed literature in markets where the product is authorized. This dual approach captures safety signals that may appear first in regional publications due to local prescribing practices or genetic predispositions. Regulatory bodies like the EMA explicitly require marketing authorization holders to monitor local journals in designated countries.

Literature monitoring relies on pre-defined, highly sensitive Boolean queries combining drug substance names, brand names, and adverse event terminology. These strategies are designed to maximize recall, ensuring no potential Individual Case Safety Report (ICSR) is missed. Queries are often constructed using MedDRA terms and are validated against a gold standard set of known relevant articles.

The workflow is a classic recall-then-precision pipeline:

• Stage 1 (Recall): Broad screening of titles and abstracts against the search strategy to identify a set of potentially relevant articles.
• Stage 2 (Precision): Detailed full-text review of the shortlisted articles to determine if they contain a valid, identifiable patient case meeting the four minimum criteria for an ICSR.

Monitoring is not ad-hoc. The frequency of screening is defined by regulatory obligations and product risk profile:

• Weekly or bi-weekly screening of major databases like PubMed and Embase is standard for marketed products.
• Local journal screening may occur less frequently, such as monthly or quarterly, depending on the volume of publications and regional requirements.

To ensure comprehensive coverage, monitoring must span multiple bibliographic databases, as no single source indexes all relevant journals. Core databases include:

• PubMed/MEDLINE: The foundational biomedical literature database.
• Embase: Provides broader European and pharmacological journal coverage.
• LILACS: Essential for capturing literature from Latin America and the Caribbean.

Every step of the process must be meticulously documented for regulatory inspection. This includes the version-controlled search strategies, the screening logs showing the disposition of each abstract (included/excluded with rationale), and the full-text assessment forms. This audit trail demonstrates to regulators like the FDA and EMA that the process was systematic, unbiased, and reproducible.

The foundational unit of pharmacovigilance data—a structured report detailing a single adverse event experienced by an individual patient in relation to a medicinal product. Literature monitoring directly feeds the ICSR pipeline by identifying valid adverse event mentions in published case reports and clinical studies.

• Contains patient demographics, drug exposure, and reaction details
• Must be coded to MedDRA terminology before submission
• Exchanged electronically using the E2B (R3) XML standard
• Literature-derived ICSRs are a regulatory mandate under GVP Module VI

The systematic process of identifying new or previously unknown causal relationships between a drug and an adverse event. Literature monitoring serves as a critical input source alongside spontaneous reporting databases like FAERS and VigiBase.

• Relies on disproportionality analysis for quantitative screening
• Literature signals often emerge from high-quality peer-reviewed studies
• Requires signal validation before regulatory action
• Integrates with aggregate reporting cycles (PBRER, DSUR)

The Medical Dictionary for Regulatory Activities—a clinically validated international terminology used for standardized coding of adverse event information. All literature-extracted adverse event mentions must be mapped to MedDRA's hierarchical structure.

• Organized into five levels: SOC > HLGT > HLT > PT > LLT
• Enables cross-product and cross-region safety comparisons
• Standardised MedDRA Queries (SMQs) group terms for targeted retrieval
• Version updates occur biannually, requiring ongoing terminology maintenance

The systematic evaluation of the likelihood that a drug caused an observed adverse event. Literature monitoring often uncovers complex case narratives requiring rigorous causality analysis before inclusion in safety databases.

• Evaluates temporal relationship between exposure and event
• Considers dechallenge/rechallenge information
• Accounts for confounding by indication and concomitant medications
• Standardized tools include the Naranjo Scale and WHO-UMC criteria

The European Medicines Agency's centralized database for managing suspected adverse reactions. Marketing authorization holders must screen literature for potential ICSRs and submit findings to EudraVigilance in compliance with GVP Module VI.

• Mandatory for all products authorized in the European Economic Area
• Supports electronic transmission via E2B (R3) gateway
• Integrated with the EVWEB and EVPOST reporting tools
• Enables cross-product signal detection across the EU network

The periodic compilation of cumulative safety data into documents like the Periodic Benefit-Risk Evaluation Report (PBRER) and Development Safety Update Report (DSUR). Literature monitoring findings are a mandatory component of these submissions.

• PBRER includes a cumulative literature review section
• Requires assessment of new safety signals against expectedness criteria
• Incorporates seriousness criteria classification (death, hospitalization, disability)
• Submitted to regulators on defined periodicity based on product lifecycle