Standard Operating Procedure: Pharmacovigilance (PV) Case Processing and Reporting

This Standard Operating Procedure (SOP) outlines the mandatory framework for the collection, assessment, documentation, and regulatory reporting of Adverse Events (AEs) and Serious Adverse Events (SAEs). As an expert operations requirement, this document ensures organizational compliance with Good Pharmacovigilance Practices (GVP) and international regulatory standards (e.g., EMA, FDA, ICH E2B), aiming to minimize patient risk through proactive safety monitoring and timely signal detection.

1. Intake and Initial Case Processing

• Receipt of Information: Record the date of receipt by the safety department (Day 0).
• Minimum Criteria Validation: Verify the four pillars of a valid case:
  • An identifiable reporter.
  • An identifiable patient (e.g., initials, age, gender).
  • A suspect medicinal product.
  • An adverse event.
• Triage and Prioritization: Categorize the case based on seriousness and expectedness (e.g., Expedited 15-day report vs. Periodic Safety Update Report).
• Source Verification: Log the source document (e.g., medical records, consumer report, literature search).

2. Medical Assessment and Data Entry

• MedDRA Coding: Map adverse events to the Medical Dictionary for Regulatory Activities (MedDRA) terminology to ensure standardized reporting.
• Causality Assessment: Determine the relationship between the drug and the event using established algorithms (e.g., Naranjo Scale or WHO-UMC criteria).
• Seriousness Determination: Flag if the event leads to death, life-threatening conditions, hospitalization, disability, or congenital anomaly.
• Narrative Writing: Compile a concise, chronological, and non-repetitive summary of the clinical course, including relevant medical history and concomitant medications.

3. Regulatory Reporting and Quality Control

• Regulatory Submission: Transmit the Individual Case Safety Report (ICSR) via Electronic Transmission (e.g., EudraVigilance, Gateway) within the mandated legal timeframe.
• Quality Review: Conduct a blind peer review by a second qualified pharmacovigilance specialist to check for data integrity and logic errors.
• Archiving: Securely store the case file in the Global Safety Database for the duration required by local legislation (typically 10+ years).

4. Signal Detection and Risk Management

• Aggregated Review: Monitor trends in AEs to detect potential safety signals that differ from the established risk-benefit profile.
• Risk Minimization Measures: Implement updates to the Summary of Product Characteristics (SmPC) or Patient Information Leaflets (PIL) if a new risk is identified.
• Periodic Reporting: Schedule and generate PSURs (Periodic Safety Update Reports) or PADERs as required by the product's post-marketing phase.

Pro Tips & Pitfalls

• Pro Tip: Maintain a "Day 0" log that is audit-ready at all times. Auditors prioritize the timestamp of when the first company employee became aware of the information, regardless of their role.
• Pro Tip: Use automated data validation rules in your safety database to flag missing "minimum criteria" data points during entry, preventing incomplete submissions.
• Pitfall (Under-reporting): Do not disregard reports because they seem "anecdotal" or "incomplete." Legally, the company must document even minimal reports and follow up for missing information.
• Pitfall (Quality Over Speed): While expedited reporting is critical, submitting inaccurate data to save time leads to costly "Corrective and Preventive Action" (CAPA) plans later. Accuracy must never be sacrificed for speed.

Frequently Asked Questions (FAQ)

Q: What is "Day 0" in Pharmacovigilance? A: Day 0 is the date on which any personnel of the company (including medical representatives or consultants) first receive the minimum four criteria of an adverse event report. This starts the clock for regulatory submission deadlines.

Q: How should we handle reports received via social media? A: If a company manages its own social media pages, it must monitor them for adverse events. Once identified, these reports must be treated with the same urgency as reports via phone or email, documented, and assessed according to this SOP.

Q: What is the difference between an adverse event (AE) and an adverse drug reaction (ADR)? A: An AE is any untoward medical occurrence in a patient administered a pharmaceutical product, regardless of whether it is causally related. An ADR is a response to a drug which is noxious and unintended, where a causal relationship is at least reasonably possible.