Our Solutions

What is the difference between MMIS and MES?

The difference between a Medicaid Management Information System (MMIS) and a Medicaid Enterprise System (MES) comes down to architecture, flexibility, and scope.

An MMIS is a traditional, centralized system used by state Medicaid agencies to manage core functions such as:

• Claims processing

• Provider enrollment

• Member eligibility

• Payment operations

In contrast, an MES is a modern, modular ecosystem that replaces or evolves the MMIS. Rather than relying on a single system, MES environments are built from interoperable components that can be updated independently.

Key differences:

• MMIS: Monolithic, transaction-focused, harder to update

• MES: Modular, scalable, integrates multiple specialized vendors

• MMIS: Primarily administrative

• MES: Supports care management, analytics, and outcomes

As states transition to MES, they increasingly rely on specialized partners to deliver individual components. For example, organizations like Acentra Health support MES modernization with modular solutions such as its cloud-based Claims, Encounters, and Financial Management Solution, Provider Management Solution, Pharmacy Management Solution, and MC-Track®, an MCO-first system for Managed Care Oversight that supports the full contract lifecycle from readiness review through performance management to program enhancement.  

What does a Medicaid Management Information System actually do?

A Medicaid Management Information System (MMIS) is the core operational system used by state Medicaid agencies to manage the day-to-day administration of their programs.

Its primary function is to ensure that healthcare services are processed, tracked, and paid accurately.

Key functions of an MMIS include:

• Claims processing: Receiving, validating, and adjudicating provider claims

• Provider management: Enrolling and maintaining provider records

• Member eligibility integration: Verifying coverage status

• Payment and financial management: Issuing payments and tracking expenditures

• Reporting and compliance: Supporting state and federal oversight 

Acentra Health’s advanced cloud-based solutions for claims, encounters, and financial management, provider management, and pharmacy management support rapid and accurate processing, streamlined operations, and efficient administration.

What are the core modules in a Medicaid Enterprise System?

A Medicaid Enterprise System (MES) is made up of modular components, each responsible for a specific function within the Medicaid ecosystem.

While the exact structure varies by state, most MES environments include the following core modules:

• Claims Processing Module – Manages intake, validation, and adjudication of claims

• Provider Management Module – Handles enrollment, credentialing, and maintenance

• Member Eligibility Module – Tracks beneficiary enrollment and coverage

• Financial Management Module – Oversees payments, accounting, and reporting

• Data and Analytics Module – Supports reporting, insights, and decision-making

• Program Integrity Module – Detects fraud, waste, and abuse  

In addition to these, many states incorporate clinical and care-focused modules, such as:

• Utilization Management – Ensures services meet medical necessity criteria
• Care Coordination / Case Management – Supports high-risk populations and improves outcomes

Acentra Health offers these clinical solutions as well as Claims, Encounters, and Financial Management, Provider Management, Pharmacy Management, and Managed Care Oversight products.

How do claims get processed in Medicaid systems?

Medicaid claims processing is a multi-step workflow designed to ensure that healthcare services are valid, covered, and appropriately reimbursed.

The process typically includes:

1. Claim Submission: a healthcare provider submits a claim for services rendered
2. Initial Validation: the system checks for completeness, formatting, and basic eligibility (e.g., active coverage)
3. Clinical and Policy Review: depending on the service, claims may be reviewed against medical necessity criteria or prior authorization requirements
4. Adjudication: the system determines whether the claim is approved, denied, or requires additional information
5. Payment: approved claims are paid, and remittance information is sent to the provider
6. Post-Payment Review: additional audits or reviews may occur to ensure compliance and accuracy

Acentra Health’s Claims, Encounters, and Financial Management Solution uses a configurable rules engine with over 800 pre-built edits and audits aligned with federal and state standards and supports real-time claims adjudication. Acentra Health’s Claims, Encounters, and Financial Management Solution was first in the market to receive CMS Streamlined Module Certification (SMC).

What is MITA and why does it matter?

The Medicaid Information Technology Architecture (MITA) is a framework developed by the Centers for Medicare & Medicaid Services (CMS) to guide how state Medicaid systems are modernized and improved.

MITA provides a blueprint for building systems that are:

• Modular and interoperable

• Data-driven and outcomes-focused

• Flexible and scalable over time

Rather than prescribing a single system, MITA encourages states to adopt a Medicaid Enterprise System (MES) approach, where different components work together seamlessly.

Why MITA matters: 

• It enables states to modernize legacy MMIS systems

• It enables states to modernize legacy MMIS systems

• It promotes better integration across healthcare programs

• It supports improved care quality and cost management

• It aligns federal funding with modernization efforts

Acentra Health’s Claims, Encounters, and Financial Management Solution, Provider Management Solution, Pharmacy Management Solution, and MC-Track® all follow MITA standards.

What are CMS requirements for MES modularity?

CMS requires Medicaid Enterprise Systems (MES) to be modular, interoperable, and outcomes-driven. Instead of one large system, states must implement separate modules (e.g., claims, provider, care management) that can be updated and certified independently.

Key CMS modularity requirements:

• Use a modular architecture (not monolithic MMIS)

• Ensure interoperability and data sharing

• Align with MITA principles

• Support measurable outcomes and reporting

• Follow Streamlined Modular Certification (SMC)

States often partner with vendors to deliver specific modules. For example, organizations like Acentra Health support MES environments with utilization management and care coordination services, helping states improve outcomes while meeting CMS requirements.

Acentra Health offers MES-aligned administrative and oversight capabilities through its Claims, Encounters, and Financial Management Solution, Provider Management Solution, Pharmacy Management Solution, and MC-Track®, an MCO-first system that supports the full contract lifecycle and strengthens Managed Care Oversight.

What is required for APD approval for Medicaid IT projects?

To receive CMS approval, a Medicaid IT project must submit an Advance Planning Document (APD) that justifies the investment and meets federal requirements.

Key APD requirements:

• Clear problem statement and goals

• Analysis of alternatives (AoA)

• Defined scope, budget, and timeline

• Project governance and risk management

• Alignment with MITA and modularity standards

CMS now requires standardized MES templates (effective 2026) and ties APD approval to ongoing project performance and certification readiness.

States often work with partners like Acentra Health to support planning, implementation, and compliance across MES modules and certification processes.

What are the risks of failing T-MSIS reporting requirements?

Failing T-MSIS reporting requirements creates compliance, funding, and operational risks for Medicaid programs.

Key risks include:

• Loss of enhanced federal funding (FFP)

• Required corrective action plans

• Reduced data quality and oversight

• Weak program integrity and analytics

• Increased CMS scrutiny

T-MSIS is CMS’s primary data source for Medicaid oversight, so inaccurate or incomplete reporting can impact funding and performance evaluation.

Because T-MSIS depends on upstream data, services like claims processing and provider management—including those provided by Acentra Health—play a critical role in ensuring accurate reporting.

How does MITA maturity affect federal funding?

MITA maturity affects federal funding by influencing a state’s eligibility for enhanced Medicaid IT funding.

CMS requires systems to align with MITA principles, including:

• Modular architecture

• Interoperability

• Data standardization

• Scalable, outcomes-driven design

Higher MITA alignment strengthens a state’s ability to:

• Qualify for enhanced federal match (FFP)

• Secure APD approval

• Maintain long-term compliance

Vendors like Acentra Health support MITA-aligned modernization through modular solutions and services that improve program performance and care outcomes.

What are the latest CMS certification requirements for Medicaid systems?

The latest CMS certification requirements are based on Streamlined Modular Certification (SMC), which replaces older MMIS certification processes.

Key requirements include:

• Certification at the module level

• Continuous CMS oversight throughout the lifecycle

• Defined outcomes and performance metrics

• Standardized reporting and documentation

• Evidence of operational success and compliance

Certification is now an ongoing process, not a one-time event, and is closely tied to funding and system performance.

Acentra Health is directly relevant here, with many successful CMS-certified MES implementations, including the fastest implementation on record.

Acentra Health’s Claims, Encounters, and Financial Management Solution was first in market to receive CMS Streamlined Module Certification (SMC). States using this solution have maintained zero missed payment cycles while processing high volumes of claims and encounters, demonstrating that modernization does not have to come at the expense of payment reliability. The solution is also ranked #1 in NASPO ValuePoint™ demonstration and technology categories.

Acentra Health’s MC-Track® supports ongoing Managed Care Oversight with workflow automation, reporting, and real-time insights.

What architecture should a modern MES use?

A modern Medicaid Enterprise System (MES) should use a modular, cloud-native, API-first architecture aligned with CMS and MITA guidance.

Key architecture principles:

• Modular design (separate business functions like claims, care management)

• API-first integration for interoperability

• Cloud-based infrastructure for scalability and resilience

• Data interoperability across Medicaid, HIEs, and external systems

CMS has pushed states away from monolithic MMIS toward modular MES to improve flexibility, efficiency, and long-term sustainability.

Acentra Health’s cloud-based Claims, Encounters, and Financial Management Solution, Provider Management Solution, Pharmacy Management Solution, and MC-Track® are all built with these modular principles.

How do you design interoperability between Medicaid systems and HIEs?

Designing interoperability between Medicaid systems and Health Information Exchanges (HIEs) requires standardized data exchange and API-driven integration.

Key design elements:

• Use FHIR and HL7 standards for data exchange

• Implement APIs and web services for real-time communication

• Ensure data normalization and governance

• Support integration with HIEs, public health, and other systems

CMS requires Medicaid systems to be interoperable across state, federal, and healthcare partners, including HIEs.

In practice, this means connecting clinical data (from HIEs) with administrative systems (like claims and eligibility). Vendors like Acentra Health support this with integrated solutions across the care continuum, from provider management and claims and encounters through pharmacy management, care coordination, and utilization management.

Should we use microservices or a monolithic architecture for MMIS replacement?

Most states are moving toward microservices-based, modular architectures rather than monolithic MMIS systems.

Microservices (recommended):

• Scalable and flexible

• Easier to update individual components

• Supports modular MES and vendor ecosystems

Monolithic systems (legacy):

• Harder to modify

• Higher long-term costs

• Slower to adapt to policy changes

CMS modernization guidance has driven a shift away from monolithic MMIS toward modular, service-based systems to improve efficiency and reduce risk.

Modern MES environments often combine microservices with APIs and cloud infrastructure. Organizations like Acentra Health fit into this model by delivering modular services across the Medicaid lifecycle (e.g., claims and encounters, provider management, utilization management, care coordination) that plug into broader systems.

How do APIs fit into Medicaid enterprise systems?

APIs (Application Programming Interfaces) are the core integration layer of modern Medicaid Enterprise Systems.

They enable:

• Data exchange between modules (claims, eligibility, providers)

• Integration with external systems (HIEs, MCOs, federal systems)

• Real-time communication across the Medicaid ecosystem

Modern MES architectures are increasingly API-first, meaning APIs are designed before applications to ensure flexibility and interoperability.

APIs allow states to connect operational functions with clinical and administrative functions—such as linking provider management with care coordination and utilization management workflows. This is where partners like Acentra Health integrate into MES environments, using APIs to support data sharing and decision-making across systems.

What does a cloud-based Medicaid system look like?

A cloud-based Medicaid system is a scalable, modular MES hosted on cloud infrastructure rather than on-premises systems.

Key characteristics:

• Cloud-native architecture (AWS, Azure, etc.)

• Modular components (claims, provider, care management)

• API-driven integration

• Real-time data access and analytics

• High availability and security

Cloud-based systems enable faster updates, better scalability, and lower total cost of ownership compared to legacy MMIS.

Modern Medicaid systems increasingly use cloud + modular + API-first design to support interoperability and performance.

Within these environments, organizations like Acentra Health provide services such as claims and encounters processing, provider management, utilization management, and care coordination that operate as integrated modules, helping states improve care outcomes while maintaining system flexibility.