1.1 Introduction

Concept sets play an important role when working with data in the format of the OMOP CDM. They can be used to create cohorts after which, as we’ve seen in the previous vignette, we can identify intersections between the cohorts. PatientProfiles adds another option for working with concept sets which is use them for adding associated variables directly without first having to create a cohort.

It is important to note, and is explained more below, that results may differ when generating a cohort and then identifying intersections between two cohorts compared to working directly with concept sets. The creation of cohorts will involve the collapsing of overlapping records as well as imposing certain requirements such as only including records that were observed during an individuals observation period. When adding variables based on concept sets we will be working directly with record-level data in the OMOP CDM clinical tables.

1.2 Adding variables from concept sets

For this vignette we’ll use the Eunomia synthetic dataset. First lets create our cohort of interest, individuals with an ankle sprain.

library(PatientProfiles)
library(CodelistGenerator)
library(CohortConstructor)
library(dplyr)
library(ggplot2)
library(omock)

cdm <- mockCdmFromDataset(datasetName = "GiBleed", source = "duckdb")
#> ℹ Reading GiBleed tables.
#> ℹ Adding drug_strength table.
#> ℹ Creating local <cdm_reference> object.
#> ℹ Inserting <cdm_reference> into duckdb.

cdm$ankle_sprain <- conceptCohort(
  cdm = cdm,
  conceptSet = list("ankle_sprain" = 81151),
  name = "ankle_sprain"
)
#> Warning: ! `codelist` casted to integers.
#> ℹ Subsetting table condition_occurrence using 1 concept with domain: condition.
#> ℹ Combining tables.
#> ℹ Creating cohort attributes.
#> ℹ Applying cohort requirements.
#> ℹ Merging overlapping records.
#> ✔ Cohort ankle_sprain created.

cdm$ankle_sprain
#> # Source:   table<results.test_ankle_sprain> [?? x 4]
#> # Database: DuckDB 1.4.1 [martics@Windows 10 x64:R 4.2.1/C:\Users\martics\AppData\Local\Temp\Rtmp6tGZSu\file81bc46b3821.duckdb]
#>    cohort_definition_id subject_id cohort_start_date cohort_end_date
#>                   <int>      <int> <date>            <date>         
#>  1                    1       3147 1988-11-29        1988-12-27     
#>  2                    1       2266 1993-03-29        1993-04-19     
#>  3                    1       3599 1973-03-30        1973-04-27     
#>  4                    1       4432 2014-06-27        2014-07-25     
#>  5                    1         63 2000-10-15        2000-10-29     
#>  6                    1       4210 1976-04-29        1976-05-13     
#>  7                    1       4872 1999-07-10        1999-07-24     
#>  8                    1       2893 1997-08-06        1997-09-03     
#>  9                    1       4476 1971-06-01        1971-06-15     
#> 10                    1        338 1969-02-07        1969-03-07     
#> # ℹ more rows

Now let’s say we’re interested in summarising use of acetaminophen among our ankle sprain cohort. We can start by identifying the relevant concepts.

acetaminophen_cs <- getDrugIngredientCodes(
  cdm = cdm,
  name = c("acetaminophen")
)

acetaminophen_cs
#> 
#> ── 1 codelist ──────────────────────────────────────────────────────────────────
#> 
#> - 161_acetaminophen (7 codes)

Once we have our codes for acetaminophen we can create variables based on these. As with cohort intersections, PatientProfiles provides four types of functions for concept intersections.

First, we can add a binary flag variable indicating whether an individual had a record of acetaminophen on the day of their ankle sprain or up to 30 days afterwards.

cdm$ankle_sprain |>
  addConceptIntersectFlag(
    conceptSet = acetaminophen_cs,
    indexDate = "cohort_start_date",
    window = c(0, 30)
  ) |>
  glimpse()
#> Rows: ??
#> Columns: 5
#> Database: DuckDB 1.4.1 [martics@Windows 10 x64:R 4.2.1/C:\Users\martics\AppData\Local\Temp\Rtmp6tGZSu\file81bc46b3821.duckdb]
#> $ cohort_definition_id        <int> 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, …
#> $ subject_id                  <int> 3147, 4432, 63, 4210, 2893, 3666, 719, 261…
#> $ cohort_start_date           <date> 1988-11-29, 2014-06-27, 2000-10-15, 1976-…
#> $ cohort_end_date             <date> 1988-12-27, 2014-07-25, 2000-10-29, 1976-…
#> $ `161_acetaminophen_0_to_30` <dbl> 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, …

Second, we can count the number of records of acetaminophen in this same window for each individual.

cdm$ankle_sprain |>
  addConceptIntersectCount(
    conceptSet = acetaminophen_cs,
    indexDate = "cohort_start_date",
    window = c(0, 30)
  ) |>
  glimpse()
#> Rows: ??
#> Columns: 5
#> Database: DuckDB 1.4.1 [martics@Windows 10 x64:R 4.2.1/C:\Users\martics\AppData\Local\Temp\Rtmp6tGZSu\file81bc46b3821.duckdb]
#> $ cohort_definition_id        <int> 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, …
#> $ subject_id                  <int> 3147, 4432, 63, 4210, 2893, 3666, 719, 261…
#> $ cohort_start_date           <date> 1988-11-29, 2014-06-27, 2000-10-15, 1976-…
#> $ cohort_end_date             <date> 1988-12-27, 2014-07-25, 2000-10-29, 1976-…
#> $ `161_acetaminophen_0_to_30` <dbl> 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, …

Third, we could identify the first start date of acetaminophen in this window.

cdm$ankle_sprain |>
  addConceptIntersectDate(
    conceptSet = acetaminophen_cs,
    indexDate = "cohort_start_date",
    window = c(0, 30),
    order = "first"
  ) |>
  glimpse()
#> Rows: ??
#> Columns: 5
#> Database: DuckDB 1.4.1 [martics@Windows 10 x64:R 4.2.1/C:\Users\martics\AppData\Local\Temp\Rtmp6tGZSu\file81bc46b3821.duckdb]
#> $ cohort_definition_id        <int> 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, …
#> $ subject_id                  <int> 3147, 4432, 63, 4210, 2893, 3666, 719, 261…
#> $ cohort_start_date           <date> 1988-11-29, 2014-06-27, 2000-10-15, 1976-…
#> $ cohort_end_date             <date> 1988-12-27, 2014-07-25, 2000-10-29, 1976-…
#> $ `161_acetaminophen_0_to_30` <date> 1988-11-29, 2014-06-27, 2000-10-15, 1976-…

Or fourth, we can get the number of days to the start date of acetaminophen in the window.

cdm$ankle_sprain |>
  addConceptIntersectDays(
    conceptSet = acetaminophen_cs,
    indexDate = "cohort_start_date",
    window = c(0, 30),
    order = "first"
  ) |>
  glimpse()
#> Rows: ??
#> Columns: 5
#> Database: DuckDB 1.4.1 [martics@Windows 10 x64:R 4.2.1/C:\Users\martics\AppData\Local\Temp\Rtmp6tGZSu\file81bc46b3821.duckdb]
#> $ cohort_definition_id        <int> 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, …
#> $ subject_id                  <int> 3147, 4432, 63, 4210, 2893, 3666, 719, 261…
#> $ cohort_start_date           <date> 1988-11-29, 2014-06-27, 2000-10-15, 1976-…
#> $ cohort_end_date             <date> 1988-12-27, 2014-07-25, 2000-10-29, 1976-…
#> $ `161_acetaminophen_0_to_30` <dbl> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, …

1.3 Adding multiple concept based variables

We can add more than one variable at a time when using these functions. For example, we might want to add variables for multiple time windows.

cdm$ankle_sprain |>
  addConceptIntersectFlag(
    conceptSet = acetaminophen_cs,
    indexDate = "cohort_start_date",
    window = list(
      c(-Inf, -1),
      c(0, 0),
      c(1, Inf)
    )
  ) |>
  glimpse()
#> Rows: ??
#> Columns: 7
#> Database: DuckDB 1.4.1 [martics@Windows 10 x64:R 4.2.1/C:\Users\martics\AppData\Local\Temp\Rtmp6tGZSu\file81bc46b3821.duckdb]
#> $ cohort_definition_id           <int> 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, …
#> $ subject_id                     <int> 3147, 2266, 3599, 4432, 63, 4210, 4872,…
#> $ cohort_start_date              <date> 1988-11-29, 1993-03-29, 1973-03-30, 20…
#> $ cohort_end_date                <date> 1988-12-27, 1993-04-19, 1973-04-27, 20…
#> $ `161_acetaminophen_1_to_inf`   <dbl> 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 0, 0, …
#> $ `161_acetaminophen_0_to_0`     <dbl> 1, 0, 0, 1, 1, 1, 0, 1, 0, 0, 0, 0, 0, …
#> $ `161_acetaminophen_minf_to_m1` <dbl> 1, 1, 0, 1, 1, 0, 1, 1, 1, 0, 0, 1, 1, …

Or we might want to get variables for multiple drug ingredients of interest.

meds_cs <- getDrugIngredientCodes(
  cdm = cdm,
  name = c(
    "acetaminophen",
    "amoxicillin",
    "aspirin",
    "heparin",
    "morphine",
    "oxycodone",
    "warfarin"
  )
)

cdm$ankle_sprain |>
  addConceptIntersectFlag(
    conceptSet = meds_cs,
    indexDate = "cohort_start_date",
    window = list(
      c(-Inf, -1),
      c(0, 0)
    )
  ) |>
  glimpse()
#> Rows: ??
#> Columns: 18
#> Database: DuckDB 1.4.1 [martics@Windows 10 x64:R 4.2.1/C:\Users\martics\AppData\Local\Temp\Rtmp6tGZSu\file81bc46b3821.duckdb]
#> $ cohort_definition_id           <int> 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, …
#> $ subject_id                     <int> 2651, 2235, 3308, 3195, 1205, 1590, 362…
#> $ cohort_start_date              <date> 1957-06-27, 1959-03-28, 1951-07-19, 20…
#> $ cohort_end_date                <date> 1957-07-25, 1959-04-25, 1951-08-16, 20…
#> $ `1191_aspirin_0_to_0`          <dbl> 1, 1, 0, 0, 0, 0, 1, 0, 0, 1, 0, 0, 0, …
#> $ `1191_aspirin_minf_to_m1`      <dbl> 1, 1, 1, 1, 1, 1, 1, 1, 0, 1, 1, 1, 1, …
#> $ `5224_heparin_minf_to_m1`      <dbl> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, …
#> $ `723_amoxicillin_0_to_0`       <dbl> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, …
#> $ `723_amoxicillin_minf_to_m1`   <dbl> 0, 1, 0, 0, 0, 0, 0, 1, 1, 1, 1, 1, 1, …
#> $ `7804_oxycodone_minf_to_m1`    <dbl> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, …
#> $ `161_acetaminophen_minf_to_m1` <dbl> 1, 0, 0, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, …
#> $ `11289_warfarin_minf_to_m1`    <dbl> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, …
#> $ `161_acetaminophen_0_to_0`     <dbl> 0, 0, 1, 0, 1, 1, 0, 0, 1, 0, 1, 0, 0, …
#> $ `7052_morphine_minf_to_m1`     <dbl> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, …
#> $ `11289_warfarin_0_to_0`        <dbl> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, …
#> $ `5224_heparin_0_to_0`          <dbl> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, …
#> $ `7052_morphine_0_to_0`         <dbl> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, …
#> $ `7804_oxycodone_0_to_0`        <dbl> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, …

1.4 Cohort-based versus concept-based intersections

In the previous vignette we saw that we can add an intersection variable using a cohort we have created. Meanwhile in this vignette we see that we can instead create an intersection variable using a concept set directly. It is important to note that under some circumstances these two approaches can lead to different results.

When creating a cohort we combine overlapping records, as cohort entries cannot overlap. Thus when adding an intersection count, addCohortIntersectCount() will return a count of cohort entries in the window of interest while addConceptIntersectCount() will return a count of records withing the window. We can see the impact for acetaminophen for our example data below, where we have slightly more records than cohort entries.

acetaminophen_cs <- getDrugIngredientCodes(
  cdm = cdm,
  name = c("acetaminophen")
)

cdm$acetaminophen <- conceptCohort(
  cdm = cdm,
  name = "acetaminophen",
  conceptSet = acetaminophen_cs
)
#> ℹ Subsetting table drug_exposure using 7 concepts with domain: drug.
#> ℹ Combining tables.
#> ℹ Creating cohort attributes.
#> ℹ Applying cohort requirements.
#> ℹ Merging overlapping records.
#> ✔ Cohort acetaminophen created.

bind_rows(
  cdm$ankle_sprain |>
    addCohortIntersectCount(
      targetCohortTable = "acetaminophen",
      window = c(-Inf, Inf)
    ) |>
    group_by(`161_acetaminophen_minf_to_inf`) |>
    tally() |>
    collect() |>
    arrange(desc(`161_acetaminophen_minf_to_inf`)) |>
    mutate(type = "cohort"),
  cdm$ankle_sprain |>
    addConceptIntersectCount(
      conceptSet = acetaminophen_cs,
      window = c(-Inf, Inf)
    ) |>
    group_by(`161_acetaminophen_minf_to_inf`) |>
    tally() |>
    collect() |>
    arrange(desc(`161_acetaminophen_minf_to_inf`)) |>
    mutate(type = "concept_set")
) |>
  ggplot() +
  geom_col(aes(`161_acetaminophen_minf_to_inf`, n, fill = type),
    position = "dodge"
  ) +
  theme_bw() +
  theme(
    legend.title = element_blank(),
    legend.position = "top"
  )

Additional differences between cohort and concept set intersections may also result from cohort table rules. For example, cohort tables will typically omit any records that occur outside an individual´s observation time (as defined in the observation period window). Such records, however, would not be excluded when adding a concept based intersection.