Complications of unintentional dural puncture during labour epidural analgesia: a 10-year retrospective observational study
Bibliographic record
Abstract
INTRODUCTION: Unintentional dural puncture (UDP) occurs in 0.5-1.5% of labour epidural analgesia cases. To date, little is known about evidence of UDP-related complications. This work aimed to assess the incidence of intrapartum and postpartum complications in parturients who experienced UDP. METHODS: This is a 10-year retrospective observational study on parturients admitted to our centre who presented UDP. Data collection gathered UDP-related complications during labour and postpartum. All women who displayed UDP received medical therapy and bed rest. An epidural blood patch (EBP) was not used in this population. Once asymptomatic, patients were discharged from the hospital. RESULTS: Out of 7718 neuraxial analgesia cases, 97 cases of UDP occurred (1.25%). During labour, complications appeared in a small percentage of analgesia procedures performed, including total spinal anaesthesia (1.0%), extended motor block (3%), hypotension (4.1%), abnormal foetal heart rate (2%), inadequate analgesia (14.4%), and general anaesthesia following neuraxial anaesthesia failure (33.3% of emergency caesarean sections). During the postpartum period, 53.6% of parturients exhibited a postdural puncture headache, 13.4% showed neurological symptoms, and 14.4% required neurological consultation and neuroimaging. No patient developed subdural hematoma or cerebral venous sinus thrombosis; one woman presented posterior reversible encephalopathy syndrome associated with eclampsia. Overall, 82.5% of women experienced an extension of hospital stay. CONCLUSION: Major complications occurred in a small percentage of patients during labour. However, since they represent high-risk maternal and neonatal health events, a dedicated anaesthesiologist and a trained obstetric team are essential. No major neurological complications were registered postpartum, and EBP was not performed. Nevertheless, all patients with UDP were carefully monitored and treated until complete recovery before discharge, leading to an extension of their hospitalization.
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.001 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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".