The Challenge Arizona and Hawaii Share: Medicaid Encounter Data in Capitated Managed Care

If you work in capitated managed care, you know exactly what inspired this blog post. You could probably write a book on encounter denials, retroactive capitation rate adjustments, and stricter RADV audits.

The systems processing encounters were built when fax machines were cutting-edge. Yet the data requirements keep getting more complex — risk adjustment, quality scoring, rate setting, and the relentless CMS push for complete, timely encounter data.

For states like Arizona and Hawaii, which not only share a similar managed care philosophy but having been running on the same aging mainframe since 1999, the gap between legacy infrastructure and Medicaid reality is more than theoretical. It’s measured in denied encounters, swollen reserves, and analysts buried in rework instead of care coordination.

What Makes Medicaid Encounter Data So Complex in Capitated States?

In a fee-for-service environment, claims flow is relatively straightforward. Providers submit – the state adjudicates – payment follows. The claim itself is the financial transaction; encounter data is a byproduct.

Capitated managed care inverts that logic. The state pays managed care organizations (MCOs) a per-member-per-month capitation rate. MCOs pay providers. The encounter data submitted back to the state isn’t tied to a payment. It’s a reporting obligation that serves actuarial, quality, and compliance purposes. Same data formats – different stakes.

This creates data integrity problems across every layer. MCOs must capture, validate, and submit encounters in HIPAA 837 and NCPDP formats that conform to state-specific requirements. The state must then validate, reconcile, and use that data for functions it was not designed to support, from HEDIS reporting to federal encounter submissions to CMS. Add dual-eligible populations into the mix – where Medicare and Medicaid coverage overlap with different rules, billing structures, and coordination-of-benefits requirements – and the complexity compounds.

CureIS was the first healthcare IT company to develop a commercial solution that specifically addressed dual eligibles data challenges. That early immersion in the problem revealed what general-purpose claims systems miss: navigating and automating encounter processes requires purpose-built thinking.

The AHCCCS Model: A Case Study in Encounter Data at Scale

Arizona’s AHCCCS program is one of the longest-running capitated Medicaid managed care models in the country, and offers a lens into what encounter data complexity looks like at an operational scale.

The challenges here don’t exist in simpler Medicaid environments. Data teams tackle these, and many other daunting scenarios:

• The behavioral health coding matrix (known as the B2 matrix) requires specific coding combinations that don’t map neatly to standard claims logic.
• Provider registration validation adds another layer. Encounters can be rejected not because the clinical data is wrong, but because a provider’s enrollment status misaligns with state requirements at the time of the service.
• File-level validation failures can cascade, causing rejection of entire batches rather than individual records. One bad apple poisons the whole barrel.
• In Arizona, ICD-10 specificity requirements are enforced at a level that catches submissions other states might accept.

For MCOs and their delegated entities, the operational burden is significant. Encounter rejection rates directly affect data completeness, which in turn affects rate-setting accuracy and quality scores. The feedback loop between submission, rejection, correction, and resubmission drains resources from work that affects people: care coordination and member services.

From Arizona to the Pacific: Shared Infrastructure, Shared Challenges

Here’s a fact that surprises most people (outside these two states): Arizona and Hawaii have shared the same core Medicaid IT infrastructure since 1999.

Under an intergovernmental agreement, AHCCCS operates the Prepaid Medical Management Information System (PMMIS) that processes Medicaid data for both states. Hawaii’s version, (HPMMIS) runs on the same Arizona mainframe. Both systems were built on 1980s technology; both must now process modern encounter data at 2026 volume and complexity.

Hawaii’s Med-QUEST program layers additional technical challenges:

• Five MCOs serve the state’s Medicaid population, including both local nonprofits like AlohaCare and HMSA, and national carriers like UnitedHealthcare and Kaiser Permanente. Each brings different operational approaches to encounter data.
• Over half of Hawaii’s population relies on Medicaid.
• Ninety-five percent of the state’s land area is rural, with healthcare services concentrated on Oahu. Small, geographically dispersed provider networks across multiple islands create data capture challenges that mainland states don’t face.

Both Arizona and Hawaii are also navigating the complexities of dual-eligible populations. Hawaii is presently transitioning to Fully Integrated Dual Eligible Special Needs Plans, while Arizona continues to manage one of the most mature dual-eligible managed care programs in the country. In both cases, accurate encounter data is the linchpin. Without it, risk adjustment is unreliable, quality measurement is incomplete, and rate-setting operates on data that nobody fully trusts.

Solving the Problem at the Source

The encounter data challenge in capitated Medicaid isn’t a reporting problem – it’s a data management problem, and that distinction matters enormously.

Where some enterprise solutions attempt to retrofit claims processing logic onto a fundamentally different data flow, purpose-built encounter management addresses the issue where it actually originates.

In Arizona, one of the state’s largest health systems took this approach, and the numbers tell the story:

• Encounter denials reduced by ~90 percent over three years.
• AHCCCS sanctions eliminated entirely. Reserves dropped from $20 million to under $1 million.
• Turnaround times for 1-to-30-day submissions improved from below 65 percent to 90 percent.
• Six full-time equivalents recovered from manual encounter rework could finally focus moving the mission forward.

Their CureIS solution achieves a 98-plus percent first-pass acceptance rate because it was designed from the ground up for the specific logic of capitated encounter submission – pre-scrubbing, validating, reconciling encounters against claims in real time – instead of asking fee-for-service tools to do a job they were never built for.

Powered by the UniSync™ Healthcare Data Management Platform and its EncounterCURE module, this approach manages the entire encounter lifecycle in a single solution, from scoping and selection through verification, preparation, submission, and reconciliation. Three key principles drive its success in Arizona:

• Deep integration with state-specific validation rules.
• Automated error detection before submission – not after.
• Intelligent reconciliation across service categories.

The same principles apply to any organization managing encounters on similar infrastructure and facing similar complexity. The problems aren’t unique. Solving them differently enables different results.

Faster, Smarter Modernization

Both Arizona and Hawaii have recognized the need to modernize their shared legacy infrastructure. AHCCCS is pursuing mainframe modernization initiatives, and both states are investing in next-generation provider management systems.

This transition period presents both risk and opportunity. The complexity of encounter data doesn’t pause while systems are upgraded. Organizations that have already solved their encounter data challenges will navigate the transition with confidence. Those still managing encounters through manual processes and general-purpose tools will find the road considerably rougher.

For any Medicaid managed care environment, the question isn’t whether encounter data complexity will continue to grow. It’s how the systems and solutions in place can keep pace. The organizations that answer that question now, rather than later, are the ones that will maintain data integrity, protect their rate-setting accuracy, and meet the rising bar CMS continues to set.

Twenty years of solving these problems has taught us something worth sharing: you don’t have to wait for the mainframe to modernize before your data does.

Chris Sawotin, CEO

——————————————————-

CureIS Healthcare is a middleware developer with deep expertise in government programs including Medicare Advantage, Medicaid, and ACA Marketplace plans. We’ve been solving encounter data challenges for managed care organizations for over two decades. We were the first healthcare IT company to deliver a commercial solution for dual eligibles data management, and we are among the few leveraging purpose-built AI agents to manage the full encounter lifecycle. Our data centers are SOC 2 Type II attested. HIPAA compliant.

Our purpose-built solutions leverage the proprietary UniSync™ Health Data Management Platform+, which reconciles complex data from many sources of truth into one governed, conformed – real-time – AI-ready data foundation our clients can trust.

Find out how more agile data management could improve your encounter operations.