Duplicate discounts in 340B have become one of the most consequential issues shaping the program’s future. What once appeared to be a technical compliance concern has evolved into a broader debate about data transparency, manufacturer oversight, Medicaid managed care complexity, and the role of federal regulators. At the center of that debate is a fundamental question: how can stakeholders prevent duplicate discounts without fundamentally changing how the 340B program operates?

In a recent episode of 340B Pulse, Muhammad Atif spoke with Greg Doggett, attorney and longtime 340B policy and compliance leader at Powers, Pyles, Sutter & Verville. Drawing on decades of experience across 340B Health, Walgreens, and private legal practice, Greg explained why the program is facing unprecedented complexity, how HRSA’s proposed rebate-based approach fits into that story, and why litigation may ultimately shape the next phase of 340B more than regulation or legislation.

This article translates that conversation into a practical framework for covered entities, pharmacy leaders, compliance teams, finance executives, policymakers, and healthcare organizations navigating an increasingly uncertain 340B landscape.

What are duplicate discounts in 340B?

Duplicate discounts occur when a manufacturer provides both a 340B discount and a rebate on the same drug claim.

The most familiar example involves Medicaid. A manufacturer may provide a discounted 340B price to a covered entity while also paying a Medicaid rebate to a state Medicaid program for the same prescription. Federal law prohibits this scenario because manufacturers should not be required to provide two separate discounts on a single claim.

Historically, duplicate discount prevention was relatively manageable in traditional Medicaid fee-for-service programs because the federal government established a mechanism known as the Medicaid Exclusion File. Covered entities identify how they bill Medicaid claims, allowing states to determine whether rebates should be requested.

The challenge emerges in Medicaid managed care.

Unlike fee-for-service Medicaid, managed care lacks a single national mechanism for duplicate discount prevention. States, managed care organizations, and providers often rely on different processes, requirements, and reporting standards, creating a fragmented environment that is significantly harder to manage.

As Greg explains, the duplicate discount issue itself is not new. What is new is the scale of complexity created by varying state approaches, evolving manufacturer policies, and increasing pressure for claim-level transparency.

Why has the duplicate discount debate become so controversial?

The duplicate discount debate has become controversial because manufacturers and covered entities view the problem through fundamentally different operational and financial lenses.

Manufacturers argue that they lack sufficient visibility into claim-level activity. Without detailed data, they contend that they cannot confidently determine whether duplicate discounts are occurring and may be paying millions of dollars in unintended rebates.

Their primary concerns include:

  • Limited access to claim-level data
  • Difficulty validating rebate requests
  • Lack of standardized duplicate discount prevention mechanisms
  • Potential exposure to significant financial losses

Covered entities acknowledge the need to prevent duplicate discounts but argue that proposed solutions create new operational and financial risks.

Their concerns include:

  • Increased administrative burden
  • Cash flow disruption
  • Additional reporting requirements
  • Expanded data-sharing obligations
  • Potential diversion of resources away from patient care

The disagreement is not simply about compliance. It is increasingly about who bears the cost, operational burden, and data responsibilities required to prevent duplicate discounts at scale.

Why is Medicaid managed care so much harder than fee-for-service Medicaid?

Medicaid managed care is significantly harder because there is no equivalent of the federal Medicaid Exclusion File that exists for traditional fee-for-service Medicaid.

In fee-for-service Medicaid, providers, states, and manufacturers operate within a relatively clear framework. While not perfect, there is at least a nationally recognized mechanism for identifying 340B claims and preventing duplicate discounts.

Managed care operates differently.

Each state may establish its own requirements. Individual managed care organizations within the same state may adopt different approaches. Some require claim modifiers. Others rely on retrospective reporting. Some provide clearer guidance than others.

This creates several challenges:

  • Different rules across states
  • Different requirements across managed care plans
  • Limited federal guidance
  • Difficulty identifying 340B claims at the point of billing
  • Administrative complexity for multi-state providers

Many covered entities determine 340B eligibility retrospectively through split-billing and inventory management systems. As a result, they often cannot definitively identify a claim as 340B at the moment it is submitted.

That disconnect between prospective billing requirements and retrospective eligibility determination sits at the heart of many Medicaid managed care compliance challenges.

Why are manufacturers pushing for rebate-based models?

Manufacturers are increasingly advocating for rebate-based models because they believe rebates provide greater transparency and more reliable duplicate discount prevention.

Under a rebate structure, covered entities would purchase drugs at standard pricing and later receive rebates after submitting qualifying claims data.

From the manufacturer perspective, this approach creates several advantages:

  • Greater visibility into claim-level utilization
  • Improved ability to validate claims
  • More confidence that duplicate discounts are prevented
  • Standardized data collection opportunities

Manufacturers argue that duplicate discount prevention becomes easier when claims are verified before discounts are applied.

For many manufacturers, the rebate model is fundamentally a data and validation solution.

However, whether the benefits outweigh the operational burden remains the central point of disagreement.

Why are covered entities concerned about rebate conversion?

Covered entities are concerned because a rebate model would fundamentally change how the 340B program functions financially and operationally.

Today, providers receive savings upfront through discounted purchasing.

A rebate model reverses that process.

Organizations would first pay full price and then wait for rebates to be issued later.

For many providers, especially safety-net organizations operating on thin margins, that creates significant concerns:

Cash flow pressure

Organizations may need substantially more working capital to purchase high-cost medications before rebates are received.

Administrative burden

New processes would be required to track, reconcile, submit, validate, and dispute rebate transactions.

Technology investments

Systems may need substantial modifications to support new reporting requirements and manufacturer-specific workflows.

Staffing requirements

Additional compliance, finance, and operational resources may be necessary to manage ongoing rebate administration.

Patient service impacts

Resources redirected toward rebate management could reduce funding available for patient programs and community services.

Greg noted that many providers view rebate conversion not as a simple policy adjustment, but as a fundamental redesign of the program’s operating model.

What did HRSA’s blocked rebate pilot reveal?

HRSA’s proposed rebate pilot became one of the most important 340B developments of the past year because it highlighted the legal limits of regulatory action.

The pilot was challenged in court before implementation.

The court found that federal regulators had not adequately justified changing the longstanding interpretation of 340B discounts as upfront discounts. The court also concluded that the agency had not sufficiently considered the operational and financial impact on covered entities.

The outcome revealed several important realities:

  • Regulatory changes face significant legal scrutiny
  • Courts expect agencies to justify major policy shifts thoroughly
  • Stakeholder impact analysis matters
  • Future rebate models must be supported by stronger administrative records

The decision did not permanently eliminate the possibility of rebate-based models.

Instead, it forced regulators to adopt a more deliberate and defensible approach before attempting another implementation.

What would rebate conversion look like inside a health system?

If rebate conversion expands, implementation would require coordination across multiple departments.

According to Greg, this would be an “all-hands-on-deck” effort involving:

340B Operations Teams

Managing compliance, claim qualification, and rebate workflows.

Information Technology

Supporting data submission, integrations, reporting, and vendor connectivity.

Finance Departments

Assessing cash flow implications, rebate tracking, and financial forecasting.

Leadership Teams

Making strategic decisions around staffing, budgeting, and organizational priorities.

Human Resources

Supporting workforce planning and potentially creating new operational roles.

The challenge is not simply building new processes.

It is redesigning organizational workflows around a fundamentally different reimbursement model.

Why is litigation increasingly shaping 340B policy?

One of the most important themes from the discussion was that major 340B questions are increasingly being resolved in court rather than through traditional policymaking channels.

Contract pharmacy restrictions, rebate models, manufacturer data requirements, and agency authority have all become subjects of litigation.

This trend creates uncertainty because:

  • Court decisions take years
  • Outcomes are difficult to predict
  • Multiple cases may affect the same issue simultaneously
  • Stakeholders struggle to plan long-term investments

The result is a policy environment where organizations often wait for legal decisions before making strategic commitments.

As Greg noted, the court system is not fast. Many of today’s most important questions may remain unresolved for years.

Could a neutral 340B clearinghouse be the compromise solution?

One of the most interesting ideas discussed during the episode was the concept of a neutral federal 340B clearinghouse.

Rather than requiring covered entities to submit data separately to individual manufacturers, a centralized clearinghouse could operate as an independent intermediary.

Under this approach:

  • Covered entities would submit claims data to a single system
  • Data would be validated against relevant federal programs
  • Duplicate discounts could be identified centrally
  • Manufacturers would receive needed verification
  • Providers would avoid multiple reporting frameworks

Potential benefits include:

  • Standardized governance
  • Reduced administrative burden
  • Consistent national processes
  • Greater stakeholder trust
  • Improved duplicate discount prevention

While opinions vary regarding feasibility, the concept represents one of the few proposals that attempts to balance competing interests rather than favoring one side exclusively.

How are vendor platforms becoming part of 340B infrastructure?

Technology vendors increasingly play a critical role in duplicate discount management.

Platforms such as Beacon, Truzo, Kalderos, and other manufacturer-supported systems are becoming operational infrastructure for claim validation and data exchange.

Many covered entities already interact with these platforms because manufacturers require data submissions as a condition of accessing certain contract pharmacy arrangements.

As rebate discussions continue, these systems may become even more important because they provide the technological foundation needed for claim verification and rebate administration.

The larger policy question is not whether technology will be involved.

It is who controls the data, how it is governed, and what protections exist for covered entities.

Can AI help solve 340B complexity?

AI is already beginning to influence both manufacturer and provider operations.

Potential use cases include:

  • Duplicate discount detection
  • Claims validation
  • Compliance monitoring
  • Workflow automation
  • Exception identification
  • Audit preparation
  • Data quality improvement

For manufacturers, AI may improve confidence in duplicate discount detection.

For covered entities, AI may reduce labor-intensive compliance activities and free staff to focus on higher-value operational work.

However, AI also raises important questions regarding:

  • Data privacy
  • Information security
  • Data ownership
  • Appropriate use of patient-related information
  • Transparency in decision-making

As data-sharing requirements expand, these concerns will likely become increasingly important.

What does the future of 340B look like?

The future of 340B will likely be defined by three overlapping forces:

Legal uncertainty

Major policy questions continue moving through the courts.

Data transparency demands

Manufacturers are seeking more detailed claim-level information.

Operational adaptation

Covered entities are preparing for potential changes while managing current compliance requirements.

Despite growing pressure for rebate-based approaches, Greg’s assessment was notable: rebate conversion is not inevitable.

Likewise, he rejected the idea that duplicate discounts are inherently unsolvable under the current system.

The more realistic future may involve compromise solutions, stronger data governance frameworks, improved technology infrastructure, and continued legal battles that gradually define the boundaries of the program.

For now, one reality remains clear: organizations that understand duplicate discount prevention, data governance, reimbursement workflows, and regulatory developments will be best positioned to navigate whatever comes next.

NorthArc partners with healthcare organizations to modernize 340B operations, strengthen compliance visibility, improve data governance, and build AI-powered workflows that help teams navigate growing regulatory and operational complexity without sacrificing program integrity.

FAQ

What is a duplicate discount in 340B?

A duplicate discount occurs when a manufacturer provides both a 340B discount and a rebate on the same drug claim, which federal law generally prohibits.

Why is Medicaid managed care a major 340B challenge?

Medicaid managed care lacks a single national duplicate discount prevention mechanism, resulting in varying state and plan requirements that create significant operational complexity.

Why do manufacturers support rebate-based models?

Manufacturers believe rebate models provide greater claim-level visibility, improve validation capabilities, and reduce the risk of paying duplicate discounts.

Why are covered entities concerned about rebate conversion?

Covered entities worry about cash flow impacts, administrative burden, staffing requirements, technology investments, and potential effects on patient services.

What happened to HRSA’s rebate pilot?

The pilot was challenged in court and blocked before implementation because the agency did not adequately justify the policy shift or sufficiently consider provider impacts.

What is a neutral 340B clearinghouse?

A neutral clearinghouse would be an independent system that receives claims data, validates eligibility, and helps prevent duplicate discounts without requiring providers to submit data separately to multiple manufacturers.

Is a rebate-based 340B model inevitable?

According to Greg Doggett, no. While rebate models remain under consideration, their adoption is not guaranteed and will likely face continued legal and operational scrutiny.

What is most likely to shape the future of 340B?

Based on Greg’s assessment, lawsuits and court decisions are currently more likely to shape the program’s future than new HRSA regulations or congressional legislation.