[{"data":1,"prerenderedAt":190},["ShallowReactive",2],{"article-pace-encounter-data-compliance":3},{"id":4,"title":5,"author":6,"body":7,"category":6,"date":6,"description":169,"extension":182,"featured":183,"image":6,"imageAlt":6,"meta":184,"navigation":185,"path":186,"seo":187,"stem":188,"tags":6,"__hash__":189},"articles\u002Farticles\u002Fpace-encounter-data-compliance.md","Pace Encounter Data Compliance",null,{"type":8,"value":9,"toc":168},"minimark",[10,13,23,27,31,34,37,40,44,47,50,53,56,61,64,67,71,74,77,84,90,96,100,103,109,115,121,127,133,137,140,143,146,149,151],[11,12],"hr",{},[14,15,17,18,22],"h2",{"id":16},"title-encounter-data-accuracy-for-pace-organizations-the-cms-compliance-gap-most-plans-havedescription-cms-is-transitioning-pace-organizations-to-a-new-risk-adjustment-model-by-cy-2029-and-encounter-data-quality-is-the-gating-factor-most-pace-organizations-have-significant-submission-gaps-that-are-already-affecting-risk-scores-and-revenuedate-2026-02-04author-ayin-health-solutionscategory-compliancetags-pace-encounter-data-cms-compliance-risk-adjustmentimage-photographyayin_still_7pngimagealt-administrative-team-reviewing-compliance-documentationfeatured-false","title: \"Encounter Data Accuracy for PACE Organizations: The CMS Compliance Gap Most Plans Have\"\ndescription: \"CMS is transitioning PACE organizations to a new risk adjustment model by CY 2029, and encounter data quality is the gating factor. Most PACE organizations have significant submission gaps that are already affecting risk scores and revenue.\"\ndate: 2026-02-04\nauthor: \"Ayin Health Solutions\"\ncategory: \"Compliance\"\ntags: ",[19,20,21],"span",{},"\"PACE\", \"Encounter Data\", \"CMS\", \"Compliance\", \"Risk Adjustment\"","\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Administrative team reviewing compliance documentation\"\nfeatured: false",[24,25,26],"p",{},"Most PACE organizations have been submitting risk adjustment diagnoses through RAPS — the Risk Adjustment Processing System — for years. It works. It's familiar. And it is quietly becoming a liability. CMS has been pushing PACE organizations toward the Encounter Data System since 2024, and the pressure is no longer theoretical. A blended risk adjustment model went into effect for contract year 2026, with a full transition to encounter-data-only scoring targeted for CY 2029. Organizations that haven't built a reliable encounter data submission workflow are not just behind on compliance — they are leaving risk score accuracy on the table right now, and the gap compounds every month.",[14,28,30],{"id":29},"what-cms-is-actually-requiring","What CMS Is Actually Requiring",[24,32,33],{},"The April 2024 final rule (CMS-4205-F) formalized a set of operational obligations for PACE organizations that took effect January 1, 2025. The grievance provisions get the most attention — 30-day resolution timelines, formal written procedures, participant rights notifications — but the encounter data requirements are the ones with the longer financial tail.",[24,35,36],{},"CMS issued guidance in January 2024 stating that PACE organizations should begin submitting encounter data records (EDRs) and claim review records (CRRs) for PACE center services that don't generate a traditional claim. The explicit goal: build a complete encounter data record in EDS so that CMS has what it needs to score risk using the updated HCC model. Organizations that achieve full EDS submission are no longer required to submit diagnoses through RAPS — but that's a carrot, not just a simplification. The underlying message is that RAPS-based submission has an expiration date.",[24,38,39],{},"The encounter data submission format is X12 837 5010, the same standard used by Medicare Advantage plans. PACE center services should use Place of Service code 66. These are not new standards, but many PACE organizations have never had to apply them systematically to the full range of services they provide — including services delivered at the PACE center that generate a CRR rather than a traditional claim.",[14,41,43],{"id":42},"how-errors-propagate-into-risk-adjustment-and-revenue","How Errors Propagate Into Risk Adjustment and Revenue",[24,45,46],{},"Here is why encounter data accuracy matters beyond box-checking compliance: every diagnosis that doesn't make it into EDS cleanly is a diagnosis that may not get credited in your risk score.",[24,48,49],{},"For CY 2026, CMS is calculating PACE risk scores as a blend — 10 percent based on encounter data and FFS claims alone, and 90 percent incorporating RAPS data alongside encounter and FFS sources. That 10 percent figure sounds small. It isn't. As the blend shifts in subsequent years — and CMS has stated the target is 100 percent encounter-data-based scoring by CY 2029 — an organization that hasn't built accurate EDS submission workflows is starting that transition from a compromised baseline.",[24,51,52],{},"The propagation problem works in both directions. Undercoded encounters suppress RAF scores and reduce revenue. But overcoded encounters — diagnoses submitted without the supporting clinical documentation — create audit exposure. CMS applies specific filtering logic to determine which diagnoses from encounter records are eligible for risk adjustment, including CPT\u002FHCPCS code matching and ICD-10 to HCC mapping validation. An organization submitting encounter records without validating that the supporting codes are present and correct will see diagnoses filtered out on the back end with no visibility into why.",[24,54,55],{},"The practical result: a PACE organization can submit encounter data in good faith, believe it is compliant, and still be carrying a significant risk score accuracy gap. That gap doesn't show up in a denial. It shows up when the reconciliation happens and the revenue isn't there.",[57,58,60],"h3",{"id":59},"the-raps-trap","The RAPS Trap",[24,62,63],{},"Many PACE organizations have been running a parallel submission strategy — RAPS for risk adjustment, with EDS submissions incomplete or inconsistent. This was tolerable when RAPS was the primary input for PACE risk scoring. It is increasingly untenable. CMS has stated clearly that the inability to transition PACE organizations to the updated 2024 CMS-HCC model was directly caused by PACE organizations not submitting comprehensive diagnoses to EDS. The blended model for CY 2026 is a consequence of that submission gap, not a courtesy.",[24,65,66],{},"Organizations still treating RAPS as the primary system of record for risk adjustment data need to treat the 2026 blend as a warning and the 2029 deadline as a hard stop.",[14,68,70],{"id":69},"the-validation-workflow-gaps-most-pace-plans-have","The Validation Workflow Gaps Most PACE Plans Have",[24,72,73],{},"The encounter data problem is not primarily a technology problem. Most PACE organizations have access to a clearinghouse or submission vendor that can route X12 837 files to EDS. The problem is what happens before the file leaves your system and what happens after it's accepted.",[24,75,76],{},"Most PACE organizations are missing three things:",[24,78,79,83],{},[80,81,82],"strong",{},"Front-end code validation."," The diagnosis codes on an encounter record need to be supported by the procedure codes present on the same encounter. PACE center services are particularly vulnerable here because the clinical team documents the visit and the administrative team codes it, and the handoff between those two processes is often manual or loosely structured. If the CPT code on the encounter doesn't map to an HCC-eligible service, the diagnosis won't count — regardless of how accurately the physician documented the condition.",[24,85,86,89],{},[80,87,88],{},"Systematic CRR submission for non-claim services."," PACE organizations provide a wide range of services that don't generate a traditional claim — adult day services, social services, transportation. These encounters are documented, but the CRR submission process for getting those diagnoses into EDS is often an afterthought or completely absent. Every service that doesn't generate an EDR or CRR is a potential gap in the diagnostic record.",[24,91,92,95],{},[80,93,94],{},"Rejection and edit monitoring."," EDS returns edits and rejections on submitted records. Many PACE organizations have no one actively monitoring those returns. Rejected records don't get resubmitted. Edits don't get corrected. The submission log shows activity, but the underlying data is incomplete. An acceptance acknowledgment from EDS is not confirmation that the diagnoses were applied to risk scores — it confirms the file was received.",[14,97,99],{"id":98},"what-a-compliant-submission-process-looks-like","What a Compliant Submission Process Looks Like",[24,101,102],{},"A PACE organization with a defensible encounter data submission workflow has several things in place that most currently don't.",[24,104,105,108],{},[80,106,107],{},"A complete encounter inventory."," Every service type the organization provides should be mapped to a submission pathway: EDR for services with claims, CRR for services without. That mapping should account for PACE center services specifically and should be reviewed whenever the service mix changes.",[24,110,111,114],{},[80,112,113],{},"Validation before submission."," Encounter records should be checked for diagnosis-to-procedure code alignment before they reach the clearinghouse. This is not an audit function — it belongs in the pre-submission workflow so errors get fixed in the correct period rather than discovered at reconciliation.",[24,116,117,120],{},[80,118,119],{},"A closed-loop rejection process."," Every EDS edit and rejection should be routed to someone with both the clinical coding knowledge to understand the error and the operational authority to correct and resubmit. In most PACE organizations, that person doesn't exist as a defined role — the function falls through the gap between the clinical team and the billing team.",[24,122,123,126],{},[80,124,125],{},"Periodic reconciliation against RAPS."," Until the full transition to EDS-only scoring, organizations should be reconciling diagnoses submitted through RAPS against what's been accepted in EDS. Gaps in that reconciliation are revenue gaps.",[24,128,129,132],{},[80,130,131],{},"Documentation that supports the submission."," CMS audit protocols for PACE organizations — which were updated in 2024 — look at the connection between clinical records and submitted diagnoses. Encounter data that isn't supported by the medical record creates audit exposure regardless of whether it was accepted by EDS.",[14,134,136],{"id":135},"the-timeline-and-what-it-means-for-data-collection-now","The Timeline and What It Means for Data Collection Now",[24,138,139],{},"The CY 2029 target for full encounter-data-based risk scoring isn't a distant deadline. It takes three years of encounter data to fully populate a risk model. Organizations that begin building reliable EDS submissions in 2026 will be working with 2026, 2027, and 2028 data when the transition completes. Organizations that wait until 2028 to fix their submission workflows will be entering a fully encounter-data-dependent risk scoring environment with incomplete historical records.",[24,141,142],{},"The 2026 blended model — 10 percent encounter data, 90 percent RAPS\u002Fencounter blend — already penalizes organizations with poor EDS submission quality. That penalty grows each year as the blend shifts. The math is straightforward: every percentage point of the blend that relies on encounter data is a percentage point where submission quality directly determines revenue.",[24,144,145],{},"CMS is watching this. PACE audit resources published by the National PACE Association reflect CMS's increased scrutiny on encounter data accuracy, and the updated audit protocol includes specific review of encounter submission completeness and the alignment between clinical records and submitted diagnoses.",[24,147,148],{},"For a compliance officer or ops director at a PACE organization, the question is not whether to fix the encounter data submission workflow. It's whether to fix it before or after the revenue impact becomes visible.",[11,150],{},[24,152,153],{},[154,155,156,157,162,163,167],"em",{},"If your organization is working through encounter data submission gaps or preparing for the risk adjustment model transition, ",[158,159,161],"a",{"href":160},"\u002Fsolutions","Ayin's encounter data services"," are built specifically for PACE and Medicare Advantage plans — or ",[158,164,166],{"href":165},"\u002Fcontact","reach out directly"," to talk through where your current workflow stands.",{"title":169,"searchDepth":170,"depth":170,"links":171},"",2,[172,174,175,179,180,181],{"id":16,"depth":170,"text":173},"title: \"Encounter Data Accuracy for PACE Organizations: The CMS Compliance Gap Most Plans Have\"\ndescription: \"CMS is transitioning PACE organizations to a new risk adjustment model by CY 2029, and encounter data quality is the gating factor. Most PACE organizations have significant submission gaps that are already affecting risk scores and revenue.\"\ndate: 2026-02-04\nauthor: \"Ayin Health Solutions\"\ncategory: \"Compliance\"\ntags: \"PACE\", \"Encounter Data\", \"CMS\", \"Compliance\", \"Risk Adjustment\"\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Administrative team reviewing compliance documentation\"\nfeatured: false",{"id":29,"depth":170,"text":30},{"id":42,"depth":170,"text":43,"children":176},[177],{"id":59,"depth":178,"text":60},3,{"id":69,"depth":170,"text":70},{"id":98,"depth":170,"text":99},{"id":135,"depth":170,"text":136},"md",false,{},true,"\u002Farticles\u002Fpace-encounter-data-compliance",{"description":169},"articles\u002Fpace-encounter-data-compliance","sABN2Qoj3TRdmUGPqbH9l608URVmd2PPWcjTMrQzZBg",1790973089856]