FY 2027 ICD-10-CM: 190 New Codes and What Actually Changes
Welcome! Let me say this clearly from the start: the number of new ICD-10-CM codes is not the real problem — deployment is. In my work as a physician executive and physician consultant, I see practices treat the annual ICD-10 update like a coding-department event, when in reality it is a documentation, template, and workflow event that touches far more than the code file itself.
190
That is the headline number for FY 2027 ICD-10-CM: 190 new diagnosis codes, 30 deletions, and 4 code description revisions, effective for encounters and discharges from October 1, 2026 through September 30, 2027. Those figures reflect reportable diagnosis codes as shown in the FY 2027 ICD-10-CM addendum and code files. Published counts can vary because CMS and CDC release the addendum and code files rather than a single headline total, and different parties may count non-billable classification headers differently. The code set changed on October 1. The more important question for your organization is this: did your templates, pick lists, favorites, scrubbers, and provider habits change with it?
Most people get this wrong because they focus on whether coders have the update memo, not whether the rest of the revenue cycle has operationalized it. That is where the revenue cycle starts to leak. And that is where physician-led oversight makes such a difference: we do not stop at “the code exists.” We ask whether the documentation, charge capture process, and front-end workflows now support compliant use of that code.
What changed in FY 2027 ICD-10-CM
For FY 2027, the federal update reflects the following, based on the CMS and CDC/NCHS ICD-10-CM addendum and code files:
- 190 new diagnosis codes
- 30 deletions
- 4 code description revisions
- Effective date: October 1, 2026
- Applies to: encounters and discharges from October 1, 2026 through September 30, 2027
The FY 2027 ICD-10-CM Official Guidelines also include revisions and clarifications affecting:
- Sepsis
- Cancer treatment
- Hypertension
- Genetic disorders
- DES exposure
One structural point matters here as well: Chapter 17 was expanded in title to include genetic disorders.
And yes, for contrast only, the AMA released the CPT 2027 code set on September 9, 2026, effective January 1, 2027. But this article is not about CPT. This is about what changed already in ICD-10-CM on October 1 and what your organization has to do operationally right now.
The real issue is not awareness. It is deployment.
Here is the pattern I see over and over in the operational side of the practice.
A practice tells me, “Our coders reviewed the update.” That sounds reassuring. But by January, the same practice is dealing with avoidable rework because the coders knew the new codes while the system around them did not. The EHR favorites still point providers to outdated diagnosis selections. Specialty templates still steer documentation toward old terminology. Charge capture tools were never rebuilt. Scrubber logic was not reviewed. Denials and manual corrections begin to stack up downstream, and everyone acts surprised even though the root cause started months earlier.
That is not a coding knowledge problem. That is a workflow deployment problem.
This is why I continue to tell leaders that revenue integrity is built operationally, not just educationally. If your people know the rule but your infrastructure still points them toward last year’s behavior, your team will spend the next quarter cleaning up preventable errors. This is where revenue cycle management either holds together or quietly unravels.
What actually has to change
If you want the FY 2027 ICD-10-CM update to function inside your organization, there are five areas that require attention.
1. Diagnosis pick lists and favorites
Start here, because this is where old habits hide.
If your physicians, APPs, or staff use diagnosis favorites, specialty pick lists, problem-based shortcuts, or encounter-specific preference lists, those tools must be reviewed against the FY 2027 file. New codes do not matter if your users cannot find them easily or if deleted codes are still embedded in routine workflow.
I advise practices to ask:
- Which deleted codes are still visible in favorites?
- Which new codes need to be added to specialty-specific pick lists?
- Are there commonly used diagnosis pathways that still route users to outdated options?
- Are high-volume service lines using custom lists that bypass central updates?
This is one of the most overlooked parts of annual code maintenance. People assume the software update solved the workflow issue. It often does not.
2. Templates must support the new documentation reality
Templates are never neutral. They teach behavior.
If the FY 2027 ICD-10-CM changes affect how a condition is described, staged, linked, or clarified, then your templates and smart phrases should be reviewed immediately. Otherwise, providers continue documenting in a pattern built around the old code structure.
That is especially important when guideline clarifications touch areas like:
- sepsis
- cancer treatment
- hypertension
- genetic disorders
- DES exposure
When the Official Guidelines change, documentation support needs to change with them. The annual update is not just a coding-file event. It is a clinical documentation event.
Documentation accuracy is rarely isolated to one code set. Your diagnosis support, leveling logic, and claim defensibility all connect.
3. Charge capture and scrubber edits need active review
A surprising number of organizations leave money and time on the table because they assume scrubber logic, edits, and charge tools will somehow “catch” everything after go-live.
They will not catch everything.
Your charge capture workflows and edit logic should be evaluated for:
- deleted diagnoses still triggering in legacy workflows
- new diagnoses that need payer-facing validation support
- diagnosis-to-procedure pairing review where relevant
- downstream edits that may now fire differently because descriptions or groupings changed
- reporting logic tied to retired diagnosis values
This is where audit readiness becomes practical. You are not just reviewing what changed in the code book. You are reviewing where that change touches claims, edits, and operational friction.
And when exposure increases, it usually does so quietly — through outdated build, inconsistent documentation, and “temporary” workarounds that become normalized.
4. Provider education has to be brief, targeted, and behavior-based
Most people get this wrong by over-educating the wrong audience and under-educating the high-impact users.
Your physicians and clinical teams do not need a lecture on every new diagnosis code. They need focused education on what changed in their workflow, their specialties, and their documentation habits.
That means teaching things like:
- what no longer appears in favorite lists
- what new diagnosis options they should expect to see
- what documentation details now matter more
- which shortcuts or macros need to stop being used
- which service lines are seeing the biggest operational impact
As a physician leader, I have found that short, specialty-specific guidance outperforms long update packets almost every time. Adoption improves when education is operational and immediate.
5. Monitor after go-live or you are only guessing
October 1 implementation is not the finish line. It is the start of the observation period.
After go-live, monitor:
- diagnosis utilization shifts
- claim edit volume
- denial patterns
- manual correction rates
- provider variation by specialty or location
- deleted-code usage that still appears in workflow logs or exception queues
This is where strong monitoring becomes measurable. If the update was deployed well, you should see stable workflow adoption and lower rework. If it was not, your metrics will tell you quickly.
I encourage leadership teams to review the first 30 to 90 days with discipline. Not because you can eliminate every issue, but because early pattern recognition protects healthcare revenue integrity and reduces avoidable operational waste.
A physician-led view of what this requires
As a physician consultant, I want to be direct: the organizations that handle annual ICD-10 updates best are usually not the ones with the biggest coding department. They are the ones that understand that code changes live inside human behavior.
If your coders are updated but your templates are stale, your workflow is stale.
If your EHR has the new file but your providers still click last year’s favorites, your workflow is stale.
If your policy memo is complete but your scrubber build is incomplete, your workflow is stale.
That is why physician-led revenue integrity matters. It brings the coding rule, the documentation expectation, the operational build, and the revenue consequence into the same conversation.
What leaders should do this week
If you have not completed your FY 2027 ICD-10-CM deployment review, start with this short checklist:
- Validate deleted and new diagnosis codes in high-volume pick lists and favorites.
- Review specialty templates and smart phrases for documentation alignment.
- Test charge capture tools and scrubber edits for retired values and new logic needs.
- Give providers concise, specialty-specific update guidance.
- Monitor edits, denials, and correction trends after October 1 go-live.
None of this is glamorous. All of it matters.
The closing rule
If the code file changed but your workflow did not, your ICD-10 update is not finished.
Schedule a consultation
If you would like physician-led guidance on documentation, coding, or audit readiness, I invite you to schedule a consultation here: https://drsloankelly.com/contact.
Thank you for reading and for doing the hard work of leading through change with clarity.
Dr. Dreama Sloan-Kelly, MD, CCS, CPC / CEO/President, Dr. Sloan-Kelly Consulting LLC