MES Modularity: How to Get Value Beyond CMS Compliance
Ask Medicaid directors whether their states have implemented Medicaid Enterprise Systems (MES) modularity, and they will say yes; the Centers for Medicare and Medicaid Services (CMS) mandates it. Then ask them if they’re getting maximum value from modularity, and many would hesitate. What’s often overlooked is that the most value comes from how modules work together, not from modularity itself.
Integrated vs. Assembled Modularity
Imagine two states implement MES modularity to meet CMS requirements. Each state operates separate modules for claims, encounters, and financials (CEF); pharmacy; and provider management.
The first state used what we call integrated modularity. In this approach, states’ CEF, pharmacy, and provider modules are on a shared architecture and designed to work together. Data moves between them without translation. Analytics draw from shared data, and policy changes automatically cascade across every module they impact.
The second state chose assembled modularity. They have separate modules that perform well on different architectures but aren’t designed to work together. Data has to pass through middleware, integration layers, and transformation engines. Handoffs often create bottlenecks. And staff typically must manually synchronize policy changes.
Both states are fully compliant. But the first state’s modules are built on the same foundation, thus are more connected. Integrated modularity creates value in everything from lower costs and faster implementation to more consistent member experiences and unified data.
Why Architecture Matters
The benefits of integrated modularity highlight just how important MES architecture is. States often evaluate the effectiveness of MES modules on what they do. How well does the claims engine adjudicate? How complete is the provider enrollment workflow? Or how effectively does the pharmacy module manage drug utilization review?
Questions like these are important, but they measure modules in isolation. And Medicaid programs don’t operate in isolation. Member care touches claims, providers, and pharmacy. This is why connections across modules ultimately shape overall program effectiveness.
When modules are disconnected, as they are in assembled modularity, there are seams between them. Every seam needs coordination for the life of the system. That translates into extra work as well as insight and efficiency gaps. It’s only when the seams disappear that the system can multiply value.
The Power of Exponential Value
Multiplying MES value through integrated modularity gives states a massive advantage. Each module delivers its own return. And together, thanks to the connections between them, modules deliver exponential value.
This exponential value means more than one plus one equals three. It’s value that keeps multiplying from the “mortar” between the modules on a common architecture. Because every module draws on the same data and rules, gains in one area can carry into the others. And the benefits compound over time.
Implementation is a Choice
CMS mandates modularity, but states decide how to implement it. Those that choose integrated modularity can create new value that benefits operations as well as member, provider, and staff experiences. This is modularity at its best. It’s modularity designed to deliver more than compliance, but a better experience for all.
To learn more about integrated modularity, read our recent white paper.





