Update ETL to v5.4.2 #56
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #40, we updated the DDL to Common Data Model (CDM) v5.4.2. This PR updates the ETL scripts to comply with CDM v5.4.2.
In two cases (
visit_occurrence,visit_detail) some of the variable names were updated. In most cases, new variables were added to a given table. In this scenario, I generally added the variables and assigned NULL to the new value. Updates to add meaningful values to the new variables will be handled in separate PRs on a table by table basis. Here is a summary of the variables that were added and how they were updated/handled in this PR:device_exposureproduction_id,unit_concept_id,unit_source_value,unit_source_concept_iddevice_exposuretable #55 for details.locationcountry_concept_id,country_source_value,latitude,longitudemeasurementmeasurement_event_id,meas_event_field_concept_idobservationvalue_source_value,observation_event_id,obs_event_field_concept_idprocedure_occurrenceprocedure_end_date,procedure_end_datetimeprocedure_occurrence#54 for details.There are some tables in v5.4.2 which aren't being built as part of the ETL. Adding the code to build these tables will also be handled in a separate PR.