The RESULTS Act (H.R. 5269) overhauls how Medicare calculates private payor–based payment rates for clinical diagnostic laboratory tests by directing CMS to obtain ‘‘final payment’’ data for high‑volume tests from a single certified, independent national nonprofit claims data entity and its qualifying comprehensive claims database. The bill updates timing, technical definitions (including a new ‘‘widely available non‑ADLT’’ category), and requires CMS to publish explanations of how rates are calculated.
It also creates a CPI‑based fallback payment when CMS cannot obtain qualifying data.
Why it matters: the statute moves Medicare away from relying solely on laboratory self‑reporting toward a market‑based, third‑party claims repository for most high‑volume, non‑ADLT tests. That change reallocates influence over rate inputs from labs to the entity (or entities) that control the certified database, alters compliance obligations, and creates new operational and privacy requirements for data stewards and payors — with direct consequences for lab revenue stability, CMS administration, and private payor data governance.
At a Glance
What It Does
Directs CMS to contract with a certified national nonprofit ‘‘qualifying independent claims data entity’’ and to use its qualifying comprehensive claims database to supply final private‑payor payment and volume data for widely available non‑ADLT clinical diagnostic laboratory tests beginning with data collection periods in 2027 (reporting in 2028). It defines ‘‘final payment rate,’’ tightens quality controls on submitted claims, and requires CMS to publish supporting explanations of calculated rates.
Who It Affects
Clinical diagnostic laboratories (especially labs that furnish high‑volume tests), private payors and claims administrators whose paid‑claims data must be included in the certified database, the nonprofit entities that operate national claims repositories, and CMS as the contracting and oversight agency. Indirectly affects Medicare beneficiaries through changes in network participation incentives and payment stability.
Why It Matters
This is a structural shift in the source of market data that determines Medicare lab payments: CMS will rely on a centralized, certified third‑party claims feed rather than primarily on laboratory reporting. That reduces certain reporting burdens for high‑volume tests but concentrates influence with the certified data entity and raises new verification, privacy, and governance questions that will determine whether payment rates accurately reflect market reality.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill amends section 1834A of the Social Security Act to change how CMS collects and uses private‑payor claims data when it sets Medicare payment rates for clinical diagnostic laboratory tests. For tests that are ‘‘widely available’’ and not classified as ADLTs, CMS must — starting with data collection periods that begin in 2027 and reporting periods starting in 2028 — obtain ‘‘applicable information’’ (final payment amounts and volumes) from a qualifying comprehensive claims database held by a certified national nonprofit claims data entity with which CMS has a contract.
The statute requires the entity and its database to meet explicit criteria intended to ensure national representativeness and data quality.
The bill specifies what ‘‘qualifying independent claims data entity’’ and ‘‘qualifying comprehensive claims database’’ mean in practical terms: the entity must be a national nonprofit not affiliated with insurers, providers, or government agencies; be certified as a qualified entity under existing statutory standards; comply with HIPAA and states’ privacy/security laws; and apply rigorous quality assurance and statistical validation. The database must include large volumes of validated, state‑representative private payor claims, version control to identify final paid claims, and data from a minimum number of payors and claims (the statute sets numerical floors).
The bill also defines ‘‘widely available’’ tests as those billed by more than 100 providers during a specified six‑month lookback period.If CMS cannot contract with a qualifying entity or the certified database lacks applicable information for a particular widely available test and data collection period, the bill establishes a default payment rule: payment for that test for a qualified rate period equals the prior year’s payment increased by the annual CPI‑U for all items. For tests that are not ‘‘widely available,’’ the bill preserves laboratory reporting and provides for cross‑walking to comparable tests or using the existing gap‑filling process when no comparable data exist.
Finally, the statute requires CMS to publish explanations and supporting data for calculated rates, tightens exclusions (for example, specifying that ‘‘final payment’’ excludes denied, appealed, erroneous, or recouped payments), and updates several timing and percentage‑cap provisions that limit year‑to‑year rate reductions.
The Five Things You Need to Know
CMS must contract, ‘‘as soon as practicable’’ after enactment, with a certified national nonprofit claims data entity to supply final paid claims for widely available non‑ADLT tests for data collection periods beginning in 2027.
A qualifying comprehensive claims database must include at least 50,000,000,000 claims and claims from more than 50 private payors and claims administrators, and be statistically representative of all 50 States and DC.
The bill defines a ‘‘widely available non‑ADLT clinical diagnostic laboratory test’’ as any non‑ADLT test billed by more than 100 providers during the first six months of the year preceding the data collection period.
If CMS cannot obtain qualifying data for a widely available test, payment for a qualified rate period defaults to the prior year’s payment for that test increased by the annual CPI‑U (all items, U.S. city average).
For purposes of the new approach, the bill defines ‘‘final payment rate’’ to exclude denied payments, payments under appeal or review, payments made in error, and payments recouped by the private payor.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
CMS required to contract with certified nonprofit claims entity for high‑volume tests
This amendment directs the Secretary to identify and enter into a contract with a ‘‘qualifying independent claims data entity’’ to report applicable information for widely available non‑ADLT tests for data collection periods beginning in 2027 and reporting in 2028. Practically, CMS must run a procurement and certification process, determine contract scopes (data formats, security, QA), and integrate the incoming feed into existing rate‑setting processes. The timing language — ‘‘as soon as practicable’’ — will pressure CMS to begin procurement and technical integration quickly.
New statutory definitions for entity, database, and 'widely available' tests
The bill creates precise entrance criteria: the qualifying independent claims data entity must be a national nonprofit unaffiliated with payors, providers, or government, certified as a qualified entity, HIPAA‑compliant, and must apply comprehensive QA with statistical testing. The qualifying comprehensive claims database must contain very large volumes of validated claims (statutory floor: 50,000,000,000 claims), cover data from more than 50 private payors/administrators, be representative across all States and DC, include version control to capture final paid claim amounts, and contain the needed lab test claims. The statute also sets the operational test for ‘‘widely available’’ (more than 100 providers billing the test during a six‑month lookback) — a gate that shifts many common tests onto the third‑party data path.
Incorporates third‑party data into the weighted median and adds CPI fallback
The bill amends the weighted‑median calculation to use final payment rates reported either by labs (for many tests) or by the qualifying claims database (for widely available non‑ADLT tests). If CMS cannot secure a contract or the certified database lacks applicable information for a particular widely available test, the law provides a narrowly described ‘‘default payment’’ equal to the prior year’s payment increased by the CPI‑U. The statute defines the ‘‘qualified rate period’’ during which the default applies and clarifies when the default terminates once qualifying data become available.
Rules for low‑volume tests and when no market data are reported
For non‑widely available tests (and ADLTs), the bill preserves the laboratory reporting pathway and provides a tiered approach if no applicable information is reported: first attempt cross‑walking to the most appropriate existing test under the fee schedule; if no comparable test exists, use the statutory gap‑filling process. It also states that if CMS used a cross‑walk or gap‑fill the prior year, it must continue that process or hold the payment flat depending on circumstances — a mechanism that reduces year‑to‑year volatility for niche tests.
Defines 'final payment', moves data collection periods, excludes certain data, and mandates public explanations
The bill tightens what counts as ‘‘applicable information’’ by introducing the ‘‘final payment rate’’ concept (last payment in the year or period, excluding denied, appealed, erroneous, or recouped payments) and requires databases to provide version control so only finalized claim amounts are used. It moves data collection windows forward to 2027/2028 for the new approach, limits the inclusion of Medicaid MCO data for certain early periods, adjusts statutory caps that limit annual payment reductions, and requires CMS to publish an explanation and supporting data for each calculated payment rate so laboratories can assess accuracy.
This bill is one of many.
Codify tracks hundreds of bills on Healthcare across all five countries.
Explore Healthcare 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
- High‑volume clinical laboratories — benefit from a consolidated, market‑based data source that can reduce reporting burden for widely available tests and potentially produce more stable, predictable payment rates than ad‑hoc reporting cycles.
- Qualifying nonprofit claims data entities — stand to gain new contracting and certification opportunities, along with grant‑like franchise power as the statutory source for market data if they meet the criteria and win a CMS contract.
- CMS and rate analysts — gain access to a single, version‑controlled repository of final paid claims (if the database meets the statutory QA and representation standards), which can simplify verification and reduce the need to reconcile disparate lab reports.
Who Bears the Cost
- Private payors and claims administrators — must provide validated, version‑controlled paid claims to the certified database and support QA processes, incurring data‑provision costs and potential operational adjustments.
- Smaller and specialized clinical laboratories — face risk that cross‑walking or gap‑filling will undervalue niche tests when market‑level data are used or when a default CPI rule freezes payments; they also keep obligations for data reporting on non‑widely available tests.
- CMS — must run procurement/certification, oversee compliance and privacy, integrate the feed into rate methodology, and defend any legal challenges; these administrative and implementation costs are significant but not funded in the statutory text.
- For‑profit claims data vendors and alternative data providers — may be excluded by the nonprofit requirement, losing commercial opportunities unless they reorganize or partner with a qualifying nonprofit.
Key Issues
The Core Tension
The central dilemma is between accuracy and feasibility on one hand — Congress wants final, nationally representative paid‑claims data that are feasible for CMS to use — and concentration and responsiveness on the other: relying on a certified nonprofit claims repository may improve data quality and reduce lab reporting burden, but it concentrates influence over Medicare price inputs and risks freezing payments or mispricing niche tests when market data are incomplete or slow to appear.
The bill exchanges the practical difficulty of collecting consistent, final paid rates directly from hundreds of laboratories for a new concentration risk: payment inputs will depend on the availability, accuracy, and governance of one or a small number of certified nonprofit claims repositories. The statutory floors (for example the 50,000,000,000‑claim minimum and requirement for data from over 50 payors) are draconian thresholds that may be intended to ensure representativeness but could limit the field to a very small number of large operators and raise questions about competition and transparency in who qualifies.
The statute attempts to reduce measurement error by insisting on version control and excluding non‑final payments, but implementing that accurately requires significant coordination between payors, claims processors, and the certified entity — and the bill does not appropriate funding to support CMS oversight or the data entity’s onboarding costs.
Operationally, determining ‘‘final payment’’ in complex claims environments is nontrivial: appeals, reconciliations, pharmacy/ancillary carve‑outs, and retroactive adjustments are common. The bill relies on the database to deliver version‑controlled final amounts, but payors’ processes for finalizing payments vary.
The CPI‑based fallback provides a predictable stopgap but sacrifices responsiveness to market shifts and could propagate stale rates during periods without qualifying data. The nonprofit‑only eligibility raises legal and market questions: why exclude for‑profit repositories if they meet QA and privacy standards?
That choice makes sense if Congress is seeking perceived independence, but it also narrows supply and creates incentives for large nonprofits to consolidate market power. Finally, the statutory deadlines (for CMS contract, and for notice‑and‑comment rulemaking by December 31, 2026) are tight relative to the technical work required, leaving implementation risk and likely operational delays that the text does not address.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.