Adverse events from spinal manipulation in the pregnant and postpartum periods: a critical review of the literature
Bibliographic record
Abstract
BACKGROUND: The safety of spinal manipulation during pregnancy and the postpartum periods has been a matter of debate among manual therapists. Spinal manipulative therapy during these periods is a commonly performed intervention as musculoskeletal pain is common in these patients. To date there has not been an evaluation of the literature on this topic exclusively. METHODS: A literature search was conducted on PubMed, CINAHL and the Index to Chiropractic Literature along with reference searching for articles published in English and French in the peer-reviewed literature that documented adverse effects of spinal manipulation during either pregnancy or postpartum. Case reports, case series, and any other clinical study designs were deemed acceptable for inclusion, as were systematic reviews. The appropriate Scottish Intercollegiate Guidelines Network (SIGN) tools were used to rate included articles for quality when applicable. RESULTS: Five articles identifying adverse events in seven subjects following spinal manipulation were included in this review, along with two systematic reviews. The articles were published between 1978 and 2009. Two articles describing adverse effects from spinal manipulation on two postpartum patients were included, while the remaining three articles on five patients with adverse effects following spinal manipulation were on pregnant patients. Injury severity ranged from minor injury such as increasing pain after treatment that resolved within a few days to more severe injuries including fracture, stroke, and epidural hematoma. SIGN scores of the prospective observational cohort study and systematic reviews indicated acceptable quality. CONCLUSIONS: There are only a few reported cases of adverse events following spinal manipulation during pregnancy and the postpartum period identified in the literature. While improved reporting of such events is required in the future, it may be that such injuries are relatively rare.
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.010 | 0.049 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.004 | 0.004 |
| Bibliometrics | 0.011 | 0.008 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.003 | 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".