Skip to content

Cover New Jersey children under 19 in Medicaid and CHIP regardless of immigration status (Cover All Kids) - #10987

Merged
hua7450 merged 7 commits into
mainfrom
nj-cover-all-kids
Nov 17, 2026
Merged

hua7450 merged 7 commits into
mainfrom
nj-cover-all-kids

Conversation

@hua7450

@hua7450 hua7450 commented Nov 15, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

From January 1, 2023, New Jersey enrolls children under 19 in NJ FamilyCare whatever their immigration status ("Cover All Kids"). The model gave these children only emergency Medicaid: New Jersey reads false in undocumented_immigrant.yaml, and its lawfully residing election covers only lawful statuses. Undocumented and DACA children under 19 failed both the Medicaid and the CHIP immigration tests.

This PR adds a per-state age limit for coverage regardless of immigration status: 19 for New Jersey from 2023-01-01, 0 for every other state. Children under the limit pass both immigration tests. They then reach the existing child categories, with no change to income tests or values:

  • Medicaid, up to 147% of the poverty guideline for ages 6-18 (medicaid_group CHILD and medicaid_cost);
  • separate CHIP, up to 355% (per_capita_chip, $2,853.59 for New Jersey in 2024).

Partly addresses #3654 (New Jersey). The other states with age-limited coverage regardless of status become one-row edits to the new parameter. This PR comes before the adult-group child-coverage gate (#10776), so parents of undocumented New Jersey children don't wrongly fail that gate.

Legal basis

Rule Text Model
Children whatever their status Each appropriations act from FY2023 through FY2027, in the Division of Medical Assistance and Health Services language: "Notwithstanding the provisions of any law or regulation to the contrary, … Payments by the Division of Medical Assistance and Health Services are authorized to be made to Managed Care Organizations and medical care providers to enroll in NJ FamilyCare any child who, except for immigration status, meets financial and other eligibility provisions of the program." regardless_of_immigration_status/child_age_limit.yaml, NJ 19
Under 19 N.J.S.A. 30:4J-11: "a child under 19 years of age" The limit is 19, compared with <
Start date DHS response to the Office of Legislative Services, FY2023: "Beginning January 1, 2023, children that are income-eligible but were previously ineligible because of their immigration status will become eligible for NJ FamilyCare. Children will enroll in the same coverage, with the same Managed Care Organization options as all other enrolled children." NJ 0 before 2023-01-01, then 19
Same income rules as other children The acts' "meets financial and other eligibility provisions of the program" Existing Medicaid child categories and NJ separate CHIP limit

Sources:

The FY2023 and FY2024 acts name the "General Medicaid Services program classification"; FY2025-FY2027 name "General Medical Services". The provision is otherwise the same each year, and no cited page carries line-item veto brackets. P.L.2021, c.132, which the DHS Cover All Kids FAQ cites as the law, holds the 2021 first phase (premiums, waiting period, outreach) and has no immigration language.

Source conflict

N.J.S.A. 30:4J-11(a)(4) still limits a qualified child applicant to a citizen or lawful permanent resident:

  • N.J.A.C. 10:78-3.2(a) requires "a citizen of the United States, an alien lawfully admitted for permanent residence, or an alien who can be classified as an eligible alien";
  • for the NJ FamilyCare-Children's Program, N.J.A.C. 10:79-3.2(a) says "an individual must be a citizen of the United States, or an eligible alien in accordance with this chapter". Both are published through 57 N.J.R., June 16, 2025.

The later appropriations acts displace those texts "notwithstanding the provisions of any law or regulation to the contrary". The project lead ruled on 2026-11-15 to follow the acts and to register the conflict: #10987 (comment).

This PR records it as us-nj:medicaid-cover-all-kids-immigration-status in source_conflicts/candidates.yaml (pe_us.follows: statute, state: ruled, with a ruling block that links the comment above). Following CONTRIBUTING.md (Source conflicts, step 1), it adds no # Source conflict marker; the deciding line carries a # Candidate: comment. After merge, the rulespec-us register entry pins this PR's merge commit, and a follow-up PR adds the marker to child_age_limit.yaml and refreshes the pin.

Changes

  • parameters/gov/hhs/medicaid/eligibility/regardless_of_immigration_status/child_age_limit.yaml (new):
  • variables/gov/hhs/medicaid/eligibility/is_medicaid_immigration_status_eligible.py: adds age < child_age_limit[state] to the OR of routes.
  • variables/gov/hhs/chip/is_chip_immigration_status_eligible.py: the same term.
  • source_conflicts/candidates.yaml: the candidate above.
  • changelog.d/nj-cover-all-kids.added.md.

The term doesn't check the child's status, so any New Jersey child under 19 passes. In practice only UNDOCUMENTED and DACA children change: New Jersey's lawfully residing election (lawfully_residing/child.yaml, age limit 21) already passes LPRs in the five-year bar, refugees, asylees, parolees, TPS holders and the statuses section 71109 drops from October 2026.

Other readers of the two immigration tests:

  • Emergency Medicaid (is_emergency_medicaid_eligible) reads the negation of the Medicaid test. Covered New Jersey children move from emergency Medicaid to full Medicaid.
  • ACA below-FPL exception (aca_ptc_below_fpl_immigration_exception): the only possible change is for New Jersey DACA children in model year 2025, the one year the model's ACA status list treats DACA as lawfully present.
  • Other routes for children: is_optional_senior_or_disabled_for_medicaid and is_chip_eligible_standard_pregnant_person also read the tests. A New Jersey child under 19 who qualifies through them is covered by the same acts.
  • State programs: the CA CCHIP, MS, RI, OR and IL readers are gated to their own states. The Basic Health Program reader is active only in MN, NY, OR and DC.

Not changed

  • Federal share. medicaid_federal_share and chip_federal_share still apply federal matching rates to these state-funded children: 0.50 for Medicaid and 0.65 for CHIP in New Jersey. The Office of Legislative Services' FY2023 analysis says "No federal Medicaid and CHIP cost reimbursements are available for this new eligibility group" (https://pub.njleg.gov/publications/budget/governors-budget/2023/DHS_analysis_2023.pdf#page=40). The same error already applies to state-funded coverage in CA, DC, MA, NY and OR. Medicaid and CHIP federal share counts state-funded coverage as federally matched #10986 tracks the cross-state fix.
  • Pregnancy past 19. The DHS Cover All Kids FAQ (https://nj.gov/coverallkids/faqs/) says: "If your child turns 19 during their pregnancy, their coverage will continue for a year after the end of their pregnancy." The annual age < 19 test drops that person; a comment at New Jersey's parameter row records it.
  • Lapse. Appropriations language lapses each fiscal year. The acts were checked through FY2027, which ends June 30, 2027; the parameter carries the age limit forward.

Tests

New YAML cases, appended to the variable-named files. Wages are full-time (2,080 hours) at New Jersey's minimum wage: $13.00 an hour in 2022, $15.13 in 2024. Poverty guidelines (48 states): $23,030 for three in 2022; $25,820 for three and $31,200 for four in 2024.

File Case Expected Arithmetic
is_medicaid_immigration_status_eligible.yaml Case 19, undocumented 8-year-old, NJ, 2024 true 8 < 19
is_medicaid_immigration_status_eligible.yaml Case 20, undocumented 19-year-old, NJ, 2024 false 19 is not under 19; pins <
is_medicaid_immigration_status_eligible.yaml Case 21, DACA 17-year-old, NJ, 2024 true 17 < 19
is_medicaid_immigration_status_eligible.yaml Case 22, undocumented 8-year-old, NJ, 2023 true 8 < 19; pins the 2023-01-01 start with Case 42 (2022)
is_chip_immigration_status_eligible.yaml Case 17, undocumented 8-year-old, NJ, 2024 true 8 < 19
is_chip_immigration_status_eligible.yaml Case 18, undocumented pregnant 19-year-old, NJ, 2024 false 19 is not under 19; pins < for the CHIP pregnancy path, which has no age cap of its own
is_medicaid_eligible.yaml Case 41, undocumented parent with an undocumented 8-year-old and a citizen 6-year-old, 2024 is_medicaid_eligible [false, true, true]; is_older_child_for_medicaid [false, true, true]; no CHIP $31,470.40 ÷ $25,820 = 121.9% ≤ 147%
is_medicaid_eligible.yaml Case 42, same family in 2022 is_medicaid_eligible [false, false, true]; no CHIP $27,040 ÷ $23,030 = 117.4%; 2022 is before the start date
is_chip_eligible_child.yaml Case 38, two undocumented parents with an undocumented 12-year-old and a citizen 7-year-old, 2024 is_chip_eligible_child [false, false, true, true]; chip_category [NONE, NONE, CHILD, CHILD]; chip [0, 0, 2,853.59, 2,853.59] $62,940.80 ÷ $31,200 = 201.7%, between 147% and 355%; $579,649,320 ÷ 203,130 = $2,853.59

No existing expectation changes. No other baseline or partner contract test has a New Jersey case with an undocumented or DACA person whose Medicaid or CHIP result this changes. The one other NJ undocumented-child case, in nj_ccap_eligible_child.yaml, reads the CCDF immigration test.

Review fixes

From DTrim99's review at 781d33da10:

axiom: TheAxiomFoundation/rulespec-us#2263 queued

🤖 Generated with Claude Code

hua7450 and others added 3 commits November 15, 2026 14:00
New Jersey's appropriations acts from FY2023 authorize enrolling in NJ
FamilyCare any child who, except for immigration status, meets the
program's other rules. DHS began enrollment on January 1, 2023. A new
per-state age limit, regardless_of_immigration_status/child_age_limit
(19 for New Jersey from 2023, 0 elsewhere), passes children under it on
the Medicaid and CHIP immigration tests, so undocumented and DACA
children reach the existing child categories and separate CHIP.

Records the conflict between the appropriations acts and N.J.S.A.
30:4J-11 / N.J.A.C. 10:78-3.2(a) as a source-conflict candidate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
N.J.A.C. 10:79 governs the NJ FamilyCare-Children's Program (Medicaid and
CHIP children), and 10:79-3.2(a) still requires citizenship or eligible
alien status. Add it to the parameter's references and to the
us-nj:medicaid-cover-all-kids-immigration-status candidate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keeps main's Indiana CHIP cases 23-37 in is_chip_eligible_child.yaml and renumbers the New Jersey Cover All Kids case to 38.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@DTrim99

DTrim99 commented Nov 16, 2026

Copy link
Copy Markdown
Collaborator

PR Review: Cover New Jersey children under 19 in Medicaid and CHIP regardless of immigration status (Cover All Kids)

Summary

The policy change is right, and so is the way it is built. I read the governing texts myself before reading the code:

  • Each New Jersey appropriations act from FY2023 through FY2027 carries the Division of Medical Assistance and Health Services condition. I read each cited page and they match word for word.
  • N.J.S.A. 30:4J-11 sets the "child under 19 years of age" limit.
  • The DHS FY2023 discussion-point response gives the January 1, 2023 start date.
  • The Office of Legislative Services FY2023 analysis says the coverage is state-funded.

All four support a per-state age limit of 19 for New Jersey from 2023-01-01. The new term only relaxes the immigration gate. Undocumented and DACA children still have to pass New Jersey's existing income tests:

  • Medicaid child categories, up to 147% FPL for ages 6-18;
  • separate CHIP, up to 355%.

So the model does not give Medicaid to children above New Jersey's limits. Medicaid and CHIP are not double-counted, because is_chip_eligible_child requires ~is_medicaid_eligible. Every other state reads 0, so no other state's result changes. All 38 checks pass at head 781d33da10.

Two process items remain before merge:

  • The new source-conflict candidate says state: ruled but carries no dated, linked project-lead ruling.
  • The queued rulespec-us issue still points at a pre-merge head and a test case number that the merge with main renumbered.

Critical (must fix)

None.

Should address

  1. The ruled candidate has no linked, dated ruling record (source_conflicts/candidates.yaml:8817, entry us-nj:medicaid-cover-all-kids-immigration-status).

    • What the entry says. It sets state: ruled. Its note says only "the November 2026 ruling records the conflict anyway". The PR body says "The project lead ruled on 2026-11-15". Neither the entry, the PR thread, Include state medicaid eligibility for undocumented immigrants which applies only to certain age groups  #3654 nor Medicaid and CHIP federal share counts state-funded coverage as federally matched #10986 links that ruling.
    • What the other ruled entries do. They carry a ruling: block (by, date, record), or a note in the form "Ruled 2026-11-12 by the project lead; the ruling record is https://github.com/PolicyEngine/policyengine-us/pull/10762#issuecomment-…". Examples are us-ca CAPI and us-de LIHEAP.
    • Why neither default rule covers this. CONTRIBUTING.md#source-conflicts gives two automatic rules: "Statute first" (statute over a form, instructions, a manual or agency practice) and the regulation-over-manual reading. This conflict is a statute against an earlier statute (30:4J-11(a)(4)) and two regulations (N.J.A.C. 10:78-3.2(a), 10:79-3.2(a)). Under "Regulations are law", a regulation that conflicts with a statute "goes to the project lead, who decides it case by case, and the ruling is recorded in the register." That makes the ruling record load-bearing.
    • Fix. Post or locate the 2026-11-15 ruling. Then add:
      ruling:
        by: PolicyEngine
        date: '2026-11-15'
        record: <comment URL>
      Also change the note to "Ruled 2026-11-15 by the project lead; the ruling record is ." If no linkable ruling exists, set state: open until one is recorded.
  2. The axiom issue doesn't match the current head (Encode New Jersey Cover All Kids: NJ FamilyCare for children under 19 regardless of immigration status from January 1, 2023 (P.L.2022, c.49 and later appropriations acts; N.J.S.A. 30:4J-11) (PE-US PR 10987) TheAxiomFoundation/rulespec-us#2263).

    • What still checks out. The issue is OPEN, labelled pe-parity and dispatch-ready. It has module paths, corpus citations, verbatim law, required outputs and companion tests, and it records the blocker: the corpus has no NJ appropriations acts and no N.J.S.A. Title 30.
    • What is stale. The issue cites head 52f91c008f. Its companion-test row 6 cites "is_chip_eligible_child.yaml Case 23". The later merge of main (781d33da10) brought in Indiana CHIP cases 23-37, and the New Jersey case is now Case 38. At the current head, "Case 23" is "Indiana child at 256 percent FPL exceeds the 2017 CHIP income limit".
    • Fix. Edit the issue to cite head 781d33da10 and Case 38. The other five companion rows (Medicaid immigration-test Cases 19-21, CHIP immigration-test Case 17, is_medicaid_eligible Cases 41-42) still match.

Suggestions

  1. Pin the start date with a 2023 case. Deleting the 2023-01-01: 19 row fails Case 19, so the row is pinned. The date itself is only bounded to (2022-01-01, 2024-01-01]: moving it to 2024-01-01 passes every test. Repeating Case 19 with period: 2023 would pin it exactly.
  2. Pin the < on the CHIP side (is_chip_immigration_status_eligible.py:64). Medicaid Case 20 pins age < 19, but no CHIP case sits at 19. is_chip_eligible_child has its own age cap, so the child path is safe. is_chip_eligible_standard_pregnant_person reads the CHIP immigration test with no age cap, though, and New Jersey's CHIP pregnant limit is 205%. Under a <= mutation, an undocumented pregnant 19-year-old in New Jersey at about 200% FPL would get CHIP, and no test would fail. Add a CHIP immigration case at age 19 expecting false.
  3. Federal share (documented deferral).
  4. Pregnancy past 19. The DHS Cover All Kids FAQ says: "If your child turns 19 during their pregnancy, their coverage will continue for a year after the end of their pregnancy." The annual age < 19 test drops that person. This is a narrow case. A one-line comment at the New Jersey row, or a follow-up note on Include state medicaid eligibility for undocumented immigrants which applies only to certain age groups  #3654, would record it.

Verified correct

  • The law.
    • The appropriations acts. The cited page of each act carries the same condition: P.L.2022, c.49, p.106; P.L.2023, c.74, p.120; P.L.2024, c.22, p.142; P.L.2025, c.74, p.144; P.L.2026, c.27, p.134. It reads: "Notwithstanding the provisions of any law or regulation to the contrary … Payments by the Division of Medical Assistance and Health Services are authorized to be made to Managed Care Organizations and medical care providers to enroll in NJ FamilyCare any child who, except for immigration status, meets financial and other eligibility provisions of the program." The FY2023 and FY2024 acts say "General Medicaid Services" and FY2025-FY2027 say "General Medical Services", as the PR says. I found no change to age or income in any later act.
    • N.J.S.A. 30:4J-11 (Family Health Care Coverage Act, N.J.S.A. 30:4J-8 et seq.). The 2008 text reads "'Qualified applicant' means: a. a child under 19 years of age: (1) whose family gross income does not exceed 350% of the poverty level; … (4) who is a citizen of the United States, or has been lawfully admitted for permanent residence…". The codified text current as of January 1, 2024 is identical.
    • P.L.2021, c.132 (S3798, approved June 29, 2021) is the 2021 Cover All Kids law that the DHS FAQ cites. It amends 30:4J-12, -18 and -19 (premiums, waiting period, outreach) and has no immigration language. The immigration expansion rests only on the appropriations language, as the PR says. No separate Cover All Kids immigration statute exists. P.L.2021, c.71 is the Design-Build Construction Services Procurement Act and is unrelated.
    • Start date. DHS FY2023 response, pp. 12-13: "Beginning January 1, 2023, children that are income-eligible but were previously ineligible because of their immigration status will become eligible for NJ FamilyCare. Children will enroll in the same coverage, with the same Managed Care Organization options as all other enrolled children." The FAQ says "Children under 19 years old can qualify" and applicants "do have to meet the income guidelines."
    • State funding. OLS FY2023 DHS analysis, p. 40, quoted above.
    • The regulations. N.J.A.C. 10:78-3.2(a) (PDF p.33) and 10:79-3.2(a) (PDF p.30) say what the candidate quotes, in the edition published through 57 N.J.R., June 16, 2025.
  • Code.
    • The term age < child_age_limit[state] is added by OR in both immigration tests. It is vectorized, uses a Person/YEAR entity and period, and reads the state through state_code_str, the same lookup as undocumented_immigrant[state].
    • The parameter lists the same 51 jurisdictions as undocumented_immigrant.yaml. No state-gated int or enum key is added, so the NH Add New Hampshire state supplementation for 2026 #10156 pattern doesn't arise.
    • Every other state reads 0, and age < 0 is always false, so other states are unchanged.
    • The design follows the existing patterns: all-ages coverage stays in the undocumented_immigrant boolean (DC, MA, NY, OR from 2023-07-01), and CA, IL and WA keep their own program variables.
  • Income tests still apply. is_medicaid_eligible requires a non-NONE medicaid_category, which is income-tested, alongside the immigration test. is_chip_eligible_child requires the NJ CHIP limit (3.55) and ~is_medicaid_eligible, so there is no double-counting.
  • Other readers.
    • Emergency Medicaid reads the negated Medicaid test, so covered children move from emergency to full Medicaid.
    • The ACA below-FPL exception changes only for DACA children in 2025, as the PR says.
    • The CA, IL, MS, OR and RI readers and the BHP reader are gated to their own states.
    • Work requirements apply to ages 19-64 only.
  • Hand-checked expectations.
    1. Medicaid Case 19: undocumented 8-year-old, NJ, 2024. The federal test fails (not a qualified status), NJ undocumented_immigrant is false and the CA route is false. 8 < 19, so true.
    2. Medicaid Case 20: 19 < 19 is false, so false. This pins <.
    3. Medicaid Case 21: DACA is neither in eligible_immigration_statuses nor in the lawfully residing list (SHO Policy parameter for % of net income SNAP eligibility threshold  #12-002), so only the new term applies. 17 < 19, so true.
    4. CHIP Case 17: undocumented, not a lawfully residing status. 8 < 19, so true.
    5. Case 41, income:
      • $15.13 × 2,080 = $31,470.40;
      • 2024 FPG for three = $15,060 + 2 × $5,380 = $25,820;
      • $31,470.40 ÷ $25,820 = 1.219, at or below the NJ older-child limit of 1.47.
        So both children are Medicaid-eligible. The parent is at or below the 1.38 adult limit but fails the immigration test, so false. CHIP is false for everyone because the children are Medicaid-eligible.
    6. Case 42:
      • $13.00 × 2,080 = $27,040;
      • 2022 FPG for three = $13,590 + 2 × $4,720 = $23,030;
      • ratio = 1.174, at or below 1.47.
        The citizen child is true. For the undocumented child the NJ limit is 0 in 2022 and 8 < 0 is false, so Medicaid and CHIP are both false. is_older_child_for_medicaid is true for both children, because the category test ignores status.
    7. Case 38:
      • 2 × $31,470.40 = $62,940.80;
      • 2024 FPG for four = $15,060 + 3 × $5,380 = $31,200;
      • ratio = 2.017, above 1.47 and 1.38, so no Medicaid for anyone;
      • 2.017 is at or below 3.55 and both children are under 19, so chip_category is CHILD for both.
        The outcomes are the same with 2023 guidelines (209.8%).
    8. Case 38, CHIP value: $579,649,320 ÷ 203,130 = $2,853.588, so $2,853.59 within the 0.01 margin.
    9. medicaid_household_size is [3, 3, 3] and [4, 4, 4, 4], because a single tax unit covers every member.
  • Mutation. Deleting the Medicaid term fails Cases 19 and 21. Deleting the CHIP term fails Cases 17 and 38. Deleting the NJ 2023 row fails Case 19.
  • Housekeeping.
    • Tests are appended to variable-named files and use plain periods.
    • The changelog fragment changelog.d/nj-cover-all-kids.added.md is present.
    • No partner-test files are touched.
    • The parameter description follows the template.
    • The multi-page DHS reference uses the quoted #page 12-13 title form, as CLAUDE.md requires.
    • The candidate has the required id, program, question, years, two or more sources, readings, pe_us and state fields. It adds no marker, and the NJ row carries a # Candidate: comment, as step 1 requires.

Axiom line assessment

The PR body reads axiom: TheAxiomFoundation/rulespec-us#2263 queued.

  • Valid: the issue is OPEN and labelled pe-parity.
  • Dispatch-ready: it gives target module paths, corpus citations, verbatim law with pages, required outputs and companion tests that use external hand derivations, not PolicyEngine output. It records the blocker: corpus ingest of the NJ acts and N.J.S.A. 30:4J-11.
  • Mismatch: it cites head 52f91c008f and CHIP "Case 23", which is now Case 38 (Should 2). It was last updated 2026-11-15 19:07 UTC, before the merge commit.

CI status

All 38 checks pass on head 781d33da10 (run 43796475213, created 2026-11-16 03:09 UTC). None are pending. That run covered the source-conflict guard, with the new candidate and the new parameter file's comments.

Branch status

Verdict: REQUEST_CHANGES

@DTrim99 DTrim99 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Requesting changes: 0 critical, 2 should address (the ruled candidate us-nj:medicaid-cover-all-kids-immigration-status needs a linked, dated ruling record or state: open; rulespec-us#2263 cites an old head and CHIP Case 23, now Case 38), 4 suggestions. Full report in the comment above. The policy (NJ children under 19 from 2023-01-01, income tests unchanged) checks out.

@hua7450

hua7450 commented Nov 16, 2026

Copy link
Copy Markdown
Collaborator Author

Source-conflict ruling (project lead, 2026-11-15): us-nj:medicaid-cover-all-kids-immigration-status

New Jersey children under 19 are covered by Medicaid and CHIP regardless of immigration status from 2023-01-01. This follows the FY2023 through FY2027 appropriations acts, which authorize enrolling "any child who, except for immigration status, meets financial and other eligibility provisions of the program", notwithstanding any law or regulation to the contrary. It takes precedence over N.J.S.A. 30:4J-11 and N.J.A.C. 10:78-3.2(a) and 10:79-3.2(a), which limit NJ FamilyCare to citizens and eligible noncitizens.

hua7450 and others added 2 commits November 16, 2026 15:11
- Record the project lead's 2026-11-15 ruling on the
  us-nj:medicaid-cover-all-kids-immigration-status candidate: a ruling
  block (by, date, record) and a note that links the ruling comment on
  PR 10987.
- Pin the January 1, 2023 start with Case 22 of
  is_medicaid_immigration_status_eligible.yaml (the Case 19 child in 2023).
- Pin the under-19 limit on the CHIP side with Case 18 of
  is_chip_immigration_status_eligible.yaml: an undocumented pregnant
  19-year-old, whose CHIP pregnancy path has no age cap of its own.
- Note at New Jersey's parameter row that the DHS Cover All Kids FAQ
  keeps a child who turns 19 while pregnant covered until a year after
  the pregnancy, which the annual age test does not model.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@hua7450
hua7450 requested a review from DTrim99 November 16, 2026 20:13
@DTrim99

DTrim99 commented Nov 17, 2026

Copy link
Copy Markdown
Collaborator

PR Review (round 2): Cover New Jersey children under 19 in Medicaid and CHIP regardless of immigration status (Cover All Kids)

Summary

Both should-address items from round 1 (at 781d33da10) are fixed at head a830e1f4df, and three of the four suggestions were taken.

Prior findings

Finding Status Evidence
Should 1: state: ruled candidate with no linked, dated ruling record Fixed candidates.yaml now has ruling: {by: PolicyEngine, date: '2026-11-15', record: …/pull/10987#issuecomment-6927857659}. The note opens "Ruled 2026-11-15 by the project lead; the ruling record is …". The comment was posted 2026-11-16 20:09 UTC by the author's account (MEMBER) and has not been edited. Its heading is "Source-conflict ruling (project lead, 2026-11-15): us-nj:medicaid-cover-all-kids-immigration-status". It decides the candidate's exact question: NJ children under 19, Medicaid and CHIP, from 2023-01-01, following the FY2023-FY2027 acts over N.J.S.A. 30:4J-11 and N.J.A.C. 10:78-3.2(a) and 10:79-3.2(a). The four precedents (10762#issuecomment-6837369871, 10746#…-6863978318, 10748#…-6863978810, 10760#…-6863979262) were also posted from the author's account, each headed "Ruling by the project lead, : <id>". The block's fields match the one ruling: block on main (us-ca:ssp-blind-couple-food-allowance). A process item, so the mutation rule doesn't apply.
Should 2: rulespec-us#2263 cited head 52f91c008f and CHIP "Case 23" Fixed The issue is OPEN, labelled pe-parity, and was updated 2026-11-16 20:13:52 UTC, after the head commit. It cites a830e1f4df. Companion row 6 is is_chip_eligible_child.yaml Case 38, which at head is "New Jersey undocumented child and citizen child both receive CHIP in 2024". Rows 1 and 2 add the new Case 22 and CHIP Case 18. Main has not changed any of the four test files since the merge base (29f81ccc36), so the case numbers match in the merged tree too.
Suggestion 1: pin the 2023-01-01 start Taken Case 22 of is_medicaid_immigration_status_eligible.yaml is the Case 19 child in 2023. It fails if the row moves past 2023-01-01, and Case 42 (2022) still fails if the row is deleted. Moving the row to any date in (2022-01-01, 2023-01-01] would pass every test. That cannot be told apart: the variable is yearly, so the parameter is read at January 1.
Suggestion 2: pin < on the CHIP side Taken Case 18 of is_chip_immigration_status_eligible.yaml is an undocumented pregnant 19-year-old in NJ in 2024, expected false. A <= mutation at is_chip_immigration_status_eligible.py gives 19 <= 19, true, and fails the case.
Suggestion 3: federal share for state-funded children Not taken (documented deferral) The PR body's "Not changed" section keeps it and cites #10986 (OPEN, "Medicaid and CHIP federal share counts state-funded coverage as federally matched"). The deferral is reasoned and the same gap already exists for CA, DC, MA, NY and OR, so it stays a suggestion.
Suggestion 4: pregnancy past 19 Taken The NJ row of child_age_limit.yaml now reads "Not modeled: the DHS FAQ (https://nj.gov/coverallkids/faqs/) covers a child who turns 19 while pregnant until a year after the pregnancy." This matches the FAQ text quoted in round 1. The comment does not match the source-conflict ratchet's conflict-comment pattern.

New findings

Critical

None.

Should address

None.

Suggestions

  1. Federal share (carried over, deferred to Medicaid and CHIP federal share counts state-funded coverage as federally matched #10986). medicaid_federal_share still returns 0.50 and chip_federal_share 0.65 for these New Jersey children. The OLS FY2023 analysis (p. 40) says "No federal Medicaid and CHIP cost reimbursements are available for this new eligibility group." The fix belongs in the cross-state follow-up.

Verified

  • Changes since round 1. One author commit (a830e1f4df) touches four files: the parameter comment, two test cases and the candidate's ruling and note. The merge 0362382b0d (main at 29f81ccc36) has an empty remerge diff, so there are no hand-resolved blocks to check. No formula or parameter value changed.
  • The candidate against CONTRIBUTING.md#source-conflicts step 1.
    • It has id, program: medicaid and a question.
    • years is from: 2023, type: calendar.
    • It has five sources with valid kinds (statute, statute, regulation, regulation, guidance), all https.
    • It has readings, and pe_us with follows: statute, the tracked child_age_limit.yaml path and the PR URL.
    • state is ruled.
    • It adds no marker, and the NJ row keeps its # Candidate: comment.
    • The guard does not validate ruling keys. The block's shape matches the precedent on main.
    • The id is not in the vendored register: pin.yaml and known-source-conflicts.yaml are unchanged on main since the merge base.
  • Hand-checked new expectations.
    1. Medicaid Case 22 (undocumented, age 8, NJ, 2023).
      • The federal test fails, because UNDOCUMENTED is neither a qualified status nor lawfully residing.
      • NJ undocumented_immigrant is false from 2021, and the CA route is gated to CA.
      • The NJ limit read at 2023-01-01 is 19, and 8 < 19, so the result is true.
    2. CHIP Case 18 (undocumented, age 19, pregnant, NJ, 2024).
      • federally_eligible_status is false, and lawfully_residing is false, so the pregnancy option doesn't apply.
      • 19 < 19 is false, so the result is false. It pins < for the CHIP pregnancy path, which has no age cap of its own.
  • Unchanged expectations. Medicaid Cases 19-21, CHIP Case 17, is_medicaid_eligible Cases 41-42 and is_chip_eligible_child Case 38 are byte-identical to round 1. Their round-1 hand checks stand: Case 38 is 201.7% FPL and $2,853.59.
  • Readers after merging main. Limit SSI ineligible-child allocations to co-resident children and compute SSI and Medicaid deeming by month #10146 (merged 2026-11-17 07:00 UTC, after this head's CI ran) adds one reader, medicaid_optional_senior_or_disabled_unearned_income_deemed_from_ineligible_parent_monthly. It treats an SSI-disabled child who passes is_medicaid_immigration_status_eligible as an eligible child for parental deeming. Its comment says this covers "state-covered noncitizen children", so a New Jersey undocumented disabled child under 19 now has parental income deemed on the aged, blind and disabled path, as intended.
    • No test in the merged tree pairs an NJ undocumented or DACA person with that reader. The new deeming YAML's undocumented rows supply is_medicaid_immigration_status_eligible as an input, and its NJ rows are all citizens.
    • No Python test added on main since the merge base uses UNDOCUMENTED or DACA.
  • Main-side guards. The merged tree is clean.

Axiom

axiom: TheAxiomFoundation/rulespec-us#2263 queued is valid.

  • The issue is OPEN and labelled pe-parity.
  • It is dispatch-ready: proposed module paths, corpus citations and status, verbatim law with pages, required outputs, and six companion tests with hand derivations from external figures.
  • It names the blocker: the corpus has no NJ appropriations acts or N.J.S.A. 30:4J-11.
  • It now matches head a830e1f4df, including Case 38 and the new Case 22 and CHIP Case 18.

CI

All 37 checks pass on head a830e1f4df (run 43947493501, pull_request, created 2026-11-16 20:13 UTC). None are pending or failing. This run covered the guard tests with the new ruling block and parameter comment.

Branch

Verdict: APPROVE

@DTrim99 DTrim99 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Approving (round 2): both prior should-address items are fixed (ruling record linked in the candidate; rulespec-us#2263 matches this head), and 3 of 4 suggestions were taken. 1 optional suggestion remains. CI 37/37 green at a830e1f. Full report in the comment above.

# Conflicts:
#	source_conflicts/candidates.yaml
@hua7450
hua7450 merged commit 3364ed6 into main Nov 17, 2026
1 check passed
@hua7450
hua7450 deleted the nj-cover-all-kids branch November 17, 2026 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants