development:data_architecture
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
development:data_architecture [2016/08/22 18:06] frank_defalco created |
development:data_architecture [2016/08/23 13:24] (current) frank_defalco |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| * **Source Data** : Person level data that is acquired through different parts of the healthcare system. These sources are said to exist in the "//native schema//". | * **Source Data** : Person level data that is acquired through different parts of the healthcare system. These sources are said to exist in the "//native schema//". | ||
| * **Standardized Data** : Data that has been converted into the OMOP CDM format. These data are said to exist in the "//CDM schema//". | * **Standardized Data** : Data that has been converted into the OMOP CDM format. These data are said to exist in the "//CDM schema//". | ||
| - | * **Derived Data** : Data that is the result of some form of processing on data that came from the OMOP CDM format. These data are said to exist in the "//results schema//" | + | * **Derived Data** : Data that is the result of some form of processing on data that came from the OMOP CDM format. These data are said to exist in the "//results schema//". Most of these data are aggregate summary statistics. |
| - | * **Administrative Data** : Data that is created or maintained to describe a concept, process or system function within the broader OHDSI architecture. These data are said to exist in the "//OHDSI schema//". | + | * **OHDSI Platform Metadata** : Metadata that is created or maintained to describe a concept, process or system function within the broader OHDSI architecture. These data are said to exist in the "//OHDSI schema//". |
| === Data Life-Cycle === | === Data Life-Cycle === | ||
| - | There is a life-cycle of data within the OHDSI data architecture. Data primarily originates from a person level data source. These data sources include electronic health records, administrative claims records, clinical trial data and billing data among others. These person level data sources are typically received in their own proprietary format which we refer to as the "Native Format". The approach used within OHDSI is to standardize these sources of person level data by performing [[documentation:etl_best_practices|ETL processes]] and converting them from their Native format to the [[documentation:cdm|OMOP Common Data Model (CDM)]] format. | + | There is a life-cycle of data within the OHDSI data architecture. Data primarily originates from a person level data source. These data sources include electronic health records, administrative claims records, clinical trial data and billing data among others. These person level data sources are typically received in their own proprietary format which we refer to as the "Native Format". The approach used within OHDSI is to standardize these sources of person level data by performing [[documentation:etl_best_practices|ETL processes]] and converting them from their Native format to the [[documentation:cdm|OMOP Common Data Model (CDM)]] format. Once this conversion is complete the intent is for the CDM to be a read only data source. |
| + | |||
| + | Once a data source has been converted from the native schema to the CDM schema the OHDSI tools provide features to perform many different analyses. These analyses include high level population level descriptive statistics and characterization, definition and generation of cohorts, study specification and population level estimation among others. The processes that implement these features generate new data that has been derived from the CDM data schema. This derived data is then stored in the results schema. The OHDSI Platform Metadata that describes the concepts and processes that were used to derive these results from the CDM schema are stored in the OHDSI schema. | ||
development/data_architecture.1471889176.txt.gz · Last modified: 2016/08/22 18:06 by frank_defalco
Page Tools
