Part 2 program-level federal-assistance requirement

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Current rule checkpoint

The live explanation in 42 CFR 2.12(e)(2) makes federal assistance to the program a coverage requirement. A patient may benefit from federal support without the record being covered when the SUD diagnosis, treatment, or referral is not provided by a program that is itself federally assisted under section 2.12(b). eCFR displays the section as current through August 20, 2026 and last amended August 13, 2026. The HHS fact sheet confirms the February 16, 2026 compliance date for the 2024 amendments.

Start with the exact program

The coverage explanation separates patient benefit from program assistance. Map the legal entity, unit, personnel group, site, services, holding out, record system, and relevant period before examining operation, authorization, funding, or federal tax assistance.

Entity-wide evidence needs mapping

A parent grant, enterprise Medicare enrollment, affiliate contract, tax status, or government relationship may connect differently to each unit. Preserve recipient, holder, site, service, allowable use, organizational relationship, effective date, and source.

Status can vary over time

Reassess new awards, expiration, closeout, authorization, ownership, service-line changes, site moves, tax changes, government contracts, and restructuring. Keep historical program status linked to older records.

Define the program before tracing assistance

Identify the legal person or entity, specialized unit or personnel group, sites, services, holding out, patients, workforce, systems, and covered period. A hospital, practice, parent organization, affiliate, or network may contain several configurations. Document why the chosen boundary fits the actual SUD diagnosis, treatment, or referral activity.

Then examine every assistance route in section 2.12(b): federal operation, contract, license, certification, registration or authorization, financial assistance, government-unit funding, deductible contributions, and tax-exempt status. Record the instrument, federal actor, holder or recipient, program link, site, service, start and end, amendments, authoritative source, reviewer, and conclusion.

Distinguish entity evidence from program evidence

An enterprise grant, Medicare enrollment, Controlled Substances Act registration, federal contract, pass-through award, or tax status needs a supported map to the exact program. An affiliate's instrument does not automatically transfer across an organization, while assistance that is broader than one service may still reach the program. Preserve the facts and counsel's reasoning.

Patient-level Medicare, Medicaid, court, voucher, or other public support can prompt investigation without proving program assistance. Conversely, a program may be federally assisted even when the individual patient's care is paid privately.

Maintain status over time

Create a dated program register with boundaries, holding out, services, assistance routes, evidence, status, reviewer, controls, and next review. Keep historical entries because an expiration, closeout, relocation, ownership change, or new service does not rewrite the facts for older records.

Translate a supported result into notices, consent and disclosure paths, access, vendors, payer workflows, incident response, legal requests, retention, and patient rights. Verify configuration with a sample record.

Example

Thirteen service configurations are classified. Ten connect program, SUD service, holding out, federal route, instrument, and dates; three show only patient-level benefits. Completeness is 10 of 13 configurations.

Record a configuration-specific conclusion

Classify each program and period as federally assisted through a named route, not supported on the evidence reviewed, or unresolved. Cite the instrument, entity and program link, service, site, effective dates, reviewer, operational controls, and next review. Do not generalize the conclusion to another unit or period without evidence.

For unresolved configurations, protect records under an interim handling decision while the missing instrument or relationship is investigated. For supported configurations, verify that the live system, workforce, notice, consent, disclosure, incident, and legal-demand controls match the decision.

Close the review only after sampling a real record and preserving the result, exceptions, corrective owner, and completion evidence.

Set the next review date.

Program-level assistance checklist

• define the exact person, entity, unit, personnel group, sites, services, and dates;
• document holding out and actual SUD diagnosis, treatment, or referral activity;
• review every federal operation, authorization, funding, and tax-assistance route;
• connect each instrument to the program rather than to a patient or affiliate by assumption;
• preserve historical status and reassess after operational or organizational change; and
• implement and test privacy controls for every supported configuration.

This requirement does not mean that patient-specific federal support is irrelevant or that one unsupported route ends the analysis. Current Part 2, all assistance routes, organizational facts, other privacy law, and the record period require qualified review.