Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

errors in inst/csv/OMOP_CDMv6.0_Field_Level.csv #722

Open
JohnBurantRIVM opened this issue Jan 8, 2025 · 2 comments
Open

errors in inst/csv/OMOP_CDMv6.0_Field_Level.csv #722

JohnBurantRIVM opened this issue Jan 8, 2025 · 2 comments

Comments

@JohnBurantRIVM
Copy link

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.

@JohnBurantRIVM
Copy link
Author

Also, in the v6.0 CSV field spec, all fields for the death table are given, but the death table has been eliminated from v6.0...?

@MelaniePhilofsky
Copy link
Collaborator

@JohnBurantRIVM CDM v6.0 is not supported by the OHDSI community. Currently, we are using v5.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants