Children who spend more 3 hours in front of a screen are at a higher risk of getting type 2 diabetes

Reducing time spent in front of a screen could facilitate in early prevention of Type 2 diabetes


Tech Desk March 15, 2017
Reducing time spent in front of a screen could facilitate in early prevention of Type 2 diabetes. PHOTO: REUTERS

A study conducted by researchers at the University of Glasgow, UK has found that spending more time in front of a screen can lead to a higher risk of getting type 2 diabetes in childhood.

The researchers used data from the Child Heart and Health Study in England – a survey of almost 4,500 children between nine and 10 carried out in three UK cities between 2004 and 2007.

Children in the survey had fasting cardiometabolic risk marker assessments, anthropometry measurements and also reported the screen time they spent daily.

This gadget tells you exactly how many calories your food has

The study found that levels of adiposity variables were higher among children who reported more than 3 hours of screen time compared with those who reported an hour or less of screen time

Those who reported over 3 hours of screen time daily had higher ponderal index, skinfold thickness, fat mass index, leptin and insulin resistance. This suggests a strong association between time spent watching TV or playing video games with adiposity and insulin resistance.

Playing 'Pokemon Go' can add thousands of daily steps

The findings of the study then suggest that reducing the time children spend in front of a screen could facilitate in early T2D prevention.

Global prevalence of type 2 diabetes (T2D) and obesity have been increasing in adults as well as adolescents and children. Health effects of activities that encourage sedentary behaviour have been a particular focus of researchers who are creating awareness of the early determinants of adiposity and T2D risk in young people.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ