Doubling Calcium and Phosphate Concentrations in Neonatal Parenteral Nutrition Solutions Using Monobasic Potassium Phosphate
Bibliographic record
Abstract
BACKGROUND: Premature infants require high intakes of Ca and P to mimic fetal accretion rates. With the current phosphate salt used, adequate amounts cannot be provided due to the precipitation of Ca and P in TPN solutions. OBJECTIVE: To compare monobasic potassium phosphate (monobasic regimen) and monobasic plus dibasic potassium phosphate (dibasic regimen) on calcium phosphate solubility in 5 amino acid products, and to determine whether solubility differences observed in these products can be explained by buffering capacity. METHODS: TPN solutions were prepared according to standard clinical practice. The following amino acid products were used at 3% concentrations: Primene, Vamin N, TrophAmine, Aminosyn-PF, and Travasol. Dextrose 10%, standard electrolytes, heparin, vitamins and trace elements were added. Calcium (as gluconate) and phosphate (as monobasic or dibasic regimen) were added in one-to-one molar ratios from 0-45 mmol/L. Solutions were inspected macroscopically and microscopically for precipitation under three conditions: immediately, 24 h after preparation at room temperature, and 3 h later in a 37 degrees C water bath. Buffering capacity was determined for each amino acid product by titrating with standardized 0.1 M NaOH. RESULTS: Variations in Ca:P solubility and buffer capacity exist between amino acid solutions. With Primene and Vamin no macroscopic or microscopic precipitation was detected up to 45 mmol/L using monobasic regimen, compared to 25 mmol/L using dibasic regimen with Trophamine. Buffer capacity did not account for the solubility differences observed between the five amino acid products, which were related to the pH of the final solution. CONCLUSIONS: These data will allow clinicians to double the current concentrations of calcium and phosphate in neonatal TPN solutions using monobasic regimen. Although this is particularly relevant to situations when fluid intake is restricted, the effect of the acid load needs to be investigated in extremely low birth weight infants.
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.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| 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".