ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

My External Version Experience

Updated on January 22, 2015

I was clipping along my healthy and relatively easy pregnancy when the ultra sound technician discovered our little girl was Breech at our 33 week appoitment. I was completely stunned. What I had thought to be kicks at the top of my stomach, weren’t just kicks but were also punches and head movement as the aforementioned body parts were at the top of my uterus and her little rear end had sunk deep into my pelvis in a position called Frank Breech.

It took a few seconds for me to register the implications of this discovery—that my goal of having a completely natural virginal delivery wasn’t looking likely. It brought tears to my eyes and I felt crushed. The doctor told me that there was still a chance she could turn and that they would check again at my next appointment 2 weeks later. During those two weeks I tried every nutty suggestion I could find based on articles like this one:

http://spinningbabies.com/baby-positions/breech-bottoms-up/305-body-work-for-breech

Every day I got into a swimming pool and did flips and head stands. I put ice on top of my uterus while sitting at my desk hoping the cool sensation on her head would convince her to turn. I inverted myself while watching TV, rocked on my hands and knees while talking on the phone and at the end of the two weeks I had convinced myself that she had flipped. She hadn’t. And she still hadn’t when they checked again at 37 weeks. In these weeks I felt myself slipping into a funk as I struggled watching my dream of a natural birth disintegrate. I wish I had possessed the wisdom to be grateful that our baby was healthy (despite being poorly positioned) and had accepted that she would come in her own time and in her own way.

Since hindsight is 20/20, I jumped at the option of the External Version Procedure when my doctor suggested it at my 37 week appointment and it was scheduled for the following day. I had been preparing myself for this route and had found the following resources helpful when understanding what I was getting myself into:

http://www.webmd.com/baby/external-cephalic-version-version-for-breech-position

https://www.youtube.com/watch?v=6AM6wDwTjmc

The procedure was preformed at our hospital in case of any complications. We were checked into a triage room where I had to change into a hospital gown and was hooked up to an IV and a fetal monitor for an hour leading up to the procedure. They also injected me with a medication which relaxed my uterus to prevent contractions. I remember feeling so nervous…nervous about it being unsuccessful, nervous about the process doing harm to my baby, nervous that although uncommon, the procedure might go badly and I’d have to have an emergency C-Section right then and there. My husband tried to ease my nerves by making me laugh at silly things and trying some relaxation techniques we had learned in the efforts of preparing for a natural birth, but by the time my two doctors showed up for the procedure I was a jittery, sweaty mess.

The doctors asked my husband to stand at my feet and each of them took position on both of my sides. On my command, both of them dug their hands into my stomach and began pressing and rubbing and I felt the baby begin to move. Unlike the woman feature in the video I shared above, I was not able to lay there and calmly observe the procedure because I was in excruciating pain. It felt as though they were pulling my organs out while a friction-like burn seared in my abdomen. I screamed and panted like a woman in labor while the doctors put their entire weight into pushing my baby around in my uterus. After about 60 seconds they stopped and I was able to breath. It hadn’t worked. They gave me a few minutes to compose myself before asking me if I wanted to try again. I considered saying no but realized that it was my last chance at having a vaginal birth so I conceded. The second attempt I only withstood about 30 seconds before the pain became too much and I was begging them to stop. That baby wasn’t turning and I just had to accept it. As deflated as I felt with this realization, I was slowly coming to peace with the looming C-Section know that I had done everything in my power to turn our little girl.

We later discovered that my amniotic fluids were dangerously low so our little girl had to come out via C-section rather emergently anyway. I only note this here because I suspect that the low fluid levels attributed to the intense pain and not every woman who opts to have the procedure will be in the agony I experienced.

The bottom line is that babies come in the way they are intended to and it’s important to trust your body and your medical professional. And don’t forget—as I easily did—what’s most important is a safe delivery of a healthy baby which in my case was only made possible by a C-Section.

Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)