What is Encounter Data Processing System (EDPS)? Definition, Formula, and Benchmark

The Encounter Data Processing System is CMS's data pipeline for receiving Medicare Advantage encounter submissions. Every MA encounter — every professional, institutional, DME, and Part D event — must be submitted to EDPS within the CMS-defined timely-filing window. EDPS processes those submissions, produces acceptance/rejection responses via MAO-004 reports, and feeds the risk-adjustment calculation engine that ultimately produces plan payments.

EDPS replaced the Risk Adjustment Processing System (RAPS) on a phased schedule from 2012 to 2018. RAPS accepted a stripped-down diagnosis-code submission format; EDPS requires full claim-level detail including procedure codes, place of service, provider NPI, and service dates. This expanded data requirement enables CMS to validate that reported diagnoses come from appropriate provider types and encounter types — a diagnosis reported from a radiology encounter, for example, would fail the requirement that risk-eligible diagnoses come from face-to-face encounters.

Encounter submissions use the ANSI X12 837 transaction set, the same format used for Medicare fee-for-service claims. Plans' submissions are filtered for data quality and policy compliance before acceptance. Rejected encounters must be corrected and resubmitted before the risk-adjustment deadline — typically late January of the year following the payment year. Late-arriving encounters are either excluded from the current payment year's risk score or pushed into a future reconciliation cycle depending on timing.

MAO-004 is the per-submission acceptance/rejection response. Plans' analytics teams must continuously monitor MAO-004 rejection rates and reason codes; patterns (provider-type mismatches, invalid ICD-10-CM codes, missing required fields) indicate systemic submission issues that require corrective action. Persistent high rejection rates can trigger CMS corrective action plans.

For providers, EDPS is largely invisible — their 837 claim submission to the MA plan flows through the plan's own claims adjudication before being forwarded to EDPS. But data quality at the original claim submission determines EDPS acceptance. Incomplete provider NPI data, invalid procedure-diagnosis pairings, and missing modifiers that are tolerated in plan adjudication can cause EDPS rejection downstream, which in turn causes risk-adjustment revenue loss — a loss that sometimes passes back to the provider group in risk-sharing contracts.

Data governance around EDPS submission is mature. Vendor platforms handle EDPS submission for most plans; internal teams validate submission completeness, monitor MAO-004 patterns, and manage correction and resubmission cycles. CMS's own data quality programs (MADE, EDGE server validation) continuously monitor submission integrity.

Encounter Data Processing System (EDPS) is one of the compliance areas where documentation discipline determines audit outcomes more than policy sophistication. Practices that invest in clean Encounter Data Processing System (EDPS) records, consistent 837 file workflows, and auditable raf score evidence come out of OIG, RAC, and MAC audits with materially smaller recoupment exposure than practices with equivalent policies but weaker paper trails.