MAO-002 Updates Signal a New Phase of RAF Eligibility Enforcement

CMS has released an important operational update to the MAO-002 report that could significantly affect how Medicare Advantage organizations manage encounter submissions, chart review programs, and telehealth-related risk adjustment workflows.

Effective for submissions on or after May 14, 2026, and for dates of service on or after January 1, 2026, CMS is updating MAO-002 reporting logic to align with policies finalized in the Calendar Year (CY) 2027 Medicare Advantage Rate Announcement.

At the center of the update are two areas that have become increasingly important in Medicare Advantage risk adjustment:

• Unlinked chart review records
• Audio-only services

While the memo itself is relatively short, the operational implications are significant.

MAO-002 Is Becoming More Than a Reporting Output

Historically, organizations often viewed the MAO-002 report primarily as a processing and reconciliation output.

This update reinforces that the MAO-002 report is increasingly functioning as:

• a risk adjustment eligibility signal
• a payment integrity mechanism
• a compliance indicator
• an encounter governance tool

CMS is effectively embedding policy enforcement directly into encounter reporting logic.

Unlinked Chart Review Records

Beginning May 14, 2026, unlinked chart review records on the MAO-002 report will receive:

• RA Flag: PD (Preliminary – Disallowable)
• Reason Code: PD

This applies when:

  1. The service through date is on or after January 1, 2026, and

  2. The submitted encounter does not contain a PACE contract ID.

Operationally, this is one of the most important components of the update.

CMS is now formally signaling that standalone chart review diagnoses without linked encounters may no longer support RAF eligibility for non-PACE organizations.

This represents a meaningful shift for organizations that have historically relied on retrospective chart review workflows to identify and submit diagnoses separately from encounter-linked claims activity.

Why Encounter Linkage Now Matters More

The policy direction here is clear.

CMS is increasing emphasis on:

• encounter-backed diagnoses
• traceable care delivery
• submission governance
• audit defensibility

In practical terms, organizations may need stronger controls around:

• retrospective coding workflows
• encounter linkage validation
• diagnosis traceability
• chart review governance processes

The focus is moving beyond simply identifying diagnoses.

The question increasingly becomes:

“Can the diagnosis be operationally tied to a valid encounter and supported through the full submission lifecycle?”

Audio-Only Services and Risk Adjustment Eligibility

The memo also updates how CMS evaluates audio-only services within MAO-002 processing.

Beginning May 14, 2026, certain professional, DME, and institutional outpatient encounters may receive:

• RA Flag: PD
• Reason Code: PH

This applies under conditions involving audio-only modifiers:

• Modifier 93
• Modifier FQ

CMS distinguishes between:

• service dates prior to January 1, 2026, using allowable HCPCS validation logic, and
• service dates on or after January 1, 2026, where all accepted service lines are audio-only services.

This reflects CMS’s continued tightening around which telehealth interactions can support risk adjustment eligibility.

A Broader Shift Toward Payment Integrity

Taken together, these MAO-002 changes fit into a much larger CMS trend across Medicare Advantage.

CMS is increasingly emphasizing:

• payment integrity
• encounter validation
• documentation traceability
• audit readiness
• operational defensibility

Across risk adjustment programs, the focus is moving from:

“Was the diagnosis submitted?”

to:

“Was the diagnosis supported, traceable, and policy-aligned?”

This shift affects not only coding teams, but also:

• encounter operations
• compliance programs
• chart review vendors
• telehealth workflows
• RAF reconciliation processes

Operational Considerations for MA Organizations

Given these updates, organizations may want to reassess:

Encounter Linkage Processes

Ensuring diagnoses submitted through chart review activity are appropriately tied to encounters.

Telehealth Coding Controls

Reviewing workflows involving audio-only modifiers and HCPCS eligibility.

MAO-002 Monitoring

Increasing visibility into PD and PH flags that may indicate future RAF disallowance risk.

Retrospective Coding Governance

Reevaluating how retrospective diagnoses move through submission and validation workflows.

The Bottom Line

This CMS update may appear technical on the surface, but its implications are strategic.

The MAO-002 report is evolving into a more active mechanism for determining whether submitted diagnoses remain risk adjustment eligible.

For Medicare Advantage organizations, RAF generation is increasingly expected to be:

• encounter-backed
• traceable
• policy-aligned
• audit-defensible

And CMS is embedding those expectations directly into the encounter processing lifecycle itself.