Differences

This shows you the differences between two versions of the page.

--- documentation:next_cdm:metadata [2016/10/27 00:59] – ericavoss
+++ documentation:next_cdm:metadata [2017/07/10 16:26] (current) – clairblacketer
@@ Line 1: / Line 1: @@
+====Metadata====
+===Proposals are now tracked as github issues===
+[[https://github.com/OHDSI/CommonDataModel/issues/79|link to github issue]]
 Proposing person: Vojtech Huser
@@ Line 8: / Line 12: @@
 ====== Use case ======
-  - only run certain data quality checks when they are appropriate to the dataset (e.g., general population dataset)
+  - display metadata within Atlas-Achilles Web (when reviewing data characterization plots and tables)
-  - display metadata within Atlas-Achilles Web
+  - allow organizations with multiple OMOP CDM datasets to have a mechanism to store dataset metadata (analysis of this use will provide input for phase 2 of metadata standardization)
+  - only run certain data quality checks when they are appropriate to the dataset (e.g., general population dataset; this use case depends on proper concept level standardization)
 ====== CDM changes ======
-The proposal is adding a single table to the CDM specs.
+The proposal is adding a single table to the CDM specs. In phase 1, we are trying to provide a mechanism for sites to capture metadata. The concept level standardization is planned in phase 2.
 ===== new METADATA table =====
@@ Line 28: / Line 34: @@
 | 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  |
+**Modified proposal**
+^ Column                    ^ Description                                                                                                                                                                          ^ Data_type     | Required  |
+| 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_AS_STRING           | Store the metadata value (string)                                                                                                                                                    | NVCHAR        |           |
+| VALUE_AS_CONCEPT_ID       | OMOP Vocabulary CONCEPT_ID that reflects the metadata value                                                                                                                          | int           | No        |
+| METADATA_DATETIME         | The date and time associated with metadata                                                                                                                                           | datetime      | No        |
+| METADATA_DATE             | date                                                                                                                                                                                 | date          | No        |
 **Example records:**