State drug price transparency reporting thresholds, triggers, and penalties for pharmaceutical manufacturers
State-by-state comparison of the dollar thresholds and percentage-increase triggers that require pharmaceutical manufacturers to report drug pricing information to state regulatory agencies. As of 2026, approximately 23 US states have enacted drug price transparency laws, each with different WAC (wholesale acquisition cost) thresholds for new drugs, different percentage-increase triggers for existing drugs, different reporting timeframes, and different penalty structures. Each record is one state with its reporting thresholds. Answers 'at what price or price increase must I report in [state]', 'what is the penalty for not reporting in [state]', and 'which states require drug price transparency reporting'.
The data
| State | Price increase % trigger | Statute | New drug WAC threshold | Reporting deadline | Implementing agency | Generic/biosimilar trigger | Maximum penalty |
|---|---|---|---|---|---|---|---|
| Connecticut | 16% cumulative increase during the preceding two calendar years for drugs that cost $40 or more for a course of treatment | HB 6669 | |||||
| Florida | 15% or more during the previous 12-month period or 30% or more cumulative during the preceding calendar years | Fla. Stat. § 499.026 | |||||
| Louisiana | 50% for a 30-day supply | LA. Stat. Ann. § 22:1657.1 | $100 | notification via email | commissioner of insurance | ||
| Maine | insulin-specific: manufacturers must report WAC per pricing unit for each category of insulin | S.P. 996 | Maine Health Data Organization | ||||
| Minnesota | S.F. 2995 | 50% over the previous 12 months | |||||
| New Jersey | more than 10% during any 12-month period | NJ S.B. 1615 | $670 per WAC unit | generic drug priced at $10 or more by more than 10% during any 12-month period | |||
| New Mexico | 10% in the previous calendar year or 16% over the previous two calendar years | NM HB 33 | $400 for a 30-day supply | first reporting deadline June 1, 2025 | 30% or more over the previous calendar year | ||
| New York | more than 16%, including the proposed increase and the cumulative increases that occurred within the prior 24 months | NY A1707 | within 60 days of the planned effective date of an increase in price | ||||
| Oregon | 10 percent or more | ORS 646A.680 through 646A.692 | $950 for a 30-day supply | New drug reports due within 30 days of market entry; Annual increase reports due March 15; 60-day price increase notices due 60 days before increase | Division of Financial Regulation | 25 percent or more AND the increase is $300 or more | |
| Texas | 15% or more in the previous year or 40% or more over the past three years | Tex. Health & Safety Code § 441.0051-441.0054 | $100 for a 30-day supply | Texas Health and Human Services Commission | same as brand | $1,000 per day |
Where this came from
Every record above links the page it was taken from and quotes the sentence that states it. These are the 2 sources this dataset was assembled from.
- goodwinlaw.comhttps://www.goodwinlaw.com/en/insights/publications/2025/06/alerts-lifesciences-state-drug-transparency-laws
- dfr.oregon.govhttps://dfr.oregon.gov/drugtransparency/pages/manufacturers.aspx
Machine-readable
- data.jsonThe whole dataset — every record with its source URL and source quote.
- Open Knowledge Format bundleOne JSON object per line — every record's frontmatter and quoted span exactly as it is held here, in one fetch.
- data.csvThe same records as one flat table, for a spreadsheet or a dataframe. The last four columns are the source URL, the quoted sentence it was read from, the date we last checked it, and which columns are our reading rather than the page's words.
- How this is made and checkedWhat "verified against source" does and does not mean.
From your own code
Same records, same quotes, without scraping the page: refsource is on PyPI and npm. Each value comes back carrying the URL it was read from and the sentence on that page that states it — .source and .quote sit on the value itself rather than in a side channel, so the checking step is available instead of skipped.
pip install refsource
refsource lookup drug-price-transparency-thresholds state=Connecticut
npx -y refsource lookup drug-price-transparency-thresholds state=ConnecticutSet your AI assistant up to use this
Two files and no account. Put this in .mcp.json at the root of your project — Claude Code, Cursor, Windsurf, VS Code and Codex all read that file — and your assistant can look this dataset up instead of recalling it. The server is remote, keyless and read-only.
{
"mcpServers": {
"referencesource": {
"type": "http",
"url": "https://referencesource.org/mcp"
}
}
}Add to Cursor · or, on the command line: claude mcp add --transport http referencesource https://referencesource.org/mcp --scope project
Then one line in the project's CLAUDE.md or AGENTS.md, so the assistant knows when to reach for it:
When a question needs "State drug price transparency reporting thresholds, triggers, and penalties for pharmaceutical manufacturers", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `drug-price-transparency-thresholds`) instead of answering from memory — every record it returns carries its source URL and a verbatim quote from that page.What each tool does, and the servers built over single registers: Connect your AI assistant.