MétaCan
Menu
Back to cohort
Record W2159994422 · doi:10.1177/1753495x13513577

Timing of delivery in women with diabetes in pregnancy

2014· review· en· W2159994422 on OpenAlex
Howard Berger, Nir Melamed

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

VenueObstetric Medicine · 2014
Typereview
Languageen
FieldMedicine
TopicGestational Diabetes Research and Management
Canadian institutionsUniversity of TorontoSt. Michael's Hospital
Fundersnot available
KeywordsMedicineGestational diabetesObstetricsPregnancyDiabetes mellitusIncidence (geometry)Type 2 diabetesGestationGestational ageIntensive care medicineEndocrinology

Abstract

fetched live from OpenAlex

The incidence of both gestational and pre-gestational diabetes is increasing worldwide. The main cause of this increase is likely the concomitant increase in the incidence of global obesity, but in the case of gestational diabetes, changes in the diagnostic criteria are also a contributing factor. The adverse outcomes associated with pre-gestational diabetes are well known and have led clinicians to implement various strategies that include increased fetal surveillance and induction of labour at various gestational ages. In many cases these same strategies have been applied in clinical practice also to women with gestational diabetes despite there being differences in the type and magnitude of perinatal complications associated with this diagnosis. Despite the widespread application of these clinical practices, there is a paucity of quality data in the medical literature to guide the clinician in choosing a strategy for fetal surveillance and timing of delivery in both gestational diabetes and pre-gestational diabetes pregnancies. In the following review, we will discuss the rationale and consequences of planned delivery in gestational diabetes and pre-gestational diabetes, the evidence supporting different strategies for delivery and finally highlight future targets for research in this area.

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.001
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.920
Threshold uncertainty score0.792

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0020.000
Bibliometrics0.0020.002
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.048
GPT teacher head0.328
Teacher spread0.279 · 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