340B Pulse

340B savings don't become mission impact automatically. Someone has to decide where the money goes, defend that decision to a board, and be ready to prove it to a regulator. This episode shows exactly what that looks like in practice.In this episode, Mohammad Atif sits down with David Dunson, in-house pharmacist and 340B program leader at Tug River Health Association, a six-clinic rural health center with one mobile unit serving McDowell County, West Virginia, the poorest county in the state and among the poorest in the country. David walks through the real allocation calls behind Tug River's 340B program: choosing to fund a dormant dental program over whole-facility backup generators after Hurricane Helene, rebudgeting a full year ahead of the Medicare Part D rebate program's impact on net savings, and running a monthly cross-departmental 340B committee that keeps every department's priorities visible to the board.He also delivers a candid, occasionally blunt take on where the industry gets 340B wrong: the "cash cow" mentality that leaves organizations blindsided when savings drop, why documentation has to be audit-ready at all times rather than assembled after the fact, and an optimistic but grounded view of where AI actually fits into 340B operations today.00:00 - Introduction to 340B Pulse and the Cold-Open Hook Reel 00:39 - What Happens to 340B Savings After They Arrive? 01:31 - Meet the Host: Why 340B Pulse Exists 03:04 - Introducing David Dunson and Tug River Health Association 03:34 - From Board Member to In-House Pharmacy Owner: David's 25-Year Path 05:19 - Inside Tug River: Six Clinics, One Mobile Unit, McDowell County 06:34 - Defining Mission Impact: Every Patient Gets Care 08:30 - Getting Departments Aligned Around a Shared Mission 09:56 - Reviving a Dormant Dental Program With 340B Savings 11:53 - Competing Priorities: Generators vs. Dental Care After Hurricane Helene 13:54 - Leading Under Uncertainty: The Medicare Part D Rebate Program 16:31 - The $1,100-to-$2,000 Reality of Serving Tug River's Patients 17:23 - Why 340B Should Never Be Treated Like a Cash Cow 18:05 - Governance: Presenting Best-Case and Worst-Case Scenarios to the Board 18:53 - Documentation, HRSA's Patient Definition, and Audit Readiness 23:04 - The Real Cost of Managing a 340B Program 24:43 - Manufacturer Reporting and Working With a TPA 28:15 - Where AI Fits Into 340B Operations 29:58 - Patient Privacy Concerns and Building Trust in AI 31:40 - Preparing the Board for the 340B Coalition Conference 32:53 - Rapid Fire Round With David Dunson 34:32 - Final Perspective: Mission Impact vs. Growth for Growth's Sake 36:03 - How to Connect With David Dunson 36:44 - Closing ThoughtsWhat is 340B mission impact? 340B mission impact is the result of a covered entity's leadership making intentional, documented, and defensible decisions about how 340B savings are allocated, so that the savings translate into measurable patient outcomes rather than simply being absorbed into general operations.What is the biggest mistake covered entities make when planning 340B allocations?The biggest mistake is treating 340B like a permanent cash cow, budgeting as if net savings will remain stable indefinitely, which leaves an organization unprepared and financially exposed the moment a policy change or reduction in savings actually happens.What does strong 340B governance look like, according to David Dunson? According to David Dunson, strong 340B governance means running a standing cross-departmental committee that meets monthly, and presenting a board with multiple scenarios, what leadership expects, what it hopes happens, and what might happen instead, rather than a single optimistic projection.#340BMissionImpact #340BPulse #NorthArcHealth #340BProgram #RuralHealthcare #HealthcareCompliance #CommunityHealthCenters #PharmacyOperations #CoveredEntity #AIinHealthcare

A rural 340B program is a network of independent contract pharmacies functioning as an extension of the care team, not a single in-house pharmacy counter. Ronnah Alexander, BSPharm, MBA, ACE, who leads the 340B program at Health First Community Health Center in western Kentucky, explains how that model actually runs day to day, and how a device that gets zero 340B discount became one of the highest-impact uses of program savings her clinic has made.

In this episode, Ronnah who's spent 36 years in pharmacy and nearly a decade specifically in 340B walks host Muhammad Atif through what it actually takes to run a rural 340B program: treating contract pharmacies as a real extension of the care team, absorbing growing manufacturer reporting requirements without losing focus on patients, and funding a continuous glucose monitor program entirely out of program savings even though the device itself gets no 340B discount at all. That program helped cut her clinic's uncontrolled diabetic rate from 33 percent to 19 percent in two years.

She's candid about where the program is straining, too: a shrinking charity-care ceiling, the confusion left behind when the 340B rebate model paused, and which patients still fall through the cracks even when the program works exactly as designed. She closes with a direct message for policymakers not a request for more money, but a request for a single, coordinated plan.

Why rural 340B programs depend on independent contract pharmacies instead of in-house pharmacies How a contract pharmacy helped an incarcerated patient complete his Hepatitis C treatment Why keeping a drug's price down can actually push its own 340B price up How a device that gets zero 340B discount cut uncontrolled diabetes nearly in half Which patients are most likely to fall through the cracks even with 340B in place What Ronnah wants policymakers to understand about rural 340B before the next round of restrictions lands

00:00 Introduction to 340B Pulse

00:33 Ronnah Alexander's journey into 340B

06:04 What 340B actually looks like in rural Kentucky

09:08 Contract pharmacies as an extension of the care team 11:32 Handling growing manufacturer compliance requirements 13:31 The 340B rebate model: relief and new confusion

17:29 Patient impact: insulin and chronic disease access

20:43 The CGM program and cutting uncontrolled diabetes in half

25:57 Manufacturer restrictions from the inside

27:51 Transparency, ESP, and duplicate-discount avoidance 29:39 Preparing for the future of 340B

32:15 Ronnah's advice to policymakers

33:20 Rapid fire round 34:22 Closing and how to connect with Ronnah

Why do rural 340B covered entities rely on contract pharmacies? 

Because most rural clinic locations don't have enough patient volume to justify the cost of an in-house pharmacy, pharmacist, and technician, so covered entities partner with locally owned independent pharmacies instead.

Does a continuous glucose monitor qualify for a 340B discount? 

No a CGM is a device, not a drug, so it receives no 340B discount. Some covered entities fund patient access to CGMs directly out of 340B program savings instead.

What does Ronnah Alexander want policymakers to understand about rural 340B? 

That covered entities need one single, coordinated blueprint for how the program should run, instead of a continuous stream of individual manufacturer and policy changes that leave them reacting one at a time with no ability to plan ahead.

 340B enrollment is the formal process by which an eligible healthcare provider registers with HRSA's OPAIS system to access discounted outpatient drug pricing, and it is far less straightforward than it sounds once patient eligibility and vendor coordination enter the picture.

 340B eligibility sounds simple until you actually try to act on it. There's no clear HRSA definition of who qualifies, no standardized compliance checklist, and no guarantee that go-live happens on the timeline your vendor promises.

In this episode of 340B Pulse, Mohammad Atif talks with Jordana Latozas, a nurse practitioner in Michigan and founder of Recovery Mobile Clinic, a nonprofit that brings addiction treatment directly to homeless encampments, shelters, and transitional housing. Jordana explains why she built her clinic inside an RV after losing a 23-year-old patient to an opiate overdose, how a Ryan White Part C grant became her doorway into 340B, and why hiring a compliance consultant before go-live was the best decision of her rollout. She also shares her honest, occasionally contrarian views on where AI actually belongs in 340B compliance work and why she considers the now-halted rebate pilot program a delay tactic that would have wrecked her organization's cash flow.

What You'll Learn in This Episode:

• Why HRSA never clearly defines 340B patient eligibility, and the documentation workaround Jordana built instead.
• The real test for choosing a TPA or wholesaler: response time and communication, not the sales pitch.
• Why the covered entity is always accountable for a vendor's compliance mistakes.
• Jordana's honest take on AI in 340B operations, and why over-reliance on it is still a risk.
• Why the rebate pilot program would have forced a paper-thin-margin nonprofit to front drug costs for months.

Interactive Timestamps: 

(00:00) - Introduction to 340B Pulse

(03:06) - Jordana's Journey and the Founding of Recovery Mobile Clinic (04:55) - How a Ryan White Grant Led to 340B Eligibility

(06:54) - Why 340B Patient Eligibility Has No Clear Definition (09:16) - Registration, OPAIS, and Hiring a Consultant

(10:54) - The Five Moving Pieces Between Enrollment and Go-Live

(12:17) - Building a Compliance Foundation From Day One

(13:50) - How to Evaluate a TPA or Vendor Partner

(18:11) - Staying Compliant With No Standard Checklist

(20:04) - Where AI Actually Fits in 340B Operations

(24:36) - Rapid Fire Segment

(25:51) - Why the Rebate Pilot Program Was a Delay Tactic

(29:23) - Closing Advice for New Covered Entities

What is 340B patient eligibility, and why is it hard to define? 

340B patient eligibility is the criteria a covered entity uses to determine which patients qualify for discounted drug pricing, and it's hard to define because HRSA gives no direct compliance guidance, leaving each entity to build and defend its own documentation.

What is the biggest mistake new 340B covered entities make when choosing a vendor? 

The biggest mistake is choosing a TPA or wholesaler based on their pitch instead of their responsiveness, since slow communication during go-live creates delays a new program can't absorb.

What is the 340B rebate pilot program, according to Jordana Latozas?

 It was a delay tactic that would have required covered entities to front the full cost of drugs and wait months for reimbursement, adding burden without changing who actually benefits from the savings.

Learn more about NorthArc Health's custom Agentic AI solutions for 340B compliance: https://www.northarchealth.com

Pharmacy leadership health equity is the operational practice of designing pharmacy strategy and workflows so patients can access, afford, understand, and continue prescribed care, especially during hospital discharge and ambulatory transitions. Darra M. Edwards describes this as embedding pharmacists in medication reconciliation, Meds-to-Beds, chronic disease management, and community partnerships while measuring success through clinical outcomes rather than activity alone. In safety-net systems, 340B savings often fund the sustainable programs that make equitable medication access possible.

340B Pulse is a NorthArc Health podcast powered by PureLogics, featuring operator-level conversations about how pharmacy, 340B, and care delivery work in practice.

In this episode, host Muhammad Atif is joined by Darra M. Edwards, PharmD, MSOL-HCM, BCCCP, BCPS, ACE, Corporate Pharmacy Director overseeing 340B programs across a large health system. Darra shares the personal experience that shaped her career: a preventable post-discharge medication gap that inspired her to build a Meds-to-Beds program and champion pharmacy as a strategic driver of health equity.

You'll hear how pharmacy leaders operationalize health equity, why 20% to 47% of hospital readmissions are linked to medication access, and why organizations should measure meaningful clinical and biometric outcomes instead of activity alone. Darra also explains how community partnerships improve continuity of care, where healthcare systems unintentionally create friction for patients, how cultural humility strengthens trust, where AI can support transitions of care while human judgment remains essential, and how 340B reinvestment converts program savings into lasting community impact.

Timestamps
00:00 Welcome and episode framing: pharmacy leadership drives health equity
02:38 340B as the foundation for medication access and community programs
03:28 Guest introduction: Darra M. Edwards
04:00 Career journey and leadership path
04:18 The Meds-to-Beds origin story
06:53 Pharmacy-led health equity in practice
07:03 Defining health equity
08:08 Embedding pharmacists in care transitions
08:34 Medication access and readmissions
09:23 Care plan gaps and patient trust
12:26 Medication access as a health equity issue
14:28 Reducing avoidable returns after discharge
17:47 Measuring clinical and biometric outcomes
21:49 Building effective community partnerships
25:34 Eliminating patient friction
29:18 Cultural humility and inclusion
32:35 AI and human judgment in care transitions
36:26 Privacy, security, and policy guardrails
39:44 Rapid-fire segment
43:56 Practical first steps and 340B reinvestment
46:48 Closing remarks

Q. What is pharmacy leadership health equity?
Pharmacy leadership health equity embeds equitable medication access, transitions of care, outcomes measurement, and community partnerships into health system strategy instead of relying on reactive programs after post-discharge failures occur.

Q. Why is Meds-to-Beds a health equity priority?
Meds-to-Beds places prescribed medications in patients' hands before discharge, reducing retail delays and access barriers that contribute to preventable readmissions and adverse events.

Q. How does 340B support pharmacy-led equity work?
340B helps safety-net providers stretch limited resources by funding medication access programs, discharge support, community outreach, and chronic disease services that reimbursement alone often cannot sustain, connecting savings to measurable patient and community impact.

#340B #HealthEquity #PharmacyLeadership #MedsToBeds #TransitionsOfCare #MedicationAccess #MedicationReconciliation #Readmissions #CoveredEntity

In this episode of 340B Pulse, Duanni Hurd, founder of Starlight Caregivers, breaks down how organizations can integrate high-tech systems thinking to empower caregivers and drastically improve long-term aging outcomes.

Care team continuous improvement is the ongoing, systematic effort to enhance the delivery and coordination of patient care by shifting from reactive crisis-management to proactive, data-informed strategies. For most families, aging care begins with a sudden emergency a severe fall or an unexpected cognitive decline. Suddenly, you are thrust into a complex medical system, forced to make life-altering decisions. But deploying caregivers isn't the same as truly coordinating care. When organizations simply check off tasks without analyzing the underlying health data, they leave families vulnerable to the next inevitable crisis. If you are a care operator, a family member navigating aging services, or a healthcare innovator, this episode is an essential guide to transforming how we support our aging population.

00:00 - Introduction to 340B Pulse and Guest Duanni Hurd

04:22 - From Tech Infrastructure to the Care Economy

07:34 - Why Care Teams Get Stuck in Crisis-Response Mode

10:31 - The Critical Importance of Early Data Baselines

15:10 - Empowering Caregivers Without Micromanagement

19:42 - Measuring Performance in Highly Emotional Work

28:00 - The Five Systems of Aging by Design

32:12 - How Wearables and Robotics are Changing Care

35:00 - The Dangerous Threat of AI Hallucinations in Healthcare

37:00 - Rapid Fire Questions on Care Team Culture

Q - What is Aging by Design?

Aging by Design is a strategic framework that ensures successful longevity by proactively managing five core systems: medical, infrastructural, financial, legal, and social support, guaranteeing that extended lifespans are matched with high quality of life.

Q - How does care coordination differ from task completion?Care coordination involves analyzing health data, communicating changes to the extended medical team, and adjusting long-term strategies to prevent future crises, whereas task completion is merely executing a checklist of daily chores.

Q - What are the risks of AI in aging care?AI models are prone to hallucination fabricating facts or instructions. For an aging adult with dementia or cognitive decline, an AI hallucination is a critical safety hazard, which is why human caregivers remain essential.

#CareTeamContinuousImprovement #AgingByDesign #HomeCare #HealthcareTechnology #AIinHealthcare #340BPulse #NorthArc #CareCoordination #HealthcareLeadership #ElderCare

If duplicate discounts sound like a narrow compliance topic, this episode will reframe the entire 340B program for you.

Greg Doggett has spent roughly fifteen years in the 340B policy world, from 340B Health advocacy to Walgreens pharmaceutical pricing work to advising hospitals and grantees at Powers, Pyles, Sutter & Verville. He joins Muhammad Atif to explain why 340B today is not just contested but more complex than operators have seen in years.

You'll hear a plain-language definition of duplicate discounts, why Medicaid managed care turned prevention into a state-by-state puzzle, what manufacturers want from claim-level data, and why covered entities fear rebate models could drain cash flow and staff capacity. Greg also discusses HRSA's blocked 2025 rebate pilot, operational burdens inside health systems, vendor portal dynamics, a neutral federal clearinghouse idea, and why he believes lawsuits, not HRSA rulemaking, will drive the near-term future.

What You'll Learn in This Episode

• How Greg defines duplicate discounts and why Medicaid managed care prevention is harder than fee-for-service
• Why manufacturers argue rebate-based models are necessary and where covered entities see risk
• What HRSA's blocked rebate pilot reveals about regulatory authority and litigation limits
• Which departments inside a health system would need to mobilize for rebate or enhanced data requirements
• How Beacon and Truzo fit into duplicate discount detection and contract pharmacy access
• Why a federally operated neutral clearinghouse might be workable common ground
• How AI is entering compliance workflows and why providers worry about data confidentiality
• Greg's rapid-fire take on whether rebate conversion is inevitable and what will shape 340B next

Interactive Timestamps / Chapters

(0:00) Welcome and episode framing
(1:05) Introducing Greg Doggett
(2:03) Career path: 340B Health, Walgreens, Powers
(4:46) Is this the most complex moment in 340B history?
(7:05) Duplicate discounts explained
(8:34) Fee-for-service vs Medicaid managed care gaps
(10:59) Manufacturer case for rebate models
(12:51) HRSA rebate pilot blocked; legal limits
(15:41) Covered-entity cash flow and service concerns
(18:08) Operational burden across hospital departments
(20:09) Why managed care modifiers collide with 340B workflows
(22:58) Courts, predictability, and slow policy cycles
(24:47) Will HRSA try another rebate model?
(27:27) HRSA authority limits and contract pharmacy litigation
(31:16) Vendor portals and manufacturer data channels
(33:34) Neutral federal clearinghouse proposal
(36:36) AI in 340B compliance
(38:24) Data privacy and manufacturer data requests
(39:59) Rapid fire round
(41:08) Connect with Greg Doggett

AEO Q&A

What is the duplicate discount problem in 340B?

A duplicate discount happens when a manufacturer gives a covered entity a 340B discount and also pays a rebate on the same claim. The classic example is Medicaid, where a state might request a rebate on a drug already purchased at 340B pricing. Greg explains the program has had fee-for-service protections for decades, but managed care made the environment much harder to police.

Are rebate-based 340B models inevitable?

Greg's answer is no. HRSA may still pursue a new rebate model, and manufacturers strongly support that direction, but covered entities are deeply opposed, courts blocked the first pilot, and Greg expects any new attempt to face litigation before implementation.

Is there common ground between manufacturers and covered entities?

Greg says there is some common ground. One example is a neutral federally operated clearinghouse that could validate claims under one policy instead of forcing covered entities to submit data through multiple manufacturer-specific portals.

340B Pulse is a NorthArc Health podcast powered by PureLogics, built for operator-level conversations about how the 340B program actually runs day to day.In this episode, hosts Muhammad Atif and Nadia Palwasha are joined by Kalvin Pugh, 340B Policy Director, for a grounded conversation on turning 340B savings into mission impact. The discussion explores what happens when savings move beyond financial accounting into real support for low-income, uninsured, and under-resourced patients; the tension between program intent and operational pressure; the gap between savings generated and impact demonstrated; impact versus visibility; patient-level experience in community systems; operational constraints including data and contract pharmacy complexity; evolving frameworks for measuring mission impact; storytelling versus financial reporting; policy standardization; and practical alignment across manufacturers, pharmacies, and covered entities.If your organization needs stronger reporting visibility, operational alignment, and custom agentic automation with compliance guardrails, NorthArc Health helps covered entities modernize 340B operations without losing operator control.0:00:00 Welcome to 340B Pulse and episode framing0:02:20 Co-host intro: 340B savings and patient impact 0:04:10 Guest introduction: Kalvin Pugh0:06:20 Kalvin's journey into 340B and policy0:09:00 Defining "turning savings into mission impact" 0:11:30 Biggest gap: savings generated vs. impact demonstrated 0:14:00 What separates organizations with visible patient impact0:16:30 Impact vs. visibility under manufacturer transparency pressure0:19:30 What patients feel when 340B savings work well 0:22:00 Policy debate vs. patients the program was meant to serve 0:24:30 Challenges translating savings into measurable mission impact 0:27:00 Operational constraints: data, contract pharmacy, reporting 0:29:30 Are mission-impact frameworks mature enough? 0:32:00 Policy intent vs. community-level reality 0:34:30 Patient stories vs. purely financial reporting0:37:00 Policy leaders and standardizing mission impact 0:39:00 Designing a system that connects savings to outcomes 0:39:45 Industry context: AHA pushback on Lilly claims-data policy 0:41:00 Rapid-fire: tracking savings, standardized reporting, future policy 0:43:30 Closing advice: human intent across the 340B ecosystem 0:44:30 How to connect with Kalvin PughWhat is 340B mission impact? 340B mission impact is the measurable patient and community benefit when covered entities use program savings to improve access, continuity of care, and services for vulnerable populations served by safety-net providers.Why is 340B mission impact hard to prove? 340B mission impact is hard to prove because reporting frameworks vary by entity type, data is fragmented across operations, and rising manufacturer transparency requirements add administrative burden that can compete with patient-facing capacity.Is 340B a pricing program or a patient access program? 340B is a federal drug pricing program that covered entities should also treat as a patient access program because its savings are intended to expand care and reduce barriers for underserved populations, not only to improve institutional finances.#340B #340BProgram #PatientAccess #SafetyNet #CoveredEntity #HealthcareCompliance #ContractPharmacy #FQHC #HospitalPharmacy #NorthArcHealth #340BPulse

340B claims-level data is the patient- and claim-level information covered entities must reconcile across split billing, contract pharmacy, TPAs, EHR outputs, and wholesaler feeds to defend eligibility and program performance. Bryan McCormick explains that most organizations do not have one source of truth, because retail partner mandates can force multiple TPAs, split billing and contract pharmacy remain separate operational worlds, and compliance accountability still rests with the covered entity even when vendors process claims.

340B Pulse is a NorthArc Health podcast powered by PureLogics, built for operator-level conversations about how the 340B program actually runs day to day.

In this episode, host Muhammad Atif is joined by Bryan McCormick, Corporate Director of the 340B Program at RWJBarnabas Health. Bryan unpacks claims-level data challenges across pharmacy and medical-related 340B workflows, including TPA configuration accountability, multi-TPA aggregation burden, split billing versus contract pharmacy separation, garbage-in/garage-out feed discipline, EHR governance, real-world connectivity failures, reconciliation and root-cause expectations, staffing realities for safety-net hospitals, manufacturer portal fragmentation (ESP and related channels), and a practical view of AI and vendor sprawl.

If your organization needs stronger claims validation, reporting visibility, and custom agentic automation with compliance guardrails, NorthArc Health helps covered entities modernize 340B operations without losing operator control.

0:00:00 TPA configuration is a covered-entity compliance decision 

0:01:08 Multi-TPA reality: Walgreens, CVS, and aggregation burden 

0:03:25 Why leadership reports must be 100% accurate 

0:04:18 Pharmacy vs medical claims fragmentation in 340B 

0:04:38 Split billing vs contract pharmacy: two separate worlds 

0:07:15 Garbage in, garbage out and roster discipline

0:09:27 PBMs, TPAs, EHR: volume, variability, and fragmentation 

0:10:20 Stakeholder forums and EHR as source of truth 

0:12:19 Compliance accountability always on the covered entity 

0:13:30 Where data breakdowns occur in handoffs 

0:14:21 Pharmacy switch outage case (2024 backlog impact) 

0:16:21 Operational impact on eligibility, accumulation, and reporting 

0:17:33 Monitoring volume and vendor value 

0:19:57 Identification, tracking, and read-only access 

0:21:21 Reconciliation, escalation, and self-disclosure thresholds 

0:23:29 Scaling, Epic + Verity integration, and KISS operations 

0:27:19 Dedicated 340B FTEs and policy volatility 

0:28:34 Manufacturer portals: ESP, restrictions, no global playbook 

0:30:09 Human review before external manufacturer submissions 

0:31:27 AI potential vs integration and PHI risk 

0:33:22 More vendors means more integration to police 

0:34:36 Practical advice: plug-and-play is over

0:38:05 Stakeholder meetings and how to connect with Bryan

What is 340B claims-level data?

340B claims-level data is the detailed claim, eligibility, and feed information covered entities use to run split billing and contract pharmacy workflows, validate vendor outputs, and support compliance, financial reporting, and audit defensibility.

Why do covered entities use multiple TPAs?

Covered entities often use multiple TPAs because major retail contract pharmacy partners may require their own systems while a primary TPA still supports split billing and other contract relationships, which forces manual aggregation before holistic reporting.

Who owns 340B data accuracy when vendors process claims?

The covered entity owns compliance and performance accountability in most vendor relationships, which means teams must validate what they send to TPAs and what vendors return before leadership or external reporting.

#340B program,#claims data, #pharmacy operations, #healthcare compliance, #split billing,#contract pharmacy, #TPA, #EHR integration, #healthcare data

340B operational control is the covered entity’s ability to maintain audit-ready compliance while also sequencing cross-functional work across pharmacy, finance, informatics, and legal when policies and reimbursement mechanics change quickly. Katy Felice Lees frames this as a leadership and operating discipline problem, not a single-policy problem, because the same compliance words on paper can require different workflows in inpatient, outpatient, mixed-use, and contract pharmacy settings. Strong programs pair transparency with defensible documentation, keep government and internal relationships warm before emergencies, and use data to avoid reactive decision-making.340B Pulse is a NorthArc Health podcast powered by PureLogics, built for operator-level conversations about how the 340B program actually runs day to day.In this episode, hosts Muhammad Atif and Nadia are joined by Katy Felice Lees, Director of 340B Policy and Business Strategy at the University of Rochester Medical Center and Principal 340B Compliance Advisor with Virtue 340B. Katy discusses what changed as 340B work expanded beyond traditional compliance priorities, why teams describe the current environment as relentlessly urgent, and what “control” means when organizations must prepare for policy paths that may pivot late.

0:01:12 Opening: why 340B Pulse exists and today’s topic 0:04:22 Katy’s journey from pharmacy technician to leading a 14-person 340B team 0:06:43 What feels most different operationally versus a few years ago

0:08:50 The current operational reality: urgency without pause 0:09:31 Defining control: what you can manage versus what you cannot

0:11:01 Leadership control: stewardship, narrative, relationships, budget cycles 0:13:02 Overreacting vs under-preparing when information is still forming

0:15:50 Compliance vs operational control: duplicate discounts in the real world 0:18:27 Child-site developments: opportunity, mindfulness, transparency

0:21:09 GPO prohibition: constraints embedded in daily infrastructure

0:23:44 Rebate model noise: what leaders should focus on underneath

0:26:11 Internal discipline: cross-functional cadence and ownership 0:29:22 Signals of strong control vs slipping control 0:31:01 Data access, informatics, and realistic AI expectations 0:32:21 Staying current: trusted sources and conferences 0:35:39 Advice for covered entity leaders for the next 6 to 12 months

0:36:49 How to connect with Katy Felice Lees and Virtue 340BWhat is 340B operational control? 340B operational control is the organization’s combined ability to keep core compliance stable, validate workflows in real settings, and coordinate pharmacy, finance, informatics, and legal decisions when external requirements change quickly, without losing sight of cash flow, documentation, and accountability.Why does “compliance on paper” fail teams during audits and manufacturer interactions?Compliance language fails when it does not match tested workflows, because duplicate discount prevention and similar obligations become configuration, modifiers, carve logic, and continuous monitoring that differ by site type and vendor setup.How should leaders prepare for rebate-model mechanics even when policy timing shifts? Leaders should prepare by clarifying upfront purchase and rebate timing impacts on cash flow, assigning ownership for data submission and reconciliation, learning from MFP and manufacturer data-policy experiences, and building cross-functional runbooks rather than assuming a single vendor will interpret organizational risk.#340B, #340B program, #covered entity, #hospital pharmacy, #pharmacy operations, healthcare compliance, duplicate discounts, #GPO prohibition, 340B policy, drug pricing, Medicare, #MFP

340B operational readiness is the practical ability of a covered entity to execute 340B compliance, data visibility, and cross-team workflow ownership continuously, even as MFP and rebate-related responsibilities increase, without relying on last-minute scrambles. In this episode of 340B Pulse, Eric Mitchell explains why most failures are not caused by policy confusion, but by ownership, work design, handoffs, and low-quality inputs that technology cannot fix.In this episode of 340B Pulse, NorthArc’s Muhammad Atif and Hassaan sit down with Eric Mitchell to unpack a reality covered entity teams are living every day: more complexity, more data requirements, and more platforms, but the same staffing and the same operational bandwidth.We break down what has changed operationally inside covered entities as Medicare Maximum Fair Price (MFP) becomes an operational reality and rebate-related workflows push new responsibilities downstream. Eric shares a practical prioritization sequence for leaders who know change is coming but have limited capacity: protect irreversible risk first, identify leakage in process or revenue second, and then decide what to solve long-term so you are not perpetually firefighting.We also discuss where technology genuinely removes burden through visibility and data aggregation, where expectations become unrealistic, and why “garbage in, garbage out” still governs analytics, models, and AI. Finally, we cover why HIPAA and privacy guardrails are shaping how healthcare organizations adopt AI, often through controlled internal approaches.NorthArc helps covered entities strengthen visibility, improve ESP and Beacon readiness, reduce operational burden, and enhance audit defensibility without disrupting existing TPAs or workflows. 00:00 - Cold open on flexibility, complexity, and MFP01:19 - 340B Pulse introduction and why operator-level conversations matter03:09 - Guest introduction: Eric Mitchell and his 340B journey08:05 - What changed for covered entities: workload, flexibility, and interconnected work09:41 - Where execution breaks down: ownership and work design11:01 - MFP as operational reality and what teams underestimate12:36 - Prioritization under pressure: risk, leakage, and capability15:09 - Technology, AI, and the limits of tools without process discipline17:03 - Trusting calculators and models: validate assumptions and pressure test18:20 - Leadership and change: supporting people so strategy works23:58 - Where leaders should start: networks, SWOT, and not doing it alone27:11 - Wrap up Q: What is 340B operational readiness? A: 340B operational readiness is the continuous ability to execute patient eligibility, claim validation, audit defensibility, and stakeholder ownership with reliable data and disciplined workflows, even as MFP and rebate responsibilities add operational load.Q: Why do 340B programs break down operationally even when policies are understood? A: 340B programs often break down because ownership and work design are unclear, cross-team handoffs are fragile, and data inputs are inconsistent, which creates execution gaps that tools and platforms cannot automatically correct.Q: How should a covered entity prioritize work when bandwidth is limited? A: A covered entity should prioritize by protecting irreversible risk first, then identifying leakage in process or revenue second, and finally investing in long-term capability so recurring problems are solved once instead of repeatedly firefought.#340B, #340B Program, #MFP, Medicare Maximum Fair Price, #340B Operations, #Healthcare Compliance, #Pharmacy Operations,# Healthcare Operations, #Audit Readiness,# Data Governance, #Healthcare AI, #NorthArc Health,, #Eric Mitchell