migrateDataModel

Migrate data from current state to next state
It is strongly advised that you have a backup of all data (either sqlite files, a backup database (in the case you
are using a postgres backend) or have kept the csv/zip files from your data generation.

A user friendly way to create patient level prediction models using
the Observational Medical Outcomes Partnership Common Data Model. Given a cohort
of interest and an outcome of interest, the package can use data in the Common
Data Model to build a large set of features. These features can then be used to
fit a predictive model with a number of machine learning algorithms. This is
further described in Reps (2017) <doi:10.1093/jamia/ocy032>.

Egill Fridgeirsson

PatientLevelPrediction

Develop Clinical Prediction Models Using the Common Data Model

Jenna Reps

Martijn Schuemie

Marc Suchard

Patrick Ryan

Peter Rijnbeek

Observational Health Data Science and Informatics 

migrateDataModel function

<dl><dt>connectionDetails</dt>
<dd>DatabaseConnector connection details object</dd>
<dt>databaseSchema</dt>
<dd>String schema where database schema lives</dd>
<dt>tablePrefix</dt>
<dd>(Optional) Use if a table prefix is used before table names (e.g. "cd_")</dd></dl>

Arguments

Migrate Data model — migrateDataModel

<dl>

<dt>connectionDetails</dt>
<dd>DatabaseConnector connection details object</dd>


<dt>databaseSchema</dt>
<dd>String schema where database schema lives</dd>


<dt>tablePrefix</dt>
<dd>(Optional) Use if a table prefix is used before table names (e.g. "cd_")</dd>

</dl>

migrateDataModel: Migrate Data model

Description

Usage

Value

Arguments