Effect of birth ball usage on labour outcome and perinatal outcome
Bibliographic record
Abstract
Introduction: Reduction of pain during labor is addressed via general approaches, pharmacologic and non-pharmacological methods. Birth ball promotes optimal positioning of foetal presenting part to maternal pelvis and pain sensation reduction during labor. Objectives: To determine the effectiveness of birth ball exercises on reducing labour pain and duration and improving labour outcome among pregnant mothers. Methods: Randomized control trial was conducted in Obstetric Unit in Castle Street Hospital for Women. SNSOE technique was applied for allocation concealment. Interviewer administered data collection sheet, birth ball and an analogue visual pain scale were used as study instruments. Selected perinatal outcomes, duration and labour pain were compared between two study groups. Study was ethically cleared by the Ethic Review Committee of Faculty of Medicine, Colombo. Trial was registered in Sri Lanka Clinical Trial Registry. Results: Mean age was 29.33 years (SD=5.27 years). Mean gestational age of all the study participants was 279.47 days. (SD=5.63 days). Majority of the study participants had delivered their babies via NVD (N=66: 78.65) and 16.7% (N=16), of them were subjected to EM/LSCS. Mean BMI value was 28.13 kg/m2 (SD=1.72). Height and weight of the study participants showed a negative correlation with the duration of labour. Duration of labour showed a positive correlation with the BMI of the mothers. Significant reduction of mean labour pains and labour duration was noted in the group which experienced birth ball exercises when compared to the control group. Conclusions and recommendations: Duration of labour can be significantly reduced by applying the birth ball exercises procedure. It is beneficial to use the birth ball exercise procedure as a method of reducing labour pains. Expected amount of adverse perinatal outcomes was less among the mothers who used birth ball exercise. Birth ball exercise procedure can be identified as a practical strategy to increase intrapartum obstetric outcomes.
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.001 | 0.001 |
| 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.005 | 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".