Reworking HR1 Medicaid Rules#7752
Conversation
…ome supporting variables for medically frail
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #7752 +/- ##
============================================
- Coverage 100.00% 70.67% -29.33%
============================================
Files 2 3918 +3916
Lines 13 56491 +56478
Branches 0 270 +270
============================================
+ Hits 13 39925 +39912
- Misses 0 16565 +16565
- Partials 0 1 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Adding logic to pass work requirements based on community engagement. For now, these are simple variables, but may later be changed into computed variables.
The law involves checking for conditions in a month, but this might be too granular to do in the policy engine. Tests currently failing for this reason.
daphnehanse11
left a comment
There was a problem hiding this comment.
Blocking: several work-requirement formulas use Python or with PolicyEngine arrays instead of vectorized bitwise operators. For example, medicaid_work_requirement_eligible returns has_exemption or has_ce, has_medicaid_work_requirement_ce returns enrolled_half_time or passed_hours or passed_income, and has_medicaid_work_requirement_exemption chains the exemption flags with or. This raises ValueError: The truth value of an array with more than one element is ambiguous in multi-person simulations. Repro on this branch with two people in 2027-03: has_medicaid_work_requirement_ce, medicaid_work_requirement_eligible, and yearly is_medicaid_eligible all raise that error. Please replace these with parenthesized vectorized expressions using |.
See #7751 for details, but this is a plan to revise some of the code for HR1 Medicaid work requirements to better match what CMS is providing as its provisional rules