CMS EDPS 2026: Stricter Claim Checks

CMS EDPS March 2026 Update: A Complete, Simple, and Detailed Breakdown

If you’ve heard about the latest CMS HPMS update and want a clear, straightforward explanation of what it means—this guide is for you.

This blog breaks down the March 20, 2026 Encounter Data Processing System (EDPS) update in a way that’s easy to understand, even if you’re not deeply familiar with healthcare claims, coding, or risk adjustment.

Think of this as your one-stop guide to what changed, why it matters, and what you should do about it.

What is this update about?

At its core, this update is about how CMS checks healthcare claims before accepting them.

CMS has made changes to:

  • Remove some old rules

  • Modify existing rules

  • Add several new rules

These rules are called “edits”, and they act like checkpoints that every claim must pass through.

What is EDPS (in simple terms)?

EDPS is the system CMS uses to:

  • Receive claims (encounter data)

  • Validate them

  • Decide whether to accept or reject them

Think of EDPS like an airport security system:

  • Some passengers (claims) pass smoothly

  • Some get flagged for extra screening

  • Some are stopped entirely

Types of EDPS Edits

Every claim is evaluated using edits that fall into two categories:

1. Informational Edits 📝

  • Claim is accepted

  • But flagged for issues

-> These are warnings, not failures
-> However, they often become strict rules in the future

2. Reject Edits

  • Claim is rejected

  • Must be corrected and resubmitted

-> These directly impact payment and timelines

Why This Update Is Bigger Than Usual

This is not a regular quarterly update.

Instead, it includes:

  • Changes from the past three quarters

  • Combined into a single release

-> Result:
A larger-than-normal update with broader impact

CMS will return to regular quarterly updates starting June 2026.

Major Themes of This Update

Let’s simplify everything into a few big ideas:

1. Stricter Validation

Some rules that were previously flexible are now strict.

-> Meaning: Less tolerance for missing or incorrect data

2. More Detailed Checks

CMS is now checking:

  • Relationships between fields

  • Not just individual values

-> Meaning: Data must make sense together, not just individually

3. More Areas Being Monitored

New edits focus on:

  • Clinical trials

  • Dialysis (ESRD)

  • Preventive care

  • Telehealth

  • Screening procedures

Key Changes: What Got Stricter

Some edits were updated to remove older flexibility.

Example Changes:

  • HIPPS codes are now strictly required

  • Required qualifiers must always be present

  • Certain occurrence codes must always include supporting data

-> Earlier: Some of these were just warnings
-> Now: They can cause claim rejection

Changes to Existing Rules

Some edits were refined rather than made stricter.

Examples:

  • Duplicate claim logic adjusted
    → Fewer false duplicate flags

  • Updates to service lists for outpatient programs

-> These changes improve accuracy rather than restrict submissions

New Edits Introduced

This is the largest part of the update.

CMS added several new validations across different areas.

Clinical Trials: A Major Focus Area

CMS introduced multiple edits to ensure proper billing for clinical trials.

Now required:

  • Specific diagnosis codes indicating a clinical trial

  • Correct modifiers (like trial indicators)

  • Proper procedure and billing combinations

  • Supporting documentation (like billing notes)

-> Why this matters:
CMS wants to ensure clinical trial claims are clearly identifiable and properly documented

ESRD (Dialysis) Billing Updates

New validations include:

  • Required value codes for dialysis services

  • Valid combinations of condition codes

  • Mandatory drug-related modifiers for certain medications

-> Why this matters:
Dialysis billing must now be highly precise and consistent

Preventive Care (HIV PrEP)

New rules ensure:

  • Preventive drugs are billed with proper diagnoses

  • Supply charges are tied to actual drug billing

-> Why this matters:
Prevents incomplete or disconnected billing

Screening Services (Colorectal, etc.)

CMS added checks to ensure:

  • Correct type of bill is used

  • Proper diagnosis and procedure combinations exist

-> Why this matters:
Improves accuracy of preventive service reporting

Telehealth & Institutional Claims

New validations include:

  • Correct use of telehealth modifiers

  • Logical consistency between different claim fields

-> Why this matters:
CMS is improving oversight of:

  • Remote care services

  • Facility-based billing

A Big Shift: Cross-Field Validation

One of the most important changes:

-> CMS is no longer just checking individual fields
-> It is checking whether fields make sense together

Example:

  • A certain place-of-service code cannot exist with a specific revenue code

-> This is called cross-field validation

What This Means for You

Immediate Impact:

  • Increase in claim rejections

  • More informational flags

  • Higher need for accurate coding

High-Risk Areas:

  • Institutional claims

  • Clinical trials

  • Dialysis services

  • Preventive care billing

What Teams Should Do

For Coders:

  • Ensure all required fields are complete

  • Use correct combinations of codes

  • Pay attention to new clinical trial requirements

For Reviewers:

  • Monitor informational edits closely

  • Treat them as early warnings

For Technical Teams:

  • Update validation systems

  • Test claims before submission

For Leadership:

  • Track rejection trends after March 20

  • Focus on high-risk claim categories

Appendix Notes (Important but Non-Operational)

The document also includes:

  • References to standardized billing codes (UB-04)

  • Copyright and usage restrictions

-> These do not affect day-to-day operations but are important legally

Final Takeaway

This update represents a clear shift in direction.

CMS is moving from:
-> Simply collecting data

To:
-> Actively enforcing data quality and accuracy

In One Sentence

Claims must now be more complete, accurate, and logically consistent—or they will be flagged or rejected.

If you’re preparing for this update, the best approach is simple:

  • Validate early

  • Code carefully

  • Review thoroughly

Because in this new system, even small gaps won’t slip through unnoticed.