The Federal Baseline
For context: the federal Open Payments deadline for calendar year 2025 activity was March 31, 2026, with CMS opening a review-and-dispute window from April 1 through May 15, and publishing finalized data on June 30. That single date drives most compliance calendars, but treating it as the only date that matters is where multi-state programs run into trouble.
In This Analysis
Massachusetts
Massachusetts requires manufacturers to disclose sales and marketing activities directed at Massachusetts-licensed health care practitioners and covered recipients, with a low disclosure threshold of $50 for any single payment or transfer of value. On top of the disclosure itself, manufacturers must file an annual compliance program certification with the Massachusetts Department of Public Health, with certification and registration renewal windows that run separately from the federal calendar, often falling in the summer months.
Vermont
Vermont's Prescribed Product Gift Ban and Disclosure Law predates the federal Sunshine Act and remains broader in scope. Vermont restricts most gifts to health care providers outright rather than simply requiring their disclosure, meaning a payment that is perfectly reportable under federal Open Payments rules can still be prohibited under Vermont law if it falls within Vermont's stricter gift-ban categories.
Minnesota
Minnesota requires annual reporting of certain payments to practitioners and caps permissible gifts at $50, a threshold compliance teams need to track separately from the federal limits and from Massachusetts' own $50 disclosure trigger, since the rules attached to each figure differ even where the dollar amount looks the same.
Nevada
Nevada requires its own compliance filings and disclosures, and importantly counts virtual interactions, not just in-person meetings, toward its reporting thresholds, a distinction that matters increasingly as HCP engagement shifts toward remote and hybrid formats. Nevada and Massachusetts both require annual compliance program certifications with deadlines that fall outside the federal cycle, reported to arrive around June 1 and July 1 respectively.
Why This Matters for Multi-State Compliance Programs
The practical risk isn't any single state's requirement in isolation: it's treating transparency reporting as a single annual federal event when it is, in practice, an ongoing calendar of overlapping obligations with different thresholds, different definitions of a reportable "gift" or "payment," and different certification cycles. A compliance program built entirely around the March 31 federal deadline can still be non-compliant in Massachusetts, Vermont, Minnesota, or Nevada on dates that have nothing to do with CMS.
Building a Unified Transparency Calendar
qordata's Transparency Reporting Solution is built to harmonize federal and state-level reporting obligations in a single platform, so compliance teams aren't reconciling separate calendars and separate data pulls for every jurisdiction they operate in.
