Getting started

In dscore: D-Score for Child Development

  knitr::opts_chunk$set(echo = TRUE, fig.retina = 2)
  # options(width = 80)
  suppressPackageStartupMessages(library(dplyr))
  suppressPackageStartupMessages(library(ggplot2))

Overview

The $D$-score is a one-number summary measure of early child development. The $D$-score has a fixed unit. In principle, we may use the $D$-score to answer questions on the individual, group and population level, but be aware that no instruments have yet been validated for individual application. For more background, see the introductory booklet D-score: Turning milestones into measurement.

This vignette shows how to estimate the $D$-score and the $D$-score age-adjusted Z-score (DAZ) from child data on developmental milestones. The vignette covers some typical actions needed when estimating the $D$-score and DAZ:

1. Identify whether the dscore package covers your measurement instrument;
2. Map your variable names to the GSED 9-position schema;
3. Calculate $D$-score and DAZ;
4. Summarise your results.

Is your measurement instrument covered?

The dscore package covers a subset of all possible assessment instruments. Moreover, it may have a restricted age range for a given instrument. Your first tasks are

• to evaluate whether the current dscore package can convert your measurements into $D$-scores;
• to choose a key that best suits your objectives.

The inventory by @fernald2017 identified 147 instruments for assessing the development of children aged 0-8 years. Well-known examples include the Bayley Scales for Infant and Toddler Development and the Ages & Stages Questionnaires. The $D$-score is defined by and calculated from, subsets of milestones from such instruments.

Assessment instruments connect to the $D$-score through a measurement model. We use the term key to refer to a particular instance of a measurement model. The dscore package currently supports the following keys (in historic order):

1. dutch, a model developed for the Dutch development instrument;
2. gcdg, a model covering 14 instruments using direct measurements;
3. gsed1912, covers 20 instruments using a mix of direct and caregiver-reported measurements (Dec 2019);
4. 293_0, covers only GSED SF (138 items) and GSED LF (155 items). GSED core model. (Aug 2022)
5. gsed2212, covers 23 instruments using a mix of direct and caregiver-reported measurements. Extends the GSED core model. (Jan 2022).

Different keys lead to different $D$-scores. Hence, we may compare only $D$-scores that are calculated under the same key. Our advice to set the key is:

• For new data, use the generic key = "gsed". This choice will automatically fetch the latest GSED key;
• To explicitly set the most recent key use key = "gsed2212". The ignores later keys.
• Use older keys dutch, gcdg or gsed1912 to regenerate old results. These are unlikely to be useful for new data;
• Superseeded keys are: gsed2206, gsed2208, lf2206, sf2006 and 294_0. These are available for research purposes, and will be removed in future versions.

The table given below displays the number of items per instrument for various keys. If the entry is blank, the key does not cover the instrument.

| Code | Instrument | Items | dutch | gcdg |gsed1912|gsed2212| 293_0 | | ------ | ------------------------------------------------------- | -----:|------:|------:|------:|--------:|------:| | aqi | Ages & Stages Questionnaires-3 | 230 | | 29 | 17 | 17 | | | bar | Barrera Moncada | 22 | | 15 | 13 | 13 | | | bat | Battelle Development Inventory and Screener-2 | 137 | | | | | | | by1 | Bayley Scales for Infant and Toddler Development-1 | 156 | | 85 | 76 | 76 | | | by2 | Bayley Scales for Infant and Toddler Development-2 | 121 | | 16 | 16 | 16 | | | by3 | Bayley Scales for Infant and Toddler Development-3 | 320 | | 105 | 67 | 67 | | | cro | Caregiver Reported Early Development Instrument (CREDI) | 149 | | | 62 | 64 | | | ddi | Dutch Development Instrument (Van Wiechenschema) | 77 | 76 | 65 | 64 | 64 | | | den | Denver-2 | 111 | | 67 | 50 | 50 | | | dmc | Developmental Milestones Checklist | 66 | | | 43 | 43 | | | gri | Griffiths Mental Development Scales | 312 | | 104 | 93 | 18 | | | gs1 | GSED SF (v1, Phase 2 validation) | 139 | | | | 138 | | | gl1 | GSED LF (v1, Phase 2 validation) | 155 | | | | 155 | | | gh1 | GSED HH (v1, JAN 2023 version 20230113) | 55 | | | | 55 | | | gto | GSED LF (v0, Phase 1 validation) | 155 | | | | 155 | 155 | | gpa | GSED SF (v0, Phase 1 validation) | 139 | | | | 138 | 138 | | iyo | Infant and Young Child Development (IYCD) | 90 | | | 55 | 57 | | | kdi | Kilifi Developmental Inventory | 69 | | | 48 | 48 | | | mac | MacArthur Communicative Development Inventory | 6 | | 3 | 3 | 3 | | | mds | WHO Motor Development Milestones | 6 | | | 1 | 1 | | | mdt | Malawi Developmental Assessment Tool (MDAT) | 136 | | | 126 | 126 | | | peg | Pegboard | 2 | | 1 | 1 | 1 | | | pri | Project on Child Development Indicators (PRIDI) | 63 | | | | | | | sbi | Stanford Binet Intelligence Scales-4/5 | 33 | | 6 | 5 | 5 | | | sgr | Griffiths for South Africa | 58 | | 19 | 19 | 19 | | | tep | Test de Desarrollo Psicomotor (TEPSI) | 61 | | 33 | 31 | 31 | | | vin | Vineland Social Maturity Scale | 50 | | 17 | 17 | 17 | | | | | | 76 | 565 | 807 | 818 | 293 | | | Extensions | | | | | | | | ecd | Eerly Child Development Indicators (ECDI) | 20 | | | | 18 | | | mul | Mullen Scales of Early Learning | 232 | | | 138 | | |

Unfortunately, it is not possible to calculate the $D$-score if your instrument is not on the list, or if all of its entries under the key headings are blank. You may wish to file an extension request to incorporate your instrument in a future version of the dscore package. It remains an empirical question, however, whether the requested extension is possible.

For some instruments, e.g., for cro only one choice is possible ("gsed"). For gri, we may choose between "gcdg" and "gsed1912" or "gsed2212". Your choice may depend on the goal of your analysis. If you want to compare to other $D$-scores calculated under key "gcdg", or reproduce an analysis made under that key, then pick "gcdg". If that is not the case, then "gsed2212" is probably a better choice because of its broader generalizability. The default key is "gsed". Before version 1.5.0 the default linked to "gsed1912". Since version 1.7.0 the default selects "gsed2212".

The extensions for Mullen were added to the ""gsed1912" key. The extension was made based on two datasets, the Provide dataset [@provide] and the Bambam dataset [@bambam]. The Mullen items were matched to existing items and two well fitting items were selected as anchors in a new model on the combined Provide and Bambam data.

library(dscore)
ib <- builtin_itembank %>% 
  filter(key == "gsed2212") %>% 
  mutate(a = get_age_equivalent(items = item, pct = 50, 
                                itembank = builtin_itembank)$a,
         a = a * 12) %>% 
  select(a, instrument, label) %>% 
  na.omit()

ggplot(ib, aes(x = a, y = instrument, group = instrument)) +
  scale_y_discrete(limits = rev(unique(ib$instrument)), name = "") +
  scale_x_continuous(limits = c(0, 60), 
                     breaks = seq(0, 60, 12), name = "Age (months)") +
  geom_point(pch = 3, size = 1, colour = "blue") + 
  theme_light() +
  theme(axis.text.y = element_text(hjust = 0, family = "mono"))

The designs of the original cohorts determine the age coverage for each instrument. The figure above indicates the age range currently supported by the "gsed2212" key. Some instruments contain many items for the first two years (e.g., by1, dmc), whereas others cover primarily upper ages (e.g., tep, ecd). If you find that the ages in your sample deviate from those in the figure, you may wish to file an extension request to incorporate new ages in a future version of the dscore package.

Map variable names to the GSED 9-position schema

The dscore() function accepts item names that follow the GSED 9-position schema. A name with a length of nine characters identifies every milestone. The following table shows the construction of names.

Position | Description | Example ----------:|:-------------------- |:------------- 1-3 | instrument | by3 4-5 | developmental domain | cg 6 | administration mode | d 7-9 | item number | 018

Thus, item by3cgd018 refers to the 18th item in the cognitive scale of the Bayley-III. The label of the item can be obtained by

library(dscore)
get_labels("by3cgd018")

You may decompose item names into components as follows:

decompose_itemnames(c("by3cgd018", "denfmd014"))

This function returns a data.frame with four character vectors.

The dscore package can recognise r nrow(dscore::builtin_itemtable) item names. The expression get_itemnames() returns a (long) vector of all known item names. Let us construct a table of instruments by domains:

items <- get_itemnames()
din <- decompose_itemnames(items)
knitr::kable(with(din, table(instrument, domain)), format = "html") %>% 
  kableExtra::column_spec(1, monospace = TRUE)

We obtain the first three item names and labels from the mdt domain gm as

items <- head(get_itemnames(instrument = "mdt", domain = "gm"), 3)
get_labels(items)

In practice, you need to spend some time to figure out how item names in your data map to those in the dscore package. Once you've completed this mapping, rename the items into the GSED 9-position schema. For example, suppose that your first three gross motor MDAT items are called mot1, mot2, and mot3.

data <- data.frame(id = c(1, 1, 2), age = c(1, 1.6, 0.9), mot1 = c(1, NA, NA), 
                   mot2 = c(0, 1, 1), mot3 = c(NA, 0, 1))
data

Renaming is easy to do by changing the names attribute.

old_names <- names(data)[3:5]
new_names <- get_itemnames(instrument = "mdt", domain = "gm")[1:3]
names(data)[3:5] <- new_names
data

There may be different versions and revision of the same instrument. Therefore, carefully check whether the item labels match up with the labels in version of the instrument that you administered.

The dscore package assumes that response to milestones are dichotomous (1 = PASS, 0 = FAIL). If necessary, recode your data to match these response categories.

Calculate the $D$-score and DAZ

Once the data are in proper shape, calculation of the $D$-score and DAZ is easy.

The milestones dataset in the dscore package contains responses of 27 preterm children measured at various age between birth and 2.5 years on the Dutch Development Instrument (ddi). The dataset looks like:

head(milestones[, c(1, 3, 4, 9:14)])

Each row corresponds to a visit. Most children have three or four visits. Columns starting with ddi hold the responses on DDI-items. A 1 means a PASS, a 0 means a FAIL, and NA means that the item was not administered.

The milestones dataset has properly named columns that identify each item. Calculating the $D$-score and DAZ is then done by:

ds <- dscore(milestones)
dim(ds)

Where ds is a data.frame with the same number of rows as the input data. The first six rows are

head(ds)

The table below provides the interpretation of the output:

Name | Interpretation ---- | ------------- a | Decimal age n | number of items used to calculate $D$-score p | Percentage of passed milestones d | $D$-score estimate, mean of posterior sem | Standard error of measurement, standard deviation of the posterior daz | $D$-score corrected for age

Summarise $D$-score and DAZ

Combine the milestones data and the result by

md <- cbind(milestones, ds)

We may plot the 27 individual developmental curves by

library(ggplot2)
library(dplyr)

r <- builtin_references %>% 
  filter(pop == "dutch") %>% 
  select(age, SDM2, SD0, SDP2)

ggplot(md, aes(x = a, y = d, group = id, color = sex)) + 
  theme_light() + 
  theme(legend.position = c(.85, .15)) +
  theme(legend.background = element_blank()) +
  theme(legend.key = element_blank()) +
  annotate("polygon", x = c(r$age, rev(r$age)), 
           y = c(r$SDM2, rev(r$SDP2)), alpha = 0.1, fill = "green") +
  annotate("line", x = r$age, y = r$SDM2, lwd = 0.3, alpha = 0.2, color = "green") +
  annotate("line", x = r$age, y = r$SDP2, lwd = 0.3, alpha = 0.2, color = "green") +
  annotate("line", x = r$age, y = r$SD0, lwd = 0.5, alpha = 0.2, color = "green") +
  coord_cartesian(xlim = c(0, 2.5)) +
  ylab(expression(paste(italic(D), "-score", sep = ""))) +
  xlab("Age (in years)")+
  scale_color_brewer(palette = "Set1") +
  geom_line(lwd = 0.1) +
  geom_point(size = 1)

Note that similarity of these curves to growth curves for body height and weight.

The DAZ is an age-standardized $D$-score with a standard normal distribution with mean 0 and variance 1. We plot the individual DAZ curves relative to the Dutch references by

ggplot(md, aes(x = a, y = daz, group = id, color = factor(sex))) + 
  theme_light() + 
  theme(legend.position = c(.85, .15)) +
  theme(legend.background = element_blank()) +
  theme(legend.key = element_blank()) +
  scale_color_brewer(palette = "Set1") +
  annotate("rect", xmin = -Inf, xmax = Inf, ymin = -2, ymax = 2, alpha = 0.1,
            fill = "green") +
  coord_cartesian(xlim = c(0, 2.5), 
                  ylim = c(-4, 4)) +
  geom_line(lwd = 0.1) +
  geom_point(size = 1) +
  xlab("Age (in years)") +
  ylab("DAZ") 

Note that the $D$-scores and DAZ are a little lower than average. The explanation here is that these all children are born preterm. We can account for prematurity by correcting for gestational age.

The distributions of DAZ for boys and girls show that a large overlap:

ggplot(md) + 
  theme_light() +
  scale_fill_brewer(palette = "Set1") +
  geom_density(aes(x = daz, group = sex, fill = sex), alpha = 0.4, 
               adjust = 1.5, color = "transparent") +
  xlab("DAZ")

Under the assumption of independence, we may test whether sex differences are constant in age by a linear regression that includes the interaction between age and sex:

summary(lm(daz ~  age * sex, data = md))

This group of very preterms starts around -2.5 SD, followed by a catch-up in child development of approximately 1.0 SD per year. The size of the catch-up is equal for boys and girls.

We may account for the clustering effect by including random intercept and age effects, and rerun as

library(lme4)
lmer(daz ~  1 + age + sex + sex * age + (1 + age | id), data = md)

This analysis yields the same substantive conclusions as before.

References

dscore documentation built on Jan. 22, 2023, 1:50 a.m.