Source data that are mapped into OMOP 5.3.1 can be preserved by aggregating into a single OMOP field. These source data should be delimited and can be identified with tags. Children's Hospital of Colorado created and stored JSON objects for this purpose. Another approach is to cerate an OMOP extension to store this data. Of issue: what is the best approach to aggregation and preservation of raw and source data on N3C OMOP instance?
Source data that are mapped into OMOP 5.3.1 can be preserved by aggregating into a single OMOP field. These source data should be delimited and can be identified with tags. Children's Hospital of Colorado created and stored JSON objects for this purpose. Another approach is to cerate an OMOP extension to store this data. Of issue: what is the best approach to aggregation and preservation of raw and source data on N3C OMOP instance?