Hydralazine for treatment of severe hypertension in pregnancy: meta-analysis
Bibliographic record
Abstract
OBJECTIVE: To review outcomes in randomised controlled trials comparing hydralazine against other antihypertensives for severe hypertension in pregnancy. STUDY DESIGN: Meta-analysis of randomised controlled trials (published between 1966 and September 2002) of short acting antihypertensives for severe hypertension in pregnancy. Independent data abstraction by two reviewers. Data were entered into RevMan software for analysis (fixed effects model, relative risk and 95% confidence interval); in a secondary analysis, risk difference was also calculated. RESULTS: Of 21 trials (893 women), eight compared hydralazine with nifedipine and five with labetalol. Hydralazine was associated with a trend towards less persistent severe hypertension than labetalol (relative risk 0.29 (95% confidence interval 0.08 to 1.04); two trials), but more severe hypertension than nifedipine or isradipine (1.41 (0.95 to 2.09); four trials); there was significant heterogeneity in outcome between trials and differences in methodological quality. Hydralazine was associated with more maternal hypotension (3.29 (1.50 to 7.23); 13 trials); more caesarean sections (1.30 (1.08 to 1.59); 14 trials); more placental abruption (4.17 (1.19 to 14.28); five trials); more maternal oliguria (4.00 (1.22 to 12.50); three trials); more adverse effects on fetal heart rate (2.04 (1.32 to 3.16); 12 trials); and more low Apgar scores at one minute (2.70 (1.27 to 5.88); three trials). For all but Apgar scores, analysis by risk difference showed heterogeneity between trials. Hydralazine was associated with more maternal side effects (1.50 (1.16 to 1.94); 12 trials) and with less neonatal bradycardia than labetalol (risk difference -0.24 (-0.42 to -0.06); three trials). CONCLUSIONS: The results are not robust enough to guide clinical practice, but they do not support use of hydralazine as first line for treatment of severe hypertension in pregnancy. Adequately powered clinical trials are needed, with a comparison of labetalol and nifedipine showing the most promise.
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.015 | 0.041 |
| Meta-epidemiology (narrow) | 0.004 | 0.002 |
| Meta-epidemiology (broad) | 0.024 | 0.035 |
| Bibliometrics | 0.005 | 0.004 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.003 | 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".