The history and future of record linkage in the ONS longitudinal study
Recent News
Recent Outputs
Upcoming Events
Sorry, there are currently no upcoming Events.
Smith, J. (1999) Statistical Journal of the United Nations Economic Commission for Europe, 16(2-3), 197 - 205 [ONS LS]
Other information:
Abstract:
The Office for National Statistics Longitudinal Study (LS) is a large dynamic record linkage database, with regular updates of information from censuses and vital events, such as births and deaths, covering one percent of the population of England and Wales. It now encompasses over twenty-five years' data and is supported within a 'safe setting' for analysis on a wide range of subjects. The LS does not carry identification information such as name and address. It uses the National Health Service Central Register (NHSCR) to provide the means of linkage between censuses and vital events and the LS database. Events are added to the LS, either through flagging mechanisms at NHSCR or by trawling for LS events in the national event registers. They are added to the database regularly to maintain a dynamic dataset for analysis. Every ten years, since 1971, a large project is mounted to add the census sample into the LS database. To date, each census sample has been linked manually using the NHSCR, but plans for the 2001 Census link are to complete it using computer matching techniques. Initial tests have shown that this will be an efficient method of linkage. Keystones to the success of the LS are the up-to-date register systems at NHSCR and the extensive security systems which preserve confidentiality. The study now has a long history of linkage and confidentiality techniques.
Available online: Statistical Journal of the United Nations Economic Commission for Europe,
© 2025 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. |