MétaCan
Menu
Back to cohort

Fetal Kicking Monitoring Device for Intrauterine Death Prevention

2016· article· en· W2340487428 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

VenueIndian Journal of Science and Technology · 2016
Typearticle
Languageen
FieldMedicine
TopicNeonatal and fetal brain pathology
Canadian institutionsUniversity of Ottawa
Fundersnot available
KeywordsFetal movementFetusMedicinePregnancyFetal heartObstetrics

Abstract

fetched live from OpenAlex

Background: The fetal health is possible to fluctuate and deteriorate and lead to unexpected loss of the pregnancy. Time is crucial for heart life and any decrease in oxygen to the heart muscle is crucial and means death. Therefore, it is substantial to do an obstetric tracing, in order to spot the sudden changes in the fetus health. Problem Statement: Away from all the methods that could measure heart health, fetus movements monitoring is one way to identify the fetal wellbeing. One very popular movement that is used to gauge fetal health is a fetal kick, in which a frequency of perceived and/or registered fetal kicks by a healthy fetus is higher as compared to the frequency of perceived and/or registered fetal kicks a by an unhealthy fetus. However, the conventional methods such as ultrasound and manual measurement endure some errors. Objective: The aim of this study is to develop a portable belt that can be used to measure the fetal movement accurately by setting the appropriate threshold. Methods: A total of 9 Force Sensitive Resistors (FSR) were used to detect a simulated force exerted by fetus on the abdomen of pregnant women in order to count the fetal movements. Finding: Based on the overall result the sensor detects 90% of the kicks given. Conclusion: We believe that this device could help the pregnant women to measure the fetal movement with less attention and can reduce the error. Keywords: Fetal Health and Technology, Kicks, Monitoring, Sensor

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.660
Threshold uncertainty score0.249

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0000.001
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.023
GPT teacher head0.307
Teacher spread0.283 · 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