Uses one or several covariate builder functions to construct covariates.
getDbCovariateData(connectionDetails = NULL, connection = NULL, oracleTempSchema = NULL, cdmDatabaseSchema, cdmVersion = "5", cohortTable = "cohort", cohortDatabaseSchema = cdmDatabaseSchema, cohortTableIsTemp = FALSE, cohortId = -1, rowIdField = "subject_id", covariateSettings, aggregated = FALSE)
An R object of type
A connection to the server containing the schema as created using the
A schema where temp tables can be created in Oracle.
The name of the database schema that contains the OMOP CDM instance. Requires read permissions to this database. On SQL Server, this should specifiy both the database and the schema, so for example 'cdm_instance.dbo'.
Define the OMOP CDM version used: currently supported is "5".
Name of the (temp) table holding the cohort for which we want to construct covariates
If the cohort table is not a temp table, specify the database schema where the cohort table can be found. On SQL Server, this should specifiy both the database and the schema, so for example 'cdm_instance.dbo'.
Is the cohort table a temp table?
For which cohort ID should covariates be constructed? If set to -1, covariates will be constructed for all cohorts in the specified cohort table.
The name of the field in the cohort table that is to be used as the row_id field in the output table. This can be especially usefull if there is more than one period per person.
Either an object of type
Should aggregate statistics be computed instead of covariates per cohort entry?
Returns an object of type
covariateData, containing information on the covariates.
This function uses the data in the CDM to construct a large set of covariates for the provided cohort. The cohort is assumed to be in an existing table with these fields: 'subject_id', 'cohort_definition_id', 'cohort_start_date'. Optionally, an extra field can be added containing the unique identifier that will be used as rowID in the output.