A multi-state 340B program is a single covered-entity operating model applied across hospitals, clinics, pharmacies, vendors, and state regulatory environments that do not match each other. It scales when the organization standardizes its compliance core, documents every justified local exception, and governs vendors on outcomes rather than service levels.
That distinction sits at the center of a recent episode of 340B Pulse, the NorthArc Health podcast powered by PureLogics. Host Muhammad Atif spoke with Dr. Maria Campanella, who leads 340B operations and compliance across a multi-state nonprofit health system with hospitals and clinics in markets throughout the U.S. She studied pre-pharmacy at Xavier University in New Orleans, moved into specialty pharmacy in Atlanta managing a large Ryan White clinic for infectious disease patients, and served as a 340B program director for operations and compliance before taking on enterprise scale.
Her framing is worth stating plainly. At one site, the question is whether a claim was processed correctly. Across many, the question becomes whether the organization can detect risk early, hold vendors accountable, and give leadership a reliable view of what is actually happening.
What Makes a Multi-State 340B Program Different From a Single-Site One?
A multi-state 340B program differs from a single-site program because regulatory requirements, Medicaid rules, pharmacy models, payer environments, and contracting law all change at the state line. The same written policy can produce different operational behavior in different markets, and leadership often cannot see the difference from the center.
Dr. Maria put it directly: with every state, there are different regulatory and compliance requirements, so the program has to be adjusted for those territories or those markets. In a multi-state 340B program, that adjustment is not optional, and it is not a failure. The failure mode is adjusting without recording that you adjusted.
At What Point Does Site-by-Site 340B Management Stop Being Reliable?
Site-by-site management stops being reliable in a multi-state 340B program when compliance findings start clustering in audits. Dr. Maria’s answer to that exact question was specific: a lot of compliance issues in your audits, particularly diversion or duplicate discounts, are red flags.
This is a useful signal because it is measurable and already in hand. Most organizations do not need a new report to detect that they have outgrown informal coordination. They need to read the findings they already have as a pattern rather than as a series of unrelated site problems.
The structural fix she describes for a multi-state 340B program has two halves. Keep internal teams for compliance, regulatory, and government affairs. Then add a centralized team whose job is to oversee and standardize those processes for each entity.
What Should a Multi-State 340B Program Standardize, and What Should Stay Local?
A multi-state 340B program should standardize its compliance core and its operating documentation, while allowing vendor selection and legal contracting to vary where state law requires it. The dividing line is whether the variation is legally or operationally forced, or merely inherited.
Here is how Dr. Maria drew that line in practice:
| Standardize enterprise-wide | Allow to vary by market |
|---|---|
| TPA relationships and configuration | Vendor selection where a state or entity requires a different one |
| Policies, procedures, and SOPs | Legal contracting processes, which follow state law |
| Diversion prevention controls | Site complexity: mixed-use settings, clean sites, infusion |
| Duplicate discount prevention | Local staffing structures and operational maturity |
| High WAC spend monitoring | Payer and Medicaid environments |
She called the compliance items the core heartbeat of the program. Avoid diversion. Avoid duplicate discounts. Avoid high WAC spend. Those stay identical everywhere, regardless of how complex a given covered entity is.
Legal contracting is the clearest example of the other side. Most local states have to run their own contracting processes, so a multi-state 340B program cannot standardize those. The system ties them back together in national oversight committees instead.
How Should Leaders Tell a Justified Variation From a Normalized Control Weakness?
Leaders of a multi-state 340B program distinguish a justified variation from a normalized control weakness by routing it through a named person and a standing committee. Dr. Maria’s model is a local leader in each market who acts as the point of contact and meets with a national oversight committee to bridge the gap.
The mechanism matters more than the policy language. A variation that a local leader has to explain to a national committee is a documented exception. A variation nobody has to explain is just how that site has always done it, which is exactly what turns into an audit finding later.
She was also clear that the committee is not a one-way channel. Every entity should be included in new implementations and projects, and the oversight committee should voice its opinion back. That two-way flow is what keeps a multi-state 340B program’s enterprise policy connected to site-level reality.
Why Do More Reports Not Produce More Control?
More reports do not produce more control because report volume answers what happened without answering why it happened, who owns it, what the risk is, and what action is required. Most 340B teams are not short on vendor reports, TPA reports, pharmacy reports, dashboards, financial summaries, or audit files.
The gap is synthesis, and it widens with every market a multi-state 340B program adds. A missing-claims error surfaced in one market is a ticket. The same missing-claims error surfaced in three markets is a systemic control failure with a financial impact that nobody has totaled.
How Do You Build Exception-Based Management Across Markets?
You build exception-based management in a multi-state 340B program by having every local market feed one centralized dashboard, built in-house or on a platform like Tableau or Power BI, that can be filtered down to a single market, entity, issue, or data feed.
Dr. Maria was precise about the direction of flow. The local feed runs to the centralized dashboard, so each market is feeding into one place. From there, you filter to whichever market, entity, case report, or data feed you want to audit.
Three things that dashboard should do:
- Flag discrepancies automatically rather than waiting for a month-end review.
- Cross-reference across markets. If one system shows an error of missing claims, check whether another market has the same root cause, and quantify the financial impact.
- Consolidate support tickets. Logging and grouping vendor tickets by issue is how you see a repeating pattern and conclude that a fix is not working, which is the trigger to ask what the next viable option is.
Documentation in a multi-state 340B program follows the same logic. Her team runs one shared drive with subfolders for compliance, legal, finance, TPAs, project management, and technology, plus a separate subfolder for each contract pharmacy agreement and each state the system operates in. Anyone can request access and find what they need. The structure is identical across all sites.
What Separates Vendor Governance From Vendor Contract Administration?
Vendor governance differs from contract administration because a contract defines what the vendor owes you, while governance verifies that you actually received it. A vendor can meet every service level it agreed to and still leave a covered entity without visibility into its own program. In a multi-state 340B program, verification has to happen per market, because a vendor performing well in one state tells you nothing about the next.
Dr. Maria’s governance checklist is concrete. Standardize the auditing and monitoring of your crosswalk and your open support cases inside the contract itself. Watch EDI feed turnaround time, because a slow feed means missed eligible claims. Hold a weekly or bi-weekly cadence call with the account manager to work through open cases, recent observations, and training.
She is equally direct that vendor reports are not evidence. Covered entities should independently validate:
- Duplicate discounts
- Medication exclusion files
- Split billing and crosswalk accuracy
- High WAC exposure
Market analysts should run those checks weekly or bi-weekly. Not annually, and not only when something looks wrong.
What Should You Do When a Vendor Meets Its SLA but Misses the Outcome?
When a vendor meets its SLA but the operational outcome does not follow, escalate above the account manager, convene focus groups with your own leaders and technical staff to put improvement suggestions directly to the vendor, and request a credit of administration fees for contracted work that was not delivered.
That last step is the one most covered entities never take. In Dr. Maria’s words, if you are missing certain accumulations or things that are in your contract, you can request that the vendor credit you those administration fees you pay, because these are things you are paying the vendor to do.
Read as a control inside a multi-state 340B program, that is significant. It converts a service failure from an operational annoyance into a recoverable financial item, which is what gets a vendor issue onto a finance leader’s agenda instead of dying in a support queue.
How Should a Multi-State 340B Program Absorb the Rebate Model, ESP, and Truzo?
A multi-state 340B program absorbs simultaneous policy change by centralizing the tracking rather than the response. Dr. Maria described being hit from several directions at once by the HRSA rebate model, 340B ESP, and Truzo, and her team’s answer was a single tracker.
That tracker records every change, which states are affected, and the financial impact per market. Alongside it, the team monitors DSH percentage as an early indicator of whether the system is losing Medicaid patients, so a compliance signal and a financial signal are read together rather than separately.
For the intelligence feed itself, she named three sources her compliance and regulatory team monitors: 340B Health’s free webinars for legislative updates, the 340B Report newsletter for changes and effective dates.
She also suggested a structural option worth considering: rather than folding policy monitoring into an already-loaded 340B oversight committee, stand up a separate council whose only remit is policy changes, manufacturer restrictions, and reimbursement, meeting frequently to work through financial impact and next steps.
What Is the Real Cost of the Rebate Model to a Covered Entity?
The real cost of the rebate model to a multi-state 340B program is staffing and cash flow, not policy disagreement. Someone has to monitor, track, and submit the requested data. If a rebate is denied, someone has to appeal it. Then someone has to confirm the rebate was actually received.
Dr. Maria’s organization is a nonprofit that is already sometimes operating in the red, and the drugs affected are high-cost, paid for up front. Most of the patients served are uninsured or underinsured, so the reimbursement that some assume offsets the cost is not arriving.
She raised a data question that has had little public attention. Covered entities are being asked to submit patient health information, and there is no clear answer yet about what happens to that PHI once it leaves.
Her position on the fairness of it was unambiguous. Savings go back into the community through medical missions at home, free copay assistance, and cash cards to help patients afford medications. Being made to clear an administrative hurdle to reach a discounted price promised more than 30 years ago, while the mission is quality of care for an indigent population, is a hard thing to justify to the people doing the work.
Where Does AI Actually Help a Multi-State 340B Program?
AI helps a multi-state 340B program with reporting, analytics, and pattern detection, but it does not remove the person doing the hands-on submission, monitoring, and appeal work. That is the line Dr. Maria drew, and it is a more useful line than most vendor marketing offers.
The examples she gave are exactly the right shape for automation. We submitted this appeal and did not get a response, so what is the next step. We received this rebate from one manufacturer but not from another. Those are reconciliation and exception questions, repeated at volume, across markets, against different manufacturer requirements.
That is where an agentic system earns its place: holding the clocks, flagging the gaps, and surfacing the exception to a human who then decides. Not replacing the human, and not pretending the appeal writes itself.
For a multi-state 340B program weighing this, the practical test is whether a proposed system reduces the number of things a person has to remember to check. If it only produces another report, it has added to the problem Dr. Maria described rather than solved it.
Which Metrics Actually Indicate Program Health?
The metrics that indicate multi-state 340B program health are the ones that show direction rather than totals. Dr. Maria named two specifically, and both are unusual choices.
WAC spend against 340B spend, monthly. Run from your internal dashboard with your TPA. Savings should be growing and the chart should be climbing. That comparison tells you whether the program is efficient in a way that total savings or claim volume never will, because both of those rise with growth even when the program is drifting.
Referral capture, on the vendor scorecard. She called referral optimization a big winner, because it increases savings and extends reach to patients, particularly for specialty drugs and infectious disease management where patients see multiple providers.
She added one warning sign that runs the other way: if you are not optimizing your program and you have far more vendors than you need for work you could do internally, you are relying too heavily on vendor logic. Training your own staff to handle auditing and crosswalk management is often cheaper than the outsourced contract fee.
Frequently Asked Questions
What should a multi-state 340B program standardize first? Standardize the compliance core first: diversion prevention, duplicate discount prevention, and high WAC spend monitoring, along with policies, procedures, and SOPs. These do not change by state and should be identical at every site.
Should internal audits be kept locally or centrally? Both, in a multi-state 340B program. Each entity or territory keeps its own internal audits and shares them with the corporate oversight group. External audits should be run by the contracted vendor across all entities, with a report of findings per market delivered to the national group.
How often should a covered entity meet with its TPA account manager? Weekly or bi-weekly. The agenda should cover open cases needing resolution, anything the vendor observed in the last two weeks, and training or process guidance.
Can a covered entity recover fees from an underperforming vendor? Yes, where the shortfall relates to contracted work. If accumulations covered in the contract are being missed, the covered entity can request that the vendor credit back the administration fees paid for that service.
What is a controlled inventory of local variations? It is a maintained record of every place a site departs from the enterprise standard, with the reason, the owner, the approving authority, and a review date. Without it, an undocumented workaround is indistinguishable from a control failure during an audit.
Does AI replace 340B compliance staff? No. AI is well suited to analytics, reconciliation, and exception detection across markets and manufacturers. Submission, monitoring, and the appeal process still require a person, which is why the strongest deployments reduce the checking burden rather than the headcount.
The Takeaway for Health System Leaders
Asked for one principle for scaling a multi-state 340B program without losing control, Dr. Maria did not name a system. She named a posture: be present and visible with your third-party vendors and your management.
The rest follows from that. Optimize the program, including referral capture. Make sure internal and external audits align across entities in different states. Keep the oversight committee on one accord, with strong leaders from every relevant department cross-referencing each other’s work. And recognize that it is more than a 340B department problem, which is why finance and legal belong in the room.
A multi-state 340B program does not become scalable by adding reports, vendors, or software. It becomes scalable when the organization can make consistent decisions, detect risk early, and prove what it did.