Skip to content

Releases: tuva-health/tuva-core

the_tuva_project v0.18.0

Choose a tag to compare

@aneiderhiser aneiderhiser released this 07 May 21:06
da0b493

This is the stable release for 0.18.0

What's Changed

🚨 Breaking Changes 🚨

  • [BREAKING CHANGE] 1203 update facility id to facility npi by @chase-jones in #1262
  • [Breaking Change] 1270 add 9 nullable columns to core eligibility for cms risk adjustment part cd aca esrd by @chase-jones in #1271

Other Changes

Full Changelog: v0.17.1...v0.18.0

the_tuva_project v0.18.0-rc

Pre-release

Choose a tag to compare

@github-actions github-actions released this 24 Apr 04:35
da0b493

This is the release candidate for 0.18.0

What's Changed

🚨 Breaking Changes 🚨

  • [BREAKING CHANGE] 1203 update facility id to facility npi by @chase-jones in #1262
  • [Breaking Change] 1270 add 9 nullable columns to core eligibility for cms risk adjustment part cd aca esrd by @chase-jones in #1271

Other Changes

Full Changelog: v0.17.1...v0.18.0

the_tuva_project v0.17.2

Choose a tag to compare

@aneiderhiser aneiderhiser released this 02 Apr 17:07

Highlights

  • Tuva Data Assets on DoltHub: Tuva data assets are now organized as 6 versioned databases on DoltHub: terminology, value sets, reference data, provider data, concept library, and synthetic data. DoltHub is now the release source of truth, while S3, GCS, and Azure Blob remain the distribution layer used by the existing seed-loading macros.
  • Versioned Seed Releases: Package seeds and synthetic integration-test inputs now load from versioned release artifacts that have been copied to S3/Azure/GCS from DoltHub. Releases can be controlled with tuva_seed_version, per-database overrides via tuva_seed_versions, and storage overrides via tuva_seed_buckets.
  • CI Improvements: CI now uses dbt-style command routing instead of alias-style commands. For example, /ci dbt build --full-refresh runs across all 6 warehouses, while /ci snowflake dbt run or /ci redshift dbt run --select core__medical_claim target specific warehouses and selections.
  • Docs in the Tuva Repo: The docs site now lives in the tuva repo under docs, which keeps docs closer to the code and metadata they describe.

Input Layer

  • No net new breaking input-layer contract changes relative to v0.17.1.
  • Input-layer YAML definitions now include clearer mapping_instructions and required_for_data_marts metadata.

Data Mart Updates

  • CMS-HCC Institutional Logic: institutional_status is now derived from long_term_institutional_flag, improving institutional classification in CMS-HCC workflows.

Bug Fixes

  • BigQuery Seed Loading: BigQuery now handles both empty-string nulls and \N null markers in release-backed CSV artifacts.
  • DuckDB Provider Attribution: Fixed a DuckDB planner issue affecting provider attribution workflows.

Miscellaneous

  • integration_tests is Synthetic-Only: integration_tests now runs only against published synthetic datasets, with small as the default size and large also available.
  • Header-Only Synthetic Seed Files: Local CSVs in integration_tests/seeds are now header-only; dbt seed hydrates them from published versioned synthetic artifacts.
  • Seed Publishing Tooling: Added scripts to publish DoltHub-backed seed releases to S3 and mirror them to GCS and Azure.

the_tuva_project v0.17.2-rc

Pre-release

Choose a tag to compare

@aneiderhiser aneiderhiser released this 31 Mar 17:16

Highlights

  • Tuva Data Assets on DoltHub: Tuva data assets are now organized as 6 versioned databases on DoltHub: terminology, value sets, reference data, provider data, concept library, and synthetic data. DoltHub is now the release source of truth, while S3, GCS, and Azure Blob remain the distribution layer used by the existing seed-loading macros.
  • Versioned Seed Releases: Package seeds and synthetic integration-test inputs now load from versioned release artifacts that have been copied to S3/Azure/GCS from DoltHub. Releases can be controlled with tuva_seed_version, per-database overrides via tuva_seed_versions, and storage overrides via tuva_seed_buckets.
  • CI Improvements: CI now uses dbt-style command routing instead of alias-style commands. For example, /ci dbt build --full-refresh runs across all 6 warehouses, while /ci snowflake dbt run or /ci redshift dbt run --select core__medical_claim target specific warehouses and selections.
  • Docs in the Tuva Repo: The docs site now lives in the tuva repo under docs, which keeps docs closer to the code and metadata they describe.

Input Layer

  • No net new breaking input-layer contract changes relative to v0.17.1.
  • Input-layer YAML definitions now include clearer mapping_instructions and required_for_data_marts metadata.

Data Mart Updates

  • CMS-HCC Institutional Logic: institutional_status is now derived from long_term_institutional_flag, improving institutional classification in CMS-HCC workflows.

Bug Fixes

  • BigQuery Seed Loading: BigQuery now handles both empty-string nulls and \N null markers in release-backed CSV artifacts.
  • DuckDB Provider Attribution: Fixed a DuckDB planner issue affecting provider attribution workflows.

Miscellaneous

  • integration_tests is Synthetic-Only: integration_tests now runs only against published synthetic datasets, with small as the default size and large also available.
  • Header-Only Synthetic Seed Files: Local CSVs in integration_tests/seeds are now header-only; dbt seed hydrates them from published versioned synthetic artifacts.
  • Seed Publishing Tooling: Added scripts to publish DoltHub-backed seed releases to S3 and mirror them to GCS and Azure.

the_tuva_project v0.17.1

Choose a tag to compare

@github-actions github-actions released this 12 Mar 17:23
1272ab2

What's Changed

🎉 Exciting New Features 🎉

🪲 Bug Fixes 🪲

Other Changes

New Contributors

Full Changelog: v0.17.0...v0.17.1

the_tuva_project v0.17.0

Choose a tag to compare

@github-actions github-actions released this 12 Feb 05:50
e79949f

What's Changed

  • Feature/add extension column pass-through support for core models by @rabee05 in #1191
  • Fix observation staging for claims-only logic by @sarahmcmorgan in #1199

New Contributors

Full Changelog: v0.16.2...v0.17.0

the_tuva_project v0.16.2

Choose a tag to compare

@github-actions github-actions released this 05 Feb 23:46
c177bf8

What's Changed

Improvements

🪲 Bug Fixes 🪲

Full Changelog: v0.16.1...v0.16.2

the_tuva_project v0.16.1

Choose a tag to compare

@github-actions github-actions released this 30 Jan 04:01
ec9dd13

What's Changed

Other Changes

Full Changelog: v0.16.0...v0.16.1

the_tuva_project v0.16.0

Choose a tag to compare

@github-actions github-actions released this 15 Jan 17:44
34b604f

What's Changed

🚨 Breaking Changes 🚨

🎉 Feature Enhancements 🎉

🪲 Bug Fixes 🪲

  • 1165 redshift error failed to find conversion function from unknown to character varying by @chase-jones in #1166
  • Pull through patient ID on core__medication by @krishyfishy in #1182

Other Changes

Critical Breaking Changes Summary

Required Actions:

  1. Add fields to EXISTING tables (required if claims_enabled: true):

    • eligibility: Add hospice_flag, institutional_snp_flag, long_term_institutional_flag, enrollment_status
  2. Upgrade dbt to 1.10.0

Full Changelog: v0.15.5...v0.16.0

the_tuva_project v0.15.5

Choose a tag to compare

@github-actions github-actions released this 04 Dec 22:41
4d0d12b

What's Changed

🎉 Exciting New Features 🎉

🪲 Bug Fixes 🪲

Other Changes

Full Changelog: v0.15.4...v0.15.5