| Literature DB >> 34816253 |
H J Odendaal1, I C Crockart2, C Du Plessis1, L Brink1, C A Groenewald1.
Abstract
OBJECTIVES: To use machine learning to determine what information on Doppler velocimetry and maternal and fetal heart rates, collected at 20-24 weeks gestation, correlates best with fetal growth restriction according to the estimated fetal weight at 34-38 weeks. STUDYEntities:
Keywords: Doppler velocimetry; Fetal heart rate; Fetal heart rate accelerations; Fetal movements; Machine learning; Umbilical artery
Year: 2021 PMID: 34816253 PMCID: PMC8607280
Source DB: PubMed Journal: Glob J Pediatr Neonatal Care ISSN: 2689-422X
Figure 1:An example graph showing the gained and lost beats of the fetal heart rate at 20 to 24 weeks.
The Feature Overview for each dataset, with a brief description of each feature. The names of the features have been changed for coherency purposes.
| Fetal and maternal heart rate information collected at 20-24 weeks (n=4764) |
|---|
| The number of times gained beats were recorded for the maternal heart rate |
| The sum of all the gained beats recorded for the maternal heart rate |
| Ratio of the total gained beats recorded per hour of recording for the maternal heart rate |
| The total time (in seconds) of the entire recording that were recorded as accelerations for the maternal heart rate |
| The total time (in seconds) of the recording for the maternal heart rate |
| The number of times lost beats were recorded for the maternal heart rate |
| The sum of all the lost beats recorded for the maternal heart rate |
| The number of times gained beats were recorded for the fetal heart rate |
| The sum of all the gained beats recorded for the fetal heart rate |
| Ratio of the total gained beats recorded per hour of recording for the fetal heart rate |
| The total time (in seconds) of the entire recording that were recorded as accelerations for the fetal heart rate |
| The total time (in seconds) of the recording for the fetal heart rate |
| The number of times lost beats were recorded for the fetal heart rate |
| The sum of all the lost beats recorded for the fetal heart rate |
|
|
| Pulsatility index for the umbilical artery (n=644) |
| Pulsatility index for the uterine artery (n=657) |
| Pulsatility index for the middle cerebral artery (n=638) |
| Whether or not the intrauterine growth restriction was less than 3% (n=429) |
| Whether or not the intrauterine growth restriction was less than 10% (n=429) |
Background maternal and fetal information of the participants.
| Variable | Mean | SD | Median | Range |
|---|---|---|---|---|
| Maternal age (years) | 24.6 | 5.9 | 24 | 16 - 45 |
| Body mass index (kg/m2) | 25.5 | 5.7 | 24.2 | 13.7 - 55.9 |
| Gestation at enrolment (days) | 134.8 (20.3 weeks) | 46.4 | 132 | 38 - 272 |
| Gestation at 20-24 weeks visit | 158.5 (22.6 weeks) | 6.3 | 160 | 136 −182 |
| Gestation at 34-38 weeks visit | 245.4 (35.1 weeks) | 7.2 | 243 | 226 −270 |
| Gestation at birth (days) | 270.7 (38.7 weeks) | 21.8 | 275 | 61 - 313 |
| Birthweight (gram) | 3002.9 | 583.7 | 3020 | 190 - 5740 |
| Birthweight z-score | −0.38 | 1 | −0.4 | −5.7 - 4.1 |
Figure 2:Feature ranking in terms of Information Gain, a metric determined by the Orange software.
fGB=fetal gained beats, F3_UMBILICAL_ARTERY_PI= Mean pulsatility index of the umbilical artery at 34-38 weeks, F3_AVG_UTERINE_ARTERY_PI=Mean pulsatility index of the uterine artery at 34-38 weeks, f_nLB=number of fetal lost beats, fAccDuration=Duration of fetal heart rate acceleration; nfGB=number of fetal gained beats, F3_MCA_PI= Mean pulsatility index of the middle cerebral artery at 34-38 weeks.
Figure 3:The receiver operator characteristic curve analysis graph for the four algorithms used.