fetchChronographData: Fetch data for constructing chronographs from the server

Description Usage Arguments Details

View source: R/Chronographs.R

Description

Fetch data for constructing chronographs from the server

Usage

1
2
3
fetchChronographData(connectionDetails, cdmDatabaseSchema,
  cohortDatabaseSchema, tablePrefix = "legend",
  indicationId = "Depression", oracleTempSchema, outputFolder)

Arguments

connectionDetails

An object of type connectionDetails as created using the createConnectionDetails function in the DatabaseConnector package.

cdmDatabaseSchema

Schema name where your patient-level data in OMOP CDM format resides. Note that for SQL Server, this should include both the database and schema name, for example 'cdm_data.dbo'.

cohortDatabaseSchema

Schema name where intermediate data can be stored. You will need to have write priviliges in this schema. Note that for SQL Server, this should include both the database and schema name, for example 'cdm_data.dbo'.

tablePrefix

A prefix to be used for all table names created for this study.

indicationId

A string denoting the indicationId for which the exposure cohorts should be created.

oracleTempSchema

Should be used in Oracle to specify a schema where the user has write priviliges for storing temporary tables.

outputFolder

Name of local folder to place results; make sure to use forward slashes (/)

Details

Fetch data for constructing chronographs from the server.


OHDSI/Legend documentation built on Dec. 29, 2020, 3:52 a.m.