H.R. 1 Impact on Coding

H.R. 1 doesn’t directly rewrite ICD-10 or CPT, but it does change the environment in which you’re coding. The impact is mostly indirect – through eligibility, documentation, the social determinants of health (SDoH), and audit pressure – plus some likely downstream ICD-10 tweaks.

So there is no immediate code-set overhaul, but watch for SDoH/employment updates.

There’s nothing in H.R. 1 or the One Big Beautiful Bill Act (OBBBA) that explicitly amends ICD-10-CM/PCS or CPT codes. It changes coverage and eligibility, not the base code sets. In addition:

• Policy shops are already flagging that ICD-10 Coordination & Maintenance Committee meetings this fall included topics tied to H.R. 1 implementation and social/coverage impacts, i.e., SDoH coding discussions, in the same policy context as the new work requirements.
• Given the bill’s focus on work status and administrative churn, it’s very plausible you’ll see:
  • Clarified guidance or expanded use cases for Z56.x (Problems related to employment and unemployment); and
  • More emphasis on Z59.x (housing/food insecurity) as states try to track how H.R. 1 changes affect patients.

H.R. 1 and the companion Supplemental Nutrition Assistance Program (SNAP) changes require many adults 19-64 to document 80+ hours/month of work, training, or other “community engagement” to keep Medicaid and SNAP benefits.

That creates coding-adjacent pressure in a few ways:

• Clinicians will be asked to document limitations to work (functional status, chronic conditions, side effects of treatment, etc.) when patients seek exemptions from work requirements.
• Coders and clinical documentation integrity (CDI) staff can support that by:
  • Using appropriate diagnosis codes that reflect limitations and comorbidities (e.g., mental health disorders, mobility issues, cancer treatment), which may indirectly support exemption determinations or appeals; and
  • Capturing SDoH Z-codes when available to show context – unemployment, unstable housing, food insecurity, etc. – which increasingly is being used in Medicaid analytics and waiver evaluations.

States and Managed Care Organizations (MCOs) will use these data to show how work requirements affect specific populations; if it isn’t properly coded, those analyses will miss reality.

Payor mix and account classification: coding hasn’t changed, but where claims land will.

The Congressional Budget Office (CBO) and multiple analysts project millions losing Medicaid coverage because of H.R. 1’s work requirements and red tape.

Operationally, that means for coding/billing:

• You’ll see more mid-episode coverage loss:
• A patient starts a course of treatment on Medicaid, then loses eligibility at redetermination because they didn’t report hours on time.
• Coders still code the encounter the same way; but now, billing is chasing charity care, self-pay, or bad debt instead of Medicaid.
• Front-end workflow will need tighter insurance/eligibility verification at every encounter, because errors will blow back into:
  • Re-billing;
  • Retroactive classification of balances (contractual vs bad debt versus charity); and
  • Medicare bad debt and uncompensated care reporting strategies.

From a pure coding rules perspective, nothing changed; from a revenue cycle perspective, the stakes regarding correct coding and timely edits just went up.

Expect:

• More post-payment review focused on:
  • Medical necessity;
  • Upcoding patterns; and
  • Alignment between diagnosis codes, service intensity, and eligibility status.
  • Closer linkage between eligibility systems and claims data, with mismatches flagged for review (e.g., services billed after a reported loss of eligibility, or codes inconsistent with claimed disability status).

So, coders and CDI teams will want to:

• Double down on clinical validity and internal consistency (diagnosis, procedures, length of stay/LOS, modifiers); and
• Prepare for state or MCO audits that cite H.R. 1’s program-integrity mandates as the reason for stepped-up reviews.

Also, remember there are many state-specific quirks via waivers and policy choices.

Because H.R. 1 gives states a lot of leeway in implementation, you may see state-driven coding nuances, even if the national code sets don’t change:

• Some states already use state-specific billing codes, revenue codes, or modifiers tied to special programs (e.g., employment/education supports, community health worker visits).
• As states stand up H.R. 1-related initiatives under 1115 waivers, like workforce support programs or “community engagement” services, they may:
  • Require certain HCPCS or revenue codes to track those encounters; and
  • Build reporting templates that depend heavily on diagnosis and SDoH coding to identify the target population.

If you’re coding for multiple states, you’re likely to see diverging billing manuals and companion guides as they try to operationalize their H.R. 1 strategy.