MESC 2026: Why Medicaid Modernization Stalls on Data
By Leah Shakleton, Senior Director, Government Solutions
The Medicaid Enterprise Systems Conference (MESC) brought state Medicaid leaders, CMS officials, and technology vendors together in Portland, Oregon. Abacus was there talking with state agency teams and vendor partners. Across sessions and hallway conversations, one problem kept surfacing in different forms: states and their partners are sitting on more healthcare data than ever, and most of them can’t move it, connect it, or trust it fast enough to act on it.
Here’s what stood out:
1. CMS is funding Medicaid IT modernization, including early AI investment
CMS funds the bulk of state Medicaid enterprise systems through enhanced federal matching, up to 90% of costs for building new claims processing and eligibility and enrollment (E&E) systems, and 75% for ongoing operations, when a state’s system meets CMS’ conditions for enhanced funding. That funding mechanism, run through the Advance Planning Document (APD) process, has underwritten most of the claims and eligibility infrastructure states run today.
What’s newer: CMS guidance already allows planning-stage activities like impact assessments, gap analyses, and proof-of-concept work to qualify for enhanced match, which several states are now using to fund early-stage AI pilots rather than treating AI as a separate, unfunded initiative. That signals CMS sees AI experimentation as part of core modernization, not a side project states have to pay for out of pocket.
2. Long-term vendor contracts are facing greater scrutiny
Multiple sessions highlighted growing pressure on statesSeveral states are running Medicaid systems under contracts that stretch past 25 years, and CMS’ own APD guidance pushes in the opposite direction: it requires states to complete an Analysis of Alternatives for every major system investment, evaluating other solutions and reuse opportunities rather than defaulting to the incumbent. Whether that pressure translates into more competitive rebids remains to be seen. Procurement timelines are long and often delayed by protests and budget cycles, but CMS’ position favors more frequent competition. CMS also has a sharper lever: when a system falls short of the conditions for enhanced funding, it can require a corrective action plan through the APD process, and unresolved issues can cut federal match for system operations from 75% to 50%. That puts real money behind the pressure to reassess an incumbent.
3. The real blocker isn’t the new system: it’s the legacy Medicaid data
Ask any vendor supporting a state migration and you’ll hear the same thing: standing up a new eligibility or claims system is rarely the hard part. Getting decades of data out of a highly customized legacy system, cleanly and without losing history, is. Abacus works with clients to convert legacy data into formats modern platforms can use. The work is slow, detailed and domain-specific. It’s also a challenge Abacus knows well from supporting payer modernization efforts, where decades of customized business rules and historical data must be transformed and preserved as organizations move to new platforms.
4. States are drowning in reporting and starving for analytics
Most state Medicaid agencies are still built around claims data because that’s what they’ve always had. But many agencies want to shift from reactive to proactive management by incorporating clinical and other near-real-time data to better understand population health, not just what was billed after claims were adjudicated. One core problem is capacity: a large share of analytics staff time goes to producing required federal reporting and answering fast-turnaround legislative data requests, especially during legislative session. This came up repeatedly with state teams: the demand for insight is there Whether the task is legislative reporting, quality measurement, or program oversight, data preparation often consumes more time than the analysis itself. Reducing the time required to assemble trusted data is a core part of what Abacus does for agency analytics teams.
5. Medicaid AI is stalling on trust, not technology
The AI-focused sessions kept returning to the same point. In a live poll, attendees identified trust, security, privacy, governance, and policy as bigger obstacles than model performance or technical capability. States want confidence in the data behind AI outputs and clear accountability for the results. Without those guardrails, moving AI pilots into production will remain difficult.
The importance of trusted data extends beyond AI. T-MSIS submissions are subject to more than 6,000 automated data quality checks, and continued eligibility for enhanced federal funding depends on meeting those standards. Data quality has real operational and financial consequences.
The takeaway: Better data makes modernization possible
Nearly every challenge discussed at MESC pointed states, vendors, and healthcare partners toward the same goal: turning fragmented, inconsistent healthcare data into something accurate, compliant, and usable. Whether the trigger is a legacy migration, a T-MSIS reporting gap, a CMS-0057-F deadline, or an AI initiative that requires trusted inputs, data remains a common thread. Abacus helps organizations organize, govern, and use complex healthcare data so they can move modernization initiatives forward.
If your team is working through a legacy conversion, a T-MSIS data quality gap or CMS-0057-F readiness, we’d welcome the conversation.
Frequently asked questions about MESC 2026 and Medicaid data modernization
What is MESC?
MESC (Medicaid Enterprise Systems Conference) is an annual national conference for state, federal, and private-sector professionals working on Medicaid systems and the health policy that shapes them. It’s organized by the New England States Consortium Systems Organization (NESCSO) and draws well over 1,000 attendees from state Medicaid agencies, CMS, and industry vendors.
What is CMS-0057-F and when do states need to comply?
CMS-0057-F is the latest CMS Interoperability and Prior Authorization final rule, published in January 2024. It requires Medicare Advantage organizations, state Medicaid and CHIP FFS programs, Medicaid managed care plans, CHIP managed care entities, and QHP issuers to implement FHIR-based Patient Access, Provider Access, Payer-to-Payer, and Prior Authorization APIs. It builds on the 2020 CMS Interoperability and Patient Access rule (CMS-9115-F) and is expected to be followed by further interoperability rulemaking. Most operational requirements, like faster prior authorization turnaround times, took effect Jan. 1, 2026. Full API compliance is due by Jan. 1, 2027, with managed care plans complying at the start of their first rating period on or after that date. More details are available directly from CMS.
What is T-MSIS and why does data quality matter so much?
T-MSIS (Transformed Medicaid Statistical Information System) is the national database where all 50 states, D.C., and several territories report Medicaid and CHIP claims, eligibility, and provider data to CMS. CMS applies more than 6,000 automated data quality checks to these submissions, and a state’s continued eligibility for enhanced federal funding on its Medicaid IT systems is tied to meeting T-MSIS reporting and data quality standards. States that fall short can be required to submit a corrective action plan or face a reduction in federal matching funds. Full detail is on Medicaid.gov.
How does CMS fund Medicaid IT modernization?
States can request enhanced federal matching, generally 90% for building new eligibility and enrollment or claims systems and 75% for ongoing operations, through the Advance Planning Document (APD) process, provided the system meets CMS’ conditions for enhanced funding. Planning activities like gap analyses and proof-of-concept work can also qualify. Details on the funding structure and required templates are available on Medicaid.gov.
Why is migrating data off legacy Medicaid systems so difficult?
Migrating data off legacy Medicaid and payer systems is difficult because many of them were built and customized over decades, which means the underlying data structures are often undocumented, inconsistent, or specific to that one system and era of technology. This is typically the longest and highest-risk part of any system migration.
What does Abacus do for Medicaid agencies and their technology partners?
Abacus handles data ingestion, transformation, interoperability, and large-scale data management for organizations modernizing complex healthcare data systems, including state Medicaid agencies and the vendors that support them. That work includes legacy system data conversion, supporting T-MSIS reporting and data quality remediation, and building the interoperable data foundation that CMS Interoperability compliance and AI initiatives depend on.