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

Use OHDSI ddl defintions to build OMOP data internal data models and output #167

Open
PhilAppleby opened this issue Jan 17, 2024 · 1 comment
Assignees

Comments

@PhilAppleby
Copy link
Collaborator

Background: One of the changes made when adding the "mapstream" function was to switch from using the internal CDM definitions based on Django to dynamic loading of json configuration in which lists of output fields, date fields, datetime fields were used - the aim being to allow data output to be handled via configuarion with no code changes required to add / modify data objects.

The next logical step is to generate the same json (python dictionary) from OHDSI-managed ddl definitions, removing the need for code upgrades on version changes and to cater for all OMOP data tables.

@PhilAppleby
Copy link
Collaborator Author

This work is currently in test

@PhilAppleby PhilAppleby self-assigned this Jan 17, 2024
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

1 participant