What Is the IRA Maximum Fair Price and Which Drugs Are Affected in 2026?

The Inflation Reduction Act changed how pharmaceutical companies need to monitor mature, high-spend drugs in Medicare. The key operational concept is the Maximum Fair Price (MFP): a negotiated ceiling price that applies to selected drugs for a future payment year. For data teams, the challenge is not reading the statute. The challenge is building a repeatable model that connects CMS spending, FDA approval history, patent and exclusivity context, biologic status, and product identity.
How Medicare negotiation works
CMS selects high-expenditure drugs from Medicare Part D and, later, Part B. Selected drugs move through a negotiation process before the MFP applies in a future payment year. The negotiated price is published with per-unit fields, effective dates, and product identifiers that must be connected to drug approval and spending history.
For 2026 planning, teams typically need four linked views: the selected-drug list, historical Medicare spend, product approval clocks, and lifecycle protection. Each of those fields lives in a different public source.
Eligibility clocks: 7 years for small molecules and 11 years for biologics
The IRA creates different timing rules for small molecules and biologics. Small molecules are generally evaluated using a 7-year period from approval; biologics use an 11-year period. That means every exposure model must reliably distinguish Orange Book small molecules from Purple Book biologics and then calculate clocks against first approval dates.
A robust model also needs orphan-drug exclusions, generic or biosimilar competition flags, and identifier bridges across NDA, BLA, NDC, HCPCS, RxCUI, and brand names.
Why discount ranges matter
Public MFP announcements have shown steep discounts versus list-price reference points, with ranges often discussed in the 38% to 79% band. A finance team should not treat that range as a single assumption. It should model scenarios by channel, beneficiary count, utilization, remaining exclusivity, and competitive entry.
The 15 drugs selected for 2027
The next operating requirement for pharma teams is to track the 15 drugs selected for the 2027 payment year and evaluate similar assets in their own portfolios. The data problem is portfolio-wide: selected products, likely future candidates, lifecycle context, and revenue exposure all need to share the same identity model.
Data fields every exposure model needs
| Data field | Why it matters | Source domain |
|---|---|---|
| First approval date | Starts statutory eligibility clocks | FDA approvals |
| Product type | Separates small molecules and biologics | Orange Book / Purple Book |
| Medicare spend | Determines ranking and exposure | CMS Part D and Part B |
| MFP effective date | Sets payment-year impact | CMS IRA MFP |
| Patent expiry | Models mitigation runway | Orange Book and USPTO |
| Exclusivity code | Identifies additional protection | FDA exclusivity files |
Example exposure query
SELECT
d.canonical_drug_id,
d.brand_name,
ira.payment_year,
spend.total_spend_usd,
lifecycle.ira_eligibility_clock_years,
ip.latest_patent_expiry_date
FROM `tdd.ira.maximum_fair_price` AS ira
JOIN `tdd.identity.drug_spine` AS d USING (canonical_drug_id)
LEFT JOIN `tdd.cms.part_d_spending` AS spend USING (canonical_drug_id)
LEFT JOIN `tdd.fda.lifecycle_clocks` AS lifecycle USING (canonical_drug_id)
LEFT JOIN `tdd.ip.patent_cliff` AS ip USING (canonical_drug_id)
ORDER BY spend.total_spend_usd DESC;How pharma teams should operationalize this
Market access and finance teams should move from one-off spreadsheets to a governed data product. The model should update when CMS publishes new spending, when FDA approval or biologic records change, and when patent or exclusivity files are refreshed. A pre-joined estate lets analysts focus on scenario design rather than repairing join keys.
Insight: The highest-leverage work is not calculating the MFP after CMS publishes it. It is identifying which assets are moving toward selection before strategic options narrow.
Related data products
About the author
The Data Developers Research Team publishes practical guides for life sciences data teams working with public biomedical data, cloud warehouses, and query-ready data products.