Accurately defining cohort entry and exit dates is crucial in
observational research to ensure the validity of study findings. The
CohortConstructor package provides several functions to
adjust these dates based on specific criteria, and this vignette
demonstrates how to use them.
Functions to update cohort dates can be categorized into four groups:
Exit at Specific Date Functions: Adjust the cohort end date to predefined events (observation end and death date).
Cohort Entry or Exit Based on Other Date Columns: Modify cohort start or end dates to the earliest or latests from a set of date columns.
Trim Dates Functions: Restrict cohort entries based on demographic criteria or specific date ranges.
Pad Dates Functions: Adjust cohort start or end dates by adding or subtracting a specified number of days.
We’ll explore each category in the following sections.
First, we’ll connect to the Eunomia synthetic data and create a mock cohort of women in the database to use as example in the vignette.
library(CohortConstructor)
library(CohortCharacteristics)
library(PatientProfiles)
library(CDMConnector)
if (Sys.getenv("EUNOMIA_DATA_FOLDER") == ""){
Sys.setenv("EUNOMIA_DATA_FOLDER" = file.path(tempdir(), "eunomia"))}
if (!dir.exists(Sys.getenv("EUNOMIA_DATA_FOLDER"))){ dir.create(Sys.getenv("EUNOMIA_DATA_FOLDER"))
downloadEunomiaData()
}
con <- DBI::dbConnect(duckdb::duckdb(), dbdir = CDMConnector::eunomiaDir())
cdm <- CDMConnector::cdmFromCon(con, cdmSchema = "main",
writeSchema = "main", writePrefix = "my_study_")
cdm$cohort <- demographicsCohort(cdm = cdm, name = "cohort", sex = "Female")
#> ℹ Building new trimmed cohort
#> Adding demographics information
#> Creating initial cohort
#> Trim sex
#> ✔ Cohort trimmedexitAtObservationEnd()The exitAtObservationEnd() function updates the cohort
end date to the end of the observation period for each subject. This
ensures that the cohort exit does not extend beyond the period during
which data is available for the subject.
As cohort entries cannot overlap, updating the end date to the observation end may result in overlapping records. In such cases, overlapping records are collapsed into a single entry (starting at the earliest entry and ending at the end of observation).
This function has an argument limitToCurrentPeriod to
consider cases when a subject may have more than one observation period.
If limitToCurrentPeriod = TRUE (default) end date will be
set to the end of the observation period where the record is registered.
If limitToCurrentPeriod = FALSE, in addition to updating
the cohort end to the allocated observation end, cohort entries are
created for each of the subsequent observation periods.
exitAtDeath()The exitAtDeath() function sets the cohort end date to
the recorded death date of the subject.
By default, it keeps the end date of subjects who do not have a death
record unmodified; however, these can be dropped with the argument
requireDeath.
entryAtFirstDate()The entryAtFirstDate() function updates the cohort start
date to the earliest date among specified columns.
Next we want to set the entry date to the first of: diclofenac or acetaminophen prescriptions after cohort start, or cohort end date.
# create cohort with of drugs diclofenac and acetaminophen
cdm$medications <- conceptCohort(
cdm = cdm, name = "medications",
conceptSet = list("diclofenac" = 1124300, "acetaminophen" = 1127433)
)
#> Warning: ! `codelist` casted to integers.
#> ℹ Subsetting table drug_exposure using 2 concepts with domain: drug.
#> ℹ Combining tables.
#> ℹ Creating cohort attributes.
#> ℹ Applying cohort requirements.
#> ℹ Merging overlapping records.
#> ✔ Cohort medications created.
# add date first ocurrence of these drugs from index date
cdm$cohort_dates <- cdm$cohort |>
addCohortIntersectDate(
targetCohortTable = "medications",
nameStyle = "{cohort_name}",
name = "cohort_dates"
)
# set cohort start at the first ocurrence of one of the drugs, or the end date
cdm$cohort_entry_first <- cdm$cohort_dates |>
entryAtFirstDate(
dateColumns = c("diclofenac", "acetaminophen", "cohort_end_date"),
name = "cohort_entry_first"
)
#> Joining with `by = join_by(cohort_definition_id, subject_id, cohort_end_date)`
cdm$cohort_entry_first
#> # Source: table<my_study_cohort_entry_first> [?? x 7]
#> # Database: DuckDB v1.3.1 [root@Darwin 24.5.0:R 4.5.1//private/var/folders/sw/rd8zn92n2nz45cfcc5dcs_080000gr/T/RtmpwyN0k0/file110b819db0a29.duckdb]
#> cohort_definition_id subject_id cohort_start_date cohort_end_date
#> <int> <int> <date> <date>
#> 1 1 3093 1984-11-19 2019-04-07
#> 2 1 180 2019-05-02 2019-05-02
#> 3 1 3514 1981-06-14 2018-09-04
#> 4 1 5041 2007-02-14 2018-06-20
#> 5 1 4197 2016-11-27 2016-11-27
#> 6 1 1377 2008-12-02 2017-12-20
#> 7 1 3626 1988-08-06 2018-05-05
#> 8 1 1586 1954-06-21 2018-10-28
#> 9 1 4394 2018-05-28 2018-05-28
#> 10 1 5068 1962-04-09 2019-01-19
#> # ℹ more rows
#> # ℹ 3 more variables: entry_reason <chr>, diclofenac <date>,
#> # acetaminophen <date>entryAtLastDate()The entryAtLastDate() function works similarly to
entryAtFirstDate(), however now the selected column is the
latest date among specified columns.
cdm$cohort_entry_last <- cdm$cohort_dates |>
entryAtLastDate(
dateColumns = c("diclofenac", "acetaminophen", "cohort_end_date"),
keepDateColumns = FALSE,
name = "cohort_entry_last"
)
cdm$cohort_entry_last
#> # Source: table<my_study_cohort_entry_last> [?? x 5]
#> # Database: DuckDB v1.3.1 [root@Darwin 24.5.0:R 4.5.1//private/var/folders/sw/rd8zn92n2nz45cfcc5dcs_080000gr/T/RtmpwyN0k0/file110b819db0a29.duckdb]
#> cohort_definition_id subject_id cohort_start_date cohort_end_date
#> <int> <int> <date> <date>
#> 1 1 3177 2012-06-06 2012-06-06
#> 2 1 1113 2017-12-05 2017-12-05
#> 3 1 1496 1998-05-17 1998-05-17
#> 4 1 3212 2018-08-10 2018-08-10
#> 5 1 3744 2019-01-18 2019-01-18
#> 6 1 4122 2018-10-18 2018-10-18
#> 7 1 546 2019-04-07 2019-04-07
#> 8 1 906 2018-03-20 2018-03-20
#> 9 1 3123 2018-10-25 2018-10-25
#> 10 1 715 2018-02-20 2018-02-20
#> # ℹ more rows
#> # ℹ 1 more variable: entry_reason <chr>In this example, we set keepDateColumns to FALSE, which
drops columns in dateColumns.
exitAtFirstDate()The exitAtFirstDate() function updates the cohort end
date to the earliest date among specified columns.
For instance, next we want the exit to be observation end, except if there is a record of diclofenac or acetaminophen, in which case that would be the end:
cdm$cohort_exit_first <- cdm$cohort_dates |>
addFutureObservation(futureObservationType = "date", name = "cohort_exit_first") |>
exitAtFirstDate(
dateColumns = c("future_observation", "acetaminophen", "diclofenac"),
keepDateColumns = FALSE
)
cdm$cohort_exit_first
#> # Source: table<my_study_cohort_exit_first> [?? x 5]
#> # Database: DuckDB v1.3.1 [root@Darwin 24.5.0:R 4.5.1//private/var/folders/sw/rd8zn92n2nz45cfcc5dcs_080000gr/T/RtmpwyN0k0/file110b819db0a29.duckdb]
#> cohort_definition_id subject_id cohort_start_date cohort_end_date exit_reason
#> <int> <int> <date> <date> <chr>
#> 1 1 2939 1953-01-20 1974-09-29 acetaminop…
#> 2 1 1431 1949-10-02 1963-06-22 acetaminop…
#> 3 1 2431 1971-07-21 1992-09-29 acetaminop…
#> 4 1 3558 1959-03-28 1964-02-02 acetaminop…
#> 5 1 3352 1964-10-23 1981-02-10 acetaminop…
#> 6 1 2861 1963-07-08 1982-03-30 acetaminop…
#> 7 1 1511 1965-04-25 1966-01-22 acetaminop…
#> 8 1 5257 1978-03-15 1986-07-03 acetaminop…
#> 9 1 4208 1938-11-22 1941-11-08 acetaminop…
#> 10 1 1081 1961-08-16 1963-03-10 acetaminop…
#> # ℹ more rowsexitAtLastDate()Similarly, the exitAtLastDate() function sets the cohort
end date to the latest date among specified columns.
cdm$cohort_exit_last <- cdm$cohort_dates |>
exitAtLastDate(
dateColumns = c("cohort_end_date", "acetaminophen", "diclofenac"),
returnReason = FALSE,
keepDateColumns = FALSE,
name = "cohort_exit_last"
)
cdm$cohort_exit_last
#> # Source: table<my_study_cohort_exit_last> [?? x 4]
#> # Database: DuckDB v1.3.1 [root@Darwin 24.5.0:R 4.5.1//private/var/folders/sw/rd8zn92n2nz45cfcc5dcs_080000gr/T/RtmpwyN0k0/file110b819db0a29.duckdb]
#> cohort_definition_id subject_id cohort_start_date cohort_end_date
#> <int> <int> <date> <date>
#> 1 1 1316 1948-10-26 2019-06-18
#> 2 1 4899 1920-06-01 1998-11-17
#> 3 1 412 1953-05-15 2004-06-25
#> 4 1 3721 1963-11-15 2019-06-14
#> 5 1 4282 1966-04-06 2019-04-24
#> 6 1 2960 1955-02-04 2019-04-26
#> 7 1 1641 1954-09-22 2019-03-27
#> 8 1 2903 1963-09-15 2019-04-28
#> 9 1 349 1957-08-31 2019-05-04
#> 10 1 2925 1960-01-11 2019-04-08
#> # ℹ more rowsIn this last example, the return cohort doesn’t have the specified
date columns, neither the “reason” column indicating which date was used
for entry/exit. These was set with the keepDateColumns and
returnReason arguments, common throughout the functions in
this category.
trimDemographics()The trimDemographics() function restricts the cohort
based on patient demographics. This means that cohort start and end
dates are moved (within the original cohort entry dates) to ensure that
individuals meet specific demographic criteria throughout their cohort
participation. If individuals do not satisfy the criteria at any point
during their cohort period, their records are excluded.
For instance, if we trim using an age range from 18 to 65, individuals will only contribute in the cohort form the day they are 18 or older, up to the day before turning 66 (or before if they leave the database).
trimToDateRange()The trimToDateRange() function confines cohort entry and
exit dates within a specified date range, ensuring that cohort periods
align with the defined timeframe. If only the start or end of a range is
required, the other can be set to NA.
For example, to restrict cohort dates to be on or after January 1st, 2015:
padCohortStart()The padCohortStart() function adds (or subtracts) a
specified number of days to the cohort start date.
For example, to subtract 50 days from the cohort start date:
# Substract 50 days to cohort start
cdm$cohort <- cdm$cohort |> padCohortStart(days = -50, collapse = FALSE)When subtracting days, it may result in cohort start dates preceding
the observation period start. By default, such entries are corrected to
the observation period start. To drop these entries instead, set the
padObservation argument to FALSE.
Additionally, adjusting cohort start dates may lead to overlapping
entries for the same subject. The collapse argument manages
this: if TRUE, merges overlapping entries into a single record with the
earliest start and latest end date (default), if FALSE retains only the
first of the overlapping entries.
padCohortEnd()Similarly, the padCohortEnd() function adjusts the
cohort end date by adding (or subtracting) a specified number of
days.
The example below adds 1000 days to cohort end date, while dropping records that are outside of observation after adding days.
cdm$cohort_pad <- cdm$cohort |>
padCohortEnd(days = 1000, padObservation = FALSE, name = "cohort_pad")Additionally, days to add can also be specified with a numeric column in the cohort, which allows to add a specific number of days for each record:
padCohortDate()The padCohortDate() function provides a more flexible
approach by allowing adjustments to either the cohort start or end date
based on specified parameters. You can define which date to adjust
(cohortDate), the reference date for the adjustment
(indexDate), and the number of days to add or subtract.
For example, to set the cohort end date to be 365 days after the cohort start date:
For all these functions, the cohortId argument specifies which cohorts to modify. This allows for targeted adjustments without altering other cohorts. For instance, to add 10 days to the end date of the acetaminophen cohort and 20 days to the diclofenac cohort we can do the following: