MedCodeSearch

Guides Deleted codes

What Happens When a Medical Code Is Deleted?

A deleted code is absent from the next release. It is not erased from history, it does not stop being correct for the records already coded with it, and it does not automatically acquire a successor. Those three facts drive how deleted codes are handled here.

Reviewed August 2026 Checked against the official source files Reference, not coding advice

What deletion actually means

Each release of a code set restates the whole set. A code is deleted when it was present in the previous release and is absent from the new one. That is the entire mechanism: presence, then absence, from one published file to the next.

Deletion takes effect on the release's effective date — October 1 for ICD-10, one of the four quarterly dates for HCPCS Level II. It is not retroactive. A record coded while the code was in effect was coded correctly, and stays correct.

Codes are removed for several ordinary reasons, among them:

  • Replacement by more granular codes. One code becomes several, each carrying detail the original did not.
  • Restructuring. A category is reorganized and its codes are renumbered into a different arrangement.
  • Obsolescence. The item, service or concept the code identified is no longer reported — a common reason on the HCPCS side, where codes name real products.

The release addenda state what was deleted. They do not, in general, provide a machine-readable mapping from an old code to a new one, which matters for the next section.

Why a deleted code still matters

Deleted codes remain in circulation long after they leave the active set:

  • Historical records. Claims, charts and registries coded under an earlier release still carry the code.
  • Longitudinal analysis. Any study or report spanning several years has to account for codes that existed for only part of the period.
  • Audits and appeals. Reviewing an old encounter means reading it against the code set that applied at the time, not today's.
  • Plain lookup. Someone reading an old document needs to know what the code meant, whatever its status now.

A reference that simply returns “not found” for a deleted code fails all four of those needs.

What MedCodeSearch does with a deleted code

A code that has ever appeared in an imported release keeps its page. The page changes state rather than disappearing:

  • It is clearly marked as not present in the current release, so the status can never be missed.
  • It shows the description as published in the last release that contained it — the official wording, not a summary.
  • It shows the release history: one entry per release the code appeared in, with the release where it was deleted.
  • It keeps its hierarchy and notes from that release, so the context is intact.

A code that has never appeared in any imported release is a genuine 404, not a page with empty sections. The distinction is deliberate: an empty page implies the code exists and we have nothing on it, which would be false.

Why no replacement is suggested

The rule

MedCodeSearch never invents a replacement code, a successor, or a “use this instead” suggestion for a deleted code. If the official source does not publish a mapping, no mapping is shown.

The temptation is obvious: a user looking up a deleted code usually wants to know what to use now. But a plausible-looking successor derived from string similarity or from what happens to sit nearby in the hierarchy is a guess, and a guess presented as reference data is worse than silence. One deleted code may be superseded by several more specific ones, may be folded into an existing code, or may simply be gone because the thing it named is no longer reported.

What the page does give you is everything needed to answer the question properly: the last official description, the release in which the code disappeared, its position in the hierarchy, and links to that release's full change list. Where the official source does publish a cross-reference — as some HCPCS records do — it is shown as the file provides it, without embellishment.

A real example

S23.420 — “Sprain of sternoclavicular (joint) (ligament)” — was present in the FY 2026 ICD-10-CM release and is absent from FY 2027. Its page is still here. It shows the FY 2026 description, states that the code is not in the current release, and lists the releases it appeared in. What it does not do is tell you what to use instead, because the file does not say.

The complete list of what FY 2027 removed is on Code Updates: ICD-10-CM FY 2027, deleted codes.

Codes can come back

Deletion is not always permanent. A code that was removed can appear again in a later release — MedCodeSearch classifies that as reactivated rather than as a new code, because the code's history did not start over. On the page this shows up as a gap in the release history followed by a return, which is exactly what happened.

Finding what a release removed

Every imported release has an update page listing its changes, split by type:

Or start at Code Updates for every release MedCodeSearch has imported. If you already have a code in hand, looking it up directly is faster: a deleted code resolves to its page and tells you its status immediately. See How to Search ICD-10 Codes.

Official sources

Where the facts on this page come from. MedCodeSearch is an independent reference service; these organizations publish the code sets themselves.

Look up a code

Search every current ICD-10-CM, ICD-10-PCS and HCPCS Level II code, or browse a set from the top of its hierarchy.

Browse ICD-10-CM Browse ICD-10-PCS Browse HCPCS Level II Code updates

This guide explains how the code sets are built and published. It is not coding, billing, legal or medical advice, and it never recommends a code for a specific patient or claim. See the Disclaimer and Methodology pages.