CommonDataModel

by OHDSI

Definition and DDLs for the OMOP Common Data Model (CDM)

470 Stars 284 Forks Last release: almost 2 years ago (v6.0.0) Apache License 2.0 379 Commits 11 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

Common Data Model v6.0

See full CDM specification file on our github wiki or in the CDM V6.0 PDF

Release Notes for v6.0

This version address the following issues/pull requests:

CDM

  • #81 Adds the COST table
  • #137 Adds the SURVEY_CONDUCT table
  • #181 Adds the LOCATION_HISTORY table
  • #91 Latitude and longitude added to LOCATION table
  • #107 Contract owner information added to PAYERPLANPERIOD
  • #120 New fields added to PAYERPLANPERIOD (PAYERCONCEPTID, PLANCONCEPTID)
  • #166 Record inserted into METADATA to document CDM version
  • #172 NOTEEVENTID and NOTEDOMAINID (NOTEEVENTTABLECONCEPTID) added to NOTE
  • #198 Change IDs to BIGINT
  • #153 ADMISSIONSOURCECONCEPTID changed to ADMITTEDFROMCONCEPTID
  • #214 All CONCEPTIDs are mandatory except for UNITCONCEPTID, VALUEASCONCEPTID, and OPERATORCONCEPTID
  • #164 Any reference to DOMAINID was switched to EVENTFIELDCONCEPTID
  • #212 CDM Results schema created with tables COHORT and COHORT_DEFINITION
  • #210 DEATH table removed and cause of death now stored in CONDITION_OCCURRENCE
  • #166 Record inserted into METADATA identifying the CDM version
  • #172 Added NOTEEVENTID and EVENTFIELDCONCEPT_ID to NOTE table

Vocabulary

  • #186 Keep deprecated CPT concepts active and standard
  • #85 NOTE_NLP concepts added

Wiki

  • #188 Added foreign key description to wiki files
  • All THEMIS rules added to wiki

Additional Updates

  • DATE fields are now optional and DATETIME fields are mandatory

This repo contains the definition of the OMOP Common Data Model. It supports the SQL technologies: BigQuery, Impala, Netezza, Oracle, Parallel Data Warehouse, Postgres, Redshift, and SQL Server. For each, the DDL, constraints and indexes (if appropriate) are defined.

Versions are defined using tagging and versioning. Full versions (V6, 7 etc.) are usually released at most once a year and are not backwards compatible. Minor versions (V5.1, 5.2 etc.) are not guaranteed to be backwards compatible though an effort is made to make sure that current queries will not break. Micro versions (V5.1.1, V5.1.2 etc.) are released irregularly and often, and contain small hot fixes or backward compatible changes to the last minor version.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.