Documentation
Common Data Model (CDM)
Convert Database to CDM (ETL)
Tool Specific Documentation
Common Data Model (CDM)
Convert Database to CDM (ETL)
Tool Specific Documentation
This is an old revision of the document!
Proposing person: Vojtech Huser
Discussion link: http://forums.ohdsi.org/t/metadata-extension-to-cdm/1746/1
Table CDM_SOURCE provides metadata. (http://www.ohdsi.org/web/wiki/doku.php?id=documentation:cdm:cdm_source)
Tablename: METADATA
This table is relying on concept_id's that exist for CDM tables. In Atlas, search for those using advanced search and selecting Metadata.
Column | Description | Data_type |
---|---|---|
METADATA_CONCEPT_ID | OMOP Vocabulary CONCEPT_ID that identifies the information you with to track (e.g. 8 for metadata about a Visit) | INT |
METADATA_TYPE_CONCEPT_ID | OMOP Vocabulary CONCEPT_ID that identifies the type information you with to track (e.g. 1 for metadata about Domains such as a Visit) | INT |
NAME | Name of the CONCEPT_ID stored in METADATA_CONCEPT_ID or in the event there is not an applicable CONCEPT_ID NAME can be used to represent the data stored (e.g. CDM_BUILDER VERSION) | VARCHAR(250) |
VALUE | Store the metadata value you wish to capture | NVCHAR |
Example records:
METADATA_CONCEPT_ID | METADATA_TYPE_CONCEPT_ID | NAME | VALUE |
---|---|---|---|
8 | 1 | VISIT | For the outpatient visits, all activity that is recorded on a single day for a person is considered to have occurred during one visit with the visit start and end date corresponding to this date. |
0 | 0 | CDM_BUILDER VERSION | 1.8.0.9 |
We want to add the following column the table:
Column | Description | Data type | |
---|---|---|---|
DATASET_TYPE_CONCEPT_ID | Type of dataset. Reference to OMOP Concept that provides dataset type classification. | integer |
Also we want to add clarification to table CDM_SOURCE that one row in that table is expected.
Text below only reflects some historical notes related to the proposal above.
Proposing person: Patrick Ryan, Martijn Schuemie, Ajit Londhe, & Erica Voss
(may need to be updated)
Additionally we would like the CDM_SOURCE table to store metadata about each of the domains. Our idea is to implement it by adding an additional column for each domain in the CDM to the CDM_SOURCE table (i.e. CDM_SOURCE.VISIT_OCCURRENCE, CDM_SOURCE.PERSON, etc). The value this brings is this will allow us to display information about a specific domain on an ACHILLES report. For example, VISIT_OCCURRENCE logic in PREMIER is fairly complex and displaying a description of that logic at the point where someone is reviewing the data in ACHILLES would be beneficial.
Here is an example of some text for JMDC:
(already has a column) JMDC database consists of data from 60 Society-Managed Health Insurances covering workers aged 18 to 65 and their dependents (children younger than 18 years old and elderly people older than 65 years old). The old people (particularly those aged 66 or older) are less representative as compared with whole population in the nation. When estimated among the people who are younger than 66 years old, the proportion of children younger than 18 years old in JMDC is approximately the same as the proportion in the whole nation. JMDC data includes data on membership status of the insured people and claims data provided by insurers under contract. Claims data are derived from monthly claims issued by clinics, hospitals and community pharmacies.
JMDC covers workers aged 18 to 65 and their dependents (children younger than 18 years old and elderly people older than 65 years old). The old people (particularly those aged 66 or older) are less representative as compared with whole population in the nation. When estimated among the people who are younger than 66 years old, the proportion of children younger than 18 years old in JMDC is approximately the same as the proportion in the whole nation. Only the year of birth is available, so not the day or month.
The observation period is defined as the time of enrollment in the health insurance. If the member is a dependent, the enrollment depends on the enrollment of the main beneficiary.
Care sites in JMDC are institutions where care is provided, typically a department in a hospital.
Advanced Data Quality checks (inside Achilles Heel) would take advantage of this information in this new column.
Proposing person: Ajit Londhe, & Erica Voss
We would like to propose the following table to hold metadata:
Tablename: METADATA
Column | Description | Data_type |
---|---|---|
METADATA_CONCEPT_ID | OMOP Vocabulary CONCEPT_ID that identifies the information you with to track (e.g. 8 for metadata about a Visit) | INT |
METADATA_TYPE_CONCEPT_ID | OMOP Vocabulary CONCEPT_ID that identifies the type information you with to track (e.g. 1 for metadata about Domains such as a Visit) | INT |
NAME | Name of the CONCEPT_ID stored in METADATA_CONCEPT_ID or in the event there is not an applicable CONCEPT_ID NAME can be used to represent the data stored (e.g. CDM_BUILDER VERSION) | VARCHAR(250) |
VALUE | Store the metadata value you wish to capture | NVCHAR |
Example records:
METADATA_CONCEPT_ID | METADATA_TYPE_CONCEPT_ID | NAME | VALUE |
---|---|---|---|
8 | 1 | VISIT | For the outpatient visits, all activity that is recorded on a single day for a person is considered to have occurred during one visit with the visit start and end date corresponding to this date. |
0 | 0 | CDM_BUILDER VERSION | 1.8.0.9 |
NOTES original table was
Column | Description | Data type | |
---|---|---|---|
DATASET_TYPE_CONCEPT_ID | Type of dataset. Reference to OMOP Concept that provides dataset type classification. | integer | |
PERSON | text | ||
OBSERVATION_PERIOD | text | ||
VISIT_OCCURRENCE | Description of the logic used to populate the table (column name indicates the table). | text | |
PROCEDURE_OCCURRENCE | Description of the logic used to populate the table (column name indicates the table). | text | |
CONDITION_OCCURRENCE | Description of the logic used to populate the table (column name indicates the table). | text | |
DRUG_EXPOSURE | Description of the logic used to populate the table (column name indicates the table). | text | |
MEASUREMENT | Description of the logic used to populate the table (column name indicates the table). | text |