ArticleDrug safety2026
Toward a Framework for Case Identification in Pharmacovigilance: Not All Reports are Created Equal.
Article in Drug safety, 2026. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Not yet cited in PubMed.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
0 citing papers in PubMed.
No citing paper in PubMed yet.
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
9 authors.
Funding
No grant is acknowledged in the PubMed record.
Abstract
backgroundRetrieval of adverse event reports based on coded drug-event co-occurrence enables large-scale pharmacovigilance analyses but yields candidate reports rather than clinically adjudicated cases. Without explicit case identification, heterogeneous reports may be combined within the same case series and misinterpreted in downstream analyses.
aimThe aim of the study was to develop a structured framework for distinguishing clinically meaningful cases from candidate reports retrieved through coded drug-event co-occurrence, and to illustrate its application across information-rich and routine-review conditions.
methodsWe conducted a sequential framework-development study using two case studies. Drug-induced impulsivity was used to iteratively develop and refine the framework under information-rich conditions. Drug-induced suicidality was used to examine its application under routine-review conditions with variable information availability and explicit classification of nonassessability.
resultsIn case 1, nonrelevant reports were more frequent for drugs with uncertain or no established evidence (~ 20-40%) than for drugs with established causal roles (4%). The framework assessed relevance across exposure, event, the drug-event relationship, and setting/population. Reports retained as relevant were further characterized by reporter suspicion and evidentiary qualifiers supporting or weakening suspicion. Reports with explicit suspicion more often contained supportive qualifiers. In case 2, application of the framework classified 69% of reports as nonrelevant and 17% as nonassessable.
conclusionsIn pharmacovigilance, retrieval is not equivalent to case identification. Relevance depends on whether exposure, event, their relationship, and context correspond to the clinical question being investigated. Explicit case definitions and transparent adjudication make this distinction systematic and auditable. Independent evaluation of the framework is needed to establish its reproducibility and transferability across pharmacovigilance questions.
Identifiers
42909775What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.