updated to work w/ 0.16.0 release of tuva package

[aneiderhiser]

Updates to eligibility demo data to work with 0.16 release.

Summary by CodeRabbit

Release Notes

• New Features

  • HEDIS measures functionality enabled
  • Added enrollment status field to eligibility data

• Changes

  • Provider attribution feature disabled
  • Updated eligibility data schema version
  • Updated package dependencies to support latest features

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Configuration updates to the dbt project, including disabled provider attribution and enabled HEDIS measures tracking. Package dependencies updated to support the_tuva_project version 0.17. A new enrollment_status field added to the eligibility seed schema with conditional type definitions based on target database.

Changes

Cohort / File(s)	Summary
Configuration Updates dbt_project.yml	Disabled provider_attribution_enabled flag, added hedis_measures_enabled: true, and updated eligibility post-hook version from 0.15.0 to 0.16.0
Package Dependencies packages.yml	Updated tuva-health/the_tuva_project version constraint from 0.16.0 to 0.17.0; normalized whitespace in dbt-labs/dbt_utils version constraint
Schema Additions seeds/_seeds.yml	Added enrollment_status field to eligibility seed with conditional column typing (string for BigQuery/Databricks, varchar(255) otherwise)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A cottontail's delight in cleaner code,
New seeds of enrollment_status sowed,
HEDIS measures bloom, attribution fades,
Tuva's version advances down garden's glades! 🌱✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is minimal and lacks required sections from the template such as testing details, reviewer focus, and the pre-review checklist.	Add details on how changes were tested, specific items for reviewers to focus on, and complete the pre-review checklist including Github labels.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating configurations and dependencies to work with the 0.16.0 release of the tuva package, which aligns with the file modifications shown.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 52ed1bb and 8a6fc50.

⛔ Files ignored due to path filters (1)

• seeds/eligibility.csv is excluded by !**/*.csv

📒 Files selected for processing (3)

• dbt_project.yml
• packages.yml
• seeds/_seeds.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: bigquery

🔇 Additional comments (5)

dbt_project.yml (2)

11-14: LGTM on feature flag changes.

The configuration changes correctly enable HEDIS measures and disable provider attribution, which aligns with the 0.16.0 update.

---

38-52: Verify intentional version mismatch between seed data sources.

Only eligibility.csv is updated to version 0.16.0 while all other seeds (appointment, immunization, lab_result, medical_claim, observation, pharmacy_claim, provider_attribution) remain at 0.15.0. Please confirm this is intentional and that 0.15.0 data for other seeds is compatible with the 0.16.0 schema.

seeds/_seeds.yml (1)

113-114: LGTM!

The new enrollment_status field follows the established conditional typing pattern used throughout this file and aligns with the eligibility seed data update to version 0.16.0.

packages.yml (2)

5-5: Formatting normalization only - no functional change.

---

3-3: Version constraint update is forward-looking but current justification is inaccurate.

The updated constraint [">=0.15.0","<0.17.0"] is compatible with the latest available version (0.15.5) and allows for future 0.16.x releases when they become available. However, 0.16.x versions do not yet exist—the constraint is speculative rather than required for this update.

Likely an incorrect or invalid review comment.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}