Stable versus progressive hepatitis unique to pregnancy
Bibliographic record
Abstract
BACKGROUND: Urgent delivery of the fetus is often considered as the treatment of choice for mothers in their second or third trimester with hepatitis unique to pregnancy (HUP). OBJECTIVE: To determine whether standard liver function tests (serum bilirubin and international normalized ratio levels) help to identify mothers and their newborns who might benefit from early delivery. METHODS: A total of 149 patients with HUP were retrospectively classified as those with normal (stable-HUP, n=118) or abnormal (progressive-HUP, n=31) liver function tests. Clinical outcomes consisted of maternal lengths of hospital stay after delivery and neonatal appearance, pulse, grimace, activity, respiration score ratings at 0 and 5 min. RESULTS: Patients with stable-HUP had similar lengths of hospital stay after delivery whether delivered early (4.8±3.4 days) or at term (4.8±3.6 days). Appearance, pulse, grimace, activity, respiration score ratings at birth were similar in neonates from patients with stable-HUP delivered prematurely (5.8±2.7) and at term (7.8±1.7, P=0.48) but significantly higher at 5 min in those delivered at term (7.5±2.0 vs. 8.9±0.3, P=0.003). Too few patients with progressive-HUP were delivered at term (N=4) to allow similar comparisons in this cohort. CONCLUSION: The results of this study indicate that mothers with HUP and normal liver function tests (bilirubin and international normalized ratio) can be safely followed to term without jeopardizing the health of either mother or neonates. Additional studies are required to determine whether abnormal liver function tests represent an indication for immediate delivery of the fetus in mothers with HUP.
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.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.002 | 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".