CPT and ICD-10 updates land on a predictable schedule. The practices that absorb them without a January denial spike prepare in the autumn.
Code set changes are one of the few billing disruptions with a published date. ICD-10-CM updates take effect October 1. CPT and HCPCS updates take effect January 1. Neither should be a surprise, and yet both reliably produce a denial spike in practices that treat them as an IT update.
This page deliberately describes the pattern rather than listing specific code changes. A code list published once and left alone becomes wrong the following October, and a stale list is actively dangerous — it looks authoritative right up until it denies a claim. Always work from the current year's official release.
Why the spike happens
It is almost never the codes themselves. It is the systems and habits around them:
- Superbills and favourites lists still contain deleted codes. Providers pick from muscle memory.
- The charge description master was not updated, so institutional claims are built wrong at the source.
- Payer policies lag the code set. A code can be valid and still not be recognised by a specific payer's edit for weeks.
- Scrubber rules reference old codes and stop catching real errors.
- Prior authorisations obtained under an old code may not map cleanly to its replacement.
A workable timeline
Two to three months before the effective date Get the change list for your specialty — additions, deletions, revisions. Identify which of your top 50 billed codes are affected. That short list is where nearly all of your exposure sits.
One to two months before Update the charge description master, superbills, EMR favourites lists and order sets. Update scrubber rules. Brief the providers on the specific codes they use — not the whole change list, which nobody reads.
The month before Confirm the clearinghouse and EMR vendor have loaded the new set. Ask payers about transition policies: some allow a grace period, some do not.
The first month after Watch denials weekly rather than monthly. A code-set problem is visible within two weeks and cheap to fix then. Left until the monthly report, it has already generated a month of rework.
The documentation trap
Coding changes often introduce greater specificity requirements — a new code family may require laterality, a stage, or an encounter type that the old code did not.
If the documentation does not contain that detail, the coder cannot use the specific code, and the unspecified code may be denied or down-coded. The change is not a coding change; it is a documentation change. Brief providers on what they now need to write, not just on what the code number is.
Do not forget authorisations in flight
An authorisation approved under a code that no longer exists on the date of service is a denial waiting to happen. Any authorisation spanning the effective date should be checked and, if needed, re-obtained under the replacement code.
The measurement
Compare the denial rate for the four weeks after the effective date against the four weeks before. A well-prepared practice sees a small, brief bump. A spike that persists past six weeks means the update was applied to the software but not to the workflow.
