Add unit_source_concept_id to Observation

closes #779

Author: clairblacketer

inst/csv/OMOP_CDMv5.5_Field_Level.csv

@@ -188,6 +188,7 @@ observation,visit_detail_id,FALSE,integer,"The VISIT_DETAIL record during which
 observation,observation_source_value,FALSE,varchar(50),"This field houses the verbatim value from the source data representing the Observation that occurred. For example, this could be an ICD10 or Read code.",This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference.,FALSE,FALSE,NA,NA,NA,NA
 observation,observation_source_concept_id,FALSE,integer,"This is the concept representing the OBSERVATION_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Observation necessary for a given analytic use case. Consider using OBSERVATION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.",If the OBSERVATION_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.,FALSE,TRUE,CONCEPT,CONCEPT_ID,NA,NA
 observation,unit_source_value,FALSE,varchar(50),This field houses the verbatim value from the source data representing the unit of the Observation that occurred.,This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference.,FALSE,FALSE,NA,NA,NA,NA
+observation,unit_source_concept_id,FALSE,integer,"""This is the concept representing the UNIT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Observation necessary for a given analytic use case. Consider using UNIT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.""",If the UNIT_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.,FALSE,TRUE,CONCEPT,CONCEPT_ID,NA,NA
 observation,qualifier_source_value,FALSE,varchar(50),This field houses the verbatim value from the source data representing the qualifier of the Observation that occurred.,This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference.,FALSE,FALSE,NA,NA,NA,NA
 observation,value_source_value,FALSE,varchar(50),This field houses the verbatim result value of the Observation from the source data.  Do not get confused with the Observation_source_value which captures source value of the observation mapped to observation_concept_id. This field is the observation result value from the source.,"If the observation_source_value was a question, for example,  or an observation that requires a result then this field is the answer/ result from the source data. Store the verbatim value that represents the result of the observation_source_value.",FALSE,FALSE,NA,NA,NA,NA
 observation,observation_event_id,FALSE,integer,"If the Observation record is related to another record in the database, this field is the primary key of the linked record.","Put the primary key of the linked record, if applicable, here. See the [ETL Conventions for the OBSERVATION](https://ohdsi.github.io/CommonDataModel/cdm54.html#observation) table for more details.",FALSE,FALSE,NA,NA,NA,NA