Understanding Scottish birth parity: A comparison of estimates from different data sources
Recent News
Recent Outputs
Upcoming Events
Sorry, there are currently no upcoming Events.
Williamson, L., Graham, E. & Boyle, P. (2010) British Society for Population Studies annual conference 2010, University of Exeter, UK, 13 - 15 September 2010 [SLS]
Other information:
Abstract:
Virtually no studies have been able to directly examine birth parity in Scotland due to the lack of comprehensive data on birth order, yet this information is crucially important in understanding Scottish fertility trends. In Scotland parity data is not readily available since civil registration only records all previous births within marriage and given that in 2007 only 51% of births in Scotland occurred within marriage compared with 90% in 1977 (GROS 2008:64), parity data from civil registration is unlikely to be a true reflection of the fertility behaviour of Scottish women today. Equally, census information on number of resident children in the household may underestimate parity by omitting natural children living elsewhere. In this paper, we report a series of parity profiles for a sample of women in the Scottish Longitudinal Study (SLS) derived from two different data sources: maternity inpatient and day case data (SMR02) and vital events data. By comparing different parity profiles by marital status for the same group of women in the SLS, we consider the relative reliability of parity information from different sources and assess the extent to which using indirect estimates of parity (based on vital registration data) may be misleading. General Register Office for Scotland (GROS). (2008). Scotland’s Population 2007: The Registrar General’s Annual Review of Demographic Trends. 153rd Edition
Download output document: Paper Abstract (PDF 50KB)
Output from project: 2008_012
© 2026 CALLS Hub - Mtc - SMA Login Contact - Output Login
| 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. |