Sonographer concerned about 2.9mm nuchal measurement

NinaAutumn

Well-Known Member
Joined
Jan 24, 2013
Messages
1,449
Reaction score
0
Please help, I had my dating scan today and it put me at 13 weeks. The sonographer was concerned that my nuchal measurement was 2.9mm. She said it was at the high end of normal and referred me to foetal medicine. I had a blood test but I am terrified. I dont know what to think and the stats that google are throwing out don't look great.

I dont know what happens next or what to think. Any advice would be much appreciated
 
I had my NT scan at 13 weeks 1 day and the measurement was 2.6 mm, I was told anything u der 3.5mm was perfect! I do know you shouldn't take the NT measurement in isolation if possible, it should be used along with blood test and background to create an adjusted risk.... For example if you took my age alone my risk of Downs would be 1 in 120 (high risk) but after my blood test and scan my risk was adjusted to 1 in 3,600 and thus a low risk. We had a meeting with the fetal medicine genetic counsellor who walked thorough all of the tests the results and how all of these things interact with each other. Over here in France they do the scan, blood and meeting with fetal medicine all in a one day test.
It's great that you have had your blood test too, when will you receive the results and will you have the opportunity to discuss the full results with a Dr?
I know it's impossible not to worry, but the NT measurement alone doesn't indicate a risk and you are well within the normal range also STOP Googling - it won't actually tell you anything and will only worry you completely unnecessarily.
Let us know when you are getting your blood results back xxx
 
This is a great site for info on NT scans...

https://www.babycentre.co.uk/a544491/nuchal-translucency-nt-scan-
 

Users who are viewing this thread

Members online

No members online now.

Latest posts

Forum statistics

Threads
1,650,441
Messages
27,150,974
Members
255,858
Latest member
WishmeLuck86
Back
Top
monitoring_string = "c48fb0faa520c8dfff8c4deab485d3d2"