The Hospital's Hidden Infrastructure Part 2: SUSTAIN 340B Thursday August 13th, 2026

 

National Daily Hospital News

Executive Briefing — Thursday, August 13, 2026

The Hospital’s Hidden Infrastructure

Part II: The SUSTAIN 340B Act Protects Access—and Builds a New Compliance Operating System

Today

• A bipartisan Senate bill would protect point-of-purchase 340B discounts and codify contract-pharmacy access.
• The same legislation would establish a statutory patient definition and create new registration, documentation, reporting, audit, clearinghouse and financial-assistance obligations.
• Hospital leaders should treat the proposal as simultaneous access protection, margin exposure and enterprise compliance transformation.

Legislative status: The SUSTAIN 340B Act was introduced on August 5, 2026. It has not been enacted, and its provisions may change. The requirements described below are proposed requirements—not current law. Hospitals should use the bill for readiness assessment and scenario planning while continuing to follow existing 340B requirements.

Series navigation: Part I — Medicaid Coverage Loss  |  Part II — SUSTAIN 340B  |  Part III — AHRQ and Safety Learning  |  Part IV — Rural Maternity Standby Capacity

Four-Part Executive Series

Drug Access Is Infrastructure. So Is the System That Proves Every Discount Was Earned.

The 340B Drug Pricing Program is often described as a pharmacy program.

For many hospitals, that description is operationally incomplete.

340B savings may support medication access, specialty pharmacy, infusion services, behavioral health, care management, discharge prescriptions, rural clinics, uncompensated care and other services that ordinary reimbursement does not fully finance. The program can therefore affect patient access, service-line viability, cash flow and the hospital’s ability to sustain care for vulnerable communities.

On August 5, a bipartisan Senate group—Sens. Jerry Moran, Tammy Baldwin, Shelley Moore Capito, Tim Kaine, John Boozman and John Hickenlooper—introduced the Supporting Underserved and Strengthening Transparency, Accountability, and Integrity Now and for the Future of 340B Act, or SUSTAIN 340B Act.

The legislation attempts a difficult policy exchange:

Protect the access and financial value of 340B while making eligibility, contract-pharmacy operations, use of savings and program integrity more standardized, visible and auditable.

That exchange would bring meaningful protections. Manufacturers would have to offer covered entities the 340B ceiling price regardless of whether a drug is dispensed directly or through a contract pharmacy. The bill would restrict manufacturer conditions on access, preserve point-of-purchase discounts and sunset the federal rebate pilot within one year.

It would also create a new operating architecture. Covered entities would need to demonstrate patient eligibility at the prescription level, register arrangements, standardize contracts, maintain auditable records, submit claims-level data, report annually, extend financial assistance across sites and pharmacies, and accept expanded audit and corrective-action authority.

The governing principle is:

A hospital cannot protect 340B value with a pharmacy-only compliance model when eligibility is created by clinical care, documented in the medical record, transmitted through technology, reconciled through claims and certified by enterprise leadership.

The Bill Would Change Both Sides of the 340B Equation

Proposed provision	Protection or opportunity	Hospital operating consequence
Point-of-purchase discount	Preserves upfront 340B pricing and would end the rebate pilot within one year.	Reduces long-term working-capital exposure, but hospitals must remain ready for the currently scheduled 2027 pilot unless law or agency action changes it.
Contract pharmacies	Codifies their use without numeric or geographic caps and limits manufacturer restrictions.	Requires registered agreements, standard terms, patient-choice safeguards, annual independent audits and auditable records.
Patient definition	Creates statutory clarity and recognizes qualifying discharge and referral prescriptions.	Turns eligibility into a record-level control requiring reliable encounter, prescriber, order, referral and pharmacy data.
Child sites	Clarifies eligible relationships with parent covered entities.	Adds ownership, integration, registration and three-year record-retention controls; certain acquired sites could face an eligibility delay.
Transparency	Creates a more visible account of how the program supports patients and communities.	Requires annual reporting, standardized descriptions of savings use and executive attestation.
Data clearinghouse	Creates a common mechanism to prevent duplicate discounts.	Requires complete, accurate claims-level data from covered entities and contract pharmacies.
Financial assistance	Makes patient affordability more explicit.	Requires a transparent policy for patients at or below 200% of the federal poverty level, including a drug sliding scale as applicable.
Nondiscrimination	Restricts different payer or PBM treatment based on 340B status.	Creates a stronger basis for monitoring and challenging discriminatory reimbursement or network practices.
User fees	Finances stronger federal oversight and the clearinghouse.	Beginning in FY 2031, covered entities would share a national fee assessment based on 340B prescription volume.

The full SUSTAIN 340B bill text is 97 pages. Its importance lies less in any one provision than in the way the provisions connect.

1. Contract-Pharmacy Protection Would Come With Contract-Pharmacy Accountability

The bill would explicitly allow covered entities to use wholly owned and contract pharmacies. It would require manufacturers to offer covered outpatient drugs at or below the 340B ceiling price regardless of whether the drug is dispensed directly or through a contract pharmacy, allow delivery to covered-entity-requested pharmacy locations and limit manufacturer demands for claims data outside the proposed clearinghouse.

For hospitals serving large geographic regions, patients with transportation barriers or communities without a hospital-owned pharmacy, this could protect the practical reach of the program.

But protection would not mean passive continuation of current arrangements.

Covered entities would have to submit agreements and register each arrangement before implementation. Required contract terms would address pharmacy services, data submission, patient choice, patient eligibility, diversion safeguards, Medicaid duplicate-discount controls, audit rights and information access. Contract pharmacies would be subject to annual independent audits commissioned by the covered entity, and relevant auditable records would have to be retained for at least three years.

This means every contract-pharmacy relationship should be managed as a controlled extension of the covered entity—not merely as an external revenue channel.

Hospital leadership should be able to answer:

• Who owns each agreement and each registration?
• Which pharmacy locations are active, and which have not dispensed a qualifying prescription?
• Can the hospital obtain complete dispensing, reversal, payer and replenishment data?
• Are Medicaid fee-for-service and managed-care rules correctly configured?
• Are audit findings tracked through correction and validation?
• Can a patient obtain required financial assistance at the contract pharmacy?

2. The Patient Definition Would Become a Clinical-Data Control

The proposed definition generally requires that an individual have received an outpatient healthcare service from the covered entity within the preceding two years, that the covered entity create and maintain an auditable medical record demonstrating the relationship for each prescription or order, and that the prescription arise from the covered entity’s service or a qualifying referral.

The bill also addresses several areas that have produced operational uncertainty:

• Discharge prescriptions: An outpatient prescription following discharge from an emergency department or inpatient stay could qualify under the specified conditions.
• Referral prescriptions: Eligible covered entities could include certain prescriptions written by non-340B providers within 12 months of a documented referral, subject to consultation, documentation, dispensing and retention requirements.
• Service documentation: The outpatient service would need a documented order or referral and generally be reimbursable by Medicare or Medicaid, identifiable through CPT or HCPCS, or within the scope of an applicable grant or designation.
• Drug-only contact: Services consisting only of drug administration, dispensing or infusion generally would not establish the underlying patient relationship, subject to specified exceptions.

These rules cannot be administered reliably through employee memory or an isolated pharmacy spreadsheet.

The eligibility engine may need to connect:

• Patient identity and encounter date.
• Covered entity and child-site eligibility.
• Service code and site of care.
• Practitioner relationship.
• Prescription or order.
• Referral and consultation documentation.
• Discharge status.
• Payer and Medicaid status.
• Dispensing pharmacy.
• Reversal, replacement and duplicate-discount status.

The weakest link may not be pharmacy. It may be an interface, a missing referral note, an inconsistent discharge feed, an unregistered site, a provider-master error or a record that cannot be reproduced during audit.

3. The Clearinghouse Would Turn Data Quality Into Program Eligibility Infrastructure

The bill would direct HHS to contract with an independent third party to operate a national data clearinghouse intended to prevent duplicate discounts and support proper accounting.

Covered entities would submit claims-level information, including data available through contract pharmacies. The clearinghouse would assess completeness and accuracy, identify potential violations, support remediation and make certain claims information available for specified program-integrity purposes. Low-volume entities and hospitals facing feasibility constraints could receive aggregate-reporting or hardship pathways under defined conditions.

This is not simply a new report.

It is a new dependency between the hospital’s clinical record, split-billing logic, third-party administrator, wholesaler activity, pharmacy dispensing data, Medicaid exclusion files and federal reporting environment.

Executive implication: A covered entity may have a defensible policy and still fail operationally if the data supporting that policy are incomplete, delayed, inconsistent or irreproducible.

Data governance should therefore answer four questions:

1. Completeness: Did every relevant encounter, prescription, payer and dispensing event arrive?
2. Accuracy: Do source systems agree on patient, provider, site, drug and payer?
3. Timeliness: Are submissions and corrections completed within required windows?
4. Reproducibility: Can the hospital reconstruct the eligibility decision and supporting record years later?

4. Transparency Would Move 340B From the Pharmacy Report to the Executive Attestation

Within one year of enactment and annually thereafter, covered entities would report information covering the parent entity, child sites and contract-pharmacy arrangements.

The proposed reporting includes the number of individuals receiving 340B drugs, prescriptions by insurance type, charity care, a standardized description of how savings benefited patients and communities, patient financial demographics, medication-access policies, certain government contracts and third-party administrator relationships.

A CEO, CFO or COO would attest that the savings were used to benefit the patients and communities served by the covered entity.

That attestation changes the governance question.

Leadership would need a reconciled, documented bridge from:

340B purchase → qualifying patient → claim and dispensing event → realized savings → funded service or patient benefit → reported community impact

A description assembled once a year by pharmacy or government relations will not be enough if it cannot be reconciled to financial statements, cost-report data, community-benefit reporting and operational evidence.

Hospitals should begin building a 340B value ledger that distinguishes:

• Gross purchase-price benefit.
• Contract-pharmacy and third-party administrator fees.
• Reversals, true-ups and disputed transactions.
• Net realized program value.
• Patient financial assistance.
• Services and access supported by the net value.
• Communities and populations reached.

5. Financial Assistance Would Need to Follow the Patient Across the Network

The bill would require each covered entity to maintain a transparent financial-assistance policy available at the point of care and publicly reported. The policy would apply to patients served by child sites and contract pharmacies and generally include patients at or below 200% of the federal poverty level, with a sliding fee scale for covered outpatient drugs as applicable.

Auditable implementation records would be retained for at least three years. Application to child sites and contract pharmacies would begin three years after enactment.

This is both a patient-access requirement and a workflow requirement.

A policy is not operational merely because it appears on a website. Patients must be identified, informed, screened, approved, priced correctly and able to receive the benefit at the location where the prescription is filled. The covered entity must then be able to prove that the process worked.

Revenue cycle, financial counseling, pharmacy, health equity, patient access, information technology and contract management therefore share accountability.

6. The Rebate Debate Is Also a Working-Capital Debate

HRSA’s revised 340B Rebate Model Pilot Program is currently scheduled to begin January 1, 2027, for selected drugs and qualifying manufacturers.

The SUSTAIN 340B Act would prohibit expansion of that pilot, conclude it within one year of enactment and transition its data function to the clearinghouse. It also states congressional support for point-of-purchase discounts rather than rebates.

Hospitals should not assume the legislation will be enacted before the pilot’s implementation date.

They need parallel readiness:

• Current-path readiness: Prepare cash-flow forecasts, receivable controls, submission processes, denial management and reconciliation for the 2027 rebate pilot.
• Legislative-path readiness: Prepare for point-of-purchase protection accompanied by clearinghouse submissions, statutory patient logic and expanded reporting.

The prudent strategy is not to choose one forecast. It is to maintain both until the law, litigation and agency implementation pathway are resolved.

The Enterprise 340B Operating Model

Owner	Primary accountability	Evidence leadership should receive
Executive sponsor	Program value, risk appetite, resource allocation and attestation readiness.	Quarterly enterprise dashboard and unresolved high-risk exceptions.
Pharmacy	Purchasing, accumulation, replenishment, dispensing and contract-pharmacy oversight.	Transaction reconciliation, audit results, replenishment exceptions and drug-level exposure.
Compliance/legal	Policy, regulatory interpretation, contracts, audit response and corrective action.	Current obligation inventory, legal-change log and corrective-action status.
Finance	Net savings, fees, cash flow, rebate receivables and community-benefit reconciliation.	Gross-to-net value bridge and dual-path liquidity forecast.
Revenue cycle	Payer identification, Medicaid logic, assistance screening and discharge workflow.	Unresolved payer status, duplicate-discount exceptions and assistance completion.
Information technology/data	Interfaces, master data, lineage, completeness, security and reproducibility.	Interface failures, data-quality tests, access logs and clearinghouse readiness.
Clinical operations/medical staff	Encounter, order, referral, prescriber and discharge documentation.	Documentation defects and remediation by service line or site.
Internal audit	Independent testing of design, operation and corrective-action effectiveness.	Risk-based audit results and repeat-finding analysis.

Three Scenarios Every 340B Hospital Should Model

Scenario A: The Bill Does Not Advance Before the Rebate Pilot Begins

The hospital pays higher initial acquisition costs for selected products and waits for rebates. Early submissions produce denials, data corrections and timing uncertainty. Savings exist economically but are converted into receivables rather than immediately available cash.

Management response: Establish drug-level receivable aging, denial ownership, liquidity thresholds and daily reconciliation during implementation.

Scenario B: The Bill Advances With Materially Similar Requirements

Contract-pharmacy protections reduce manufacturer access restrictions, but the hospital discovers inconsistent patient logic, incomplete referral documentation, outdated agreements and weak savings-to-benefit reporting.

Management response: Launch an enterprise gap assessment before final regulations, prioritizing patient eligibility, pharmacy agreements, data lineage and executive attestation.

Scenario C: Contract-Pharmacy Access Expands Faster Than Governance

More prescriptions become operationally available through protected arrangements, but audit exceptions, duplicate discounts and financial-assistance failures grow with transaction volume.

Management response: Require governance capacity to grow before or with network expansion. Volume without control is not program strength.

Executive 340B Readiness Dashboard

Measure	Why it matters	Escalation signal
Net 340B value by entity, site and channel	Shows where value is created after fees, reversals and corrections.	Unexplained variance from budget or prior period.
Eligibility exceptions per 1,000 accumulations	Tests reliability of patient and prescription logic.	Rising rate, repeat cause or unresolved high-dollar exception.
Contract-pharmacy audit coverage and open findings	Measures control across the external network.	Missed audit, repeat finding or overdue corrective action.
Duplicate-discount exceptions	Protects Medicaid and manufacturer compliance.	Any systemic error or unresolved material claim set.
Data completeness and interface failures	Determines whether eligibility and clearinghouse reporting can be defended.	Missing source feed, late file or unexplained record loss.
Financial-assistance access and utilization	Shows whether patients receive the intended affordability benefit.	Site or pharmacy cannot apply policy; eligible patients are not screened.
Rebate receivable days and denial rate	Measures current-path working-capital exposure.	Aging or denials exceed the hospital’s approved liquidity tolerance.
Savings-to-community-benefit reconciliation	Supports transparency and executive attestation.	Reported narrative cannot be reconciled to finance and operations.

What Hospital Leaders Should Do Now

Within 14 Days

1. Name one executive sponsor and one operational owner for enterprise 340B readiness.
2. Create a provision-by-provision impact matrix identifying policy, workflow, contract, technology, data, financial and staffing implications.
3. Inventory every covered entity, child site, owned pharmacy, contract pharmacy, third-party administrator and Medicaid configuration.
4. Maintain two financial forecasts: implementation of the current 2027 rebate pilot and enactment of a point-of-purchase legislative pathway.
5. Escalate known audit findings and data defects that would affect patient status, referrals, discharge prescriptions, duplicate discounts or contract-pharmacy reporting.

Within 30 Days

1. Test a sample of prescriptions against the proposed patient definition and reconstruct the supporting record.
2. Compare all contract-pharmacy agreements with the proposed standard elements and confirm current registration.
3. Map data lineage from encounter and prescription through dispensing, replenishment, payer identification and reporting.
4. Build a gross-to-net 340B value ledger and link net benefit to services and communities supported.
5. Test whether financial assistance can be consistently accessed and documented at parent sites, child sites and contract pharmacies.
6. Present the board or appropriate committee with the dual-path financial exposure, major control gaps and remediation plan.

NDHN Recommended 340B Readiness Standards

These are management targets, not statutory or regulatory thresholds.

Management measure	NDHN recommended standard
340B prescriptions supported by complete eligibility logic and reproducible documentation	100%
Covered entities, child sites and pharmacy arrangements with verified current registration	100%
Contract pharmacies receiving risk-based independent audit coverage	100% annually
Material audit findings with assigned owner, due date and validation	100%
Repeat material findings after corrective action	Zero
Known systemic eligibility or duplicate-discount defects awaiting executive escalation	Zero beyond 1 business day
Material source-data feeds monitored for completeness and timeliness	100%
Eligible locations able to operationalize the approved financial-assistance policy	100%
Net 340B value reconciled to accounting records and supported patient/community benefits	Quarterly
Board or board-committee review of 340B value, access, compliance and legislative exposure	At least quarterly during material change

The Leadership Decision

The SUSTAIN 340B Act is neither simply a victory for hospitals nor simply a new compliance burden.

It is a proposed exchange.

Hospitals would gain clearer protection for contract-pharmacy access, point-of-purchase pricing, discharge prescriptions, qualifying referrals and nondiscriminatory payer treatment. In return, the program’s patient relationships, transactions, savings, assistance and community benefit would become more standardized, reportable and auditable.

The organizations most prepared for that future will not be those with the most aggressive accumulation logic.

They will be those that can demonstrate—transaction by transaction and community by community—that:

• The patient was eligible.
• The drug was properly purchased and dispensed.
• The duplicate discount was prevented.
• The patient could access needed assistance.
• The net value was real.
• The benefit supported access and care.
• The evidence can survive independent review.

340B is hidden infrastructure because its value appears at the pharmacy transaction but its purpose is realized across the hospital and community.

The program should be governed at the same level as the access, services and financial resilience that depend upon it.

---

Next in the series: As AHRQ’s national safety-learning capacity weakens, hospitals must determine whether they retain the evidence surveillance, improvement expertise, protected frontline time and learning systems needed to prevent harm rather than merely react to it.

Primary sources: Senate announcement and summary; SUSTAIN 340B Act text; HRSA 340B Rebate Model Pilot Program.

About the standards: NDHN recommended standards are management targets, not regulatory thresholds. Organizations should apply more stringent controls or timelines where patient risk, program requirements or legal advice demand them.

📍 Published at National Daily Hospital News
Published as part of the National Daily Hospital News series.
Visit the archive: https://nationaldailyhospital.blogspot.com/
LinkedIn: Spence Tepper
Facebook: Compirion
Number One Hospital Blog: Be the Number 1 Hospital

© 2026 National Daily Hospital News
Principle Author: ChatGPT5
Editor: Spence Tepper
Permission to share freely given

#HospitalLeadership #HospitalOperations #HospitalFinance #340B #SUSTAIN340B #PharmacyLeadership #DrugAccess #ContractPharmacy #HealthcareCompliance #RevenueCycle #PatientAccess #RuralHospital #CriticalAccessHospital #HealthcarePolicy #NDHN