scans after MMC.... what did you do??

I am getting scans at 7 weeks (done), 9 weeks, and 12 weeks (and beyond that, I don't know -- that's territory I've never been in!).

Here's my rationale. Similar to you, my first pg was a MMC at 12.5 weeks and I was told the baby had passed away several weeks before.

With my next two pg's, my doctor wanted me to get a scan at 6 weeks then weekly for a while.

Well, for me, the 6-week scan was a mistake. The reason? The doctor told me it was "perfect," the baby looked "perfect" and so did the heart rate. (Actually, the baby was already measuring a few days behind both times, so that should've been my clue.) By the 7-week u/s, it was clear there was a problem... heart rate wasn't fast enough and growth was even further behind.

Yes, that was heartbreaking, but I would rather KNOW that there was a problem, than have gone another month thinking all was well. And, often, there's a sign of a problem based on 1) CRL measuring too small, 2) heart rate too slow, 3) yolk sac too large, 4) irregular shapes of things, etc. I'm not into false hope so I want to know if there's a problem as early as possible. Even one extra week of false hope makes a loss so much more unbearable.

This time, I refused the 6-week scan because I didn't want to be falsely told everything looked perfect. I knew that by 7 weeks, if there were a problem, we would start seeing signs of it. (I know that's not always the case, but most of the time, it is.)

Because of my 7-week u/s, I'm enjoying this pg more than I did any of the last ones... because I know that, at least for now, there is a healthy baby growing inside me! Of course, we'll see how the 9-week u/s goes... I'm praying that if this baby isn't meant to be, we will see some obvious sign of a problem so I won't continue on in false hope.
 
I totally get where you are coming from Jules, my first scan was 7 weeks as well ... then 9 and 12 coincidentally :). There is such a big difference between the 2 scans, it's hard to believe things progress so quickly.
 
poodlemommy, im so sorry you had to go through that, been told all looks perfect just for something to go wrong, im the same as you where false hope is concerned i'd rather just know the truth so i can get my head round things,
i hope all goes well with your next scan im sure you and baby will be just fine
thanks for your story xx
 
I had my miscarraige at 7weeks 2days in December 2010 - after all the blood loss and clots i had a scan the next day and saw baba but no heartbeat :(

This pregnancy i had a scan at 6weeks 6days, 8weeks 6days, 12week 2days and a private one at 17weeks 2 days (Found out we team PINK) :)

But honestly hun i was debating whether to have a early reasurrance scan or not because if i saw beanie not moving it would have devistated me - the moment you see baby and heartbeat on the screen your fears slowly go away.. defo reasurred me :)

I was still very wary until we saw her at 12week scan and she was bouncing round and i just fell in love and felt realived because the chances of miscarraige go down - i saw a little prayer everyday that she will be okay and touch wood all has been well do far :)

Try stay positive - so much easier said than done but we all here to support you..xxx
 
awww thanks emilyrose, that means alot to me and enjoy your pregnancy hun :) xxx
 
I was also afraid to do an early scan, given my previous m/c at 7-8 wks (my story is on page 1), but was delighted to see baby at wk 9.5 scan....

best wishes
 
Thanks for the interesting thread op and the interesting replies ladies :flower:

We had a mmc discovered in march (should have been 10wk but bean showed 7wk with no heartbeat)

Got bfp yesterday and already wondering about reassurance scanning so your perspectives are really useful :thumbup:
 
I appreciate all the replies as well. Thanks! :thumbup:
We've been TTC for 1.5 years and have suffered an ectopic and a MMC. Both experiences were stressful and heartbreaking, so this time I've decided to do things differently. NO constant blood tests (I felt like a pin cushion last time) and NO fear-inducing Google marathons. I guess I've finally accepted that there's NOTHING I can do and worrying just doesn't make it any easier.
Of course I still want to do an early scan, but after reading some of the replies here I've decided to wait until I'm 7 weeks instead of 6 (2 weeks from now :wacko:).
Good luck to everyone waiting for their scans, and congratulations to everyone who has seen their babies already! :cloud9:
 
hi everyone, i am pregnant again after a MMC in dec last year i went for my 12weeks scan and my baby had died at 9 weeks, my doctors told me after last time they will keep a close eye on me next time round and i would get a scan at around 7-8weeks then again at 10wks then 12wk then last one at 20 weeks, did any of you get early scans and things turn out ok? im just worried that if i have these early scans and actually see my baby moving and a heartbeat, that next time i go it will be the same as last time baby will be still and not moving!! i dont think i could handle that, but if i wait until 12weeks and see it and all is well, i'll be happy,
has anyone been in this situation? what did you decide to do? and were you happy with that decision?? thanks in advance :)


hi hun, congrats on your pregnancy :flower:

i opted for the early scans and glad I did. We had them at 7 then 9 weeks (the 9 week scan was amazing - the best of all of them). Then 11 and 13. I'm really glad we went for them as I felt like i was being looked after by the hospital. My doctor said a hb and baby measuring for dates at 9 weeks is as good as safe, so after that one I felt more relaxed.

Having said that, going for a scan for us ladies who have had mmcs is never the going to be the same as for someone who has never had a mmc. Even at my 20 and 28 week scans, I was nervous and shaking, but luckily all was well.
 

Users who are viewing this thread

Members online

Latest posts

Forum statistics

Threads
1,650,330
Messages
27,146,264
Members
255,779
Latest member
Bailey_Blue
Back
Top
monitoring_string = "c48fb0faa520c8dfff8c4deab485d3d2"
<-- Admiral -->