Codify — Article

NOPAIN for Veterans Act requires VA to add certain non-opioid pain drugs to its formulary

Directs the VA to adopt FDA‑cleared non‑opioid analgesics on a fast, payment‑linked timetable — changing how the VA acquires and makes alternative pain treatments available to veterans.

The Brief

This bill amends title 38 to force the Department of Veterans Affairs to recognize and furnish specified non‑opioid pain medications and biologicals. It inserts a statutory definition for those products and requires the VA to add qualifying therapies to its national formulary on a statutory schedule tied to external payment milestones.

For compliance officers, VA clinicians, contract officers, and pharmaceutical manufacturers, the bill changes the gatekeeping rules for new non‑opioid options. It shortens the timeline from FDA clearance to VA formulary availability in many cases and creates a direct link between CMS payment actions and VA procurement obligations.

At a Glance

What It Does

The bill adds a statutory definition of 'non‑opioid pain management drug or biological product' and requires the Secretary of Veterans Affairs to include such products in the VA national formulary either within one year of the product becoming eligible for certain Medicare/CMS payments or within 18 months of FDA approval, whichever comes first. It also bars the VA from using the Cost of War Toxic Exposures Fund to pay for this requirement and directs the Secretary to implement the amendments promptly.

Who It Affects

Directly affected parties include VA medical centers and the Veterans Health Administration's pharmacy benefit management operations, manufacturers of FDA‑cleared non‑opioid analgesics seeking VA market access, and veterans who receive post‑operative or acute pain care through the VA. Indirectly affected stakeholders include VA contracting offices, clinicians who prescribe pain treatments, and PBM contractors managing VA formularies.

Why It Matters

The measure ties VA formulary decisions to external CMS payment determinations and a fixed post‑approval timeline, which can accelerate access to alternative pain therapies and shift budgetary pressure within VA. That linkage alters the usual clinical‑evidence and utilization review cadence VA uses to adopt new therapies and creates predictable windows for manufacturers and clinicians.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

The bill modifies 38 U.S.C. 8125 by inserting a new statutory definition that identifies qualifying products as drugs or biologicals that the FDA has cleared, approved, or granted and that are indicated to reduce post‑operative pain, provide postsurgical or regional analgesia, or treat acute pain without operating on opioid receptors. That definition is narrowly focused on FDA‑recognized indications and the pharmacologic mechanism of avoiding opioid receptor action.

Alongside the definition, the bill imposes a calendared inclusion requirement on the VA national formulary. There are two trigger paths: a product that becomes eligible for certain Medicare/CMS temporary or separate payment categories (the bill cites SSA section 1833(t)(16)(G) and 42 C.F.R. 416.174) must be added within one year of that eligibility; alternatively, a product that receives FDA approval must be added within 18 months of that approval.

The bill therefore links VA obligation either to a CMS payment decision or to a post‑approval time clock.The statute also attaches two administrative constraints. First, it explicitly prohibits using funds from the Cost of War Toxic Exposures Fund (38 U.S.C. 324) to meet the new requirement, which leaves VA to absorb costs from its other appropriations unless Congress provides new funding.

Second, the Secretary must implement the statutory amendments within 90 days after enactment, directing VA leadership to change internal processes quickly.Taken together, these provisions change the path by which a new non‑opioid analgesic moves from regulatory clearance to routine availability within the VA system: manufacturers get a clearer market access timetable; clinicians get an expanded set of options sooner in some cases; and VA operations must accelerate contracting, formulary review, and clinical guidance work to meet the prescribed schedule.

The Five Things You Need to Know

1

The bill adds a new definition to 38 U.S.C. 8125 for 'non‑opioid pain management drug or biological product' limited to FDA‑approved/cleared products that treat post‑operative, postsurgical/regional, or acute pain without acting on opioid receptors.

2

It requires the VA to add qualifying non‑opioid products to the national formulary by the earlier of (a) one year after the product becomes eligible for certain Medicare/CMS temporary or separate payments or (b) 18 months after FDA approval.

3

The bill cites two external payment milestones as triggers: eligibility under SSA section 1833(t)(16)(G) and eligibility for separate payment under 42 C.F.R. 416.174 (or successor regulations).

4

It prevents the VA from using the Cost of War Toxic Exposures Fund (38 U.S.C. 324) to implement the new formulary requirement, meaning VA must rely on other appropriations or offsets.

5

The Secretary of Veterans Affairs must implement the statutory amendments within 90 days of enactment, requiring rapid changes to VA formulary and procurement procedures.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 1

Short title — 'NOPAIN for Veterans Act'

This brief section names the statute the 'Non‑Opioids Prevent Addiction in the Nation for Veterans Act' or 'NOPAIN for Veterans Act.' It has no substantive effect on obligations but establishes the public name for legislative and administrative references.

Section 2(a) — Amendment to 38 U.S.C. 8125: Definition

Defines 'non‑opioid pain management drug or biological product'

The bill inserts a new definitional paragraph into 38 U.S.C. 8125 that limits the category to FDA‑approved, granted, or cleared drugs or biologicals indicated for reducing post‑operative pain, producing postsurgical/regional analgesia, or treating acute pain and that do not act on opioid receptors. Practically, this restricts the policy to products with explicit FDA labeling in those clinical scenarios and excludes off‑label uses and opioid‑receptor modulators.

Section 2(a) — Amendment to 38 U.S.C. 8125: Timed formulary inclusion

Establishes a two‑path timetable for adding products to the national formulary

The bill creates a new subsection that forces the Secretary to place qualifying products on the national formulary within a fixed window tied to either CMS payment eligibility or FDA approval. The clause is mechanical: one year after Medicare/CMS payment eligibility (as cited) or 18 months after FDA approval, whichever comes earlier. This substitutes external payment determinations and fixed deadlines for the VA's typical deliberative formulary review process.

2 more sections
Section 2(b)

Funding limitation — prohibits use of Cost of War Toxic Exposures Fund

This short provision bars the VA from tapping the Cost of War Toxic Exposures Fund under 38 U.S.C. 324 to comply with the new formulary obligations. That redirects the fiscal impact onto VA's existing appropriations or future Congressional appropriations, creating an explicit funding constraint embedded in the statute.

Section 2(c)

Implementation directive — 90‑day administrative deadline

The Secretary must implement the statutory amendments within 90 days of enactment. That instruction forces the VA to update internal rules, formulary lists, contracting templates, and clinical guidance on a compressed timetable, even though the substantive inclusion deadlines for individual products remain tied to the CMS/FDA triggers.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Veterans across all five countries.

Explore Veterans in Codify Search →

Who Benefits and Who Bears the Cost

Every bill creates winners and losers. Here's who stands to gain and who bears the cost.

Who Benefits

  • Veterans with acute or post‑operative pain — The bill increases the likelihood that FDA‑cleared non‑opioid alternatives will become available through VA pharmacies and clinics on a predictable schedule, expanding non‑opioid treatment options.
  • Manufacturers of FDA‑cleared non‑opioid analgesics — The statute creates a predictable path to VA formulary access tied to FDA approval or CMS payment decisions, improving market access prospects within the VA system.
  • VA clinicians and surgical teams — Prescribers gain an expanded toolkit for perioperative and acute pain management, which can inform prescribing practice and opioid‑sparing protocols.

Who Bears the Cost

  • Veterans Health Administration (VA operations and procurement) — The VA must accelerate formulary reviews, contracting, and distribution logistics to meet statutory timelines, increasing administrative workload and potential procurement costs.
  • VA appropriations (medical care budget) and taxpayers — Because the bill prohibits using the Cost of War Toxic Exposures Fund, the financial burden of purchasing and stocking new products will fall on VA's other funds unless Congress provides new appropriations.
  • VA Pharmacy Benefit Management and PBM contractors — PBM operations will face additional workload for formulary updates, price negotiations, utilization management policies, and clinical guidance development.

Key Issues

The Core Tension

The central dilemma is access versus stewardship: the bill forces faster access to non‑opioid options to reduce opioid exposure for veterans, but that speed—driven by external payment triggers and fixed deadlines—risks undercutting VA's evidence‑based formulary processes and imposes budgetary pressure the statute expressly refuses to relieve.

Two implementation frictions stand out. First, the bill ties VA formulary action to external CMS payment determinations and fixed post‑approval timelines.

CMS decisions and regulatory payment categories serve different purposes and follow different evidence standards than VA clinical and formulary review; using those milestones as the trigger can force VA to adopt products before VA's internal clinical committees complete thorough cost‑effectiveness or utilization review. That trade‑off can accelerate access but may increase exposure to therapies with limited post‑marketing evidence or uncertain real‑world value.

Second, the explicit prohibition on using the Cost of War Toxic Exposures Fund shifts cost responsibility into VA's existing budgets and creates a practical funding shortfall risk. If Congress does not appropriate additional funds, VA may meet the statutory requirement in form (placing drugs on the national formulary) but struggle to operationalize availability across facilities, leading to uneven access.

Finally, the statutory definition confines the policy to FDA‑labeled indications and products that do not act on opioid receptors, which may exclude clinically useful off‑label applications and newer mechanisms that partially interact with opioid pathways. Those exclusions could produce gaps between the statutory formulary and clinical practice.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.