aceModerate evidence
Published recordHealthGood Space
More
Identifying Patients for Cardiovascular Evaluation Using Artificial Intelligence and Team-Based Care in Ghana: The H-TRIAGE Study
- Truvace record
- TRV-2026-2465raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 51141e07658f…check it
Background: Cardiovascular diagnostic capacity is limited in many low-resource settings. We evaluated the HeartLINK Triage for Risk-Informed Allocation and Guided Evaluation (H-TRIAGE) index, a prespecified strategy combining clinical information and AI-enabled digital auscultation to prioritize cardiovascular evaluation. Methods: In this prospective study in Ghana (February-July 2026), consecutively enrolled adults underwent a standardized assessment by trained frontline nurses and community health workers. H-T…
The gain
In a prospective study of 3,800 adults in Ghana, a triage score built from symptoms, vital signs and an AI stethoscope, applied by nurses and community health workers, flagged who needed cardiologist-adjudicated evaluation and could defer roughly half of those assessed.
What this doesn’t fix
The allocation analysis was modeled rather than a real-world deployment, and external validation covered one held-out facility with 677 participants.
Sources
1 on file- Circulation: Population Health and Outcomesdoi:10.1161/circoutcomes.126.014561
Cite this record
v1Truvace Impact Record TRV-2026-2465, v1: “Identifying Patients for Cardiovascular Evaluation Using Artificial Intelligence and Team-Based Care in Ghana: The H-TRIAGE Study.” Truvace, 2026-11-11. /record/TRV-2026-2465 (accessed on the day you copy it). sha256 51141e07658fdad9…
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-2465 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.