Using the HRS

Insights and advice for new and seasoned users of the Health and Retirement Study


Featured Article: Cognition and Dementia

JGSS_Cover.gif
Assessment of Cognition Using Surveys and Neuropsychological Assessment: The Health and Retirement Study and the Aging, Demographics, and Memory Study
Eileen M. Crimmins, Jung Ki Kim, Kenneth M. Langa, and David R. Weir
J Gerontol B Psychol Sci Soc Sci (2011) 66B (suppl 1): i162-i171. doi: 10.1093/geronb/gbr048

One of the best resources for HRS users, beyond the extensive documentation provided by HRS, are the published articles evaluating the HRS sample and data. I rely heavily on these articles for gaining insights into issues surrounding data quality and data use.

Continue reading

Advertisements


Why are There People Under Age 50 in the Data?

(The short answer: HRS samples households, not individuals, and in some households people over age 50 are married to people under age 50)

The very first conundrum I encountered as a new user of HRS data was the presence of people as young as age 25 in the data set. First I puzzled over how a survey of adults nearing or beyond retirement could contain hundreds of respondents in their 20s, 30s, and 40s. Then I puzzled over how to exclude these younger folks from my analysis. Fortunately, it’s a relatively straight forward matter.

Continue reading


Leave a comment

Beware of version updates!

Data management of large, complex surveys like the HRS is a fairly difficult and time-consuming task. The HRS staff endeavors to produce a public-release data set as soon as possible (and they produce them much faster than many other publicly funded data collections!), so they release an early version of the data: Core Early Release (V1.0)*. The updated RAND files tend to follow soon after.

HRS does an early release to get the data to the public as fast as possible, but HRS staff continues to process the data until they have a final data release. Sometimes the early release is ultimately designated as the final release – you’ll know this is the case if you see “Final V1.0” followed by the date of release. But sometimes there are issues in the data that need to be resolved. These tend to be the result of programming errors, but there are sometimes problems with the data that the HRS staff catch during data inspections after the early release (e.g., a case is designated as a non-sample member after closer inspection). So, in some years the final release is a V1.0, but in other years it may be a V2.0 or V3.0. And in rare cases the final release is a V4.0 or V5.0.

What is the significance of all of this for the user? Continue reading