HCC overlap check

Paste a set of codes. See which HCCs they map to under each published model, and where two of them collapse into one.

How to use this page

What a set of codes actually yields once the model collapses the duplicates.

Paste the codes — commas, spaces or new lines, with or without the decimal point.
Pick the code set for the date of service. A code only maps in the years it existed.
Each model is shown separately, because which one applies depends on the payment year and the plan.
Two codes on one HCC count once. An HCC struck through is outranked by a higher one in the same family and contributes nothing.
The link at the bottom lays the same codes across every loaded year, which is the view for an audit that spans years.

What this page does not do

No score. This reports which HCCs a code set yields, not what they are worth — scoring needs coefficients, and for the historical years those are not loaded.
It is not advice about which codes to report. A code belongs on a claim when the documentation supports it.

Each cell is the HCC that code maps to that year. shaded means the same HCC comes from another code in the set; struck means a higher HCC outranks it; — means the code did not exist that year.

CMS23

Code	FY2018	FY2019	FY2020	FY2021	FY2022	FY2023	FY2024	FY2025	FY2026	FY2026	FY2027
T40.4X1A	·	55	·	—	—	—	—	—	—	—	—

CMS24

Code	FY2018	FY2019	FY2020	FY2021	FY2022	FY2023	FY2024	FY2025	FY2026	FY2026	FY2027
T40.4X1A	·	·	55	—	—	—	—	—	—	—	—

← Back to one year

Mapping and hierarchy come from the CMS model packages, which are public domain. This reports what a published model does with the codes given. It is not advice about which codes to report — that is answered in the chart.