The next section illustrates one example of discordant-kinship
regressions with the discord
package.
The following analysis is a simple case based on work presented elsewhere (Trattner, Kennon, and Garrison 2020). The original project was inspired by reports detailing health disparities among ethnic minorities during the COVID-19 pandemic (Hooper, Nápoles, and Pérez-Stable 2020). Data came from the 1979 National Longitudinal Survey of Youth (NLSY79), a nationally representative household probability sample jointly sponsored by the U.S. Bureau of Labor Statistics and Department of Defense. Participants were surveyed annually from 1979 until 1994 at which point surveys occurred biennially. The data are publicly available at https://www.nlsinfo.org/ and include responses from a biennial flu vaccine survey administered between 2006 and 2016. Our work originally examined whether SES at age 40 is a significant predictor for vaccination rates using the discordant-kinship model.
The data for this analysis was downloaded with the NLS Investigator and can be found here. The SES at age 40 data can be found here. For clarity and to emphasize the functionality of {discord}, the data has been pre-processed using this script. This discordant-kinship analysis is possible thanks to recent work that estimated relatedness for approximately 95% of the NLSY79 kin pairs (Rodgers et al. 2016). These kinship links are included in the {NlsyLinks} R package (Beasley et al. 2016) and are easily utilized with the {discord} package.
For this example, we will load the following packages.
# For easy data manipulation
library(dplyr)
# For kinship linkages
library(NlsyLinks)
# For discordant-kinship regression
library(discord)
# To clean data frame names
library(janitor)
# tidyup output
library(broom)
# pipe
library(magrittr)
data(data_flu_ses)
After some pre-processing, we have a data frame containing subject identifiers, demographic information such as race and sex, and behavioral measurements like flu vaccination rates and SES at age 40. A random slice of this data looks like:
CASEID | RACE | SEX | FLU_total | S00_H40 |
---|---|---|---|---|
458 | 0 | 0 | 3 | 93.57359 |
565 | 0 | 1 | 0 | 66.30124 |
527 | 0 | 0 | 5 | 47.19758 |
444 | 0 | 0 | 2 | 70.62752 |
557 | 0 | 0 | 2 | 82.85114 |
307 | 0 | 0 | 0 | 55.13105 |
Using the kinship relationships from the NlsyLinks
package, we restructure the data to better lend itself to discordant
kinship analysis. For each kin pair, the function
CreatePairLinksSingleEntered()
takes a data set like the
one above, [a specification of the NLSY database and the kin’s
relatedness], and the variables of interest. It returns a data
frame where every row is a kin-pair and each column is a variable of
interest with a suffix indicating to which individual the value
corresponds.
For this example, we will examine the relationship between flu vaccinations received between 2006-2016 and SES at age 40 between full siblings. As such, we specify the following variables from the pre-processed data frame previewed above.
# Get kinship links for individuals with the following variables:
link_vars <- c("FLU_total", "FLU_2008", "FLU_2010",
"FLU_2012", "FLU_2014", "FLU_2016",
"S00_H40", "RACE", "SEX")
We now link the subjects by the specified variables using
CreatePairLinksSingleEntered()
, from the {NlsyLinks}
package.
# Specify NLSY database and kin relatedness
link_pairs <- Links79PairExpanded %>%
filter(RelationshipPath == "Gen1Housemates" & RFull == 0.5)
df_link <- CreatePairLinksSingleEntered(outcomeDataset = data_flu_ses,
linksPairDataset = link_pairs,
outcomeNames = link_vars)
We have saved this data frame as df_link
. A random
subset of this data is:1
ExtendedID | SubjectTag_S1 | SubjectTag_S2 | FLU_total_S1 | FLU_total_S2 | S00_H40_S1 | S00_H40_S2 |
---|---|---|---|---|---|---|
896 | 89600 | 89800 | 4 | 1 | 63.18044 | 75.86339 |
183 | 18400 | 18500 | 2 | 0 | 82.99437 | 37.34971 |
1148 | 114800 | 115000 | 5 | 1 | 40.43431 | 64.80595 |
1721 | 172100 | 172400 | 2 | 1 | 49.24832 | 57.71297 |
649 | 64900 | 65000 | 2 | 2 | 88.74819 | 64.18521 |
137 | 13700 | 13800 | 3 | 0 | 81.06099 | 76.36864 |
This data is almost ready for analysis, but we want to ensure that
the data are representative of actual trends. The FLU_total
column is simply a sum of the biennial survey responses. So for a given
sibling-pair, one or both individuals may not have responded to the
survey indicating their vaccination status. If that’s the case, we want
to exclude those siblings to reduce [non-response
bias], by examining the biennial responses and removing any
rows with missingness.
# Take the linked data, group by the sibling pairs and
# count the number of responses for flu each year. If there is an NA,
# then data is missing for one of the years, and we omit it.
consistent_kin <- df_link %>%
group_by(SubjectTag_S1, SubjectTag_S2) %>%
count(FLU_2008_S1, FLU_2010_S1,
FLU_2012_S1, FLU_2014_S1,
FLU_2016_S1, FLU_2008_S2,
FLU_2010_S2, FLU_2012_S2,
FLU_2014_S2, FLU_2016_S2) %>%
na.omit()
# Create the flu_modeling_data object with only consistent responders.
# Clean the column names with the {janitor} package.
flu_modeling_data <- semi_join(df_link,
consistent_kin,
by = c("SubjectTag_S1",
"SubjectTag_S2")) %>%
clean_names()
To avoid violating assumptions of independence, in our analysis we specify that the kin-pairs should be from unique households (i.e. we randomly select one sibling pair per household).
The data we will use for modeling now contains additional information for each member of the kin pair, including sex and race of each individual, flu vaccination status for the biennial survey between 2006-2016, and a total flu vaccination count for that period. The total vaccination count ranges from 0 - 5, where 0 indicates that the individual did not get a vaccine in any year between 2006-2016 and 5 indicates that an individual got at least 5 vaccines between 2006-2016. Although our data set has individual years, we focused on the aggregate as we felt that was a measure of general tendency. A subset of the data to use in this regression looks like:
extended_id | subject_tag_s1 | subject_tag_s2 | flu_total_s1 | flu_total_s2 | race_s1 | race_s2 | sex_s1 | sex_s2 | ses_age_40_s1 | ses_age_40_s2 |
---|---|---|---|---|---|---|---|---|---|---|
17 | 1700 | 1800 | 0 | 0 | 0 | 0 | 1 | 1 | 49.26537 | 74.92440 |
29 | 2900 | 3000 | 2 | 0 | 0 | 0 | 0 | 0 | 56.80481 | 32.05423 |
37 | 3700 | 3800 | 1 | 5 | 0 | 0 | 0 | 0 | 58.55547 | 50.45408 |
40 | 4000 | 4100 | 2 | 0 | 0 | 0 | 1 | 1 | 78.19220 | 73.41860 |
58 | 5800 | 5900 | 5 | 0 | 0 | 0 | 0 | 1 | 80.56835 | 49.68414 |
61 | 6100 | 6200 | 3 | 4 | 0 | 0 | 0 | 0 | 74.43720 | 50.56920 |
67 | 6700 | 6800 | 4 | 4 | 0 | 0 | 1 | 0 | 89.67767 | 82.68649 |
74 | 7500 | 7600 | 0 | 0 | 0 | 0 | 0 | 1 | 88.15524 | 61.54234 |
83 | 8300 | 8400 | 0 | 3 | 1 | 1 | 1 | 1 | 46.41507 | 64.12765 |
85 | 8500 | 8600 | 0 | 0 | 1 | 1 | 1 | 0 | 40.12748 | 45.06552 |
To perform the regression using the {discord} package, we supply the
data frame and specify the outcome and predictors. It also requires a
kinship pair id, extended_id
in our case, as well as pair
identifiers – the column name suffixes that identify to which kin a
column’s values correspond (“_s1” and “_s2” in our case).2 Optional, although
recommended, are columns containing sex and race information to control
for as additional covariates. In our case, these columns are prefixed
“race” and “sex”. Per the pre-processing
script, these columns contain dummy variables where the reference
group for race is “non-Black, non-Hispanic” and the reference group for
sex is female. This
By entering this information into the
discord_regression()
function, we can run the model as
such:
# Setting a seed for reproducibility
set.seed(18)
flu_model_output <- discord_regression(
data = flu_modeling_data,
outcome = "flu_total",
predictors = "s00_h40",
id = "extended_id",
sex = "sex",
race = "race",
pair_identifiers = c("_s1", "_s2")
)
The default output of discord_regression()
is an
lm
object. The metrics for our regression can be summarized
as follows:
Term | Estimate | Standard Error | T Statistic | P Value |
---|---|---|---|---|
(Intercept) | 1.482 | 0.191 | 7.752 | p<0.001 |
flu_total_mean | 0.174 | 0.033 | 5.232 | p<0.001 |
s00_h40_diff | 0.007 | 0.002 | 3.276 | p=0.001 |
s00_h40_mean | 0.002 | 0.003 | 0.801 | p=0.423 |
sex_1 | -0.104 | 0.097 | -1.068 | p=0.286 |
race_1 | -0.062 | 0.102 | -0.609 | p=0.543 |
sex_2 | 0.009 | 0.097 | 0.092 | p=0.927 |
Looking at this output, the intercept can be thought of as the
average difference in outcomes between siblings, controlling for all
other variables. That is, it looks like the average difference for two
sisters of a non-minority ethnic background (the reference groups for
sex and race) is approximately 1.5. The term flu_total_mean
is essentially an extra component of the intercept that captures some
non-linear trends and allows the difference score to change as a
function of the average predictors. Here, this is the mean socioeconomic
status for the siblings, s00_h40_mean
. We also accounted
for sex and race, neither of which have a statistically significant
effect on the differences in flu vaccine shots between siblings
(different families) or within a sibling pair (same family).
The most important metric from the output, though, is the difference
score, s00_h40_diff
. Here, it is statistically significant.
An interpretation of this result might be, “the difference in
socioeconomic status between siblings at age 40 is positively associated
with the difference in the number of flu vaccinations received between
2006-2016.” This finding means that a sibling with 10% higher SES is
expected to have 0.0653316 average in flu shots.
The goal of performing a discordant-kinship regression is to see whether there is a significant difference in some behavioral measure while controlling for as much gene-and-environmental variance as possible. In this section, we walked through an analysis showing a statistically significant difference in the number of flu shots a sibling received and their socioeconomic status. From this finding, we could not claim the relationship is causal. However, we cannot eliminate causality because there are statistically significant within- and between-family differences in our predictors and outcomes.
In its current implementation, the {discord} package encourages best practices for performing discordant-kinship regressions. For example, the main function has the default expectation that sex and race indicators will be supplied. These measures are both important covariates when testing for causality between familial background and psychological characteristics.
This, and other design choices, are crucial to facilitating transparent and reproducible results. Software ever-evolves, however, and to further support reproducible research we plan to provide improved documentation and allow for easier inspection of the underlying model implementation and results.
We acknowledge contributions from Cermet Ream, Joe Rodgers, and support from Lucy D’Agostino McGowan on this project.
Notice that, with the exception of the first column indicating the specific pair, each column name has the suffix “_S1” and “_S2”. As mentioned above, these suffices identify which sibling the column values correspond.↩︎
Note these ids were previously “_S1” and “_S2”, however,
we used the clean_names()
function which coerced the column
names to lowercase.↩︎