Elevation of plasma homocysteine levels associated with acute myocardial infarction.
Bibliographic record
Abstract
OBJECTIVE: To study the effect of acute myocardial infarction (AMI) on plasma homocystein (Hcy) levels, to determine the optimal time to measure this risk factor for coronary artery disease. DESIGN: A prospective case study. SETTING: The Division of Cardiac Sciences, Grey Nuns Hospital in Edmonton. PATIENTS: Sixty-two patients (40 men, 22 women) admitted to hospital with AMI. INTERVENTION: Measurement of Hcy levels within 48 to 72 hours of admission and at 6 weeks after discharge from the Coronary Care Unit. In a second group of 15 patients, the Hcy levels were measured on hospital days 1 and 3. MAIN OUTCOME MEASURE: Comparison of the Hcy levels measured at the time of AMI and after discharge. RESULTS: Mean (and standard error of the mean) Hcy level measured during the AMI (13.6 [0.98] micromol/L) was significantly higher (p < 0.05) than at 6 weeks (12.1 [1.01] micromol/L). Based on the 48- to 72-hour and 6-week determinations, 31 and 21 patients, respectively, had abnormal Hcy levels (greater than 12 micromol/L) (p < 0.001). In the separate group of 15 patients, the Hcy level measured on day 3 (9.7 [0.6] micromol/L) was noted to be significantly higher (p < 0.01) than on day 1 (7.7 [0.8] micromol/L). CONCLUSIONS: There is an elevation of Hcy during AMI that may be related to an increase in the acute-phase reactant proteins. Thus, Hcy measurement should be deferred for 6 weeks in order to determine the true baseline level.
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.001 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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".