Data normalization activities N3C submitting sites perform - Era mapping

[DaveraGabriel]

Discussion in DI&H "Large" meeting 27May2020.
What are the implemented approaches for sites to transform to OMOP, especially the 'era' tables pertaining to medication, dose and condition? The OHDSI team has developed a sql script which accommodates missing era dates / data. In the absence of era data / dates, the "safest" data, OHDSI community will create an era end date that is equal to the start date. Discussion includes implications for downstream analysts, not "close to data creation" and how decisions can effect the analyst assumptions. for medication eras - what does it mean to have a "safe" medication era of only one day. Failing that practice, if missing data are not included, then it is left to the Analysts to discover and accommodate these missing data. Both of these approaches are less than perfect solutions for the downstream consumption of normalized OMOP data

Evan Sholle made the comment that at his site, following the recommendations of Micheal Khan - they persist the source data that has multiple mappings as a JSON file in the OMOP concept code field.

[DaveraGabriel]

Michael Kahn weighs in on OHDSI forums on SourceID Mapping "Controversy" in the following link