Moderate evidence
Published recordHealthProblem Space
More
Artificial intelligence driven software systems for cardiovascular disease detection using physiological signals: a systematic review
- Truvace record
- TRV-2026-2955raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Systematic review or meta-analysis
- Sources
- 1 sourcePeer-reviewed
- sha256
- cd7de624eff0…check it
Abstract Cardiovascular disease exacts an extraordinary global toll, with annual mortality exceeding 17.9 million lives and representing nearly one-third of all deaths worldwide. Reducing diagnostic delays, particularly in resource-limited settings, requires innovative, scalable, and cost-effective solutions. Artificial intelligence integrated with physiological signals, such as electrocardiogram (ECG), photoplethysmogram (PPG) and phonocardiogram (PCG), offers promising pathways for scalable, real-time cardiova…
The problem
A systematic review of 35 studies of AI heart-disease detection from ECG, PPG and PCG signals found only 23% used external validation and only 14% reached clinical-scale deployment.
What this doesn’t fix
Differences in reported metrics and validation methods ruled out a quantitative meta-analysis, and the search covered only English-language peer-reviewed journal articles, so relevant conference papers, preprints and non-English work may be missing.
Sources
1 on file- Artificial Intelligence Reviewdoi:10.1007/s10462-026-11756-7
Cite this record
v1Truvace Impact Record TRV-2026-2955, v1: “Artificial intelligence driven software systems for cardiovascular disease detection using physiological signals: a systematic review.” Truvace, 2026-11-16. /record/TRV-2026-2955 (accessed on the day you copy it). sha256 cd7de624eff03d3a…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2955 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.
ace