projects:workgroups:clinicalstudy
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
projects:workgroups:clinicalstudy [2020/10/12 19:38] saraujo |
projects:workgroups:clinicalstudy [2020/10/12 19:39] saraujo |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| **Objective**: To allow adequate representation of clinical trial data in OMOP. | **Objective**: To allow adequate representation of clinical trial data in OMOP. | ||
| - | **First use case**: To convert clinical trial data in CDISC SDTM format to OMOP, with a view to allowing trial planning optimization. | + | **First use case**: To convert clinical trial data in CDISC SDTM format to OMOP, with a view to allowing trial planning optimization. |
| - | **Approach**: We advocate minimum changes to the OMOP CDM and Standardized Vocabularies because we want to ensure minimum impact on OHDSI tools like Atlas, whilst providing a value-add SDTM-to-OMOP conversion with minimum data loss. We have proposed conventions introducing new concepts and modifiers, but no new CDM tables; and providing guidance for ETL developers where appropriate. Our proposals are built on OMOP CDM v6 and the Oncology extension, with v5.3.1 backward compatibility. | + | **Approach**: We advocate minimum changes to the OMOP CDM and Standardized Vocabularies because we want to ensure minimum impact on OHDSI tools like Atlas, whilst providing a value-add SDTM-to-OMOP conversion with minimum data loss. We have proposed conventions introducing new concepts and modifiers, but no new CDM tables; and providing guidance for ETL developers where appropriate. Our proposals are built on OMOP CDM v6 and the Oncology extension, with v5.3.1 backward compatibility. |
| **Status**: | **Status**: | ||
projects/workgroups/clinicalstudy.txt ยท Last modified: 2024/04/28 20:17 by zhen
Page Tools
