H.R. 2002 (119th)Bill Overview

MATCH IT Act of 2025

Health|Health
Cosponsors
Support
Lean Democratic
Introduced
Mar 10, 2025
Discussions
Bill Text
Current stageCommittee

Referred to the Committee on Energy and Commerce, and in addition to the Committee on Ways and Means, for a period to be subsequently determined by the Speaker, in each case for c…

Introduced
Committee
Floor
President
Law
Congressional Activities
01 · The brief
Plain-English summaryWhat this bill actually does

This bill directs HHS to create standardized definitions, data elements, and protocols to improve electronic patient matching. The National Coordinator must define a minimum patient-matching data set for inclusion in the US Core Data for Interoperability, with data standards and certification adoption timelines.

Why people may split

Privacy risk versus safety gains: liberals emphasize safety, conservatives privacy risks

Watch point

Relative to its intended legislative type, this bill constitutes a substantive policy change that is generally well-structured: it articulates the problem, assigns clear responsibilities, and provides specific timelines for definitions, data standards, certification integration, and incentive design, while preserving consultative processes.

This bill directs HHS to create standardized definitions, data elements, and protocols to improve electronic patient matching.

The National Coordinator must define a minimum patient-matching data set for inclusion in the US Core Data for Interoperability, with data standards and certification adoption timelines.

The bill requires regular review of definitions, incorporates the minimum data set into certified health IT and Medicare interoperability requirements, and creates voluntary Medicare bonus and anonymous reporting programs tied to patient match accuracy.

Passage60/100

Focused, technocratic reform with phased approach and voluntary incentives increases viability; implementation costs and vendor pushback are the main risks.

CredibilityPartially aligned

Relative to its intended legislative type, this bill constitutes a substantive policy change that is generally well-structured: it articulates the problem, assigns clear responsibilities, and provides specific timelines for definitions, data standards, certification integration, and incentive design, while preserving consultative processes.

Contention55/100

Privacy risk versus safety gains: liberals emphasize safety, conservatives privacy risks

02 · What it does

Who stands to gain, and who may push back.

Likely benefits vs burdens50% / 50%
Likely helpedLikely burdened

These are examples from the analysis, not a ranked list of the most-affected groups.

Likely helped
  • Potential benefitMay reduce patient misidentification and related medical errors, improving patient safety.
  • Potential benefitCould lower duplicate testing and administrative waste, reducing costs for patients and providers.
  • Potential benefitCreates consistent data standards, improving interoperability across EHR vendors and health information exchanges.
Likely burdened
  • Potential burdenWill impose compliance and implementation costs on EHR vendors and health care providers.
  • Potential burdenSmaller or resource-limited providers may face disproportionate administrative and upgrade burdens.
  • Potential burdenExpanding required patient data elements could increase privacy and identity theft risks.
03 · Why people split

Why the argument around this bill splits.

Privacy risk versus safety gains: liberals emphasize safety, conservatives privacy risks
Progressive80%

Likely supportive overall because the bill addresses patient safety, interoperability, and duplicative care.

It promotes standardized data, stakeholder consultation, and voluntary reporting while protecting against mandatory match requirements.

Leans supportive
Centrist70%

Generally favorable but cautious: this is a practical attempt to fix a measurable interoperability problem.

Support hinges on realistic implementation timelines, cost containment, and protections for smaller providers.

Leans supportive
Conservative30%

Skeptical due to expanded federal technical standards, potential regulatory burden, and costs to providers and vendors.

Concerned about federal overreach into health IT and risks from collecting more identifiers.

Likely resistant
04 · Can it pass?

The path through Congress.

Introduced

Reached or meaningfully advanced

Committee

Reached or meaningfully advanced

Floor

Still ahead

President

Still ahead

Law

Still ahead

Passage likelihood60/100

Focused, technocratic reform with phased approach and voluntary incentives increases viability; implementation costs and vendor pushback are the main risks.

Scope and complexity
52%
Scopemoderate
52%
Complexitymedium
Why this could stall
  • Projected cost estimates for providers and vendors are not provided
  • Feasibility of achieving 99.9% matching via data set is uncertain
05 · Recent votes

Recent votes on the bill.

No vote history yet

The bill has not accumulated any surfaced votes yet.

06 · Go deeper

Go deeper than the headline read.

Included on this page

Privacy risk versus safety gains: liberals emphasize safety, conservatives privacy risks

Focused, technocratic reform with phased approach and voluntary incentives increases viability; implementation costs and vendor pushback ar…

Unlocked analysis

Relative to its intended legislative type, this bill constitutes a substantive policy change that is generally well-structured: it articulates the problem, assigns clear responsibilities, and provides specific timelines…

Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.

Perspective breakdownsPassage barriersLegislative design reviewStakeholder impact map
Open full analysis