Studies have reported cardiovascular effects of Sodium-glucose cotransporter 2 (SGLT2) and dipeptidyl peptidase-4 (DPP-4) inhibitors.Although cardiovascular and renal benefits of SGLT2 inhibitors have been reported, their specific association with arrhythmias such as atrial fibrillation (AF), atrial flutter, and ventricular fibrillation remains less clearly defined.Therefore, this study aims to investigate the association between empagliflozin, sitagliptin, and linagliptin and reporting patterns of selected arrhythmias in Koreans.Raw data from the Korea Adverse Event Reporting System database were analyzed from January 2019 to December 2023.The drugs of interest were SGLT2 and DPP-4 inhibitors; however, the final disproportionality analysis was limited to empagliflozin, sitagliptin, and linagliptin because these were the drugs with relevant analyzable arrhythmia reports in the study dataset.The analyzed adverse events included atrial fibrillation (AF), atrial flutter, and ventricular fibrillation.The association between the drugs and adverse events was evaluated using disproportionality analysis and chi-squared testing in SAS software version 9.7.Disproportionality analyses revealed that empagliflozin, sitagliptin, and linagliptin showed no positive reporting signals for AF, atrial flutter, and ventricular fibrillation based on the prespecified signal detection criteria.The chi-squared test showed a statistically significant association between each drug and adverse events (p < 0.001); which was interpreted as a difference in reporting distributions within the spontaneous reporting dataset, not as evidence of clinical risk or causality.The findings indicate that selected arrhythmia terms were not disproportionately reported for empagliflozin, sitagliptin, and linagliptin in the KAERS DB during the study period.However, since this analysis was based on collected unsolicited data and the statistical results are limited to signal detection, further studies using global datasets and large-scale clinical trials are needed.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 6, 2026
Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.
Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…
AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.