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.

Sign up for GitHub

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

Jump to bottom

Decide on and implement lightweight "dev" vocabulary approach #9

Closed

katy-sadowski opened this issue Mar 23, 2024 · 1 comment

Assignees

Collaborator

katy-sadowski commented Mar 23, 2024

Decide how we should approach the use of the OMOP vocabulary as we are developing this project. Requirements:

consistency - ideally, all devs are using the exact same vocabulary tables so we can produce consistent results as we work locally
performance- vocabs should be small enough that we can quickly run dbt locally
coverage - enough coverage such that some standard concept mapping is possible across relevant columns/tables for this ETL

katy-sadowski assigned adambouras

katy-sadowski self-assigned this

Collaborator Author

katy-sadowski commented Jun 5, 2024

Added a slimmed down vocab in #4

katy-sadowski closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment