Homocysteine lowering for stroke prevention: Unravelling the complexity of the evidence
Bibliographic record
Abstract
Elevated levels of total homocysteine impair endothelial dysfunction and increase thrombosis. Homocysteine is causal in animal models, and in human studies, elevated total homocysteine is significantly associated with carotid atherosclerosis, lacunar infarction, and markedly increased risk of stroke in atrial fibrillation. Because two of the early large trials of B vitamin therapy (Vitamin Intervention for Stroke Prevention and the Norwegian Vitamin Study) did not show any reduction of stroke, and the Heart Outcomes Prevention Evaluation 2 trial was mistakenly interpreted as not showing a reduction of stroke (because the authors could not think of a biological difference between stroke and myocardial infarction), there has been widespread pessimism regarding treatment to lower total homocysteine for stroke prevention. However, the Heart Outcomes Prevention Evaluation 2 trial, the French trial of folic acid and omega three oils, the Vitamins to Prevent Stroke subgroup excluding antiplatelet therapy all showed a significant reduction of stroke. Reasons why the Vitamin Intervention for Stroke Prevention trial were negative included folate fortification in North America, provision of injections of B12 to patients with low baseline serum B12, and as it turns out, harm from cyanide in cyanocobalamin among participants with impaired renal function. In the Diabetic Intervention with Vitamins in Nephropathy trial, B vitamins including cyanocobalamin were harmful, and in a Vitamin Intervention for Stroke Prevention subgroup excluding participants who received B12 injections and those with impaired renal function, there was a statistically significant reduction of stroke/myocardial infarction/vascular death. In 2015, the China Stroke Primary Prevention Trial (CSPPT), in over 20,000 participants followed for 5 years, showed a significant reduction of stroke with folic acid in a setting where folate fortification has not been implemented. In the setting of folate fortification, the main causes of elevated total homocysteine are renal failure and metabolic B12 deficiency; the latter is very common among stroke patients (30% over age 71), and frequently missed. Serum B12 and total homocysteine should be checked routinely in stroke patients and elevated total homocysteine should be treated.
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.035 | 0.070 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.007 | 0.003 |
| Bibliometrics | 0.005 | 0.004 |
| Science and technology studies | 0.001 | 0.004 |
| Scholarly communication | 0.007 | 0.015 |
| Open science | 0.004 | 0.004 |
| Research integrity | 0.007 | 0.018 |
| Insufficient payload (model declined to judge) | 0.007 | 0.002 |
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".