Pregnancy Complicated by Complete Atrioventricular Block
Bibliographic record
Abstract
Bradycardia in pregnancy resulting from complete atrioventricular block (CAVB) is a rare but critical condition that can threaten both maternal and fetal health. If not managed appropriately, it can lead to severe complications, emphasizing the need for timely diagnosis and intervention. The incidence of CAVB during pregnancy is approximately 1 in 15,000 to 20,000 pregnancies. Most cases present clinically with symptoms such as syncope or palpitations, highlighting the importance of prompt recognition and management. While some patients with CAVB may be asymptomatic, symptomatic cases require urgent and definitive management. There is currently no established guideline for managing CAVB during pregnancy. We report the case of a 20-year-old primigravida at 35 weeks and 5 days of gestation, who presented with heart conduction problems (i.e., bradycardia) and arrived at the obstetric emergency department after receiving magnesium sulfate for seizure prophylaxis due to her high-risk profile and two intravenous doses of atropine sulfate. The patient experienced seizures and worsening bradycardia, prompting an emergency cesarean section. A female infant was delivered with a birth weight of 2,525 g, a length of 45 cm, and a New Ballard Score corresponding to gestational age of 36 weeks. No congenital anomalies were identified. The patient had an uncomplicated recovery and was discharged with a cardiologist’s recommendation for follow-up echocardiography. CAVB in pregnancy can arise from either congenital or acquired conditions, both of which may lead to maternal cardiovascular decompensation and fetal complications. In such cases, pacemaker implantation is often required to manage symptomatic bradycardia, and cesarean section may be the preferred mode of delivery to ensure both maternal and fetal safety. This case highlights the critical need for timely and appropriate management of symptomatic CAVB during pregnancy. Pacemaker implantation serves as the definitive treatment option for pregnant patients with CAVB, effectively addressing bradycardia and preventing further complications.
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.000 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".