ArticleVascular health and risk management2024
Association of Clopidogrel with Interstitial Lung Disease: Gaining Insight Through the Japanese Pharmacovigilance Database.
Article in Vascular health and risk management, 2024. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 4 papers, 1 of them a synthesis that pooled it.
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
4 citing papers in PubMed, 1 synthesis or guideline pooled it.
- Analysis of interstitial lung disease in pharmacovigilance databases: Coding challenges and interpretation biases-An update.British journal of clinical pharmacology · 2026Pooled it
- Gastrointestinal adverse events associated with axitinib: pharmacovigilance analysis of the Japanese adverse drug event report database.Pharmacological reports : PR · 2026Article
- Cardiac adverse events associated with axitinib: A real-world pharmacovigilance study based on the Japanese adverse drug event report database.Supportive care in cancer : official journal of the Multinational Association of Supportive Care in Cancer · 2026Article
- A case of clopidogrel-induced organizing pneumonia evaluated by lung biopsy and confirmed by accidental re-administration.Respiratory medicine case reports · 2025Article
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
5 authors.
Funding
No grant is acknowledged in the PubMed record.
Abstract
Background: The P2Y12 receptor inhibitors clopidogrel and prasugrel are widely used. Clopidogrel and prasugrel have different metabolic pathways, but whether their adverse event (AE) profiles differ significantly is unclear. Objective: This study aimed to compare the possible AEs induced by clopidogrel and prasugrel and to assess the rank-order of their AEs submitted to a spontaneous reporting database. Materials and Methods: Data were extracted from the Japanese Adverse Drug Event Report database (JADER). Reports of AEs associated with clopidogrel and prasugrel were analyzed to calculate the reporting odds ratios (RORs) and 95% confidence intervals (CIs). Results: Based on 5869 reports for clopidogrel (69.6%, men) and 513 reports for prasugrel (74.1%, men), 703 and 135 different AEs were identified, respectively. Bleeding complications including hemorrhage were commonly reported for both clopidogrel and prasugrel. As for AEs related to clopidogrel, unexpected AEs such as interstitial lung disease (227 reports; ROR, 1.77; 95% CI, 1.49-2.10), abnormal hepatic function (137 reports; ROR, 1.27; 95% CI, 1.07-1.51), and hepatocellular injury (96 reports; ROR, 120.0; 95% CI, 94.9-151.8) ranked at relatively high positions based on the number of occurrences, unlike prasugrel. Conclusion: This analysis of the national pharmacovigilance database highlights distinct AE profiles for clopidogrel and prasugrel. Unexpected AEs associated with clopidogrel were identified, providing valuable insights for clinical monitoring and patient safety.
Indexed as
Identifiers
What 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.