Hepcidin-guided screen-and-treat interventions against iron-deficiency anaemia in pregnancy: a randomised controlled trial in The Gambia

BackgroundWHO recommends daily iron supplementation for pregnant women, but adherence is poor because of side-effects, effectiveness is low, and there are concerns about possible harm. The iron-regulatory hormone hepcidin can signal when an individual is ready-and-safe to receive iron. We tested whether a hepcidin-guided screen-and-treat approach to combat iron-deficiency anaemia could achieve equivalent efficacy to universal administration, but with lower exposure to iron.MethodsWe did a three-arm, randomised, double-blind, non-inferiority trial in 19 rural communities in the Jarra West and Kiang East districts of The Gambia. Eligible participants were pregnant women aged 18–45 years at between 14 weeks and 22 weeks of gestation. We randomly allocated women to either WHO's recommended regimen (ie, a daily UN University, UNICEF, and WHO international multiple-micronutrient preparation [UNIMMAP] containing 60 mg iron), a 60 mg screen-and-treat approach (ie, daily UNIMMAP containing 60 mg iron for 7 days if weekly hepcidin was <2·5 μg/L or UNIMMAP without iron if hepcidin was ≥2·5 μg/L), or a 30 mg screen-and-treat approach (ie, daily UNIMMAP containing 30 mg iron for 7 days if weekly hepcidin was <2·5 μg/L or UNIMMAP without iron if hepcidin was ≥2·5 μg/L). We used a block design stratified by amount of haemoglobin at enrolment (above and below the median amount of haemoglobin on every enrolment day) and stage of gestation (14–18 weeks vs 19–22 weeks). Participants and investigators were unaware of the random allocation. The primary outcome was the amount of haemoglobin at day 84 and was measured as the difference in haemoglobin in each screen-and-treat group compared with WHO's recommended regimen; the non-inferiority margin was set at −5·0 g/L. The primary outcome was assessed in the per-protocol population, which comprised all women who completed the study. This trial is registered with the ISRCTN registry, number ISRCTN21955180.FindingsBetween June 16, 2014, and March 3, 2016, 498 participants were randomised, of whom 167 were allocated to WHO's recommended regimen, 166 were allocated to the 60 mg per day screen-and-treat approach, and 165 were allocated to the 30 mg per day screen-and-treat approach. 78 participants were withdrawn or lost to follow-up during the study; thus, the per-protocol population comprised 140 women assigned to WHO's recommended regimen, 133 allocated to the 60 mg screen-and-treat approach, and 147 allocated to the 30 mg screen-and-treat approach. The screen-and-treat approaches did not exceed the non-inferiority margin. Compared with WHO's recommended regimen, the difference in the amount of haemoglobin at day 84 was −2·2 g/L (95% CI −4·6 to 0·1) with the 60 mg screen-and-treat approach and −2·7 g/L (–5·0 to −0·5) with the 30 mg screen-and-treat approach. Adherence, reported side-effects, and adverse events were similar between the three groups. The most frequent side-effect was stomachache, which was similar in the 60 mg screen-and-treat group (82 cases per 1906 person-weeks) and with WHO's recommended regimen (81 cases per 1974 person-weeks; effect 1·0, 95% CI 0·7 to 1·6); in the 30 mg screen-and-treat group the frequency of stomachache was slightly lower than with WHO's recommended regimen (58 cases per 2009 person-weeks; effect 0·7, 95% CI 0·5 to 1·1). No participants died during the study.InterpretationThe hepcidin-guided screen-and-treat approaches had no advantages over WHO's recommended regimen in terms of adherence, side-effects, or safety outcomes. Our results suggest that the current WHO policy for iron administration to pregnant women should remain unchanged while more effective approaches continue to be sought.FundingBill & Melinda Gates Foundation and the UK Medical Research Council.

Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.