Linking IPUMS versions of NHIS and MEPS with restricted versions in the FSRDC

  • What is the FSRDC?
  • Why use the IPUMS versions of NHIS and MEPS in the FSRDC?
  • What information is in the Restricted NHIS and MEPS files?
  • How do I talk about IPUMS in the proposal?
  • Sample Proposal Language
  • Gaining FSRDC Access
  • Additional Resources
  • What is the FSRDC?

    Why use the IPUMS versions of NHIS and MEPS in the FSRDC?

    Back to Top

    What information is in the Restricted NHIS and MEPS Files?

    Note that if you are requesting the linking keys for connecting MEPS and NHIS data, your application may need to address requirements for both data providers (AHRQ and NCHS). This page is focused on FSRDC access requests for linking NHIS and MEPS, using IPUMS versions of one or both datasets. If you are not interested in linking the NHIS and MEPS data, but rather linking only the IPUMS and restricted access versions of a single dataset, see the respective instructions for NHIS and MEPS.

    Back to Top

    How do I talk about IPUMS data in the proposal?

    Sample Proposal Language

    Sample language for including IPUMS NHIS as a non-NCHS data:

    User-supplied data file: IPUMS Health Surveys NHIS (IPUMS NHIS). This file will include data from the harmonized form of NHIS data that is produced by IPUMS. We will use IPUMS NHIS variables that are based on NHIS household, family, person, sample adult, and sample child files. The IPUMS NHIS contains NHIS public-use-file identification number (NHISPID) that will be used to merge the file to restricted NHIS data. The file delivered to NCHS will be called ipums_nhis_data.sas7bdat.

    Sample language for including IPUMS MEPS as user-supplied data:

    User-supplied data file: IPUMS Health Surveys MEPS (IPUMS MEPS). This file will include data from the harmonized form of MEPS data that is produced by IPUMS. We will use IPUMS MEPS variables from the following questionnaire sections: Access to Care, Preventive Care, Charge Payment, and Health Status. The IPUMS MEPS contains the MEPS public-use-file identification number (MEPSID) that will be used to merge the file to restricted MEPS data. The file we will submit containing IPUMS data will be called ipums_meps_data.sas7bdat.

    Note that this sample language clearly includes:

    Sample language for how to merge IPUMS data with restricted data:

    NOTE: This information is only for merging restricted versions of a dataset to the IPUMS version of the same dataset. The linking keys for merging NHIS and MEPS data are not public-use and must be requested as part of your proposal.

    IPUMS NHIS merge to NHIS Restricted: Our public use file, which will contain harmonized variables, will be merged to the restricted NHIS file at the person level for each year in 2003-forward. The year-specific linking key can be constructed by concatenating HHX, FMX, and FPX; these variables are included in both the IPUMS and NCHS versions of the data. The NCHS analyst will need to merge the restricted NHIS data with the IPUMS NHIS data one year at a time by this linking key. IPUMS NHIS data will include all years in a single file; the IPUMS variable YEAR reports the survey year.

    Sample language for how to merge IPUMS MEPS data with restricted MEPS data:

    IPUMS MEPS merge to MEPS Restricted: Our public use file, which will contain harmonized variables, will be merged to the restricted MEPS file at the person level for each year using the IPUMS variable MEPSID. The linking key can be constructed by concatenating DUID, PID, and PANEL in the restricted MEPS data from AHRQ; this key can be used to merge the restricted MEPS data with the public use data one year at a time by the IPUMS variable MEPSID. IPUMS MEPS data will include all years in a single file; the IPUMS variable YEAR reports the Full-Year Consolidated File survey year.

    Merging MEPS and NHIS data: We are also requesting the NHIS linking keys from AHRQ to link NHIS to MEPS; the linkage file description can be used to associate the MEPS sample person ID (DUPERSID in original AHRQ data) to the corresponding NHIS person ID.

    Note that this sample language clearly includes:

    Gaining FSRDC access

    Additional Resources

    Back to Top