MétaCan
Menu
Back to cohort
Record W2121915858 · doi:10.5001/omj.2012.101

No More Milk in Milk-Alkali Syndrome: A Case Report

2012· article· en· W2121915858 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueOman Medical Journal · 2012
Typearticle
Languageen
FieldMedicine
TopicVitamin D Research Studies
Canadian institutionsMcMaster University
Fundersnot available
KeywordsMedicineCalciumAntacidMetabolic alkalosisProton-pump inhibitorGastroenterologyInternal medicine

Abstract

fetched live from OpenAlex

This is a case of Milk-AlKali syndrome in a patient who presented with the classical triad of hypercalcemia, metabolic alkalosis and renal impairment. The source of calcium was over-the-counter calcium-containing antacid (Tums®). Milk-alkali syndrome was first recognized secondary to treatment of peptic ulcer disease with milk and absorbable alkali. Its incidence fell after the introduction of H2-blocker and proton pump inhibitor. However, it is one of the leading causes of hypercalcemia nowadays because of the wide availability, increased marketing and use of calcium carbonate especially in osteoporosis prevention and treatment. The demographics of milk-alkali syndrome have changed compared to when it was initially described. The presentation could be acute, subacute or chronic. Early diagnosis, discounting calcium supplement and intravenous hydration are the mainstay of MAS management.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.007
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Case report · Consensus signal: Case report
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.072
Threshold uncertainty score0.998

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.007
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.002
Insufficient payload (model declined to judge)0.0020.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.

Opus teacher head0.027
GPT teacher head0.358
Teacher spread0.331 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it