Machine Learning for Hypertension Prediction: a Systematic Review

• Published in: Current hypertension reports Vol. 24; no. 11; pp. 523 - 533
• Main Authors: Silva, Gabriel F. S., Fagundes, Thales P., Teixeira, Bruno C., Chiavegatto Filho, Alexandre D. P.
• Format: Journal Article
• Language: English
• Published: New York Springer US 01.11.2022; Springer Nature B.V
• Subjects: Algorithms; Area Under Curve; Cardiology; Family Medicine; General Practice; Guidelines/Clinical Trials/Meta-Analysis (WJ Kostis; Humans; Hypertension; Hypertension - diagnosis; Internal Medicine; Machine Learning; Medicine; Medicine & Public Health; Metabolic Diseases; Nephrology; Primary Care Medicine; Section Editor; Support Vector Machine; Systematic review; Topical Collection on Guidelines/Clinical Trials/Meta-Analysis; Hypertension; Systematic review; Model construction; Evaluation metrics; Machine learning
• ISSN: 1522-6417; 1534-3111; 1534-3111
• DOI: 10.1007/s11906-022-01212-6

Purpose of Review To provide an overview of the literature regarding the use of machine learning algorithms to predict hypertension. A systematic review was performed to select recent articles on the subject. Recent Findings The screening of the articles was conducted using a machine learning algorithm (ASReview). A total of 21 articles published between January 2018 and May 2021 were identified and compared according to variable selection, train-test split, data balancing, outcome definition, final algorithm, and performance metrics. Overall, the articles achieved an area under the ROC curve (AUROC) between 0.766 and 1.00. The algorithms most frequently identified as having the best performance were support vector machines (SVM), extreme gradient boosting (XGBoost), and random forest. Summary Machine learning algorithms are a promising tool to improve preventive clinical decisions and targeted public health policies for hypertension. However, technical factors such as outcome definition, availability of the final code, predictive performance, explainability, and data leakage need to be consistently and critically evaluated.