MATCH IT Act of 2025
- Sponsor
- Rep. Kelly, Mike [R-PA-16]
- Committees
- Ways and Means Committee (primary)
- Last action
- Mar 10, 2025
Bottom line
The bill aims to improve patient safety and reduce healthcare costs by standardizing patient identification and incentivizing accurate patient record matching across the U.S. healthcare system.
What it actually does
This bill mandates the Department of Health and Human Services (HHS) to establish a uniform definition for patient match rates and requires the National Coordinator for Health Information Technology to develop a minimum data set for patient matching within the United States Core Data for Interoperability (USCDI). It also incorporates this data set into health IT certification requirements and creates a voluntary bonus measure within the Medicare Promoting Interoperability Program for providers who achieve high patient match rates.
Proponents argue
Proponents argue that accurate patient matching is fundamental to healthcare interoperability, patient safety, and cost reduction. They point to current issues like medical errors, unnecessary repeated tests, and billions in annual costs due to misidentification, asserting that standardized definitions, data sets, and incentives are crucial steps to address these systemic failures.
Opponents contend
Opponents, or those with concerns, might argue that mandating new data standards and certification requirements could impose significant administrative and financial burdens on healthcare providers and health IT vendors, especially smaller entities, without sufficient federal funding to offset these costs. Some may also raise concerns about the potential for increased data collection to inadvertently create new privacy risks, despite the bill's stated intent to protect patient privacy.
The bill is concise and focused, making it accessible for an informed reader to evaluate its core provisions within a reasonable timeframe.
Section 3(a), new Section 3023(a) of the Public Health Service Act
Establishing a Uniform Definition for Patient Match Rate
This provision requires the Secretary of HHS, within 180 days of enactment and in consultation with stakeholders, to develop a standardized definition and metrics for accurate patient matching. This definition must account for common issues like duplicate records, overlaid records (where one patient's data is mixed with another's), multiple matches, and mismatch rates within healthcare organizations. The Secretary must also review and update these standards every three years.
Supporters argue
Supporters argue that a uniform definition is a foundational step, as the current lack of standardization makes it impossible to accurately measure the problem or track improvements. This provision provides the necessary baseline for all subsequent efforts to enhance patient matching.
Critics contend
No specific opposition is typically raised against the concept of a uniform definition itself, as it is seen as a logical prerequisite for addressing patient matching issues. Concerns might arise if the definition is perceived as overly complex or difficult to implement.
Tradeoffs
The tension lies in balancing comprehensiveness (accounting for all types of matching errors) with simplicity, to ensure the definition is practical for widespread adoption across diverse healthcare settings.
Section 3(a), new Section 3023(b) of the Public Health Service Act
Development of a Standard Data Set to Improve Patient Matching
This section directs the National Coordinator for Health Information Technology to identify and adopt a minimum data set within the United States Core Data for Interoperability (USCDI) that is necessary to achieve a 99.9% patient matching rate. This data set will then be incorporated into the USCDI, and data standards for its elements will be created or updated within one year. Extensive consultation with various stakeholders, including federal agencies, is required during this process.
Section 3(b) and 3(c)
Incorporating Data Set into Certification and Medicare Incentives
This provision mandates that the new minimum data set for patient matching be incorporated into health IT certification criteria within 180 days of its finalization. Subsequently, within 24 months, it must be integrated into the Medicare interoperability program requirements. Furthermore, a voluntary bonus measure will be established within the Medicare Promoting Interoperability Program for eligible providers who achieve at least a 90% accurate patient match rate, with safeguards to ensure non-participation doesn't negatively impact scores and attestations remain private.
This 'Rule of construction' clarifies that nothing in the subsection requiring the National Coordinator to identify a minimum data set capable of supporting a 99.9% patient match rate should be interpreted as requiring an entity (e.g., a healthcare provider) to actually *meet* a 99.9% patient match rate.
Section 3(a), new Section 3023(b)(4) of the Public Health Service Act
Why it matters:This is standard legislative practice to clarify the scope and intent of a provision, preventing misinterpretation or unintended mandates. It ensures the 99.9% is a technical capability target for the data set, not a performance mandate for users.
Case for: Supporters would argue this clarification is essential to prevent undue burden on healthcare providers. It focuses the mandate on the *tools* (data set capability) rather than imposing an immediate, potentially unachievable, performance target on *users* of those tools, allowing for a more gradual and realistic improvement process.
Case against: Critics might argue that by explicitly stating that entities are not required to meet the 99.9% match rate, the bill weakens the incentive for providers to truly strive for high accuracy, potentially undermining the overall goal of drastically improving patient matching. They might prefer a more direct, albeit phased, performance requirement.
Estimated impact: This provision significantly impacts the regulatory burden on healthcare providers, shifting the focus from a direct performance mandate to a requirement for health IT systems to *enable* high matching rates.
This special rule ensures that voluntary attestations regarding patient matching rates submitted by eligible providers for the Medicare bonus measure shall not be publicly disclosed.
Section 3(c)(2)(B)
Why it matters:This is a key protection for providers, designed to encourage participation in the voluntary program by mitigating fears of public shaming or competitive disadvantage based on their initial patient matching performance. It's standard practice to place such protective clauses within the specific program details.
Case for: Proponents would argue that this non-disclosure clause is crucial for encouraging honest and widespread participation in the voluntary reporting program. Without it, providers might be hesitant to attest to their actual match rates, especially if they are initially low, thereby hindering the collection of valuable data and the overall improvement effort.
Case against: Critics might argue that public transparency around patient matching rates could create a stronger market incentive for providers to improve, as patients and payers could use this information to make more informed choices. Keeping the data private, they might contend, reduces accountability.
Estimated impact: This provision significantly influences provider willingness to participate in the voluntary bonus and reporting programs, potentially increasing participation rates and data collection.