The next round of ICD-10-CM and ICD-10-PCS changes is already taking shape. On July 30, 2026, the National Center for Health Statistics published a Federal Register notice setting the ICD-10 Coordination and Maintenance (C&M) Committee’s fall meeting for September 15-16, 2026, with 38 code topics on the table. Nothing discussed at the meeting is final — this is the start of the FY2028 pipeline, not the end of it — but it’s the earliest reliable signal of where the code sets are headed, and coding teams that wait for the final rule to react are already behind.
What’s on the September agenda
The committee, run jointly by CDC’s National Center for Health Statistics (diagnosis codes) and CMS (procedure codes), splits its two-day session by code set. Both halves run virtually, with advance registration required through a CDC-hosted Zoom link.
ICD-10-PCS: 23 procedure topics
The procedure-code half covers 23 topics, including several that reflect how fast device-based care is moving:
- Brain-computer interface device implantation and adjustment
- Spinal cord stimulation procedure updates
- New pharmaceutical administration approaches
- Additional device and technology-driven procedure refinements slated for FY2028
Notably, CMS will not hold a live public forum for the procedure-code topics this cycle — comments go through written submission only, to ICDProcedureCodeRequest@cms.hhs.gov.
ICD-10-CM: 15 diagnosis topics
The diagnosis-code half, chaired by NCHS, covers 15 topics, including proposed codes and classification changes for adverse childhood experiences, carotid web conditions, and updates to sepsis classification — an area that has generated coding and CDI disputes for years because of how loosely “sepsis” gets documented relative to clinical criteria.
The comment deadlines that actually matter
Two dates determine whether a proposal makes it into the FY2028 code set at all. Written comments on procedure-code topics being considered for an April 1, 2027 implementation date are due October 16, 2026; comments on topics being considered for an October 1, 2027 implementation date are due November 13, 2026. Miss the window and a topic either falls to the next cycle or goes final without the field’s input. For organizations with a stake in how a specific procedure or diagnosis gets classified — device manufacturers, specialty societies, health systems doing the procedures in question — this is the only point in the process where public comment shapes the outcome.
Why a two-day meeting in September is a coding operations problem
Thirty-eight topics across two agendas, two comment deadlines, and two implementation dates is a lot to track by hand, and it’s a recurring problem, not a one-time event — NCHS and CMS run this cycle twice a year, in March and September. The codes set to take effect this October 1 under FY2027 — including the roughly 238 new ICD-10-CM entries covered when that final rule dropped — trace back to proposals first surfaced at meetings like this one, sometimes as far back as September 2025. Coding and CDI teams that rely on manually updated crosswalks or a vendor’s periodic code-set refresh typically don’t see the practical effects of a C&M meeting until the final rule drops months later, at which point there’s no runway left to update documentation templates, train coders on the new procedure logic, or flag which service lines will be affected.
The topics themselves also skew toward areas where documentation specificity already lags the codes needed to support it. Brain-computer interface procedures and spinal cord stimulation updates require documentation detail that most EHR templates weren’t built to capture — implant location, device model class, stimulation target, and revision-versus-initial-placement status all affect which PCS code applies. Sepsis classification changes tend to expose exactly how inconsistent bedside documentation is against SEP-1 and clinical criteria, and any change to the diagnosis code’s structure ripples straight into severity-of-illness and mortality-risk calculations, not just the claim line. A code doesn’t fix a documentation gap by itself, and when specificity requirements move faster than documentation habits do, the usual result is a spike in queries, denials, or both.
That’s the pattern coding leaders have seen with every recent specificity expansion: the code goes final, claims start denying for lack of supporting detail, and only then does the documentation training catch up. A meeting in September that previews what’s coming is a chance to break that sequence — updating templates and coder guidance before the October 2027 effective date, rather than reacting to denials after it.
Where continuous coding intelligence helps
This is the practical argument for agentic AI in medical coding rather than a static rules engine updated on a fixed release schedule: a system that can ingest a C&M topic packet in September, map it against existing chart documentation patterns, and flag which specialties and templates need attention gives a coding team months of lead time instead of weeks. Static systems wait for the final rule; agentic ones can start working the moment the proposal is public.
That’s the gap Medikode’s automated medical coding platform is built to close — tracking regulatory pipeline changes like this one as they emerge, not after they’ve already become a compliance deadline.