Artikkel

From policy to process: What health systems are learning from Maximum Fair Price (MFP) implementation

MFP at a glance

Maximum Fair Price (MFP) implementation is showing health systems that policy change quickly becomes operational change. Early lessons point to four priorities: claim-level data visibility, cross-functional ownership, structured exception management, and a clear path to automation.
Negotiated prices for the first 10 drugs selected under the Medicare Drug Price Negotiation Program took effect on January 1, 2026, and prices for 15 more drugs follow in 2027.

Moving a new pharmaceutical policy from regulation into day-to-day operations often reveals challenges that are difficult to fully anticipate during planning.

That has been one of the clearest lessons of MFP implementation. What may begin as a reimbursement or policy issue can quickly become an operational effort that spans pharmacy, finance, revenue cycle, information technology, analytics, legal, third-party administrators, and technology partners.

During a discussion moderated by Rachel Croce, 340B consultant with Accelerate Pharmacy Solutions, Tara Feller, Director of Pharmacy Business Operations at Froedtert ThedaCare, and Kelley Curtis, Chief Pharmacy Officer and Vice President of Pharmacy at St. Luke’s Health, shared what their organizations have learned as MFP moved from planning into practice. 

The panelists reached a common conclusion. Beyond the reimbursement path, MFP implementation requires health systems to build the data visibility, organizational ownership, reconciliation processes, and infrastructure needed to understand performance at the individual claim level and respond when expected outcomes do not occur.

MFP's financial impact is harder to isolate than it may appear

For Feller’s team, planning began well before implementation as the organization evaluated possible effects on acquisition costs, inventory decisions, reimbursement, 340B eligibility, and budgeting.

Even before the first negotiated prices took effect, the impact proved broader than initially modeled. As wholesale acquisition cost (WAC) price decreases emerged, Froedtert ThedaCare revisited assumptions about claims beyond Medicare Part D and updated finance and accounting leaders on changing expectations. At the same time, the organization was evaluating inventory decisions, enrollment in the Medicare Transaction Facilitator and Beacon MFP, legal review of program terms, reconciliation workflows, and the potential for margin compression.

Those interconnected variables make it difficult to answer what may seem like a straightforward executive question: What is the true total financial impact of MFP?

The panelists said they are still working toward a complete view. Feller noted that her organization had modeled approximately 53 percent margin compression on the initial 10 products relative to 2025 performance, and said results appeared to be trending close to that projection, although so many other factors had changed that she could not say whether the model was right or the organization had been fortunate. Curtis described the opposite experience. Actual performance on those 10 products had come in well below her organization’s original budget assumptions, and the organization had run below budget on them for most of the year. “We were focused solely on Medicare, and it became much bigger than that,” she said. For health system leaders, that uncertainty is an important takeaway. Measuring the impact of MFP requires more than reviewing acquisition cost or payment levels in isolation. It requires understanding how changes affect the broader pharmacy financial model.

Claim-level data is the foundation of MFP

One of the clearest lessons from the session's open discussion with attendees was the importance of reliable claim-level data.

“The MFP is only as good as the data that’s underneath all of it,” Curtis said.

For each claim, her team needs to answer several questions:

  • Was the claim eligible for an MFP refund?
  • Was it a 340B claim?
  • Was payment received?
  • Can that payment be reconciled to the underlying transaction?

A few weeks before the discussion, Curtis said St. Luke’s had seen more more than 16,000 Medicare Part D claims come through. The organization was working across multiple systems and data sources to understand eligibility, 340B status, and payment.

That level of reconciliation matters because summary payment results can hide meaningful exceptions. Curtis said payments on paid claims were about 90 percent of what was expected, but some outliers still required substantial investigation. As claim volume increases, even a relatively small number of exceptions can create meaningful operational and financial burden. One attendee whose organization had not yet implemented a software solution described reconciliation rates swinging from 70 percent one month to 35 percent the next, and several others in the room indicated similar swings. Curtis said she had heard of organizations at 40 to 50 percent of expected payment and credited technology with helping St. Luke’s get its rate higher. Another attendee reported a rate near 90 percent with no tool in place. The leadership implication is that a high-level payment rate is not enough. Teams also need a reliable way to identify exceptions, investigate them, and trace claims through to payment.

MFP requires enterprise ownership

Although pharmacy may lead much of the work, successful MFP implementation requires cross-functional coordination.

“This definitely became an enterprise-level workflow, and definitely not pharmacy only, although it feels like it’s ours,” Curtis said. “We do own a major portion of the work.” At St. Luke’s, the work involves pharmacy business operations, the 340B team, data and analytics, information technology, finance, revenue cycle, and cash reconciliation. External partners also provide necessary information and infrastructure.

Froedtert ThedaCare involved the same functions and added a dedicated resource. The organization hired a pharmacy business analyst whose primary role includes sourcing and combining data. That analyst built a Microsoft Power BI dashboard that allows the organization to track and trend performance over time. Without that role, Feller said, the organization would still be competing for time from a centralized data and analytics team that is inundated with requests. “This MFP has been a pretty big lift, so having a dedicated resource that I can say, ‘This is one of your primary tasks,’ has been super helpful,” she said.

Across both examples, one practical question stands out: Who owns the operational work once implementation begins?

Data extraction, reconciliation, financial interpretation, issue management, and cash tracking do not always fit neatly within one function. Without clear ownership, the work can become another competing priority for teams that are already balancing extensive operational and analytical responsibilities.

Technology can help, but manual work remains

The discussion also showed how organizations’ views of technology can change once claim volume and reconciliation complexity become more visible.

Froedtert ThedaCare initially evaluated technology vendors, but chose to manage the work internally. Feller said the organization is reconsidering that decision ahead of January 1, 2027, as it prepares for added complexity.

St. Luke’s took a different approach. The organization already had a relationship with Plenful for 340B audit-related work and expanded that relationship to support MFP needs. Curtis said the team believed early on that a technology solution would be necessary, given the limits of native system functionality and the strain on internal analytics resources. The work began in December 2025, and she said it took roughly six months of hard work to reach the current state.

Even so, technology has not eliminated manual work. Curtis said that, despite having a technology solution in place, the process still amounts to a full-time role for one analyst, and opportunities for improvement remain.

That distinction matters when evaluating MFP technology. The key question is not only whether a platform can reconcile data. It is whether the solution reduces the manual effort required to investigate exceptions, act on findings, and scale operations as volume and complexity grow.

Reconciliation has a cost of its own

The economics of that evaluation are unusual. One attendee pointed out that the statute places responsibility for accurate MFP payment on manufacturers, which raises the question of how much a health system should spend to verify what it is owed. Feller’s answer was that no one appears to be holding manufacturers to that standard. “If we’re not doing it, really nobody is,” she said. “We know margin is eroding, but we’ve been tasked with ‘keep as much as you can,’ and that’s going to mean potentially adding resource and spending more money to then retain whatever margin you can.”

The same logic shaped her view of vendor selection. A platform that does the work better at a much higher price point may simply be another source of margin erosion. Attendees also asked about contingency-style pricing, in which a vendor takes a percentage of recovered payments. Both panelists said such arrangements have been offered and neither organization has pursued one, although Curtis said the model could become more palatable as more drugs and claims enter the program.

Exception management requires time and attention

The discussion around good faith inquiries (GFIs) highlighted another important operational reality: Reconciliation identifies the problem, and a separate process has to resolve it.

Feller said her organization had submitted relatively few GFIs despite identifying more situations that might justify one. Most often claims identified as 340B but not accumulated as 340B, because of the work required to assemble the information and justify each inquiry. With the 340B rebate model approaching, she said, a manual process is probably no longer the answer.Curtis also described GFI management as an area that still requires additional work, even with technology supporting reconciliation.

One audience participant shared a practical example. Their organization had used Microsoft Power BI to identify reconciliation breaks, but still relied on a spreadsheet and substantial staff time to track thousands of GFIs, gather supporting documentation, follow up on open items, and decide when issues should be escalated to CMS.

The same participant described manufacturers responding to inquiries with requests for invoice data from other accounts and sites, and said outcomes varied sharply by manufacturer, with some paying readily and others paying nothing over the course of the year.For health system leaders, that reflects an important distinction: identifying exceptions and resolving them are two different capabilities.

A dashboard may show where expected and actual results diverge. But collecting documentation, managing follow-up, responding to requests for additional information, and tracking the issue through resolution requires a separate workflow.

Accurate reporting matters at the facility level

Another practical lesson came from an audience member who found that MFP rebate payments were being attributed to a primary facility rather than to the locations generating the underlying financial benefit.

The result was an overstatement of revenue at one facility and an understatement at the specialty pharmacy that, according to the participant, generated approximately 95 percent of that rebate revenue.

For leaders assessing the financial performance of specific facilities or service lines, receiving payment is only part of the picture. Accounting and reporting structures also need to reflect where the underlying activity occurred.

Otherwise, enterprise-level totals may conceal meaningful distortions at the facility or service-line level.

The next phase of MFP is proactive management

When asked what a more mature MFP program should look like, the panelists pointed to greater automation and clearer ownership.

For Froedtert ThedaCare, future priorities include improving the GFI submission process, clarifying workflow ownership, and deciding whether technology or additional dedicated resources should support the program. Feller also noted that 340B rebate models may create new operational questions.

Curtis described a future state focused on moving from reactive work to proactive management. Her team’s goals include:

  • Automatically identifying claims paid below expectations, not only claims with no payment.
  • Detecting manufacturer, product, and National Drug Code (NDC) patterns that may point to broader issues.
  • Automating more of the GFI process.
  • Creating clearer connections among claim-level transactions, duplicate-discount activity, and cash settlement.

That progression reflects a useful maturity path for health systems:

Establish reliable data → Reconcile transactions → Identify exceptions → Manage resolution → Recognize patterns → Intervene earlier

That path matches what health systems reported in Pharmacy Outlook: Fall 2026 Edition. Split-billing software is in use at 90% of participating organizations and virtual inventory at 61%, while automated dashboards and reporting tools stand at 40%, which places reporting, automation, and claim-level visibility squarely in the next round of investment.

The organizations in this discussion are at different points along that path, but their experiences suggest that making the process functional is only the beginning.

Five takeaways for health system leaders

Treat MFP as an enterprise workflow

Pharmacy may lead the effort, but sustainable execution often requires coordination across 340B, finance, revenue cycle, information technology, analytics, and other functions.

Start with claim-level data integrity

Eligibility, 340B status, expected payment, and actual payment need to connect before leaders can accurately assess performance.

Plan for exception management, not only reconciliation

Finding a discrepancy is just the first step. Teams also need a process to investigate it, gather documentation, and manage the issue through resolution.

Evaluate technology based on the work it removes

Technology can support reconciliation, but it does not automatically eliminate manual analysis. The best solution is one that meaningfully reduces effort as complexity grows.

Build toward proactive management

As the operating environment becomes more complex, health systems may need to move beyond identifying individual missed or underpaid claims and toward recognizing patterns early enough to act sooner.

Turning MFP implementation experience into operational readiness

One of the most useful messages from the discussion was that no health system has fully solved every aspect of MFP implementation.

As Curtis said early in the session, “We’re all trying to figure this out together.”

At the same time, the discussion showed what health systems can influence now: data integrity, clarity of ownership, visibility into reconciliation, structured exception management, and thoughtful use of automation.

Health systems that strengthen those fundamentals will be better positioned not only to respond to current MFP requirements, but also to adapt as the operational environment continues to evolve.

Explore how Cencora can support operational readiness for evolving pharmacy and reimbursement workflows.

This article is based on an in-person panel discussion moderated by Cencora consultant Rachel Crose with Tara Feller of Froedtert ThedaCare, Kelley Curtis of St. Luke’s Health, and participating health system leaders.

Relaterte ressurser

Artikkel

A sustainable specialty pharmacy starts with the care model

Rapport

Pharmacy Outlook: Høstutgave 2026

Artikkel

Why referral management is critical to infusion service line success