FY 2027 ICD-10-CM Changes Take Effect October 1: A Medical Practice Readiness Checklist starts with an important calendar clarification: the transition begins October 1, 2026, not October 1, 2027. For practice administrators and revenue cycle leaders, preparation means more than confirming that a new release is available. It means establishing which dates apply, reviewing the official materials, and documenting how local billing workflows will handle the transition.
CMS identifies the applicable dates and lists the release resources. The operational checks below are recommendations for organizing your preparation, not additional CMS requirements. Keeping those categories separate helps your team distinguish an official release fact from a local implementation decision that still needs confirmation.
Confirm the October 1 Date Boundary Before Changing Your Workflow
For more context, review auditing and compliance.
CMS identifies October 1, 2026, through September 30, 2027, as the applicable discharge and patient-encounter date range for FY 2027 ICD-10-CM changes. Begin your transition plan with that range. Do not assume that the day a staff member opens, reviews, or submits a claim determines which release applies.
Write the date boundary into your internal transition record. Describe the relevant encounter or discharge date alongside the release period, rather than labeling everything simply “current.” That makes the record more useful when staff handle work from different periods during the same week.
Keep the Prior Release and the New Release Distinct
CMS specifies April 1, 2026, through September 30, 2026, as the discharge and patient-encounter date range for the midyear FY 2026 ICD-10-CM update files. The FY 2027 range begins the next day. Your reference-access plan should preserve that distinction instead of replacing every older reference with the newest version.
Ask staff to demonstrate how they would find the appropriate reference for encounters within each release period. If the answer depends on a saved shortcut, shared folder, or system setting, include that detail in the review. A reference labeled only by download date may need a clearer description of its applicable period.
Check Applicability Without Confusing CM and PCS
CMS states that ICD-10 applies to all parties covered by HIPAA, not only providers billing Medicare or Medicaid. A practice should therefore not dismiss the transition solely because its payer mix is primarily commercial. Applicability and the details of a particular payer’s policies are separate questions.
CMS also lists FY 2027 ICD-10-PCS files separately, with a stated discharge range of October 1, 2026, through March 31, 2027. Do not transfer that end date to the ICD-10-CM materials. For this readiness review, confirm that each reference belongs to the intended release and subject before using its dates in a staff communication or implementation record.
Organize the Reference Review
Clinic owners may also find retrospective billing review useful when planning their next steps.
CMS reports that the October 1, 2026, diagnosis update files are available. That gives administrators a starting point for reviewing the FY 2027 ICD-10-CM changes, but file availability does not establish which changes affect a particular practice. It also does not confirm that a vendor has made the release available in the systems your team uses.
Keep those questions distinct in status reports. “Official files available,” “local impact reviewed,” and “system behavior checked” describe different stages of preparation. Recording them separately makes it easier to identify the remaining work without treating a completed download as a completed transition.
Create a Focused Reference Review
Assign a review owner and keep a concise impact record. For each relevant finding, record the reference examined, the local workflow that may be affected, and the question or action that follows. This is a suggested administrative method, not a CMS-prescribed format.
Make the record specific enough for another person to follow. For example, “vendor confirmation needed for access to prior-period references” is more actionable than “system update pending.” Include the person responsible for obtaining the answer and a review date, so a dependency does not remain indefinitely in a general notes field.
For related guidance on organizing review scope and corrective actions, see Zavisa RCM’s article on what to expect from an independent billing audit.
Separate Official Release Materials From Optional Reference Products
The CMS FY 2027 diagnosis-file inventory includes present-on-admission, or POA, exempt entries, a conversion table, descriptions in tabular order, an addendum, tabular and index materials, and official guidelines. These are distinct resources.
AAPC also describes reference features such as official guidelines, conventions, alerts, and quick-view flow charts.
Before relying on any reference product, confirm the edition and access arrangements your staff will actually use. Keep official release materials as the basis for the transition review, and document any question that an optional aid does not resolve. A purchase decision and a readiness decision should remain separate in the implementation record.
Turn the Release Review Into a Practical Readiness Checklist
Translate the reference review into a short implementation record with owners, completion evidence, and open issues. Your existing work tracker may be sufficient. The goal is not to create another reporting burden, but to make readiness understandable to someone who was not present for every vendor call or staff discussion.
The following checks are recommended administrative steps. They do not establish a universal software procedure, payer obligation, or payment outcome. Adapt them to your systems and responsibilities, and ask for written clarification when a dependency sits outside your team’s control.
Record Readiness Evidence Rather Than Relying on Verbal Confirmation
A useful local test would examine whether staff can identify the relevant period, access the corresponding reference, and follow the intended workflow. Do not assume that a system handles this correctly simply because its latest release has been installed.
Keep vendor release notices and local test records where the transition owner can find them, including any limitations or unresolved questions.
For a test that does not behave as expected, record the expected result, observed result, and next action. This gives the next reviewer a concrete starting point rather than a vague instruction to investigate. It also distinguishes a known limitation from a question that has not yet been examined.
Assign Owners for Reference Access, Testing, Staff Preparation, and Follow-Up
- Confirm release availability in relevant systems. Assign a system owner to obtain the vendor’s release information and implementation timing. The completion record should identify the system, the confirmation received, and any remaining dependency before staff can use the update.
- Preserve prior-period reference access. Ask a reference owner to document how staff will retrieve the materials applicable to older encounters. Record the location and applicable date range, and confirm that the intended users can access it.
- Test representative encounter dates. Retain the test dates, expected behavior, observed behavior, and any issue requiring vendor follow-up.
- Prepare staff for verified workflow changes. Assign a team lead to communicate only the changes established by the review.
- Review documentation and payer questions where relevant. HFMA’s denial-prevention webinar description emphasizes stronger documentation, commercial payer alignment, and earlier medical-necessity validation. Use those themes to frame relevant local questions. Record the policy reviewed, the question raised, and the responsible reviewer rather than assuming the annual release answers every payer issue.
- Track follow-up after implementation. Assign an owner and next review date to each unresolved issue. CMS offers an ICD-10 email-update signup as a monitoring option; designate someone to assess relevant updates and record whether they require further local review.
Use a completion status that reflects the evidence. If work remains open at transition, document who will handle it and what staff should do while the question is being resolved.
Keep the checklist focused on decisions rather than activity alone. A meeting, download, or vendor message may contribute to preparation, but the record should explain what it established. Where no answer is available yet, state the outstanding question plainly instead of marking the broader task complete.
Conclusion
Readiness for October 1, 2026, rests on a clear date boundary, a focused review of official FY 2027 materials, and documented local checks. None of those elements substitutes for the others. Available files do not prove that staff have the right access, and a system update does not answer every workflow or payer question.
Frequently Asked Questions
Can a historical reference help when reviewing an older encounter after the transition?
Yes. A historical reference can be useful when reviewing an older encounter because the applicable ICD-10-CM code set depends on the date of the patient encounter or discharge. AAPC describes a historical feature that allows users to select a previous quarter going back six years and view coding data for that period. This can provide a retrospective reference point when investigating older work, provided the reviewer confirms which period is being displayed.
For example, if a team is reviewing a claim associated with an encounter from before the October 1, 2026, transition, the reviewer should not automatically rely on the FY 2027 materials simply because they are the newest available resources. The encounter date should first be identified, followed by confirmation of the applicable code-set period.
A historical lookup can also help when an administrator needs to understand what information was available during an earlier billing period. However, the historical reference should be treated as one part of the review rather than as the final determination of whether a claim was coded or billed correctly.
The feature should not be treated as proof that a payer accepted an earlier claim, that a particular code was appropriate for the documented clinical circumstances, or that a previous claim was accurate. Keep the historical reference separate from claim records, medical documentation, payer communications, and other supporting evidence. Record which source was reviewed and what question it helped answer.
What should a medical practice check before the FY 2027 ICD-10-CM transition?
Start by confirming the October 1, 2026, date boundary and identifying which encounters or discharges will fall under the FY 2027 code set. Then review the official CMS release materials and determine which parts of the update may affect the practice’s workflows.
The practice can also confirm that relevant systems and vendor resources are available, preserve access to prior-period references, and test representative encounter dates. Assigning an owner to each step can make it easier to identify unresolved questions and prevent a general “ready” status from masking outstanding issues.
Does downloading the FY 2027 ICD-10-CM files mean the practice is ready?
Not necessarily. Downloading or accessing the official files establishes that the reference materials are available to the team, but it does not establish that the practice’s billing system, encoder, clearinghouse, or other relevant technology has been updated or tested.
A readiness record should distinguish between obtaining the official materials, reviewing their potential local impact, confirming system availability, and testing the intended workflow. Keeping these activities separate gives administrators a clearer picture of what has actually been completed.
Should a practice keep access to older ICD-10-CM materials after October 1, 2026?
Yes, maintaining access to prior-period references can be useful when staff need to investigate older encounters, claims, or billing records. The newest release should not automatically replace every historical reference used for retrospective review.
Document which materials apply to which date ranges and make sure the appropriate staff know where those references are located. This can reduce confusion when older work is reviewed after the FY 2027 transition has already begun.
What is the difference between ICD-10-CM and ICD-10-PCS for this transition?
ICD-10-CM and ICD-10-PCS are separate code sets with different purposes and release materials. CMS lists FY 2027 ICD-10-CM materials separately from ICD-10-PCS materials, so administrators should confirm that they are reviewing the correct set for their particular workflow.
For the FY 2027 materials discussed in this article, CMS identifies October 1, 2026, through September 30, 2027, as the applicable ICD-10-CM discharge and patient-encounter date range. CMS separately lists an FY 2027 ICD-10-PCS discharge range that ends March 31, 2027. Those dates should not be transferred from one code set to the other.
Who should be responsible for ICD-10-CM transition readiness?
Responsibility can be divided among the people who control different parts of the workflow. A system owner may handle vendor release information and implementation timing, while a coding or reference owner can confirm access to the applicable materials. A team lead may handle staff preparation, and an administrator can track unresolved questions and follow-up.
The important point is to document ownership rather than relying on a general assumption that someone else is handling the transition. Each open item should have a responsible person and, where appropriate, a follow-up date.
How can a practice document that its workflow was tested?
Use a simple record showing what was tested, the expected result, the observed result, and any follow-up required. Representative encounter dates can be used to confirm that staff understand which reference period applies and that the intended workflow behaves as expected.
If a test produces an unexpected result, keep the issue open until the appropriate person determines whether it represents a configuration problem, a vendor dependency, a workflow question, or another issue. This creates more useful evidence than simply recording that testing occurred.
Do ICD-10-CM changes automatically determine payer requirements?
No. The annual code-set update and an individual payer’s policies are separate considerations. A practice may need to review payer-specific requirements, documentation expectations, or other billing policies in addition to reviewing the ICD-10-CM release.
Offsite Resources
ICD-10 | CMS — Official CMS resources for ICD-10 coding, including code-set updates, files, guidelines, and related information.
ICD-10 Code Books – ICD-10-CM/PCS Coding Books 2026/2027 | AAPC — AAPC reference materials for ICD-10-CM and ICD-10-PCS coding, including current and upcoming editions.
Medical Coding & Billing Tools | Codify by AAPC — Coding and billing reference tools covering CPT®, ICD-10, HCPCS codes, modifiers, and related resources.
Preventing Medical Denials Before They Start | HFMA — HFMA educational resource addressing denial prevention, documentation, payer alignment, and medical-necessity considerations.
Advanced Workshop on Mental Health System Readiness for ICD-11 | MAHE — Workshop information providing additional context on preparing healthcare systems for an ICD coding transition.
2027 CMS MPFS Proposed Rule | Medical School Healthcare Billing Compliance — University of Texas resource discussing the 2027 CMS Medicare Physician Fee Schedule proposed rule and related billing compliance considerations.
Are ICD Codes Reliable for Observational Studies? | George Washington University — Research news discussing ICD coding consistency and its implications for healthcare data quality.
What's Next?
Have unresolved administrative questions about the transition? Contact Zavisa RCM to discuss your revenue cycle readiness priorities.