Explore this article's sources with AI
Follow PeptideMethods on Google
Semaglutide and Ventricular Extrasystoles
A two-database safety analysis found disproportionate reporting of ventricular extrasystoles with semaglutide, but it cannot prove causation.
Why we wrote this. Spontaneous-report signals are easy to mistake for incidence or proof. This paper needs a careful read.
In this article (5 sections)
A 2026 pharmacovigilance analysis found that reports of ventricular extrasystoles, also called premature ventricular contractions, were disproportionately associated with semaglutide in both VigiBase and the US FDA adverse-event database. That is a safety signal, not proof that semaglutide caused the events and not an estimate of how often they occur[1].
What the researchers analyzed
The authors searched individual case safety reports in the World Health Organization's VigiBase and the FDA Adverse Event Monitoring System, formerly called FAERS. Semaglutide had to be recorded as a suspected medicine under each database's criteria. Cardiovascular outcomes were identified using standardized adverse-event terms[2].
This was a disproportionality study. It asks whether a particular event appears more often with a named medicine than expected relative to other medicine-event combinations in the same reporting system. It does not follow a defined group of semaglutide users over time, and there is no randomized control group.
After deduplication and the authors' inclusion rules, the analysis contained 1,980 semaglutide-associated cardiovascular reports from VigiBase and 1,754 from the US system[1]. Those totals are reports selected for this cardiovascular analysis. They are not counts of all people who used semaglutide.
The cross-database signal
The authors required at least three semaglutide-associated reports and a lower 95% confidence-interval bound above 1 in each database. Ventricular extrasystoles was the only screened cardiovascular or rhythm-related term that met that prespecified rule in both sources[2].
In VigiBase, the reporting odds ratio was 1.77, with a 95% confidence interval from 1.31 to 2.40. In the US database, it was 1.37, with an interval reported as 1.00 to 1.88. The paper notes that the unrounded lower bound in the US analysis was above 1[1]. Rounding matters here because the displayed lower limit sits at the decision boundary.
A reporting odds ratio is not a risk ratio. A value above 1 means the event was reported disproportionately within the database comparison. It does not mean that 77% more semaglutide users experienced the event, nor does it provide the event's incidence among treated patients.
Why spontaneous reports cannot prove cause
FDA explains that spontaneous reports can be incomplete, duplicated or influenced by publicity and reporting habits. The agency also notes that a report does not establish that a medicine caused the event[3]. VigiBase has related limits because it aggregates suspected adverse-event reports rather than prospectively measured outcomes.
People prescribed semaglutide may have diabetes, obesity or cardiovascular disease. Those conditions and other medicines can affect rhythm symptoms. The abstract does not show that the study could fully resolve these competing explanations. It also cannot supply a denominator because the reporting systems do not contain a reliable count of every exposed patient.
The finding therefore belongs in signal detection. It should be read alongside established product information and clinical evidence, not as a replacement for them. Our semaglutide research page provides the broader evidence context.
Report counts can rise for reasons unrelated to a change in biological risk. Use can expand, a medicine can receive more public attention, or clinicians and patients can become more likely to report a named concern. A newly marketed formulation may also change the mix of exposed patients. The two-database rule reduces the chance that one database's coding or reporting pattern alone produced the signal, but it does not remove these influences.
There is another important constraint. A database report can name semaglutide as suspected while also naming other medicines or medical conditions. Disproportionality methods compare reporting patterns across many records, but they do not reconstruct each patient's full clinical course with the consistency of a planned trial. That is the boundary.
Signal confirmation would require a defined population of users and a suitable comparison group. Researchers would need to measure baseline rhythm status, ascertain new events consistently and account for cardiovascular disease and other treatments. A study designed that way could estimate absolute event rates. The present paper cannot.
What we do not yet know
The analysis does not establish whether semaglutide increases premature ventricular contractions, whether any possible association differs by formulation or indication, or whether reported events were transient or clinically serious. The abstract does not provide exposure-adjusted rates, electrocardiographic confirmation for every report or a causal adjudication process.
The authors call for prospective investigation with systematic electrocardiograms and ambulatory rhythm monitoring[1]. That design could identify events in a defined exposed population, measure timing and compare groups under a planned protocol. Until such data exist, the new paper supports further study rather than a change in an individual's treatment.
How readers should use this result
A new or worsening palpitation deserves clinical attention, especially when it occurs with chest pain, fainting or severe shortness of breath. This article cannot determine the cause of a symptom or advise whether to stop a prescription. Abrupt treatment decisions can carry their own risks, so questions about symptoms and prescribed semaglutide belong with a qualified clinician.
Medical disclaimer: This article is for educational and journalistic purposes only and does not constitute medical advice. Peptides discussed may be classified as prescription medicines or research chemicals depending on your jurisdiction. Always consult a qualified healthcare professional before using any peptide product. PeptideMethods.com does not sell, distribute, or facilitate the sale of any peptide product.
Frequently asked
Did the study prove that semaglutide causes premature ventricular contractions?
No. It identified disproportionate reporting in two spontaneous-report databases. That method detects signals but cannot establish incidence or causation.
What is a ventricular extrasystole?
It is an early heartbeat arising from a ventricle, commonly called a premature ventricular contraction. Its clinical significance depends on the person and context.
What should the signal lead to next?
The authors recommend prospective research using planned electrocardiographic assessment and ambulatory rhythm monitoring to test the signal in defined populations.
Sources
- [1]Wu D et al. Disproportionality analysis of ventricular extrasystoles reported with semaglutide in VigiBase and the FDA Adverse Event Monitoring System. 2026. PMID 42993217Tier 1 · primary↩
- [2]Europe PMC indexed abstract record for PMID 42993217Tier 1 · primary↩
- [3]FDA: Questions and Answers on FDA's Adverse Event Reporting SystemTier 1 · primary↩
No revisions yet. First published .