Approval Is Not Readiness: The Operational Risk Behind Medicaid Palliative Care
A confirmation is on its way to your inbox.
Thanks for reading! Subscribe free to receive new posts.
Discussion
Be the first to share your thoughts on this article.
Community-Based Benefit Readiness Check
Before launching or expanding a community-based palliative care benefit, leaders should be able to answer these questions.
If the answer is no, the benefit may be approved, but it is not ready.
For readers who want to go deeper, these resources connect directly to the operational issues raised in this article.
Author Note
At Ono Logic, I work with healthcare, government, and mission-driven organizations on the gap between policy approval and operational execution. This article reflects lessons from community-based palliative care implementation and the broader challenge of building programs that communities can actually use.
Medicaid | Palliative Care | Operational Readiness
A Medicaid benefit can be approved, funded, and well-intentioned, and still fail in practice.
That is the uncomfortable lesson healthcare leaders should take seriously as more states explore community-based palliative care.
The failure usually does not happen in the policy language.
It happens later, in the operating model.
It happens when eligibility tools are too burdensome for providers. When assessment worksheets duplicate what nurses already document. When managed care plans interpret the benefit differently. When caregivers are essential to the care plan but invisible in the workflow. When the state can report activity but cannot tell whether patients and families are actually better supported.
That is the gap between a benefit that exists and a benefit that works.
Palliative care is often misunderstood as end-of-life care. At its best, it is broader and earlier than that.
It supports people living with serious illness by helping with symptoms, quality of life, goals of care, caregiver strain, and the practical burden of moving through a fragmented health system.
That need does not live only inside the hospital.
It lives at the kitchen table where a daughter is sorting medications she does not fully understand.
It lives in the car after an appointment, when a spouse is trying to remember what the doctor said.
It lives at 2 a.m., when pain worsens, anxiety rises, and the caregiver wonders whether to call 911.
That is why community-based palliative care matters.
If states, hospitals, health plans, and healthcare leaders build these programs around institutional needs first, they risk creating another paperwork-heavy program wrapped around a good idea.
All of that matters. But none of it is the same as care.
Through my work on Hawaii's CMS-approved community-based palliative care benefit, and the paper I co-authored on that model, I came away with one practical lesson:
A benefit becomes real only when it can survive contact with the people who have to use it.
That is where many good ideas get into trouble.
Program teams often create tools to help: eligibility checklists, assessment worksheets, referral forms, care planning templates, and reporting trackers.
These are usually created for the right reasons. They are meant to create consistency, support compliance, and make the program easier to manage.
But a tool that helps the institution can still burden the field.
The lesson is not that tools are bad.
The lesson is that tools have to be designed around the moment where they will actually be used.
This is the kind of work that often gets missed because it sits between policy, operations, compliance, and field adoption.
Community-based palliative care is team-based by nature. It may involve physicians, nurses, social workers, care coordinators, chaplains, community providers, managed care plans, and family caregivers.
But teamwork does not happen just because the model says "interdisciplinary."
It requires an operating plan that helps the right person see the right information, take the right next step, and adjust when the patient or caregiver's needs change.
Without that, the burden moves downstream. The provider is left to interpret the policy. The nurse is left to make the tool work. The managed care plan is left to apply the benefit. The caregiver is left to carry the plan. The patient is left to experience the gaps.
When each organization creates its own workaround, the benefit starts operating differently depending on which provider, plan, or community a family touches first.
That is institutional design pushed into the community.
A better operating model starts from the community and works backward.
Before launching or expanding a community-based palliative care benefit, leaders should ask:
These are operational questions, but they are also human questions.
A system built for serious illness should reduce burden, not simply move it.
Before launching or expanding a community-based palliative care benefit, leaders should be able to answer a few basic questions.
This is also a sustainability issue.
A benefit designed around community use supports health, equity, and stronger local systems. A benefit designed around institutional administration may satisfy reporting requirements while leaving the people closest to serious illness with more complexity to carry.
A sustainable palliative care benefit is not one the institution can administer easily.
It is one the community can actually use.
For Medicaid directors, hospital administrators, health plans, and healthcare leaders, the challenge is not simply to add palliative care to the list of covered services.
The challenge is to build the operating system around it.
Palliative care does not fail because people do not need it.
It fails when leaders build the benefit around institutional control instead of community use.