Probability of intrauterine device perforation in a tertiary care hospital and its affiliated clinics

Logan C. Peterson, Timothy S. Batig, Alison L. Batig*

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

Abstract

OBJECTIVE: To determine the probability of clinically identified and confirmed intrauterine device (IUD) perforations within a tertiary care hospital and its affiliated clinics. STUDY DESIGN: This was an observational study from a tertiary care center and its affiliated clinics using coding data from our electronic medical record database and a search of descriptive terminology from ambulatory and inpatient electronic records from 2008–2014. We identified the total number of IUD placements and cases of IUD perforation. Using this data, we determined the probability of identified device perforations seen within our patient population per 1,000 placements. Patient and placement variables associated with device perforation were evaluated with descriptive statistics and by comparing relative risk. RESULTS: We identified 3,959 IUD placements occurring during the study period. During that interval there were 23 cases of IUD perforation. The probability of IUD perforation was 5.8 per 1,000 placements (95% CI 1.2–10.8). There was no significant difference in perforation risk based on the training stage and type or specialty of the provider performing the procedure. CONCLUSION: In clinical practice, the probability of IUD perforation may be higher than that suggested by prior studies.

Original languageEnglish
Pages (from-to)505-511
Number of pages7
JournalJournal of Reproductive Medicine
Volume63
Issue number6
StatePublished - Dec 2018

Keywords

  • Contraception
  • Contraceptive devices
  • Contraceptive IUD
  • Copper intrauterine devices
  • Hormone-releasing IUDs
  • Intrauterine device migration
  • Intrauterine devices
  • Intrauterine devices, Medicated
  • IUD migration
  • IUD, Copper-releasing
  • IUD, Hormone releasing
  • Uterine perforation

Cite this