Litigation Details for AMGEN INC. v. PRICE (D.C. 2017)

AMGEN INC. v. PRICE (D.C. 2017)

Docket		Date Filed	2017-05-25
Court	District Court, District of Columbia	Date Terminated
Cause	05:0706 Judicial Review of Agency Actions	Assigned To	Randolph Daniel Moss
Jury Demand	None	Referred To
Patents	6,011,068
Link to Docket	External link to docket

Details for AMGEN INC. v. PRICE (D.C. 2017)

Date Filed	Document No.	Description	Snippet	Link To Document
2017-05-25	1		NSiPAR, U.S. Patent No. 6,011,068 (the ‘068 Patent), is due to expire on March 8, 2018. As a result, the … of 33 existing patent rights 21 U.S.C. § 355a(b)(2), (c)(2). One ofthe key patents covering Sf€NSiPAR…exclusivity and patent-related protections After any such periods of exclusivity and patent protections expire…and patent protection automatically applies Id. at §§ 355a(b)(l), (c)(l) (exclusivities and patent protection…of’ the underlying patent exclusivity ld. §§ 355a(b)(2), (c)(2). Because a key patent covering SENSIPAR	External link to document

Amgen Inc. v. Price, 1:17-cv-01006: Litigation Summary and Analysis

Last updated: August 8, 2026

Amgen Inc. v. Price, No. 1:17-cv-01006, was an administrative-law challenge to Medicare’s reimbursement and billing-code policy for biosimilars. The case was not a patent-infringement action and did not involve a Paragraph IV certification, Orange Book patent, patent-validity ruling, or biosimilar approval challenge. Amgen contested CMS’s policy of assigning biosimilars referencing the same biologic to a shared HCPCS billing code, arguing that the policy could reduce manufacturer-specific reimbursement visibility and weaken incentives for biosimilar development.[1]

What was Amgen v. Price about?

The dispute concerned how Medicare Part B paid for and identified biosimilar biological products.

CMS initially adopted a policy under which biosimilars sharing the same reference product were generally assigned a common HCPCS code. Manufacturer-specific information was captured through modifiers rather than separate base codes. Amgen argued that the approach failed to distinguish individual biosimilar products adequately and could distort reimbursement, prescribing, and utilization data.[2]

The case arose during the early U.S. biosimilar market, when manufacturers were competing over future reimbursement treatment, market access, and the commercial effect of interchangeable or non-interchangeable biosimilar products.

Case identification

Item	Detail
Case	Amgen Inc. v. Price
Docket	No. 1:17-cv-01006
Court	U.S. District Court for the District of Columbia
Filing year	2017
Plaintiff	Amgen Inc.
Defendants	Secretary of Health and Human Services and federal health officials
Primary agency issue	Medicare Part B biosimilar reimbursement and HCPCS coding
Patent claims	None
Paragraph IV claims	None
Orange Book dispute	None
FDA approval challenge	None identified
Commercial subject	Biosimilar coding and reimbursement policy

Following Secretary Tom Price’s departure from the Department of Health and Human Services, the caption was expected to change as successor officials were substituted under Federal Rule of Civil Procedure 25(d). The caption change did not alter the underlying controversy.

What policy did Amgen challenge?

CMS’s original framework treated biosimilars tied to the same reference product as a group for billing-code purposes. A modifier identified the manufacturer or product. CMS adopted the approach to simplify claims administration and align biosimilar reimbursement with the reference product structure.[2]

Amgen’s position was that each biosimilar is a separate biological product with its own manufacturer, approval history, price, and market position. According to Amgen, a shared code could create several commercial problems:

1. It could make product-level utilization data less transparent.
2. It could reduce the ability of providers and payers to distinguish competing biosimilars.
3. It could affect reimbursement calculations and average sales price reporting.
4. It could weaken incentives for manufacturers to launch additional biosimilars.
5. It could complicate enforcement of product-specific payment rules.

The dispute therefore involved Medicare administration, not the scope of Amgen’s patent rights.

What legal claims did Amgen assert?

Amgen proceeded under administrative-law theories, principally challenging CMS’s interpretation and implementation of the Medicare reimbursement statute and related agency rules. The dispute centered on whether CMS had acted consistently with the governing Medicare statute, the Administrative Procedure Act, and the Biologics Price Competition and Innovation Act’s treatment of biosimilars.[1]

The practical legal question was whether CMS had authority to group multiple biosimilars under a single billing code and use modifiers to distinguish products.

Amgen’s challenge focused on the agency’s policy choice. The case did not ask the court to determine whether any Amgen patent was valid, infringed, or enforceable against a biosimilar manufacturer.

What Amgen did not claim

The docket should not be characterized as a conventional biosimilar patent case. It did not involve:

• An action under the BPCIA’s patent-exchange and patent-litigation provisions.
• A request to enjoin FDA approval of a biosimilar.
• A claim that a biosimilar infringed Amgen’s patents.
• A Paragraph IV notice letter.
• A Hatch-Waxman abbreviated new drug application.
• An Orange Book listing or certification.
• A patent settlement agreement between Amgen and a biosimilar sponsor.

How did the CMS policy affect biosimilar manufacturers?

The reimbursement-code structure had direct commercial implications.

Medicare Part B generally reimburses separately payable physician-administered drugs based on a percentage of average sales price. For biosimilars, product identification affects the calculation of payment, claims administration, utilization monitoring, and the ability of providers to select among products.

A shared code could reduce administrative complexity, but it also could make the market less transparent. Separate codes could improve product-level tracking but increase billing complexity and create additional administrative requirements for providers and Medicare contractors.

The issue was material because physician-administered biosimilars depend heavily on reimbursement mechanics. Unlike retail generics, many biosimilars are purchased and administered by physicians or hospitals. The provider’s acquisition cost, reimbursement amount, inventory risk, payer policy, and product-specific utilization data can influence adoption.

When did CMS change the biosimilar coding policy?

CMS revised its approach during the litigation period. The agency moved toward assigning separate HCPCS codes to biosimilar products rather than relying on one shared code for all biosimilars referencing the same biologic.[3]

The policy change substantially reduced the prospective impact of Amgen’s challenge. Once CMS adopted product-specific coding, the principal relief sought by Amgen became less commercially significant and potentially moot.

Key timeline

Date	Event
2015-2016	CMS developed and finalized its initial biosimilar reimbursement and coding framework.
2016	CMS published the rule establishing the initial shared-code approach for biosimilars referencing the same product.[2]
2017	Amgen filed the federal action challenging the CMS policy.
2017-2018	CMS reconsidered and revised the coding framework.
2018	CMS implemented separate HCPCS coding for individual biosimilar products.[3]
After policy revision	The live controversy narrowed because the agency had changed the challenged policy.

The exact procedural disposition should be read from the docket’s final order and judgment. The key business outcome was the CMS policy change, not a judicial finding on patent rights or biosimilar validity.

Was there a Paragraph IV challenge in Amgen v. Price?

No. Amgen v. Price was not a Paragraph IV case.

Paragraph IV litigation arises when a generic applicant certifies that a listed patent is invalid, unenforceable, or not infringed. That framework applies principally to small-molecule drugs under the Hatch-Waxman Act. Biosimilar patent disputes proceed under the BPCIA and do not use an Orange Book Paragraph IV certification in the same manner.

Amgen has been involved in separate BPCIA litigation concerning products such as filgrastim and other biologic products. Those cases are distinct from the Price litigation.

What was the Orange Book status of the case?

There was no Orange Book issue.

The products and policies implicated by the case were biologics and biosimilars regulated under the Public Health Service Act. Biologic reference products and biosimilars are not analyzed through the same Orange Book listing process used for conventional pharmaceutical products approved under Section 505 of the Federal Food, Drug, and Cosmetic Act.

The relevant FDA and CMS systems were:

• FDA biologics and biosimilar approval records.
• The Purple Book for biological product reference information.
• CMS HCPCS coding.
• Medicare Part B reimbursement rules.

Did the case affect FDA approval of biosimilars?

No direct FDA approval was at issue.

The litigation affected the payment and coding environment in which biosimilars competed. It did not seek to revoke, delay, or prevent FDA approval of a specific biosimilar. It also did not decide whether a biosimilar was interchangeable with its reference product.

FDA approval, interchangeability, and CMS reimbursement are separate regulatory questions. A biosimilar can receive FDA approval without being designated interchangeable, and CMS coding treatment is administered under Medicare rules rather than through the FDA approval process.

What patent litigation affected the products connected to the dispute?

The Price case did not adjudicate patent infringement. Separate patent litigation involving Amgen and biosimilar companies remained the relevant source of launch risk.

For biosimilar sponsors, the primary patent risks included:

• Reference-product composition patents.
• Formulation patents.
• Manufacturing-process patents.
• Cell-line and host-cell patents.
• Purification and analytical-method patents.
• Dosing and method-of-treatment patents.
• Device and delivery-system patents.

For Amgen, the economic value of those rights depended on whether a biosimilar sponsor completed the BPCIA patent-exchange process, whether Amgen asserted patents, and whether the parties reached a launch settlement.

None of those patent questions was resolved in Amgen v. Price. The case therefore should not be cited as authority for patent-estate strength, patent expiration dates, or biosimilar launch timing.

How strong was Amgen’s position?

Amgen’s position had commercial logic but faced an important procedural obstacle: CMS changed the challenged policy.

Strengths

Amgen could argue that product-specific coding was more consistent with:

• The statutory distinction between individual biosimilars.
• Accurate product-level reimbursement.
• Manufacturer-specific average sales price reporting.
• Competitive transparency.
• Congressional efforts to create a functioning biosimilar market.

The policy also involved significant economic consequences for manufacturers and providers, which supported Amgen’s argument that CMS should explain its approach adequately.

Weaknesses

The case presented a difficult vehicle for securing durable relief because:

• CMS retained authority to revise administrative coding policies.
• The agency adopted separate coding during the litigation period.
• A court may avoid deciding a statutory question once the challenged policy is withdrawn.
• Amgen’s alleged future commercial injury could be difficult to establish with precision.
• Coding policy did not directly determine FDA approval, interchangeability, patent enforcement, or market exclusivity.

The policy revision was therefore more important to the market than any reported merits ruling.

Did the case create generic-entry risk for Amgen?

The case created no direct generic-entry risk in the patent sense.

It could have affected biosimilar competition indirectly by influencing:

• Provider willingness to stock competing products.
• Medicare claims processing.
• Product-level reimbursement visibility.
• The ability of manufacturers to compete on price.
• The commercial attractiveness of launching a biosimilar.

A shared-code approach might have made product differentiation more difficult. Separate codes generally improve the ability of payers and providers to track products individually. That change could support competition among biosimilars while increasing administrative complexity.

The case did not eliminate Amgen’s patent-based ability to delay or structure biosimilar launches. It also did not establish a launch date for any biosimilar.

Did the parties enter a settlement agreement?

No patent settlement agreement is associated with the Price litigation.

The case was an action against federal officials over an agency policy. It should not be confused with private settlements between Amgen and biosimilar manufacturers that may contain launch dates, patent licenses, supply provisions, or no-challenge terms.

Any commercial settlement involving an Amgen biosimilar product must be analyzed in the separate patent docket involving the relevant biosimilar sponsor.

What was the commercial significance for Amgen and competitors?

The principal commercial issue was reimbursement architecture.

Stakeholder	Potential effect of shared coding	Effect of separate coding
Amgen	Less product-level differentiation and reduced visibility into competing biosimilars	Clearer product-level utilization and reimbursement data
Biosimilar sponsors	Potentially less visibility for individual product performance	More direct product-level competition
Physicians	Simpler billing structure but less granular coding	More product-specific billing requirements
Medicare	Lower administrative complexity	Better product tracking but greater coding complexity
Payers	Less granular utilization data	Improved ability to evaluate product-level use
Investors	Greater uncertainty over market adoption mechanics	More transparent competitive data

The ruling and policy change did not establish a patent expiry date, exclusivity end date, or biosimilar entry date for any Amgen product. Revenue exposure must therefore be modeled through separate analyses of Amgen’s biologic brands, biosimilar competitors, patent estates, FDA approvals, and reimbursement policy.

What is the current litigation significance of Amgen v. Price?

The case is principally relevant as an early biosimilar reimbursement-policy dispute. Its value to current diligence is limited in four respects:

1. It does not determine the enforceability of Amgen patents.
2. It does not establish the scope of BPCIA patent remedies.
3. It does not govern FDA biosimilar approval standards.
4. It does illustrate that CMS reimbursement and coding policy can materially affect biosimilar market access.

For patent, licensing, or launch analysis, the case should be reviewed alongside the applicable BPCIA litigation, FDA Purple Book records, CMS HCPCS decisions, and any private settlement involving the relevant reference product.

Key Takeaways

• Amgen v. Price, No. 1:17-cv-01006, challenged CMS biosimilar reimbursement and HCPCS coding policy.
• The dispute involved shared versus separate billing codes for biosimilars referencing the same biologic.
• The case was not a patent-infringement action.
• There was no Paragraph IV certification, Orange Book patent dispute, or FDA approval challenge.
• CMS revised its policy toward separate coding for individual biosimilars during the litigation period.
• The policy change reduced the prospective commercial impact of the lawsuit.
• The case does not establish patent expiration dates, biosimilar launch dates, or Amgen exclusivity periods.
• Separate BPCIA litigation and private settlement agreements must be analyzed for patent-based launch risk.

FAQs About Amgen v. Price

Was Amgen v. Price a biosimilar patent case?

No. It was an administrative-law case concerning Medicare Part B reimbursement and HCPCS coding for biosimilars.

Did Amgen v. Price challenge FDA approval of a biosimilar?

No. The litigation did not seek to reverse or delay FDA approval of a named biosimilar.

Did the case involve the Orange Book?

No. The case concerned biologics and biosimilars, not an Orange Book-listed small-molecule drug.

Did Amgen win a ruling that required separate biosimilar billing codes?

CMS changed its coding policy during the litigation period. The commercial result came principally from the agency’s policy revision rather than a patent judgment against a biosimilar sponsor.

Does Amgen v. Price establish biosimilar launch timing?

No. Biosimilar launch timing depends on FDA approval, BPCIA patent litigation, patent expiry, settlement terms, injunctions, and commercial decisions. The Price case does not establish any of those dates.

References

1. U.S. District Court for the District of Columbia. (2017). Amgen Inc. v. Price, No. 1:17-cv-01006, docket filings and orders.
2. Centers for Medicare & Medicaid Services. (2016). Medicare program: Revisions to payment policies under the physician fee schedule and other revisions to Part B for CY 2017. Federal Register, 81, 80170.
3. Centers for Medicare & Medicaid Services. (2017). Medicare program: Revisions to payment policies under the physician fee schedule and other revisions to Part B for CY 2018. Federal Register, 82, 52982.