A multi-site health system can lose control of its 340B program long before a split-billing problem becomes visible. The failure often begins upstream, with the parent hospital, outpatient departments, pharmacy operations, reimbursement team, and cost report owners working from different assumptions about what keeps the organization eligible. That risk is sharper in 2026 because, as MedLearn reported, Medicaid changes under H.R. 1 and court decisions affecting the Supplemental Security Income fraction expose a weakness in the hospital eligibility formula: a hospital can serve more financially vulnerable patients while its qualifying percentage falls.
Build the framework around eligibility governance, not pharmacy workflows
Too many policy sets treat 340B as a pharmacy purchasing program. For a multi-site health system, that framing is too narrow. Hospital eligibility depends on statutory category and Medicare cost report mechanics, not on how clean the accumulator looks on a given day.
MedLearn explains that hospitals qualifying through the disproportionate share hospital category generally need a Medicare DSH adjustment percentage above 11.75 percent. Rural referral centers and rural sole community hospitals need at least 8 percent, while critical access hospitals have no DSH percentage threshold. The same article notes that HRSA generally applies these thresholds to the most recently filed Medicare cost report. Operational and payer mix changes can therefore affect eligibility after a delay. A strong systemwide policy must identify who owns that monitoring function and how often the 340B team receives updates from reimbursement and finance.
Pharmacy cannot own that work alone.
The policy should require a formal eligibility review when the health system experiences material shifts in Medicaid coverage, uninsured volumes, hospital status, or cost report treatment of inpatient days. MedLearn also makes a point administrators ignore at their own risk: uninsured care does not increase the relevant numerator simply because patients cannot pay. If the organization assumes that higher uncompensated care automatically supports 340B eligibility, the policy rests on the wrong premise.
Connect site rules to the cost report logic that drives risk
Each outpatient location in a multi-site system tends to view itself as operationally distinct. HRSA will not accept that internal distinction if the covered entity's foundational eligibility assumptions are weak or inconsistent. The policy framework must connect every registered site to the hospital's underlying eligibility logic and the records supporting it.
MedLearn's discussion of the DSH formula provides the right starting point because it separates concepts administrators often blur together. The applicable threshold concerns the DSH payment adjustment, not an informal count of low-income patients. The patient percentage combines the Medicare SSI fraction with the share of total inpatient days attributable to Medicaid-eligible patients without Medicare Part A entitlement. That distinction belongs plainly in the policy document. Site leaders hear "Medicaid volume" and can assume every financially strained patient encounter helps the hospital remain qualified. The article does not describe it that way.
For 2026, the framework should require reimbursement, patient access, and 340B administration to align when coverage status changes. MedLearn states that H.R. 1, enacted as Public Law 119-21 on July 4, 2025, establishes work or community engagement requirements for certain Medicaid adults, generally beginning January 2027, and also requires six-month eligibility renewals for most expansion adults. The article's warning belongs directly in policy: when a patient loses Medicaid eligibility but continues receiving hospital care, formerly qualifying days can become uninsured days, and the Medicaid fraction can decline even as uncompensated care increases.
That is a recognizable health-system scenario. A hospital can feel more financially stretched while its qualifying percentage moves in the wrong direction. Procedures that still treat eligibility as an annual registration issue, rather than a cross-functional monitoring process, are already behind.
Turn legal and reimbursement developments into procedure
Legal developments create problems for multi-site systems when they are discussed once and never translated into operating procedure. A framework refreshed for 2026 needs a controlled process for evaluating court decisions and CMS rulings that affect the cost report inputs tied to 340B eligibility.
MedLearn reports that in April 2025, the U.S. Supreme Court's Advocate Christ Medical Center v. Kennedy decision upheld counting Medicare patients in the SSI numerator only when they were entitled to an SSI cash payment for the hospitalization month. The same source says the decision affirmed the existing interpretation and did not create a new, uniform percentage reduction. For policy drafting, that means administrators should not turn the legal development into a one-size-fits-all operational assumption across the system.
The article also says that the Empire Health decision and CMS Ruling 1498-R3 require counting Medicare-entitled days even when Part A does not pay, including exhausted-benefit days. For a multi-site health system, that belongs in the procedure governing data validation and escalation. When reimbursement staff, outside consultants, and 340B leadership apply different assumptions to Medicare-entitled days, the organization can end up with a site portfolio built on a cost report position that was never consistently operationalized.
Important reimbursement logic cannot live only in email.
It belongs in the policy, the review calendar, the issue log, and the approval chain for any registration, recertification, or material change affecting the 340B footprint.
Make the framework difficult to bypass at the site level
The hardest part of a multi-site 340B policy is not writing the standard. It is preventing local operators from routing around it. The framework should require documented sign-off before a site is treated as part of the 340B structure for purchasing and dispensing workflows. Re-review should follow payer mix changes, service-line shifts, or revisions to hospital reimbursement assumptions.
A short control list helps:
- Eligibility ownership: identify the accountable team for monitoring hospital qualification inputs tied to the Medicare cost report.
- Legal review trigger: require documented evaluation of court decisions and CMS rulings that affect SSI fraction treatment or Medicare-entitled day counting.
- Site activation control: block operational go-live until designated leaders confirm the underlying eligibility and registration assumptions.
- Escalation standard: require immediate review when Medicaid coverage shifts can reduce qualifying days even as charity or uninsured volume rises.
The situation is familiar. A hospital-based clinic is operationally ready, pharmacy wants it loaded, and local leadership sees no reason to wait because patient care is already happening. The system's policy should still force a pause if the reimbursement team is evaluating how current cost report treatment, Medicaid churn, or SSI fraction assumptions affect the parent hospital's qualification basis. That is not bureaucracy. It is what serious 340B governance looks like.
MedLearn's core point should set the tone for the framework: the program's safety-net purpose remains relevant, but its measure of need deserves reconsideration. Until Congress changes the underlying structure, multi-site systems have to operate inside the formula that exists, not the safety-net story they wish the formula captured.
If the written policy does not clearly separate mission, eligibility mechanics, and site-level operational controls, the system is setting itself up for preventable trouble.
