Skip to content

[Breaking Change] Immunization Table addition from Input to Core layer #981

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

Open
wants to merge 17 commits into
base: minor-release-v0.15
Choose a base branch
from

Conversation

BijayaShres
Copy link
Contributor

Describe your changes

  • Introduction of a new clinical input layer table immunization
  • Transformation of the table to core__immunization
  • Introduction of 5 new terminology data set (needed to build core model)
    • terminology__act_site
    • terminology__cvx
    • terminology__immunization_route_code
    • terminology__immunization_status_reason
    • terminology__immunization_status
  • Relevant changes in integration_tests, docs_generate and ci_testing

How has this been tested?

Ran dbt build -s +core__immunization with different variation of variable combinations
Ran dbt build selectively in docs_generate and ci_testing as well

Reviewer focus

Please sync csvs for above terminologies from s3://tuva-public-resources-snowflake/versioned_terminology/ to s3://tuva-public-resources/versioned_terminology/0.15.0
Also, please sync branch release-v0.15.0-breaking-changes with latest Tuva main to see file changes clearly in the PR

Checklist before requesting a review

  • I have added at least one Github label to this PR (bug, enhancement, breaking change,...)
  • My code follows style guidelines
  • (New models) YAML files are categorized by sub folder and models listed in alphabetical order
  • (New models) I have added a config to each new model to enable it for claims and/or clinical data
  • (New models) I have added the variable tuva_last_run to the final output
  • (Optional) I have recorded a Loom to explain this PR

(Optional) Gif of how this PR makes you feel

Loom link

@BijayaShres BijayaShres requested a review from sarah-tuva July 23, 2025 17:36
@BijayaShres BijayaShres added the breaking-change Changes have been made that may cause other components to fail label Jul 23, 2025
@github-project-automation github-project-automation bot moved this to 👀 Ready for Review in The Tuva Project Jul 23, 2025

This comment was marked as outdated.

This comment was marked as outdated.

1 similar comment
Copy link

Workflow has finished with the following statuses:

  • Linter: success
  • BigQuery Clinical and Claims: failure
  • BigQuery Claims: skipped
  • BigQuery Clinical: skipped
  • Fabric Clinical and Claims: failure
  • Fabric Claims: skipped
  • Fabric Clinical: skipped
  • Redshift Clinical and Claims: failure
  • Redshift Claims: skipped
  • Redshift Clinical: skipped
  • Snowflake Clinical and Claims: failure
  • Snowflake Claims: skipped
  • Snowflake Clinical: skipped

Copy link

Workflow has finished with the following statuses:

  • Linter: success
  • BigQuery Clinical and Claims: success
  • BigQuery Claims: success
  • BigQuery Clinical: success
  • Fabric Clinical and Claims: success
  • Fabric Claims: success
  • Fabric Clinical: success
  • Redshift Clinical and Claims: success
  • Redshift Claims: success
  • Redshift Clinical: success
  • Snowflake Clinical and Claims: success
  • Snowflake Claims: success
  • Snowflake Clinical: success

Copy link
Member

@sarah-tuva sarah-tuva left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @BijayaShres, thanks for opening this new PR. Apologies for the delay in reviewing it. I just ran the CI tests and they're all passing.

I have two requests for changes. Can you take a look at the data marts listed below. This new data source needs to be added to both. Let me know if you have any questions.

@BijayaShres
Copy link
Contributor Author

BijayaShres commented Jul 30, 2025

Hi @sarah-tuva ! Thanks for reviewing the PR and running the CI tests.

I'll update both the dqi and normalize data marts to include the new data source.
Furthermore, i will also work on updating the docs docs related to normalize mart.
Let me know if there's anything else I should keep in mind.

@sarah-tuva
Copy link
Member

@BijayaShres, good idea to update docs for normalize. 🙏 Can you also create PR adding this new file type to Docs? I think we will want it in the Input Layer and Core sections.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Changes have been made that may cause other components to fail
Projects
Status: 👀 Ready for Review
Development

Successfully merging this pull request may close these issues.

6 participants