Why the study?
Does angiotensin receptor blocker (ARB) treatment reduce prostate cancer incidence in United States Veterans?
Does angiotensin receptor blocker (ARB) treatment reduce prostate cancer incidence in United States Veterans?
Retrospective analysis of over 500,000 US Veterans confirms that ARB use does not increase the risk of incident prostate cancer, supporting recent FDA conclusions.
Answers are grounded in this paper and cite their sources.
ARB use was not associated with increased prostate cancer risk; supports safety but leaves any reduction hypothesis-generating.
To address concerns regarding increased risk of prostate cancer (PrCA) among angiotensin receptor blocker (ARB) users, we used national retrospective data from the Department of Veterans Affairs (VA) through the Veterans Affairs Informatics and Computing Infrastructure. We identified a total of 543,824 unique Veterans who were classified into either ARB treated or not-treated in 1:15 ratio. The two groups were balanced using inverse probability of treatment weights. A double-robust cox-proportional hazards model was used to estimate the hazard ratio for PrCA incidence. To evaluate for a potential Gleason score stage migration, we conducted weighted Cochrane-Armitage test. Post weighting, the rates of PrCA in treated and not-treated groups were 506 (1.5%) and 8,269 (1.6%), respectively; representing a hazard ratio of (0.91, p-value .049). There was no significant difference in Gleason scores between the two groups. We found a small, but statistically significant, reduction in the incidence of clinically detected PrCA among patients assigned to receive ARB with no countervailing effect on degree of differentiation (as indicated by Gleason score). Findings from this study support Food and Drug Administration's recent conclusion that ARB use does not increase risk of incident PrCA.
No takes yet. Share an insight, caveat, or question.
Rao et al. (2013) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: