Assessing the Utility of a Novel SMS- and Phone-Based System for Blood Pressure Control in Hypertensive Patients: Feasibility Study
Bibliographic record
Abstract
BACKGROUND: Although hypertension (HTN) is a major modifiable risk factor for arterial damage, blood pressure (BP) remains poorly controlled in the hypertensive population. Telemedicine is a promising adjunct intervention that may complement traditional therapies and improve adherence rates; however, current approaches have multiple barriers to entry, including the use of relatively expensive Bluetooth devices or the dependence on smart phone utilization, which tend to exclude low-income and more elderly populations. OBJECTIVE: The aim of this study was to design and implement a new phone call- and short message service text messaging-based intervention, Epharmix's EpxHypertension, in a quality improvement project that demonstrates the feasibility of this system for BP control in a family medicine setting. METHODS: We recruited 174 patients from a community clinic in St Louis from a database of patients diagnosed with HTN. An automated call or text messaging system was used to monitor patient-reported BPs. If determined to be elevated, physicians were notified by an email, text, or electronic medical record alert. Mean systolic BPs (SBPs) and diastolic BPs (DBPs) were compared at the beginning and end of 12 weeks. RESULTS: After 12 weeks on the system, patients with a baseline SBP of 140 mm Hg or higher reduced SBP by 10.8 mm Hg (95% CI -14.5 to -7.2, P<.001) and DBP by 6.6 mm Hg (95% CI -9.9 to -3.4, P=.002), but no significant changes were observed in overall BPs and BPs in the group with baseline SBP less than 140 mm Hg. CONCLUSIONS: EpxHypertension provides a viable means to control HTN in patients with high baseline BPs despite previous therapy. This community implementation study demonstrates the feasibility of implementing EpxHypertension across a primary care setting without the need for smartphones or Bluetooth-linked BP cuffs. Future studies should evaluate its effectiveness in a randomized control trial compared with standard of care.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.008 | 0.014 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".