This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
documentation:next_cdm:metadata [2016/10/27 00:59] ericavoss |
documentation:next_cdm:metadata [2017/04/04 13:50] vojtechhuser |
||
---|---|---|---|
Line 28: | Line 28: | ||
| 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) | | | 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 | | | 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:** | **Example records:** |