As Medicaid leaders gather in National Harbor, Maryland, one question deserves a place in the conversation: Who is actively finding the processes that may fail under Medicaid’s next operating requirements?
Somewhere in a Medicaid operation, a spreadsheet reconciles records that two systems cannot reconcile themselves. A technician knows which exception needs another look. A vendor resolves a mismatch through a process the agency cannot readily inspect. The work gets done. But can the organization prove that the decision was right—and will that process hold when requirements, transaction volume, or personnel change?
Experience can keep a fragile process working for years. That same experience can conceal how much depends on a particular person, an undocumented step, or a manual repair. Leadership needs an active search for those dependencies before the next operating environment exposes them.
The governors of Oregon, California, Maine, New Mexico, and Virginia made the readiness question concrete in their October 1 request for more time to implement new Medicaid requirements. Can states verify activity and exclusions, issue accurate notices, resolve discrepancies, and retain the evidence supporting each decision? Our recommendation: tie preparation time to tested readiness milestones, and bring unresolved pathways to the NAMD conversation. Additional implementation time and relief from PERM financial consequences are separate questions. Source: Oregon Governor’s Office, October 1, 2026.
Missouri’s latest statewide audit illustrates why urgency belongs in that search. The State Auditor reported recurring Medicaid eligibility-system and timeliness weaknesses, including duplicate enrollment across systems and a death match that remained inoperative. These are public findings from one state, not a ranking of state performance. They pose a national management question: what happens when a known vulnerability remains open while the operation continues?
Finding the vulnerability is only the beginning. As we explored in Stop the Error Clock, the time between discovery and a valid, documented correction may determine how long a defect continues to affect later payments. An effective correction can change the basis supporting later coverage. It does not erase the history of earlier payments.
The response therefore needs two clocks: time to contain the operational risk, and time to complete and verify the correction. A project milestone alone does not protect today’s decisions. Leadership should know what is protecting applicants and public funds while the permanent fix is being built.
Bring one vulnerable process to your next leadership meeting.
Select a recurring reconciliation, manual exception, or fragile handoff. Name its owner. Establish the immediate protection. Set a correction deadline. Require evidence that the fix works across eligibility, notices, enrollment, and payment records. Track elapsed time and escalate missed commitments.
Use the map below to start that conversation. Ask eligibility, systems, quality, and program-integrity leaders to test the same pathway together. A correction that merely moves the defect downstream has not closed it.
Look for fragile dependencies before new requirements expose them. Name an owner, protect current decisions, make a valid correction, and verify the result.
Who owns the vulnerability, what protects decisions today, and how soon will a verified correction be in place? That is the leadership assignment. Troubleshooting the future begins with acting on what we can find now.
Ralph Choate | Founder, Editor & Principal Author
© 2026 PERM Insights & Perspectives LLC.