[CHM-375] Removal of HICN for linking variables Created: 06/06/25  Updated: 06/09/25

Status: Done
Project: CMS Hybrid Measures
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Value Sets Priority: Moderate
Reporter: Miranda Schufman Assignee: CHM Admin User
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Impact: Impact to required matching thresholds related to linking variables
Contact Name: Miranda Schufman
Contact Email: miranda.schufman@fairview.org
Institution/Name: MHealth Fairview
Solution: Greetings - can you please provide reasoning as to why the Health Insurance Claim Number (HICN) was removed as an item for matching linking variables along with other remaining items for supportive matching (birth and sex), especially when these are data elements that are regularly captured in a certified EHR?
This will have a negative impact on systems that regularly document HICN and have relied on that as an element for linkage matching alongside the MBI.
Given the challenges related to the data capture, reporting and SHRs related to this measure, I don't believe it's appropriate to remove additional linkage matching options based on a "small number of cases" submitted with HICNs during a voluntary reporting period as stated in CHM-319.

Please consider adding HICNs back in as a linking variable to match against claims.
2026 Reporting Period Hosp Inpt eCQMs:
CMS0529v6, CMS0844v6
2025 Reporting Period Hosp Inpt eCQMs:
CMS0529v5, CMS0844v5

 Comments   
Comment by CHM Admin User [ 06/09/25 ]

Thank you for your question.

The hybrid measures' specifications were updated to align with CMS's discontinuation of HICN and the transition to the MBI. As HICN is not unique to each patient, additional information was required for matching, including date of birth and sex. MBI, however, is a unique identifier, negating the need for date of birth and sex.

CMS Hybrid Measures Team

Generated at Sun Aug 31 08:15:24 UTC 2025 using Jira 10.3.8#10030008-sha1:cdaed80cecc964184c5b19b002388d56f96e274e.