Key points
- MAHs are expected to monitor appropriate medical and scientific literature using a defined, risk-based schedule and a justified source list.
- Search strategies must be controlled, versioned, and reproducible, with documented rationale for any changes.
- Each search execution must be evidenced contemporaneously, including source, date, strategy or version, screener, and outcome.
- Screening, exclusions, duplicate handling, and any follow-up should be documented with clear rationale and quality control where applicable.
- Potential safety cases must be traceable from literature hit to assessment, ICSR processing, and reporting timelines where required.
- Governance, quality control, vendor oversight, and CAPA should demonstrate ongoing control of the literature surveillance process.
What inspectors expect
Each point below should be supported by controlled documents and traceable records.
- A defined, risk-based scope and frequency for literature surveillance is documented and implemented.
- Search strategies are reproducible and controlled, including version history and rationale for changes.
- Execution records are complete and contemporaneous, including who performed the search, when it was run, where it was run, and which strategy or version was used.
- Screening decisions are documented with clear inclusion and exclusion rationale, duplicate handling logic, and quality control where applicable.
- Potential safety cases are traceable from literature hit to assessment and ICSR processing or reporting where required.
- Oversight is evidenced through KPIs or trending, periodic review cadence, and action or CAPA handling for deviations.
Summary
In practice, inspectors assess whether the literature surveillance process is controlled, reproducible, and capable of detecting reportable safety information. This includes reviewing search strategies, screening decisions, traceability to ICSR processing, duplicate handling, and evidence of governance oversight.
Common questions
These are the questions this page is designed to answer directly.
- What do regulators expect for pharmacovigilance literature surveillance?
- What evidence will inspectors ask for to prove literature surveillance is controlled?
- How should search strategies be documented and version-controlled for PV literature monitoring?
- What are common inspection findings for literature surveillance and how do you prevent them?
- How do I set up compliant medical literature monitoring for pharmacovigilance (EU/UK)?
- What is day zero for a literature case and how do reporting timelines apply?
- What should be in a literature screening SOP and what records must be retained?
- How should we manage duplicates and document screening exclusions for inspection?
- What oversight metrics should we track for literature surveillance (hits, screened, potential cases)?
- Is literature monitoring mandatory for pharmacovigilance in the EU/UK?
- What is the difference between EMA Medical Literature Monitoring (MLM) and a MAH’s own literature searches?
- What documentation do we need to demonstrate literature surveillance control during an MHRA/EMA inspection?
Evidence objects inspectors expect
Literature Surveillance SOP
- Defined scope of products and territories
- Specified data sources (e.g., bibliographic databases, journals, conference abstracts where relevant)
- Search frequency and responsibility matrix
- Inclusion and exclusion criteria
- Escalation pathway to case processing
- Governance and oversight requirements
Controlled Search Strategy Documentation
- Documented search strings
- Version control of search parameters
- Justification for databases and sources selected
- Defined search frequency
- Named responsible individual and review trigger for strategy updates
Literature Search Log
- Date of search execution
- Database or source searched
- Search string or strategy version used
- Number of results retrieved and screened
- Screening outcome and escalation to ICSR where applicable
- Reference to retained output, export, or supporting evidence
Screening and Decision Records
- Documented inclusion and exclusion rationale
- Duplicate status and duplicate rationale where applicable
- Assessment notes and follow-up actions where needed
- Linkage to safety case records where applicable
Duplicate Management & Reconciliation Controls
- Defined duplicate identification criteria
- Retention of duplicate records or a traceable duplicate audit trail
- Reconciliation between literature hits, decision logs, and safety database intake
- Evidence that follow-up or rescreening is handled consistently
Governance & Oversight Evidence
- Periodic literature oversight meeting minutes
- Trend monitoring discussions and timeliness metrics
- Action tracking, CAPA, and closure evidence
- Vendor performance oversight documentation where outsourced
Regulatory Basis (Primary Sources)
- GVP Module VI (EU) – literature cases form part of ICSR management and reporting obligations
- EMA Medical Literature Monitoring – operational scope for selected substances under Article 27 of Regulation (EC) No 726/2004
- EMA MLM Detailed Guide and Q&A – rules for screening, duplicate handling, quality control, and day zero in the MLM context
- MHRA pharmacovigilance guidance – MAHs remain responsible for relevant literature searches and inclusion of EMA MLM reports
- ICH E2D – global post-approval literature-screening and reporting principles
Typical Inspection Questions (What Inspectors Ask)
- How frequently do you run literature searches, and why that frequency?
- Which databases and sources do you search, and how were they selected?
- Show me the controlled search strategy and its version history.
- Show evidence of the last 3 search executions, including logs and outputs.
- How are inclusion, exclusion, and duplicate decisions recorded and QC’d?
- Trace one literature hit through to case processing and any reporting action.
- How do you oversee vendors performing literature monitoring, including KPIs, reviews, deviations, and CAPA?
Common Databases & Sources (Examples)
- MEDLINE/PubMed
- Embase
- Key disease-area journals
- Conference abstracts and proceedings where risk justifies them
- EMA MLM outputs for covered substances where applicable
Failure patterns
Uncontrolled search strategy: Search strings are modified ad hoc without version control or documentation, leading to inconsistent coverage. Inspectors request historical search evidence and test reproducibility; undocumented changes often result in findings.
Screening decisions not documented: Screening outcomes are handled informally (e.g., via email or undocumented review). Inspectors treat absence of documented rationale as absence of control, often resulting in inspection observations or major findings.
Duplicate handling is inconsistent: duplicate literature records are deleted, merged, or ignored without defined criteria, audit trail, or reconciliation to safety database intake. Inspectors expect duplicate decisions to be documented and traceable.
Lack of traceability to ICSR: Literature hits are identified but escalation to safety systems is not clearly evidenced. Inspectors test traceability from literature hit to safety database entry and reporting timelines.
No formal governance oversight: Literature surveillance is treated as an operational task without documented review cadence. Inspectors request evidence of oversight, review of metrics, and follow-up of issues.
What good looks like
- Search frequency and scope are defined, justified, and consistently executed.
- Search strategies are controlled, versioned, reproducible, and periodically reviewed.
- Screening decisions, exclusions, and duplicate handling are documented with clear rationale.
- Traceability from literature hit to case processing is retrieval-ready and easy to demonstrate.
- Oversight is evidenced through metrics, review cadence, action tracking, and vendor oversight where outsourced.
- Quality control and timeliness checks are defined, performed, and retained as evidence.
Operationalisation
- Define scope and search cadence on a risk basis and document it in the SOP.
- Create controlled search strategies with explicit version control and change rationale.
- Run searches consistently and retain outputs or exports per procedure so evidence is retrieval-ready.
- Standardise screening decisions with a minimal decision record, duplicate logic, and QC sampling.
- Define duplicate criteria and reconcile literature hits, decision records, and safety database intake.
- Add oversight through trend metrics, periodic review, and documented action tracking and closure.
- If EMA MLM outputs apply, define how they are received, reviewed, incorporated, and evidenced within the local process.
- If outsourced, define KPIs, review cadence, deviation and CAPA handling, and escalation routes, and evidence all oversight activity.
Need regulatory documentation today?
Save time and reduce inspection risk with structured, pre-built process-ready documentation.
Created by industry professionals, adaptable to your organisation.
Related pre-built documentation inside the app
FAQ
How often must pharmacovigilance literature be reviewed?
Frequency should be defined in the Literature Surveillance SOP and aligned to product portfolio, jurisdiction, and risk. The key requirement is consistent execution against a documented schedule with retained evidence.
Which databases are typically used for literature surveillance?
Common sources include major bibliographic databases such as MEDLINE/PubMed and Embase, together with relevant specialist journals and other justified sources. The source list should be risk-based, documented, and periodically reviewed.
Is PubMed alone enough for pharmacovigilance literature surveillance?
Not always. A single source may be insufficient if it does not adequately cover the product, therapeutic area, languages, or publication types relevant to your portfolio. The adequacy of the source list should be justified and documented.
What is day zero for a literature case?
Day zero is the date the MAH becomes aware that a literature case meets the minimum criteria for reportability. In the EMA MLM context for EEA MAHs, the relevant timing is linked to when the ICSR is transmitted to EudraVigilance or otherwise made available by the service.
Do inspectors require documentation of every screening decision?
Inspectors typically expect sufficient evidence to demonstrate controlled screening and consistent decision-making. Organisations commonly document inclusion and exclusion decisions with brief rationale and retain traceability to case processing where applicable.
What should a compliant literature search log contain?
At minimum: date and time, database or source, strategy or version used, counts retrieved and screened, potential cases, screener identity, decisions and rationale or link to decision record, escalation to case processing where applicable, and retention reference to outputs or exports.
How should duplicate literature records be handled?
Duplicate criteria should be predefined, applied consistently, and evidenced. Duplicate records should not disappear silently; the rationale, retained audit trail, and reconciliation to safety database intake should be demonstrable.
Is literature surveillance a regulatory requirement or a best practice?
It is treated as a core pharmacovigilance expectation. Marketing authorisation holders should systematically monitor relevant medical literature to identify suspected adverse reactions, process valid cases, and retain inspection-ready evidence of control.
Does the EMA Medical Literature Monitoring (MLM) service replace our own searches?
No. EMA MLM supports selected substances and sources, but it does not remove the MAH’s responsibility to ensure that literature surveillance for its products is complete, controlled, and inspection-ready.
What do inspectors usually probe first for literature surveillance?
They typically probe control and reproducibility through the SOP and controlled strategies, then request recent execution evidence, and finally test traceability by selecting a literature hit and following it through screening, case processing, and timelines.
What are common inspection findings for literature surveillance?
Common findings include uncontrolled strategy changes, missing decision rationale, weak duplicate handling, insufficient traceability to case processing, and lack of oversight evidence such as no metrics, no review cadence, or no documented action handling when issues occur.
What evidence is expected if literature monitoring is outsourced to a vendor?
Evidence of qualification or selection, clear responsibilities in the contract, defined KPIs and review cadence, records of performance review meetings, issue or deviation handling, CAPA actions and effectiveness checks, and an escalation route for potential cases.
Sources
Primary guidance used to inform this map. This page is a structured interpretation layer; always validate against the original source documents.
European Medicines Agency (EMA)
- Good pharmacovigilance practices (GVP)View source
- Guideline on good pharmacovigilance practices (GVP) – Module VI – Collection, management and submission of reports of suspected adverse reactions to medicinal products (Rev. 2)View source
- Medical literature monitoringView source
- Detailed guide regarding the monitoring of medical literature and the entry of relevant information into the EudraVigilance database by the European Medicines AgencyView source
- Monitoring of medical literature and the entry of relevant information into the EudraVigilance database by the European Medicines Agency – Questions and AnswersView source
- MLM Service User GuideView source
International Council for Harmonisation (ICH)
- Post-Approval Safety Data Management: Definitions and Standards for Expedited Reporting (E2D)View source
UK MHRA (GOV.UK)
- Good pharmacovigilance practice (GPvP)View source
- Send and receive information on adverse drug reactions (ADRs)View source