Choosing Between Passive and Active Surveillance in Post-Marketing Vaccine Safety

Passive vs Active Surveillance—What They Are and When to Use Each

Passive surveillance collects Individual Case Safety Reports (ICSRs) from clinicians, patients, and manufacturers via national systems (e.g., VAERS/EudraVigilance analogs). It excels at early pattern recognition because it listens broadly: new Preferred Terms, atypical narratives, or demographic clustering can flag emerging issues quickly. Strengths include speed of intake, rich free-text, and relatively low cost. Limitations are well known: no direct denominators, susceptibility to under- or stimulated reporting, duplicate submissions during media spikes, and variable case quality. In passive streams, you will rely on disproportionality statistics (PRR, ROR, EBGM) to identify unusual vaccine–event reporting patterns that merit clinical review.

Active surveillance uses linked healthcare data (EHR/claims/registries, sometimes laboratory feeds) to construct cohorts with person-time denominators. It supports observed-versus-expected (O/E) checks, rapid cycle analysis (RCA) with MaxSPRT boundaries, and confirmatory designs such as self-controlled case series (SCCS) or matched cohorts. Strengths include stable denominators, control of confounding, and ability to estimate incidence rates and relative risks over calendar time. Limitations include access/agreements, data harmonization, lag, and the need for robust governance and validation packs (Part 11/Annex 11 controls, audit trails, and change control). In practice, sponsors rarely choose one or the other: passive detects, active quantifies, and targeted follow-up adjudicates. To align terminology and SOP structure with regulators, many teams adapt practical PV templates from PharmaRegulatory.in, and mirror public expectations summarized by the U.S. FDA.

Comparative Design Considerations: Data, Methods, and Compliance

Surveillance strategy is as much about design and documentation as it is about databases. Passive streams must prove clean inputs: MedDRA version control, explicit Preferred Term selection rules, ICSR de-duplication criteria (e.g., age/sex/onset/lot match), and translation QA for non-English narratives. Active streams must show traceable ETL pipelines, linkage logic, and privacy safeguards. Both must demonstrate ALCOA (attributable, legible, contemporaneous, original, accurate) and computerized system controls: role-based access, validated audit trails, and time synchronization. Pre-declare decision thresholds in your signal management SOP: what PRR/ROR/EBGM constitutes a “screen hit,” what O/E ratio prompts escalation, which risk windows apply by AESI, and when SCCS/cohort studies begin. Link these rules to your Risk Management Plan (RMP) and Statistical Analysis Plan (SAP) so clinical, safety, and biostatistics use the same vocabulary when evidence evolves.

Operationally, success comes from hand-offs. Write a responsibility matrix: safety scientists review screen hits weekly; epidemiology runs O/E; biostatistics maintains RCA/SCCS code; clinical adjudicates with Brighton criteria; QA reviews audit trails; regulatory owns labels and communications. Keep this map in the PSMF and TMF, with links to datasets and code hashes, so an inspector can trace the path from intake to decision without guesswork.

Analytics That Bridge Both: From PRR to O/E, SCCS, and RCA (with Numbers)

Pre-declare screens and thresholds to avoid hindsight bias. In passive data, a common rule is PRR ≥2 with χ² ≥4 and n≥3; ROR with 95% CI excluding 1; EBGM lower bound (e.g., EB05) >2. Combine these with clinical triage: age/sex clustering, time-to-onset after dose, and mechanistic plausibility. In active data, compute O/E using stratified background rates and biologically plausible windows. Example (dummy): Week W, 1,200,000 second doses to males 12–29; background myocarditis 2.1/100,000 person-years → expected in 7 days ≈ 1,200,000 × (7/365) × (2.1/100,000) ≈ 0.48. Observed 6 adjudicated cases → O/E ≈ 12.5 → escalate. Run RCA weekly with MaxSPRT; if the boundary is crossed, initiate SCCS. A typical SCCS result might show IRR 4.6 (95% CI 2.9–7.1) for Days 0–7, IRR 1.8 (1.1–3.0) for Days 8–21.

Where laboratory markers define cases, declare method capability so inclusion is transparent: high-sensitivity troponin I LOD 1.2 ng/L and LOQ 3.8 ng/L (illustrative) for myocarditis adjudication; platelet factor 4 (PF4) ELISA performance for thrombotic syndromes. Keep quality context close to safety: representative PDE 3 mg/day for a residual solvent and cleaning MACO 1.0–1.2 µg/25 cm² reassure reviewers that non-biological explanations (contamination, carryover) are unlikely. For a plain-language overview of signal expectations and pharmacovigilance vocabulary, the WHO library provides accessible references at who.int/publications.

Designing a Hybrid Surveillance Program: A Step-by-Step Playbook

Step 1 — Define AESIs and windows. Pre-register adverse events of special interest (AESIs) by platform (e.g., myocarditis for mRNA, TTS for vector vaccines) with Brighton definitions and risk windows (0–7, 8–21 days, etc.). Step 2 — Map data flows. Draw a single diagram linking ICSRs → coding/deduplication → screen queue; and registries/EHR/labs → ETL → O/E/RCA/SCCS pipelines. Step 3 — Write thresholds. Document PRR/ROR/EBGM cut-offs, O/E escalation rules, RCA boundary settings, and SCCS triggers. Step 4 — Validate systems. For passive, validate ICSR intake (E2B R3), MedDRA versioning, translation QA, and audit trails. For active, validate linkage logic, ETL checkpoints, time sync, and back-ups under Part 11/Annex 11; containerize analytics and lock code hashes. Step 5 — Staff governance. Run a weekly multi-disciplinary signal review (safety, clinical, epidemiology, biostatistics, quality, regulatory) with minutes, owners, and due dates. Step 6 — Pre-write communications. Draft label/FAQ templates so confirmed signals can be communicated with denominators and plain language quickly.

Keep a one-page crosswalk in the TMF: SOP → dataset → code → output → decision → label. If a screen hit escalates, an inspector should be able to start at the decision memo and walk back to the raw ICSR and the database cut that produced the O/E.

Case Study (Hypothetical): Turning Noisy Signals into Decisions

Week 1–2 (Passive): 20 myocarditis ICSRs in males 12–29 after dose 2; PRR 3.0 (χ² 9.2), EB05 2.2. Narratives cite chest pain and elevated troponin (above assay LOQ 3.8 ng/L). Week 3 (Active O/E): 1.2 M doses administered; background 2.1/100,000 person-years; expected 0.48; observed 6 adjudicated Brighton Level 1–2 → O/E 12.5. Week 4 (RCA): MaxSPRT boundary crossed in Days 0–7; geographies consistent. Week 5–6 (SCCS): IRR 4.6 (2.9–7.1) for Days 0–7; IRR 1.8 (1.1–3.0) for Days 8–21. Decision: add myocarditis to important identified risks; update label/HCP guidance with absolute risks (“~12 per million second doses in young males within 7 days”). Quality check: lots in shelf life; cold chain in range; representative PDE 3 mg/day and MACO 1.0–1.2 µg/25 cm² unchanged—reducing concern for non-biological drivers.

The full package—ICSRs, coding rules, O/E worksheets, RCA configs, SCCS code/outputs, adjudication minutes, and quality context—goes into the TMF and supports rapid, defensible labeling.

KPIs, Governance, and Inspection Readiness: Keeping the System Alive

Measure both surveillance performance and decision speed. Surveillance KPIs: % valid ICSRs triaged ≤24 h, screen hits reviewed per SOP cadence, median days from screen to O/E, RCA boundary checks on schedule, % adjudications completed within SLA. Quality KPIs: audit-trail review completion, ETL error rate, linkage success, reproducibility checks (code hash matches), and completeness scores for ICSRs. Decision KPIs: time to label update, time to DHPC release, and % of decisions backed by confirmatory analytics.

Inspection readiness is narrative clarity plus evidence. Keep a “read me first” note in the TMF that maps SOPs → data cuts → code → outputs → decisions. Store all public communications (FAQs, HCP letters) with the analytics that support them. For method calibration, run periodic negative-control screens so your system demonstrates specificity, not just sensitivity.