Regulatory change arrives on a date. Operational change does not.
CMS released the CY 2027 Home Health Final Rule on 4 November. Most of it takes effect on 1 January.
I am not going to walk through the provisions here. There are good summaries, and by the time you read this your association has almost certainly sent you one. What interests me is the gap between those two sentences, because it is where I think most agencies will spend their next six months.
A rule takes effect on a date. An organisation changes across a period. Nobody writes rules the other way round, and there is no obvious way they could. But that mismatch has a cost, and in home health it is larger than in most of healthcare for reasons worth setting out.
The holiday problem is a real problem
A 1 January effective date means the work of preparing for it happens in late November and December.
In most industries that would be an inconvenience. In home health it collides with the worst available weeks. Staff take leave. Agencies run on coverage schedules. Referral patterns shift as hospitals clear beds before the holidays and families change their caregiving arrangements around them. The census does not pause, and neither does the documentation it generates.
So the preparation window is the one period in the year with the least slack in it. And the people you would most want in a room working through what changes, which is to say your senior clinicians and your QA lead and whoever actually understands your case mix, are the same people holding the coverage schedule together.
I have watched agencies handle this well and I have watched agencies handle it badly, and the difference is almost never how well they understood the rule. Understanding a rule is a few hours of reading for a capable administrator. Responding to it is a different kind of work entirely.
Understanding and absorbing are not the same skill
Here is the distinction I keep coming back to.
Understanding a rule change tells you what is different. Absorbing it means knowing what is different for you, specifically, in your own numbers, with your own patient mix and your own staffing and your own historical patterns.
Those are not the same question, and the second one is much harder, because the answer is not in the Federal Register. It is in your data.
When a threshold moves, the question is not “has the threshold moved.” It is “how many of my episodes sat within one visit of the old one, and what happens to those.” When a case-mix grouping is recalibrated, the question is not whether it was recalibrated but what share of your own census falls into the groups that moved. When a submission deadline changes, the question is whether your current process has any slack in it at all, or whether it has been quietly running two days before the old deadline for three years.
None of those questions can be answered by reading. All of them can be answered by looking, provided you can look quickly.
That capacity to look quickly is, I would argue, the actual thing agencies should be building. Not rule expertise. Rule expertise is available to rent. The ability to see your own exposure in an afternoon is not.
Why this kind of change is invisible where the work happens
There is a second structural reason home health finds this harder than a hospital would.
The work happens in houses. A hospital can brief a floor. An agency has clinicians who each drive to four or five homes a day, work alone, and may be in the office once a week. Change has to propagate to people who are not in a building, and it has to survive contact with a day that was already full.
More to the point, most of what changed in a payment rule is not visible at the point of care at all. A nurse cannot see a comorbidity grouping. She can see a patient, and she can document what she observed, and whether that documentation lands in a group that was recalibrated in November is not something she can perceive, affect, or reasonably be asked to think about during a visit.
This is worth saying plainly, because a lot of change management in our industry gets aimed at clinicians when the change is not actually theirs to absorb. Asking a nurse to keep a new threshold in mind during a visit is asking the wrong person to hold the wrong information at the wrong moment. It also tends not to work, which is the practical objection on top of the principled one.
Get Murphi AI’s stories in your inbox
Join Medium for free to get updates from this writer.
The changes are visible in reports. Which means the response belongs in reporting and in the office, and the only thing that should reach the clinician is a better draft and fewer corrections.
What usually gets done, and why it mostly does not work
Three things happen in most agencies in December, and I say this with sympathy, having watched all three.
The all-hands memo. Somebody writes a clear summary of what changed and sends it to everyone. It is accurate, it is well intentioned, and most of its recipients cannot act on any of it, because the changes are not in their hands.
The training deck. Somebody builds twenty slides on the new requirements. It gets delivered in January to people who are already behind. The content is correct. The retention is poor, because the material is abstract until somebody encounters it in a real chart.
The spreadsheet. Somebody capable builds an analysis of the agency’s own exposure. This is genuinely the right instinct, and it is the one of the three that produces real insight. It also takes two weeks, depends entirely on one person, is out of date by February, and will be rebuilt from scratch next November.
What the spreadsheet is reaching for is instrumentation. It is a hand-built, one-off version of a thing that should be standing capability. The reason it has to be hand-built is that the underlying data is usually not arranged in a way that answers operational questions, only in a way that produces claims.
What ready actually looks like
I think readiness, for this kind of change, has three parts, and only the third is about software.
Your record has to be current. Not complete in the sense of eventually finished, but current in the sense that what happened in a visit is in the chart accurately, soon, with the evidence behind it. An agency whose documentation is running three weeks behind cannot assess its own exposure to anything, because the data it would assess is not there yet. This is upstream of every other readiness question and it is the one most often skipped, because it feels like a documentation problem rather than a strategy problem.
Someone has to own the operational translation. One named person whose job it is to turn “the rule changed” into “here is what it means for our episodes, and here are the three things we are changing.” Not a committee. Committees produce memos.
You have to be able to see your own numbers against the new shape quickly. Thresholds, groupings, deadlines, and completeness, in your own data, without a two-week analysis project. This is the part that is a tooling question, and it is the part I have spent the last few years working on, so treat what follows as interested rather than neutral.
Where I think software legitimately helps, and where it does not
Murphi.ai does some of this. Our platform tracks OASIS submission deadlines, quality reporting completeness, case-mix impact, and periods sitting close to a LUPA threshold, and it keeps the documentation underneath all of that current by drafting it from the visit rather than from memory at nine in the evening. When the shape of a rule changes, the reports change shape with it, and an agency can see its own position without building anything.
That is a real contribution and I will defend it. It is also narrower than it sounds, and I want to be honest about the boundary.
Software does not absorb organisational change. People do. A tool that shows you your exposure has given you information, and information is upstream of a decision rather than a substitute for one. Somebody still has to decide whether to change the visit pattern, whether to retrain on an assessment item, whether to have a difficult conversation with a referral source, or whether to accept an impact and move on.
What good instrumentation does is change the ratio. If assessing your position takes two weeks, you get one look and then you are committed. If it takes an afternoon, you can look in December, act in January, look again in March, and correct. The quality of the decisions improves, not because the tool is clever but because the feedback loop got short enough to learn from.
The other honest thing to say is that the hours a tool returns are only worth something if they go somewhere useful. An agency that saves clinicians time and then simply absorbs it into a heavier caseload has converted a documentation improvement into a capacity increase, which is a legitimate choice, but it should be a choice rather than something that happens by default. The agencies that handle regulatory change best, in my observation, are the ones that deliberately kept some of the time back.
Six weeks
By the time this publishes, most agencies will have about six weeks, across a holiday period, to respond to a rule that is already final.
My honest advice, for what it is worth from someone who sells software in this space, is to spend the first of those weeks on a single question rather than on a summary. Pick the provision you think is most likely to affect your own numbers, and find out whether it does. Not in general. In your data, for your census.
If the answer takes you two weeks to produce, you have learned something more valuable than the answer.
I will be at the SCHCHA Annual Conference in Charleston from 15 to 17 November, and I suspect this will be the hallway conversation. If you are going to be there, I would like to hear how your agency is planning to use December.
