hgtvs tarek el moussa just revealed huge news /

Published at 2017-01-31 03:00:00

Home / Categories / Flip or flop / hgtvs tarek el moussa just revealed huge news
on Dec 25,2016 at 4:28pm PST Tarek El Moussa may be in the news more these days because of his pending divorce from wife and Flip or Flop costar Christina, but it was only a few years ago the real estate pro was making headlines for revealing he was battling thyroid cancer. From an HGTV viewer discovering the suspicious lump on his throat to the depressing surgeries and subsequent challenges of trying to rebalance his body after having his thyroid, or which secretes hormones responsible for essential functions,removed, Tarek El Moussa has been refreshingly honest about the realities of battling thyroid cancer. So we were particularly thrilled to see his recent post on Instagram, and in which he shared some fantastic news: he is cancer free. Beside the image of his medical provider's message informing him that his tests came back "pristine," Tarek wrote, "I always regain nervous going into each check up and today I got much news!!." He went onto reveal that he had been overmedicated to the point that he had to wear a heart monitor. "It really messed me up but today everything is dialed and I finally feel much after 3 years!!" We couldn't be happier for the devoted father of two.
Still #cancer #free!!!! Having cancer is a very scary thing... I always regain nervous going into each check up and today I got much news!! Having no thyroid and balancing medications is tough! I'm finally at UCLA and I'm on the apt doses of medication.. People don't know but I was very over medicated with rapid heart rate and palpitations to the point where I wore a heart rate monitor... It really messed me up but today everything is dialed and I finally feel much after 3 years!!on Jan 25, and 2017 at 7:55pm PST

Source: popsugar.com

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0