I agree with the rest to not standardize the source_value fields.
However, we might want to standardize the way in which we store non-omop source concepts. As far as I see, there are now two ways: either storing the source concept info (code, vocabulary, description) in the source_to_concept_map or in a new 2-Billionaire concept. I would suggest to use the latter and remove the source_code, source_vocabulary_id and source_description from the source_to_concept_map table and only reference the 2-Billionaire source_concept_id. Or even deprecate the source_to_concept_map table and create the mapping as a new 2-Billionaire record in the concept_relationship table. Any thoughts?
@Gowtham_Rao. Do you store the description of your non-omop source concepts somewhere? e.g. in the source_to_concept_map?