Placental Compared With Umbilical Cord Blood to Assess Fetal Blood Gas and Acid-Base Status
Bibliographic record
Abstract
OBJECTIVE: To estimate the extent to which placental cord blood sampled from the umbilical cord at its insertion into the placenta and after delivery of the placenta, is in agreement with umbilical cord blood sampled from a clamped segment of the umbilical cord after delivery of the infant, for the assessment of fetal blood gas, acid-base status, and hemoglobin levels at birth. METHODS: Forty-eight patients were studied with arterial and venous blood sampling from the umbilical cord and from the placental cord insertion, with subsequent measurement of blood gases, pH, base excess, O2 saturation, and hemoglobin. The relationships of corresponding measurements from the placental and umbilical vein and from the placental and umbilical artery were analyzed using regression analysis, paired analysis of grouped means, and by estimating limits of agreement. RESULTS: The relationships between placental and umbilical cord blood measurements were described using a linear mathematical model, and although respective measurements were all significantly related (P < .01), this was strongest for both venous and arterial base excess and hemoglobin measurements (r values 0.91 to 0.99) and variably weaker for venous and arterial Po2 (and thereby O2 saturation measurements [r values 0.36 to 0.89]) and arterial Pco2 (and thereby pH measurements [r values 0.66 to 0.73]). Whereas base excess and hemoglobin measurements for both the venous and arterial placental and umbilical cord bloods were close in value over the range of values studied, Po2 and thereby O2 saturation values were variably lower in the placental vein compared with the umbilical vein, while Pco2 values were variably lower and thereby pH values conversely higher in the placental artery compared with the umbilical artery. Limits of agreement as a measure of the difference between paired placental and umbilical cord blood measurements were such that only those for base excess and hemoglobin were likely narrow enough to be acceptable for clinical purposes. CONCLUSION: Placental cord blood provides for a close estimate of fetal base excess and hemoglobin status at birth, but with more error for Po2 and thereby O2 saturation and Pco2 and thereby pH due to continued blood gas exchange within and across the placenta after cord clamping.
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.002 | 0.009 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
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".