Skip to content

California supplement: no out-of-home care level with an ineligible spouse in the same household (POMS SI SF01415.120 B.4) #10660

Open

Description

@hua7450

What happens

in_out_of_home_care_facility pays the out-of-home care share to any eligible person, including one whose ineligible spouse lives in the same household.

What the rules say

POMS SI SF01415.120 B.4: an SSI claimant or recipient is not eligible for OSS B if they are "an individual whose ineligible spouse is living in the same household, regardless of the household/living arrangement situation. The ineligible spouse is presumed able and available to provide care and supervision as if the couple lived in their own household."

Example

January 2026, monthly. A person aged 70 with no income has in_out_of_home_care_facility: true. Their spouse is 50, not disabled, has no income, and shares their marital unit.

Version SSI Supplement
Expected under B.4 $994 $239.94
main at 25c4253483 $994 $1,393.25
PR #10601 at de245144dd $994 $632.07

The expected row is the result for the same household without the input. SSI doesn't read this input.

Scope and fix

  • PR Compute the California state supplement per person #10601 lists this under Known limitations. Its out-of-home care share is in _ca_state_supplement_rates.py, and CAPI reads the same rates.
  • in_out_of_home_care_facility is an input, so a caller can leave it false for this person. The model doesn't check for the spouse.
  • A possible fix is to drop the share when is_ssi_ineligible_spouse applies within the marital unit. This is untested.
  • Spouses who actually live apart shouldn't share a marital unit. This rule covers only those who live together.

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions