ICD-10 Annual Updates Every October and What Medical Billers Must Check to Prevent Claim Denials

Get a summary of this article with your favorite AI
Key Highlights
- •ICD-10 annual updates introduce new, revised, and invalid codes, along with changes to coding guidelines. FY 2027 includes 190 new ICD-10-CM codes and 103 new ICD-10-PCS codes.
- •Apply the correct code-set version using the date of service for outpatient reporting and the discharge date for applicable inpatient reporting, not the claim submission date.
- •Verify official CMS and CDC/NCHS files, including code tables, coding guidelines, addenda, errata, and conversion tables. Monitor mid-year updates and corrections.
- •Update EHRs, billing systems, code mappings, claim edits, and internal references. Test claims across effective-date boundaries and retain previous releases.
- •Investigate ICD-10-related denials by checking reporting dates, code validity, official instructions, system versions, submitted claim data, and payer requirements.
Every October, your coding and billing teams face a new annual ICD-10 release. But downloading the latest code files doesn't mean your organization is ready to use them. Your EHR, billing system, code mappings, claim edits, and staff references all need to reflect the applicable release.
And there's another detail to watch. ICD-10-CM and ICD-10-PCS don't always follow identical effective periods. Additional updates and corrections can also appear during the year.
So, where should you start? Confirm the correct release, review the official changes, update your systems, and test the claims that cross an effective-date boundary.
Let's walk through what your team should check and how to make the process repeatable.
What Changes in the Annual ICD-10 Code Update Each October?
The annual update can introduce new codes, retire existing ones, revise descriptions, and change coding instructions. Your first task is to identify what changed in each code set and which changes affect your organization's reporting workflows.
The FY 2027 figures provide a useful example.
| FY 2027 update | ICD-10-CM | ICD-10-PCS |
|---|---|---|
New codes | 190 | 103 |
Codes invalid effective October 1, 2026 | 30 | 38 |
Total codes in the updated classification | 74,879 | 79,258 |
The ICD-10-CM figures reflect 184 diagnosis codes finalized by the proposed-rule stage and six additional diagnosis codes finalized later, bringing the number of new codes to 190. The FY 2027 IPPS Final Rule provides the supporting code-change information.
The original FY 2027 announcement included 101 new ICD-10-PCS codes. CMS subsequently added two more through its FY 2027 PCS errata, bringing the total to 103. The revised total is 79,258 codes.
1. New, Revised, And Invalid Codes Need Separate Checks
Compare the new release with the version your team currently uses. Look for four types of changes:
- New codes that become available for reporting during the new effective period.
- Revised descriptions or titles that require updates to internal references and code displays.
- Invalid or deleted codes that should no longer be used for dates within the new reporting period.
- Updated coding instructions that may affect how staff select or report a code.
For example, the FY 2027 PCS errata introduced two additional codes:
| Code | Description |
|---|---|
XW0U3CC | Introduction of recombinant human bone morphogenetic protein-2 with collagen scaffold into joints, percutaneous approach |
XW0U4CC | Introduction of recombinant human bone morphogenetic protein-2 with collagen scaffold into joints, percutaneous endoscopic approach |
Both codes are part of New Technology Group 12 and became effective October 1, 2026. CMS also notes that these additions do not affect MS-DRG assignment.
This is a useful reminder that your team needs to check for updates after the initial release, not just when it first downloads the files.
2. Coding Guidelines and Supporting Instructions Can Change Too
Don't stop at the code list. Review the official coding guidelines and any applicable supporting instructions for the new reporting period.
For ICD-10-CM, the FY 2027 Official Guidelines identify narrative changes through bold text and moved material through underlining compared with the April 2026 version.
For ICD-10-PCS, review the guidelines included with the applicable release package. Also check whether revised titles, addenda, or corrections affect the procedures your organization reports.
A code can remain available while its reporting instructions or supporting guidance change. That's why reviewing the guidelines alongside the code files matters.
Also Read: ICD-10-CM vs. ICD-10-PCS: How Medical Coders Can Avoid Coding Errors and Choose the Right Code
Which ICD-10 Version Applies to a Claim's Date of Service or Discharge?
Use the code-set release applicable to the date of service or inpatient discharge, not the date the claim is prepared or submitted. The applicable date depends on the reporting context and the code set you're using.
The CMS Medicare Claims Processing Manual, Chapter 23, Section 10.6 explains that diagnosis codes must be reported based on the date of service, including the date of discharge when applicable, rather than the date the claim is prepared or received.
1. ICD-10-CM And ICD-10-PCS Have Different FY 2027 Reporting Periods
Here are the current FY 2027 effective periods published by CMS and CDC/NCHS.
| Code set | FY 2027 effective period | Relevant reporting date |
|---|---|---|
ICD-10-CM | October 1, 2026 to September 30, 2027 | Date of service, or discharge date where applicable |
ICD-10-PCS | October 1, 2026 to March 31, 2027 | Inpatient hospital discharge date |
You can verify these periods on the CDC ICD-10-CM files page and the CMS ICD-10 release page.
Notice that the FY 2027 PCS package currently listed by CMS ends on March 31, 2027. Don't automatically extend that package through September 30 just because it carries the FY 2027 label. Check CMS for the next applicable release before coding discharges after March 31.
2. Apply The Right ICD-10-CM Release to The Encounter
For outpatient services, use the ICD-10-CM release applicable to the date of service. For inpatient facility reporting, use the release applicable to the discharge date.
The FY 2027 ICD-10-CM release applies to services and discharges from October 1, 2026, through September 30, 2027.
Consider an outpatient example.
A patient receives a service on September 30, 2026, but your billing team submits the claim on October 10, 2026.
Which version should you use?
Use the ICD-10-CM release applicable to September 30, 2026. In this case, that's the April 1, 2026 FY 2026 release, not the FY 2027 release. The later submission date doesn't move the encounter into a new reporting period.
Now consider an inpatient stay. A patient is admitted on September 29, 2026, but discharged on October 2, 2026. For applicable inpatient diagnosis and procedure reporting, the October 2 discharge date determines the relevant release.
These examples show why your systems need date-aware code validation. A single current-year code table isn't enough to process claims from different reporting periods correctly.
3. Check The Inpatient Discharge Date For ICD-10-PCS
ICD-10-PCS is used for applicable inpatient hospital procedure reporting. The patient's discharge date determines which PCS release applies.
For example, a patient discharged on October 2, 2026, falls within the FY 2027 PCS period currently published by CMS. A discharge on March 31, 2027, also falls within that period.
For a discharge after March 31, 2027, check CMS for the subsequent applicable PCS release rather than assuming the October package remains valid.
Also remember that ICD-10-PCS isn't a replacement for CPT or HCPCS on outpatient and professional claims. Your team should confirm which code set applies before making any system changes.
4. Don't Confuse a Mid-year Release with the Next Annual Update
October 1 is the main annual changeover, but it isn't the only date your team should monitor.
For example, CMS implemented 80 new ICD-10-PCS codes effective April 1, 2026, for inpatient discharges through September 30, 2026. CDC/NCHS also published an April 1, 2026 ICD-10-CM release for services and discharges during that period.
These were separate FY 2026 updates, not part of the FY 2027 October release. You can review the CMS April 2026 PCS announcement for the procedure-code changes.
The practical point is simple: monitor official release announcements throughout the year. Don't assume that every code-set update follows a fixed quarterly schedule or that nothing changes between October 1 dates.
Which Official ICD-10 Files Should Billers Review?
Download the applicable files from CDC/NCHS and CMS, depending on the code set, and verify that each file matches the reporting period you need. Don't rely on a third-party code lookup tool or an old internal spreadsheet as your authority for code validity.
1. Use The Official Release Package For Each Code Set
CDC/NCHS maintains the official ICD-10-CM materials, while CMS publishes the ICD-10-PCS materials. CMS also provides a consolidated ICD-10 resource page with links to the current releases.
Your team should review the files relevant to its reporting responsibilities.
| ICD-10-CM files | What to review |
|---|---|
Code Tables, Tabular List, and Index | Confirm code entries, descriptions, and instructions. |
Code Descriptions in Tabular Order | Check the updated code descriptions. |
Official Coding Guidelines | Review changes to reporting instructions. |
Addendum | Identify documented additions and changes. |
Conversion Table | Compare the previous and current release. |
POA Exempt Codes | Check the applicable inpatient present-on-admission reporting list. |
| ICD-10-PCS files | What to review |
|---|---|
PCS Codes File | Confirm the complete procedure-code list. |
Code Tables and Index | Review the valid code combinations and construction instructions. |
Order File | Check long and abbreviated code titles. |
Official Coding Guidelines | Review current procedure-reporting instructions. |
Addendum | Identify documented additions and changes. |
Conversion Table | Compare codes between releases. |
Version Update Summary | Review the scope of the release. |
Errata | Check for corrections or additional changes after publication. |
You don't necessarily need every file for every workflow. For example, the POA-exempt list is relevant to inpatient diagnosis reporting, while the PCS order file supports inpatient procedure-code references.
2. Know The Difference Between Addenda, Errata, And Conversion Tables
These supporting documents serve different purposes, so don't treat them as interchangeable.
- Addenda identify additions and changes associated with a code-set release.
- Errata communicate corrections to previously published materials. The FY 2027 PCS errata is a practical example because it adds two procedure codes beyond the original announcement.
- Conversion tables help compare code entries between releases. They are useful for identifying changes, but a mapped code isn't automatically a clinically equivalent replacement.
- Version update summaries provide an overview of the changes. They help you plan your review but don't replace the official code files or guidelines.
When reviewing a file, record its official title, release label, effective period, download date, and source URL. This makes it easier to identify which version was reviewed and whether a newer file replaced it.
Also Read: ICD-10-CM Code Structure Explained: How Coders and Billers Build a Diagnosis Code
What Must Billing Teams Update and Test Before Using the New ICD-10 Version?
Update the systems, mappings, edits, and internal references that use ICD-10 data, then test representative claims across the relevant effective dates. A successful file upload doesn't automatically mean every part of your billing workflow is ready.
1. Review Every System That Stores or Validates Code Data
Start by identifying where your organization uses ICD-10 codes. Depending on your setup, that may include:
- EHR and practice management systems.
- Billing platforms and encoder applications.
- Clearinghouse connections and claim scrubbers.
- Custom code mappings and validation rules.
- Shared spreadsheets, code lists, and specialty-specific references.
- Reports and workflows that group claims by diagnosis or procedure.
- MS-DRG Grouper and Medicare Code Editor software for applicable inpatient hospital workflows.
For FY 2027, CMS lists Version 44 for the MS-DRG Grouper and Medicare Code Editor. The MCE uses edits to identify errors in ICD-10 codes reported on claims for discharges on or after October 1, 2026. Check the CMS MS-DRG classifications and software page for the applicable software and supporting files.
Ask your EHR, encoder, billing-system, and clearinghouse vendors which release they have loaded and when it will be available in production. Then compare the system's contents with the official files.
Pay particular attention to locally maintained resources. A vendor may update the central code library, but that doesn't automatically update a spreadsheet, custom edit, or reference list your team manages separately.
2. Test Claims on Both Sides of The Effective-date Boundary
Use test scenarios that cover different dates and reporting contexts. Include cases where the service occurred before October 1 but the claim is submitted afterward.
| Test scenario | What to verify |
|---|---|
Outpatient service dated September 30, 2026 | The applicable FY 2026 ICD-10-CM release is selected. |
Outpatient service dated October 1, 2026 | The FY 2027 ICD-10-CM release is selected. |
Inpatient discharge dated September 30, 2026 | The applicable earlier CM and PCS releases are used. |
Inpatient discharge dated October 1, 2026 | The FY 2027 CM and PCS releases are used. |
Inpatient admission on September 29 and discharge on October 2 | Date-based reporting follows the applicable discharge-date rules. |
Earlier service submitted after October 1 | The original reporting-date release is retained. |
Newly added or revised code | The code and its instructions match the applicable official files. |
Code invalidated on October 1 | The system applies the correct validity dates instead of treating the code as current indefinitely. |
For hospitals using the FY 2027 PCS release, include XW0U3CC and XW0U4CC in the relevant code-file checks. Also confirm that the associated software and edits reflect the current CMS package.
Record the test result, any issue identified, and who resolved it. If a test fails, correct the mapping or configuration and rerun it before the updated release moves into production.
Why Should You Track Payer Policy Updates Separately From ICD-10 Code Changes?
Track payer policy updates separately because a code being valid in the official ICD-10 classification doesn't automatically mean a particular service is covered or payable.
The code set establishes how a diagnosis or procedure is classified and reported. A payer's coverage policy establishes additional requirements that may apply to the service, plan, or benefit.
For example, a new diagnosis code may become valid on October 1, while a payer's medical policy or authorization requirements have a different effective date. Your team needs to check both rather than assume that the code update changes the coverage decision.
Maintain two separate records:
| Register | What it tracks |
|---|---|
ICD-10 release register | Code-set version, effective dates, revisions, additions, deletions, and official corrections |
Payer policy register | Policy name, affected service or code, effective date, source, responsible owner, and operational action |
When a payer announces a change, check the actual policy and its effective date. Determine whether it affects your organization's services, contracts, or billing workflows.
Don't treat a payer's coding requirement as a universal ICD-10 rule. And don't assume that a newly available diagnosis or procedure code automatically establishes coverage.
How Can Your Team Implement ICD-10 Annual Updates Without Using Outdated Files?
Use a documented implementation process with an accountable owner for each stage and evidence showing that the work was completed. This turns the annual update into a controlled release process rather than a last-minute collection of system changes.
Here is a workflow your team can adapt.
| Stage | Required action | Suggested owner | Evidence to retain |
|---|---|---|---|
Source verification | Download the applicable official files and check for corrections. | Coding manager | Source URLs, release labels, and download dates |
Change review | Identify additions, revisions, invalid codes, and affected workflows. | Coding lead | Change-impact register |
Configuration | Update code tables, mappings, claim edits, and internal references. | IT / vendor / system administrator | Configuration log and vendor confirmation |
Testing | Validate effective dates, code validity, mappings, and representative claims. | Coding QA / billing operations | Test cases, results, and issue log |
Approval | Authorize the applicable release for production use. | Coding or compliance leadership | Named reviewer and approval date |
Communication | Tell staff which release is active and where to find approved references. | Coding manager | Staff communication or training record |
Monitoring | Watch for official corrections and version-related claim issues. | Coding and revenue cycle teams | Monitoring log |
Archiving | Preserve superseded releases and implementation records. | Compliance / document control | Archived package and version history |
A smaller billing team may assign several stages to one person. A hospital or multi-location organization may divide them across coding, IT, compliance, and revenue cycle operations.
The sequence is a recommended operational model, not a CMS-mandated implementation calendar. Complete the necessary checks before the applicable effective date where the files are available in advance.
Also, don't delete older code files just because the new release is live. Your team may still need them to review earlier service dates, respond to payer questions, or investigate historical claims.
The goal is traceability. Months later, someone should be able to identify which release applied to a claim, which system version was used, who approved the update, and where the supporting files were retained.
What Should You Check If a Claim Is Denied After an ICD-10 Update?
Start by confirming whether the code-set version used on the claim was valid for the applicable service or discharge date. Then investigate whether the issue came from the code itself, a local system reference, or a separate payer requirement.
Use this focused review:
| Check | Question to answer |
|---|---|
Reporting date | Which ICD-10 release applied to the service or discharge date? |
Code validity | Was the reported code valid during that period? |
Official instructions | Did a revised description, coding instruction, or correction affect the code? |
System version | Did the EHR, encoder, billing platform, or claim edit use the correct release? |
Claim data | Does the submitted code match the code in the source record and outbound claim? |
Payer requirement | Is the denial reason based on code validity, a separate coverage rule, or another requirement? |
For example, suppose a claim for a service dated October 3, 2026, is submitted with a code that became invalid on October 1. Your team should check the FY 2027 files, confirm the code's status, and review the system's code table and validation rules.
But what if the code was valid for the reporting date? Keep the official release evidence and review the payer's stated reason before deciding whether a correction or further review is appropriate. Don't replace a supported code simply because an edit or denial message flags it.
While building Bill Matters, we noticed a common problem, a denial may flag a diagnosis code, but that doesn’t necessarily mean the code is wrong. Sometimes, the code is valid for the service or discharge date, but an outdated local reference or claim edit still flags it. In other cases, the issue may be related to the payer’s coverage rules or documentation requirements.
That’s why it’s important to understand what’s actually behind a denial before making changes to a claim that may already be correctly supported.
Bill Matters helps your team review denials by analyzing claim and denial documents, identifying relevant or missing evidence, and drafting appeals for your team to review and approve.
Your team remains in control of official ICD-10 verification and final coding decisions.
ICD-10 giving you code confusion? Let's make denials less of a puzzle.
Speed up denial reviews with Bill Matters. Less guesswork, more clarity, and appeal drafts ready for your team's review.
ICD-10 Accuracy Starts with the People Behind Every Claim
Annual ICD-10 updates bring changes that coding teams need to understand and apply correctly. Getting those changes right also depends on clear communication between the people documenting care and the teams handling coding and billing.
The American Hospital Association (AHA) covered the FY 2027 ICD-10-CM changes in an expert session on September 23, 2026, featuring Susan Latham, RHIT, CCS, ICD-10 Coding Consultant at the AHA. The session covers the diagnosis-code changes effective October 1.
These changes affect teams across the healthcare revenue cycle. Doctors need to provide clear clinical documentation, practice owners need to monitor coding and compliance, and medical billing companies need to communicate coding requirements and documentation gaps to the practices they support.
Regular feedback between physicians, coders, and billing teams helps in identifying recurring issues, addressing gaps early, and maintaining consistency across claims.

