Understanding the impact of fertility history on outcomes in mid-life in Scotland, a longitudinal approach using the Scottish Longitudinal Study (SLS)
Recent News
Upcoming Events
Sorry, there are currently no upcoming Events.
Williamson, L.E.P. & Dibben, C. (2013) SHIP conference: Exploiting Existing Data for Health Research, University of St Andrews, UK, 28 - 30 August 2013 [SLS]
Other information:
Abstract:
This study is part of the research programme involving data linkage within the Scottish Health Informatics Programme (SHIP). The research draws on and extends work on reproductive histories and life outcomes. Previous studies have shown that the number of children (parity) can be linked to specific health outcomes in mid and later life for women (references can be provided). We aim to extend this research specifically for Scotland based on Scottish data, namely the Scottish Longitudinal Study (SLS) linked to health data from the NHS Scottish Morbidity Record (SMR) datasets, including the maternity dataset SMR02 (as parity is only recorded for married women at birth registration in Scotland).
The aim of this SHIP project, involving data linkage and health outcomes, is to gain a full understanding of the impact of both fertility histories and childlessness on health outcomes and mortality. In addition, we plan to compare findings with previous research where applicable. This research is only for specific female SLS birth cohorts, as it is acknowledged that we are not able to follow-up all SLS members or SLS members to old ages since the SMR02 is only available from 1975. Nevertheless, the SLS allows follow-up of the specific SLS birth cohorts from the 1991 Census until 2009 (the most recent year death data is available linked to the SLS). From preliminary modelling, in line with previous research, we find high birth parity to be an important factor in relation to mortality.
Download output document: Conference programme & abstracts (PDF 1.5MB)
Output from project: 2011_002
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__utma | 2 years | Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. |
__utmb | 30 minutes | Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics. |
__utmc | Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit. | |
__utmt | 10 minutes | Used to throttle request rate. |
__utmz | 6 months | Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. |
_ga | 2 years | Used to distinguish users. |
_gat | 1 minute | Used to throttle request rate. |
_gid | 24 hours | Used to distinguish users. |