Good morning.
When the chart can’t agree whether to start CPR
There may be no more consequential 30 seconds in a skilled nursing community than the 30 seconds after a resident is found unresponsive.
Start CPR?
Don’t start CPR?
In one of our Deficiency Deep Dives, we reviewed a case where the team believed the resident was DNR.
CPR was not initiated.
The problem was not that the resident’s wishes had never been documented.
The problem was that they had been documented too many times, in too many places, and those places did not agree.
The face sheet said one thing.
The EMR displayed another.
Physician orders said something else.
Other indicators around the building added even more noise.
That is a dangerous kind of redundancy.
We usually think duplicating important information makes a system safer.
Sometimes it does.
But high-stakes information becomes less reliable when every duplicate is capable of becoming outdated independently.
A resident changes their code status.
The practitioner order gets updated.
But does the EMR banner change?
The face sheet?
The emergency binder?
The marker staff have been trained to look for?
Whatever other workaround your building has accumulated over the years?
Now imagine discovering that inconsistency at 2:13 Sunday morning instead of during an audit.
CMS’s current F678 guidance is very clear about the stakes. Skilled nursing facilities must be able to provide emergency basic life support when required, consistent with the resident’s physician orders and advance directives. The guidance also specifically directs surveyors to determine whether staff know how to confirm a resident’s code status in an emergency and whether the medical record reflects the resident’s wishes.
That is bigger than a documentation problem.
It is a system-design problem.
Your team needs a clearly defined, legally compliant way to determine the resident’s current code status quickly.
And every secondary place displaying that information needs a process to stay reconciled with it.
5-Minute Building Audit
Don’t ask your team, “Do we have a code-status process?”
Try this instead.
Pick a resident and ask a nurse:
“Show me how you would confirm this resident’s code status right now.”
Then ask another nurse on a different shift.
Then a CNA or supervisor who may be present during the emergency.
Don’t coach them.
Watch.
Are they looking in the same place?
Can they find the answer quickly?
Then pull three residents:
- one full code
- one DNR
- one recent admission or recent code-status change
Compare the current practitioner order and advance-directive documentation with every operational place your team relies on.
If they disagree, you found something worth fixing.
And once in a while, run the real test:
“Resident is unresponsive. Go.”
Give the team 60 seconds.
Because your process does not need to work beautifully during Tuesday morning QAPI.
It needs to work at 2:13 Sunday morning.
Deficiency Deep Dive
The case behind today’s newsletter is worth watching in full.
We spend about 30 minutes walking through the actual breakdown, the conflicting documentation, what surveyors found, and the practical audit operators can run in their own communities.
Watch the full Code Status Deficiency Deep Dive
And if these case reviews are useful, join us each week. We take one real deficiency, work backward through how the system failed, and figure out what operators can inspect before the same failure shows up in their own community.
Sign up for the weekly Deficiency Deep Dive series
This is not really about keeping the chart clean.
It is about making sure a resident’s wishes are unmistakably clear at the exact moment they matter most.
— Kevin | 