Use of umbilical artery Doppler velocimetry in the monitoring of pregnancy in women with pre-existing diabetes

Background: The usefulness of umbilical artery Doppler velocimetry for the monitoring of diabetic pregnancies is controversial. The aim of the present study was to assess whether umbilical artery Doppler velocity waveform analysis can predict adverse perinatal outcomes for pregnancies complicated by pre-existing diabetes mellitus. Methods: All diabetic pregnancies (type 1 and 2) delivered at Mater Mothers' Hospital, Queensland, between 1 January 1995 and 31 December 1999 were included. All pregnant diabetic women were monitored with umbilical artery Doppler velocimetry at 28, 32, 36, and 38 weeks' gestation. Adverse perinatal outcome was defined as pregnancies with one or more of the following: small-for-gestational age, Caesarean section for non-reassuring cardiotocography, fetal acidaemia at delivery, 1-min Apgar of 3 or less, 5-min Apgar of less than 7, hypoxic ischaemic encephalopathy or perinatal death. Abnormal umbilical artery Doppler velocimetry was defined as a pulsatility index of 95th centile or higher for gestation. Results: One hundred and four pregnancies in women with pre-existing diabetes had umbilical arterial Doppler studies carried out during the study period. Twenty-three pregnancies (22.1%) had an elevated pulsatility index. If the scans were carried out within 2 weeks of delivery, 71% of pregnancies with abnormal umbilical Doppler had adverse outcomes (P < 0.01; likelihood ratio, 4.2). However, the sensitivity was 35%; specificity was 94%; positive predictive value was 80%; and negative predictive value was 68%. Only 30% of women with adverse perinatal outcomes had abnormal umbilical arterial Doppler flow. Conclusion: Umbilical artery Doppler velocimetry is not a good predictor of adverse perinatal outcomes in diabetic pregnancies.

Obstacles to a totally functional programming style

"Totally functional programming" (TFP) advocates the complete replacement of symbolic representations for data by functions. TFP is motivated by observations from practice in language extensibility and functional programming. Its technical essence extends the role of "fold" functions in structuring functional programs to include methods that make comparisons on elements of data structures. The obstacles that currently prevent the immediate uptake of TFP as a style within functional programming equally indicate future research directions in the areas of theoretical foundations, supporting technical infrastructure, demonstrated practical applicability, and relationship to OOP.