MétaCan
Menu
Back to cohort
Record W2900314228 · doi:10.2147/ijwh.s175088

Shoulder dystocia: incidence, mechanisms, and management strategies

2018· review· en· W2900314228 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

VenueInternational Journal of Women s Health · 2018
Typereview
Languageen
FieldMedicine
TopicCardiovascular Issues in Pregnancy
Canadian institutionsUniversity of Manitoba
Fundersnot available
KeywordsMedicineShoulder dystociaIncidence (geometry)Intensive care medicineObstetricsPregnancy

Abstract

fetched live from OpenAlex

Shoulder dystocia can lead to death or brain damage for the baby. Traction on the head can damage the brachial plexus. The diagnosis should be made when the mother cannot push the shoulders out with her own efforts with the next contraction after delivery of the head. There should be no traction on the head to diagnose shoulder dystocia. McRoberts' position is acceptable but it should not be accompanied by any traction on the head. If the posterior shoulder is in the sacral hollow then the best approach is to use posterior axillary traction to deliver the posterior shoulder and arm. If both shoulders are above the pelvic brim, the posterior arm should be brought down with Jacquemier's maneuver. If that fails, cephalic replacement or symphysiotomy is the next step. After shoulder dystocia is resolved, one should wait 1 minute or so to allow placental blood to return to the baby before cutting the umbilical cord.

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.002
metaresearch head score (Gemma)0.000
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.967
Threshold uncertainty score0.909

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0020.001
Bibliometrics0.0010.000
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.039
GPT teacher head0.406
Teacher spread0.367 · 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