TRV-2026-2955Version 1 · Published

Saved · see the current record

Why this version exists

Certified into the record

The exact text we saved

This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.

TRUVACE RECORD VERSION
record: TRV-2026-2955
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-11-16T00:03:18.847404Z
status: published
lens: p_space
sector: health
headline: Artificial intelligence driven software systems for cardiovascular disease detection using physiological signals: a systematic review
dek: 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…
gain_title: (none)
problem_title: 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.
trace_subject: (none)
gain_reading: (none)
gain_evidence: (none)
problem_reading: 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.
problem_evidence: only 23% of studies conducted external validation, only 14% achieved clinical-scale deployment
quick_read: A systematic review of 35 peer-reviewed studies on AI software for detecting cardiovascular disease from heart signals found strong reported accuracy but thin real-world validation. Reported accuracies ranged from 70.5% to 99.9%, with an unweighted mean of 93.7% across the 21 studies that reported it. Only 23% of studies tested their systems on external data, and only 14% reached clinical-scale deployment.

The gaps matter because cardiovascular disease kills more than 17.9 million people a year, nearly a third of all deaths worldwide, and faster diagnosis in resource-limited settings is a stated aim of these tools. The authors say inconsistent metric reporting and limited external validation weaken confidence that benchmark results will carry over to clinics.

Most systems relied on a single signal: ECG was used in 71.4% of systems, mainly with deep learning models. None combined ECG, PPG and PCG through principled multi-signal fusion, and just one of the 35 systems offered a patient-facing conversational interface. The authors propose a framework built on multi-signal models, LLM-generated clinical narratives and edge-cloud deployment, but it is a proposal and has not been tested.
limitation: 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.
tag: Evidence-backed problem
key_points: The review searched five databases (Scopus, Web of Science, PubMed, Embase and IEEE Xplore) under PRISMA guidance and identified 35 eligible peer-reviewed studies. | Study quality and risk of bias were appraised with a framework adapted from QUADAS-2. | ECG was the input signal in 71.4% of systems, mostly analysed with convolutional and recurrent neural networks. | Reported accuracy ranged from 70.5% to 99.9% (21 studies reporting, unweighted mean 93.7%), but metric reporting was inconsistent across studies. | Only 23% of studies carried out external validation and only 14% achieved clinical-scale deployment. | No study combined ECG, PPG and PCG through principled multi-signal fusion, and only 1 of 35 systems (2.9%) had a patient-facing conversational interface. | The authors propose three research directions: multi-signal models for generalisability, LLM-driven clinical narratives for interpretability, and edge-cloud deployment for accessibility.
rundown: The review covered software systems that apply machine learning to ECG, photoplethysmogram and phonocardiogram signals, including apps, wearables and cloud platforms. Deep learning dominated, with convolutional and recurrent neural networks the most common architectures. Accuracy alone was often the headline metric, and the authors say the lack of consistent reporting made cross-study comparison difficult.

Validation was the weakest area. Many systems were evaluated on legacy public benchmark datasets such as MIT-BIH, which the authors say lack demographic diversity and real-world signal noise, and hospital-acquired data were rarely used. Large-scale deployments were rare, with examples such as the Huawei Heart Study of 187,912 participants standing out.

The authors argue single-signal ECG systems miss the mechanical and blood-flow dimensions of heart function, and that explainability tools such as saliency maps do not match how clinicians reason. They also report that regulatory alignment and real-world testing for latency, battery use and network variability were largely absent, so prototypes cannot move toward clinical certification without redesign.

The proposed framework would fuse ECG, PPG and PCG signals, use large language models to turn probability outputs into clinical narratives, and run lightweight screening on edge devices with a patient chatbot. These are recommendations for future research, not tested systems.
sources:
- peer_reviewed | Artificial Intelligence Review | https://doi.org/10.1007/s10462-026-11756-7 | 2026-11-14
prev: 0000000000000000000000000000000000000000000000000000000000000000
SHA-256 hash
cd7de624eff03d3a8ac215b389c12a9316d43aa979a4a40db7286ff83ad9d2fa
Previous version’s hash
0000000000000000000000000000000000000000000000000000000000000000
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.