You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The csv file that contains the field-level specs for the OMOP CDM v6.0 seems to have some errors in it.
For example:
(1) In the drug_exposure table, the field stop_reason is present, even though it is explained in the user guidance that this field "will be retired in v6.0."
(2) In several tables, the requirements on date/datetimes seems to be reversed. The explanation at https://ohdsi.github.io/CommonDataModel/cdm60.html#Changes_in_v60 is that "DATETIME fields were made mandatory and date fields were made optional." This is true in the spec for some tables (e.g., visit_occurrence), but the opposite is specified for condition_occurrence and drug_exposure.
It looks to me like some of the specs were updated appropriately in this file for v5.4 -> v6.0, but for certain tables, the field-level specs from v5.4 were simply repeated in the file for v6.0 when they should have been changed.
Examples above are not intended to be exhaustive, they are simply a few observations.
The text was updated successfully, but these errors were encountered:
The csv file that contains the field-level specs for the OMOP CDM v6.0 seems to have some errors in it.
For example:
(1) In the drug_exposure table, the field stop_reason is present, even though it is explained in the user guidance that this field "will be retired in v6.0."
(2) In several tables, the requirements on date/datetimes seems to be reversed. The explanation at https://ohdsi.github.io/CommonDataModel/cdm60.html#Changes_in_v60 is that "DATETIME fields were made mandatory and date fields were made optional." This is true in the spec for some tables (e.g., visit_occurrence), but the opposite is specified for condition_occurrence and drug_exposure.
It looks to me like some of the specs were updated appropriately in this file for v5.4 -> v6.0, but for certain tables, the field-level specs from v5.4 were simply repeated in the file for v6.0 when they should have been changed.
Examples above are not intended to be exhaustive, they are simply a few observations.
The text was updated successfully, but these errors were encountered: