[{"data":1,"prerenderedAt":3611},["ShallowReactive",2],{"articles":3},[4,207,404,554,788,959,1091,1291,1466,1735,1929,2076,2274,2431,2587,2741,2930,3109,3282,3443],{"id":5,"title":6,"author":7,"body":8,"category":189,"date":190,"description":191,"extension":192,"featured":193,"image":194,"imageAlt":195,"meta":196,"navigation":197,"path":198,"seo":199,"stem":200,"tags":201,"__hash__":206},"articles\u002Farticles\u002Fprovider-directory-accuracy-compliance.md","Provider Directory Accuracy: The Compliance Gap with Real Claims and Audit Consequences","Ayin Health Solutions",{"type":9,"value":10,"toc":180},"minimark",[11,15,18,23,26,32,35,38,43,46,49,52,57,60,63,67,70,73,76,79,82,85,89,92,95,98,101,105,108,111,114,117,120,123,127,130,136,142,148,154,157,160],[12,13,14],"p",{},"A member calls to schedule an appointment. She finds a primary care physician listed in her plan's online directory, confirms the address, and drives across town. The physician retired eight months ago. The practice stopped accepting her plan's members six months before that. She calls your member services line frustrated and unserved. Three days later, a claims submission comes through for that provider's NPI — still active in your adjudication system from the old contract. The claim denies. Your network team generates a manual exception. Someone updates a record. The whole sequence costs your plan time, money, and a member complaint.",[12,16,17],{},"This scenario isn't unusual. A CMS national review found that 48.74% of provider locations in Medicare Advantage online directories contained at least one inaccuracy — wrong phone number, wrong address, or outdated network participation status. For Medicaid managed care, secret shopper studies have found that more than a third of listed providers were unreachable or no longer serving Medicaid patients. The directory error is rarely a single isolated fact. It propagates — into member experience, into claims adjudication, and into audit findings.",[19,20,22],"h2",{"id":21},"what-the-regulations-actually-require","What the Regulations Actually Require",[12,24,25],{},"Federal directory accuracy requirements now span three distinct regulatory frameworks, each with specific update frequencies and accuracy thresholds.",[12,27,28],{},[29,30,31],"strong",{},"Medicaid Managed Care — 42 CFR 438.10",[12,33,34],{},"The April 2024 Medicaid Managed Care Access, Finance and Quality final rule tightened the requirements at 42 CFR 438.10(h). Managed care organizations must update provider directory information within 30 calendar days of receiving a change notification. The rule also requires states to contract with an independent entity — separate from both the state agency and any contracted MCO — to conduct annual secret shopper surveys verifying active network status, street address, phone number, and whether providers are accepting new Medicaid enrollees. Survey results must be reported to CMS annually and posted publicly. States must notify managed care plans of identified errors within three business days of detection.",[12,36,37],{},"The 30-day update requirement took full effect July 1, 2025. Plans that were operating on weekly batch updates or monthly reconciliation cycles were already out of compliance on that date.",[12,39,40],{},[29,41,42],{},"Medicare Advantage — 42 CFR 422 and the REAL Health Providers Act",[12,44,45],{},"MA plans must verify provider directory information at least once every 90 days and process updates within 30 days of becoming aware of changes. CMS requires a minimum 85% directory accuracy rate, with accuracy measured across practice locations, phone numbers, specialty designations, and network participation status. Plans must attest annually that their directory is accurate and complete.",[12,47,48],{},"The Consolidated Appropriations Act, 2026 added the REAL Health Providers Act, requiring MA organizations to conduct an annual analysis of their directory accuracy and report findings directly to CMS. Starting with plan year 2029, plans must prominently display their provider directory accuracy score within the directory itself.",[12,50,51],{},"CMS also finalized requirements for MA plans to submit provider directory data directly to Medicare Plan Finder for 2027 open enrollment — centralizing the data in a format CMS controls, which makes inaccuracies more visible and more auditable.",[12,53,54],{},[29,55,56],{},"No Surprises Act",[12,58,59],{},"The No Surprises Act added a separate layer of directory requirements for group health plans and health insurance issuers. Plans must verify all provider directory data every 90 days, process updates within two business days of receiving information, and remove providers whose information cannot be verified within the plan's established verification period. Plans must also respond within one business day to requests confirming whether a provider is in-network for a specific service, and must retain that communication for at least two years.",[12,61,62],{},"These three frameworks overlap for many plans. An MA-Medicaid dual-eligible plan may be operating under all three simultaneously.",[19,64,66],{"id":65},"how-directory-errors-become-claims-denials","How Directory Errors Become Claims Denials",[12,68,69],{},"The connection between directory inaccuracy and claims denials runs through a single identifier: the NPI.",[12,71,72],{},"Every claim submitted to your plan carries a billing NPI — either a Type 1 (individual provider) or Type 2 (organizational) identifier. Your claims adjudication system validates that NPI against your internal provider file: Is this NPI active? Is this provider contracted? Is the service type covered under this provider's agreement?",[12,74,75],{},"When your provider directory contains a provider who has left the network but whose NPI has not been deactivated in the adjudication system, two problems occur simultaneously. First, members can still find and attempt to access that provider through your directory. Second, claims submitted under that NPI continue adjudicating — sometimes correctly, sometimes incorrectly depending on what other system records say.",[12,77,78],{},"The reverse is equally common. A new provider joins your network. Your network team updates the directory. But the NPI is not yet active in the adjudication system because the credentialing approval hasn't propagated through to the claims platform. The provider submits claims. They deny. The provider calls. Your staff manually intervenes.",[12,80,81],{},"Denial code CO-207 and CO-208 are the claims-level signals of this problem — provider NPI not on file, or billing NPI not matching the registered NPI with the payer. These are administrative denials, not clinical ones. They are fully preventable if directory and adjudication data stay synchronized. They are recurring and invisible if they don't.",[12,83,84],{},"The administrative cost to rework a single denied claim runs between $118 and $181. For a plan with 50,000 members and a modestly sized contracted network, NPI and provider data mismatches can generate dozens of these denials per week during periods of active network change — onboarding, re-credentialing cycles, contract terminations.",[19,86,88],{"id":87},"what-audit-findings-actually-look-like","What Audit Findings Actually Look Like",[12,90,91],{},"CMS and state Medicaid agencies have sharpened their focus on directory accuracy over the last two years. The mechanisms are specific.",[12,93,94],{},"For MA plans, CMS conducts routine compliance audits that include directory accuracy as a scored element. Failure to meet the 85% accuracy threshold is a findings trigger. Corrective action plans are required from organizations that fall below the threshold, and CMS has established formal CAP requirements for directory accuracy as of its July 2024 guidance.",[12,96,97],{},"For Medicaid MCOs, the new independent secret shopper requirement is the audit mechanism states will use going forward. When a secret shopper calls a listed provider and finds that the provider is not accepting the plan's members, not reachable at the listed number, or has moved to an unlisted address, that is a data point in a scored survey. Plans that accumulate enough of those findings trigger a compliance review. The results are public.",[12,99,100],{},"State-level audits have also surfaced systemic issues. A January 2025 audit in Vermont identified problems in the state's oversight of Medicaid managed care programs, including provider data accuracy gaps. GAO's 2023 review of Medicaid program integrity found that nearly 60% of state audit findings were repeated from the prior year — the same problems, uncorrected. Directory accuracy is among those repeated findings.",[19,102,104],{"id":103},"the-difference-between-directory-maintenance-and-directory-auditing","The Difference Between Directory Maintenance and Directory Auditing",[12,106,107],{},"Plans often treat these as the same function. They are not.",[12,109,110],{},"Directory maintenance is the operational workflow: receiving provider change notifications, processing them within the required update window, reflecting changes in both the public-facing directory and the internal adjudication system. This requires a defined intake process, a maximum processing time, and a system of record that is authoritative for both directory display and claims validation.",[12,112,113],{},"Directory auditing is the verification function: confirming that what is in your directory matches reality. This means outbound verification — calling providers or sending attestation requests to confirm address, phone, accepting status, and network participation. It means comparing your directory data against NPPES (the National Plan and Provider Enumeration System) for NPI status. It means tracking the results of that verification and acting on discrepancies within a defined window.",[12,115,116],{},"The regulatory requirements implicitly demand both. The 30-day update rule is a maintenance standard. The independent secret shopper requirement is an audit mechanism the state performs on your behalf — or against you, depending on what they find.",[12,118,119],{},"Most small plans have some version of directory maintenance. Few have a documented, repeatable directory auditing workflow that runs independently of maintenance. The audit is what catches the errors that maintenance missed: the provider who confirmed they were still in-network six months ago but has since moved without notifying the plan, or the group practice that updated its location but whose individual providers' records were not updated individually.",[12,121,122],{},"The regulatory expectation is that you have both — and that you can demonstrate both through documented processes, update logs, and attestation records.",[19,124,126],{"id":125},"what-a-compliant-directory-workflow-requires","What a Compliant Directory Workflow Requires",[12,128,129],{},"A compliant workflow has four components that must function together.",[12,131,132,135],{},[29,133,134],{},"A single system of record."," Your provider directory and your claims adjudication provider file must draw from the same authoritative data source — or must have a real-time synchronization mechanism that keeps them aligned. When the directory says a provider is inactive, the claims system must reflect the same status within the required update window. When the claims system activates a new billing NPI, the directory must be updated to match. The two cannot be maintained separately on different schedules.",[12,137,138,141],{},[29,139,140],{},"Defined intake and processing SLAs."," Every provider change notification — whether it comes from a provider attestation, a contract termination, a credentialing re-verification, or an external source — must enter a documented workflow with a timestamp and a processing deadline. For Medicaid MCOs, that deadline is 30 days. For No Surprises Act compliance, updates to network participation status must be processed within two business days. Those SLAs must be tracked, not assumed.",[12,143,144,147],{},[29,145,146],{},"Proactive outbound verification on a defined cycle."," Waiting for providers to notify you of changes is not sufficient and not compliant. Your plan must conduct outbound attestation or verification at a defined frequency — quarterly is the minimum for most frameworks — and must document the results. Providers who cannot be verified must be flagged and, depending on the regulatory framework, removed from the directory.",[12,149,150,153],{},[29,151,152],{},"An error detection and escalation path."," When a discrepancy is identified — through a member complaint, a claims denial pattern, a failed verification, or a state survey notification — your plan must have a documented path for correcting the record within the required window and tracking the correction to completion. For Medicaid, states must notify you of errors within three business days and expect a response. That requires someone accountable for receiving and acting on those notifications.",[12,155,156],{},"Plans managing these workflows in spreadsheets and shared inboxes cannot reliably meet these standards during periods of network change. The manual touchpoints are where the 30-day clock gets missed, where the NPI update doesn't reach the claims system, and where the outbound verification cycle gets skipped when staff are occupied elsewhere.",[158,159],"hr",{},[12,161,162],{},[163,164,165,166,173,174,179],"em",{},"If your plan's directory management workflow is overdue for a compliance review, Ayin's platform and operations services are designed to close the gap between regulatory requirements and operational reality — learn more at ",[167,168,172],"a",{"href":169,"rel":170},"https:\u002F\u002Fayin.com\u002Fplatform",[171],"nofollow","ayin.com\u002Fplatform"," or ",[167,175,178],{"href":176,"rel":177},"https:\u002F\u002Fayin.com\u002Fcontact",[171],"reach out directly",".",{"title":181,"searchDepth":182,"depth":182,"links":183},"",2,[184,185,186,187,188],{"id":21,"depth":182,"text":22},{"id":65,"depth":182,"text":66},{"id":87,"depth":182,"text":88},{"id":103,"depth":182,"text":104},{"id":125,"depth":182,"text":126},"Compliance","2026-06-24","CMS and state Medicaid agencies are actively auditing provider directory accuracy — and the same errors that trigger audit findings also drive claims denials. This article explains the regulatory requirements, the claims cascade, and what a compliant directory workflow actually requires.","md",false,"\u002Fphotography\u002FAyin_still_7.png","Healthcare network and provider management",{},true,"\u002Farticles\u002Fprovider-directory-accuracy-compliance",{"title":6,"description":191},"articles\u002Fprovider-directory-accuracy-compliance",[202,203,189,204,205],"Network Management","Provider Directory","CMS","Claims","A9UlmgFGiHPsimPzQk-CqbFCPWKy2q5uc0zP_vbWeP4",{"id":208,"title":209,"author":7,"body":210,"category":390,"date":391,"description":392,"extension":192,"featured":193,"image":194,"imageAlt":393,"meta":394,"navigation":197,"path":395,"seo":396,"stem":397,"tags":398,"__hash__":403},"articles\u002Farticles\u002Fpremium-billing-health-plans.md","Premium Billing at Scale: Why Small Plans Keep Getting It Wrong",{"type":9,"value":211,"toc":382},[212,215,218,222,225,228,231,237,243,249,252,256,259,262,265,268,271,275,278,281,284,287,290,293,297,300,303,306,309,313,316,319,325,331,337,343,349,352,356,359,362,365,368,371],[12,213,214],{},"A member's premium goes unpaid for sixty days. The billing system flags it correctly. The grace period notice goes out on time. Then someone pulls the enrollment record and finds the problem: the member's LIS status changed three months ago, the billing system never received the update, and the plan has been invoicing the member for a premium they were no longer required to pay. The member thought the bill was wrong. They were right. The plan spent two months chasing a balance that legally didn't exist — and the disenrollment notice that went out last week is now a compliance problem.",[12,216,217],{},"This scenario is not unusual. It is, in fact, one of the most common premium billing failures at small and midsized Medicare Advantage plans. The billing system did exactly what it was configured to do. The failure happened upstream.",[19,219,221],{"id":220},"the-source-of-billing-errors-is-usually-not-the-billing-system","The Source of Billing Errors Is Usually Not the Billing System",[12,223,224],{},"Most billing leaders at smaller plans treat their billing software as the first place to look when something goes wrong. That instinct is usually wrong.",[12,226,227],{},"Billing systems generate invoices based on the data they receive. If enrollment data is stale, billing data is stale. If subsidy status changes aren't transmitted downstream, the billing engine doesn't know. If a member's Social Security deduction setup is delayed or misconfigured, the billing system shows a balance that doesn't reflect what SSA is holding.",[12,229,230],{},"The failure modes that cause billing errors almost always originate in one of three places:",[12,232,233,236],{},[29,234,235],{},"Enrollment data integrity."," Member demographic changes, coverage effective date corrections, and plan-to-plan transfer records all affect billing. When enrollment transactions are processed late or contain errors, billing often inherits those errors — and compounds them over multiple billing cycles before anyone catches them.",[12,238,239,242],{},[29,240,241],{},"Subsidy status transmission."," CMS transmits LIS status changes through the Monthly Membership Report (MMR) file. Plans that don't systematically reconcile MMR data against their billing configuration on a monthly basis frequently discover subsidy mismatches only when a member calls to complain or when an audit surfaces the discrepancy.",[12,244,245,248],{},[29,246,247],{},"SSA and CMS payment timing."," For members who have their MA premiums withheld from their Social Security benefit, the payment flow runs through CMS before it reaches the plan. Processing delays, hold codes, and mismatches between SSA records and the plan's enrollment file create phantom balances that the billing system dutifully tracks — and the plan diligently pursues — even when no actual money is owed.",[12,250,251],{},"Fixing billing accuracy requires fixing the data feeds that billing depends on. That starts with knowing exactly where each data element comes from and how frequently it's reconciled.",[19,253,255],{"id":254},"the-ma-premium-billing-calendar-and-its-compliance-requirements","The MA Premium Billing Calendar and Its Compliance Requirements",[12,257,258],{},"Medicare Advantage plans operate under a defined regulatory framework for how premium non-payment must be handled. Under 42 CFR § 422.74, an MA organization may disenroll a member for failure to pay plan premiums — but only after providing a grace period of at least two calendar months. During that grace period, the plan must send the member written notice that failure to pay by the end of the grace period will result in disenrollment.",[12,260,261],{},"If the balance remains unpaid after the grace period, disenrollment becomes effective the first day of the following month. CMS must be notified via the enrollment transaction system. The member receives a disenrollment notice within ten calendar days of the plan receiving CMS confirmation.",[12,263,264],{},"This sequence sounds manageable. In practice, small plans routinely break it in two ways.",[12,266,267],{},"First, they miscalculate grace period start dates. The clock starts from the premium due date, not from when the billing system flagged the account as delinquent. Manual billing workflows that run on irregular cycles can create gaps of weeks between when a balance is actually overdue and when the grace period officially begins in the system. That gap can push the entire disenrollment timeline into the following month — or require a notice to be reissued.",[12,269,270],{},"Second, they send notices without confirming the underlying balance is accurate. A notice sent to collect a premium the member doesn't owe is not just an operational error. It is a potential regulatory violation. CMS expects plans to verify that a balance is legitimate before initiating the grace period process. Issuing a disenrollment notice on an invalid balance — particularly one rooted in a subsidy data error — is one of the fastest ways to generate a member complaint that escalates to CMS.",[19,272,274],{"id":273},"lis-handling-the-billing-error-most-plans-dont-see-coming","LIS Handling: The Billing Error Most Plans Don't See Coming",[12,276,277],{},"Low-income subsidy status is one of the more technically demanding aspects of MA billing, and it is the area where small plans make the most consequential errors.",[12,279,280],{},"Full LIS (Level 1) beneficiaries pay no plan premium for a benchmark plan. Partial LIS beneficiaries (Levels 2, 3, and 4) pay reduced premiums based on their subsidy level. When a member's LIS status changes — because they gained Medicaid eligibility, lost it, or were reassigned by SSA — the plan's billing configuration must update immediately.",[12,282,283],{},"CMS communicates these changes through the MMR file, which is released monthly. The MMR contains the current subsidy level for every enrolled member, along with retroactive adjustments when status changes apply to prior months. Plans that process the MMR manually or on a delay will carry incorrect billing configurations for some portion of their LIS population at any given time.",[12,285,286],{},"The downstream effects are predictable. Overbilled LIS members — those charged a premium they aren't required to pay — tend not to pay. From the billing system's perspective, they look like non-payers. The plan initiates the grace period process. The member receives a notice demanding payment of a balance that CMS's own records say they don't owe. The member calls their State Health Insurance Assistance Program (SHIP) counselor. The complaint reaches CMS.",[12,288,289],{},"Underbilled LIS members create the opposite problem: the plan is collecting less than it should, the revenue shortfall may not surface for months, and retroactive correction requires navigating CMS's adjustment processes while maintaining member-level documentation that justifies each correction.",[12,291,292],{},"Preventing both requires treating the monthly MMR reconciliation as a billing-critical process, not a reporting task. Every LIS status change in the MMR should trigger a billing configuration review before the next invoice cycle runs.",[19,294,296],{"id":295},"lockbox-integration-and-the-reconciliation-gap","Lockbox Integration and the Reconciliation Gap",[12,298,299],{},"Most MA plans receive premium payments through multiple channels: SSA withholding, ACH\u002FEFT, check, and occasionally employer group remittances for MA employer group waiver plans. Lockbox services handle the check volume, but lockbox data rarely arrives in a format that maps cleanly to the billing system.",[12,301,302],{},"Checks frequently arrive without adequate identifying information. The member account number doesn't appear on the check. A spouse writes the check in their own name. A payment arrives for a round number that doesn't match any outstanding balance. Each of these situations requires a manual matching decision — and every manual matching decision is an opportunity for a payment to be applied to the wrong account, or not applied at all, until someone notices the discrepancy.",[12,304,305],{},"Plans that run lockbox reconciliation as a weekly or monthly batch process accumulate unmatched payments. Those unmatched payments sit in suspense accounts. Meanwhile, members whose payments are sitting in suspense continue to appear as delinquent in the billing system. Grace period notices go out. The member calls — they have proof of payment. Staff spend hours tracing the check through the lockbox data.",[12,307,308],{},"Daily lockbox reconciliation is the operational standard that eliminates most of this. It requires either a billing platform that ingests lockbox files automatically or a dedicated reconciliation process that treats unmatched payments as same-day exceptions requiring resolution. For smaller plans, daily reconciliation often feels like more overhead than the problem warrants — until the suspense account balance grows large enough to misrepresent the plan's actual cash position.",[19,310,312],{"id":311},"what-a-billing-cycle-audit-actually-covers","What a Billing Cycle Audit Actually Covers",[12,314,315],{},"CMS program audits routinely include premium billing in their scope for MA organizations. A billing cycle audit looks at a specific set of controls, and small plans consistently underinvest in the documentation that supports them.",[12,317,318],{},"The core questions an audit will answer:",[12,320,321,324],{},[29,322,323],{},"Completeness of grace period notices."," Did every member who entered a delinquency state receive a timely, accurate grace period notice? Plans that can't produce notice logs with delivery confirmation are exposed regardless of whether they sent the notices.",[12,326,327,330],{},[29,328,329],{},"Accuracy of balances at notice time."," Was the stated balance on each notice correct as of the notice date? This requires tracing the balance back to the enrollment and subsidy records that generated it.",[12,332,333,336],{},[29,334,335],{},"Timeliness of disenrollment transactions."," When a grace period expired without payment, was the CMS disenrollment transaction submitted within the required timeframe? Late submissions create gaps in member coverage records that can affect the member's ability to access care.",[12,338,339,342],{},[29,340,341],{},"LIS configuration accuracy."," Does the plan's billing system configuration match the LIS levels reflected in the most recent MMR for each member? Mismatches, even temporary ones, represent a compliance finding.",[12,344,345,348],{},[29,346,347],{},"Reinstatement and good-cause handling."," For members who were disenrolled and subsequently requested reinstatement under the good-cause provisions of 42 CFR § 422.74(d), did the plan process those requests correctly and within required timeframes?",[12,350,351],{},"Small plans typically have the processes. What they lack is the documentation that proves the processes ran correctly. An audit doesn't just verify outcomes — it verifies the process that produced them. A billing cycle audit conducted internally before CMS asks for one is one of the more efficient compliance investments a plan can make.",[19,353,355],{"id":354},"the-operations-posture-that-prevents-billing-failures","The Operations Posture That Prevents Billing Failures",[12,357,358],{},"Billing errors are not primarily a technology problem. They are a data governance and process integration problem. The plans that maintain the cleanest billing operations share a few common characteristics.",[12,360,361],{},"They treat enrollment data as a billing dependency. Changes to member records — coverage effective dates, plan codes, subsidy status, SSA withholding setup — are reviewed for billing impact before they're finalized. Enrollment and billing are not separate workflows with separate owners. They're one workflow with a handoff point that gets monitored.",[12,363,364],{},"They run monthly MMR reconciliation as a first-order operation. The MMR file is reviewed the day it's available. LIS discrepancies are flagged and resolved before the next billing cycle runs, not after the next member complaint arrives.",[12,366,367],{},"They audit their billing cycle before CMS does. Once a year, a billing cycle audit — covering notices, balances, disenrollment transactions, and LIS configuration — is completed internally and the findings are addressed. Plans that only see their billing operations through the lens of a CMS audit tend to find problems at the worst possible time.",[12,369,370],{},"Premium billing is one of those functions that operates quietly when it works and loudly when it doesn't. The noise, when it arrives, tends to arrive simultaneously as a cash flow problem, a member relations problem, and a compliance problem. The good news is that most of the underlying failure modes are predictable — which means they're preventable.",[12,372,373],{},[163,374,375,376,173,379,179],{},"Ayin Health Solutions supports premium billing operations for Medicare Advantage and Medicaid plans, including billing configuration audits, MMR reconciliation workflows, and enrollment-to-billing integration. Learn more at ",[167,377,172],{"href":169,"rel":378},[171],[167,380,178],{"href":176,"rel":381},[171],{"title":181,"searchDepth":182,"depth":182,"links":383},[384,385,386,387,388,389],{"id":220,"depth":182,"text":221},{"id":254,"depth":182,"text":255},{"id":273,"depth":182,"text":274},{"id":295,"depth":182,"text":296},{"id":311,"depth":182,"text":312},{"id":354,"depth":182,"text":355},"Operations","2026-06-10","Premium billing failures in Medicare Advantage plans create cash flow gaps, regulatory exposure, and avoidable member disenrollments. Here is where the errors actually come from — and what prevents them.","Healthcare administration operations",{},"\u002Farticles\u002Fpremium-billing-health-plans",{"title":209,"description":392},"articles\u002Fpremium-billing-health-plans",[399,390,400,401,402],"Premium Billing","Cash Flow","Enrollment","Medicare Advantage","51xp3tp5_KGHz6LElseMO6cojLcNQAk7SuLHVcCurEg",{"id":405,"title":406,"author":7,"body":407,"category":189,"date":543,"description":544,"extension":192,"featured":193,"image":194,"imageAlt":545,"meta":546,"navigation":197,"path":547,"seo":548,"stem":549,"tags":550,"__hash__":553},"articles\u002Farticles\u002Fhr1-medicaid-cuts-operationalize.md","HR1 and Medicaid Cuts: What Small Plans Need to Operationalize Now",{"type":9,"value":408,"toc":536},[409,412,416,419,425,431,437,441,444,447,450,453,457,460,463,466,470,473,479,485,491,497,503,509,513,516,519,522,525,527],[12,410,411],{},"President Trump signed H.R. 1 — the \"One Big Beautiful Bill Act\" — on July 4, 2025. The CBO projects it will reduce Medicaid enrollment by 11 million people by 2034: 7 million expansion adults, 3 million children, 1 million traditional adults. Those numbers represent capitation revenue that will vanish from small plans in waves between now and 2027. The policy debate is over. What remains is the operational question: what does your back office actually need to do before the first major deadlines land?",[19,413,415],{"id":414},"what-hr1-changed-the-operational-version","What HR1 Changed — The Operational Version",[12,417,418],{},"Three provisions drive the administrative burden on plans. Work requirements get the attention. The other two are less discussed and equally disruptive.",[12,420,421,424],{},[29,422,423],{},"FMAP reduction."," The 5-percentage-point enhanced FMAP that incentivized late-expanding states was sunsetted effective January 1, 2026. Gone. For states that expanded Medicaid between 2014 and 2021, the standard 90% federal match on expansion adults remains in place — but HR1 layered additional restrictions on how states can use provider taxes to fund their share. Section 71115 of the law froze each state's allowable provider tax capacity at the level enacted and actively imposed as of July 4, 2025. Any state that was planning to raise provider taxes to offset a budget gap can no longer do so. That constraint lands on states, but the downstream effect hits managed care plans through rate-setting. States facing a narrowed funding base will pressure capitation rates. Plans that can't demonstrate cost discipline will be the first to see it.",[12,426,427,430],{},[29,428,429],{},"Work requirements, December 31, 2026 deadline."," Most expansion adults aged 19–64 must demonstrate 80 hours per month of qualifying activity — employment, job training, at least half-time education, or community service. States must have systems operational by January 1, 2027. State outreach to affected members must begin between June 30 and August 31, 2026. CMS issued initial guidance on December 8, 2025 and is required to publish a final interim rule by June 1, 2026. That six-month window between final guidance and go-live is where the operational risk concentrates.",[12,432,433,436],{},[29,434,435],{},"State directed payment restrictions."," Starting with rating periods beginning January 1, 2028, grandfathered state directed payments are phased down by 10 percentage points per year until they hit Medicare-based limits. If your plan's provider contracts are built around rates supplemented by state directed payments, those rates are changing on a hard schedule. You need to know which contracts are exposed.",[19,438,440],{"id":439},"the-enrollment-data-problem-nobody-is-solving-yet","The Enrollment Data Problem Nobody Is Solving Yet",[12,442,443],{},"The disenrollment math is not abstract. During the COVID-era unwinding — a far smaller and more predictable disenrollment event — over two-thirds of individuals who lost coverage were disenrolled for procedural reasons, not eligibility reasons. Many re-enrolled within months, creating short coverage gaps that generate claim disputes, mid-year data corrections, and reconciliation backlogs. The work requirement disenrollment wave will be larger, faster, and driven by a new verification logic that state eligibility systems aren't built for yet.",[12,445,446],{},"For a plan with 50,000 expansion-eligible members, even a 15% disenrollment rate over 12 months means 7,500 members cycling off your roster. Each disenrollment generates a transaction. Many of those transactions will be delayed, incorrect, or duplicated — because the state systems producing them are operating under new rules, with staff shortages that were already documented before HR1 added another layer of complexity. Georgetown's Center for Children and Families found that implementing work reporting requirements alone will cost states hundreds of millions of dollars in systems and administration — and many states are starting from eligibility systems that are a decade old.",[12,448,449],{},"The operational failure mode for plans is the phantom member: a member who appears on your enrollment roster and generates capitation revenue, but whose eligibility has lapsed. When state eligibility transactions are delayed or don't transmit cleanly, your enrollment file reflects the backlog, not reality. You may be receiving capitation for members who are three months disenrolled. Claims are adjudicating against those members. Risk scores carry their data. The compliance exposure is yours.",[12,451,452],{},"This is not hypothetical. During the post-pandemic redetermination period, application processing backlogs hit 30% of applications exceeding the 45-day window in Washington D.C. and Georgia. Call center wait times exceeded three hours in Hawaii. The 2027 disenrollment wave will arrive with less preparation time, not more.",[19,454,456],{"id":455},"what-per-enrollment-accounting-changes-mean","What Per-Enrollment Accounting Changes Mean",[12,458,459],{},"HR1 doesn't implement a formal federal per-capita cap as originally debated in earlier budget proposals. What it does instead is effectively cap federal spending growth through a combination of FMAP restrictions, provider tax limits, and enrollment contraction. For plan operations, the practical effect is the same: the federal money available per eligible member is being constrained, while the cost of serving remaining members is not.",[12,461,462],{},"The administrative reporting implication is direct. As your enrolled population shrinks but your fixed administrative infrastructure stays largely constant, your administrative cost per-member-per-month rises. That ratio matters to your state Medicaid agency and to CMS audits. If you are running at a medical loss ratio that looks acceptable at current enrollment, model what it looks like at 85% of current enrollment, then at 75%. The administrative expense line doesn't compress proportionally. Your billing and reporting need to reflect that dynamic — not explain it after the fact when it shows up in an audit.",[12,464,465],{},"Six-month redeterminations for the expansion population — required under HR1 beginning January 1, 2027 — double the frequency of eligibility verification events. Each redetermination is a potential enrollment transaction, a potential gap in coverage, a potential reconciliation problem. The administrative cost of managing bi-annual redeterminations at scale will be measurable. Document it now, because your next rate negotiation will require demonstrating what your actual administrative burden is.",[19,467,469],{"id":468},"what-to-build-in-the-next-90-days","What to Build in the Next 90 Days",[12,471,472],{},"The June 1 CMS interim final rule will clarify definitions and exemptions for work requirements. The July 1 state outreach obligation kicks off the member-facing phase. January 1, 2027 is the go-live date. That is a very tight operational runway.",[12,474,475,478],{},[29,476,477],{},"Build your affected population inventory now."," Identify every expansion-eligible member aged 19–64 on your current roster. Segment by preliminary exemption category: pregnant members, members with documented disabilities, full-time students. The exempt population changes your workflow design significantly. You can't wait until the final rule to start this analysis.",[12,480,481,484],{},[29,482,483],{},"Establish near-real-time enrollment reconciliation."," If your plan is running monthly batch reconciliation against state eligibility files, that cadence will not hold in a high-churn environment. You need exception monitoring that flags anomalies within days: members appearing on your capitation file who no longer appear in the state eligibility system, members with no encounter activity in the 30 days following their redetermination window. The threshold for a phantom member investigation should be measurable and documented, not informal.",[12,486,487,490],{},[29,488,489],{},"Document your provider tax exposure."," Which of your provider contracts involve rates that were supplemented by state directed payments? Section 71115 doesn't eliminate existing SDPs immediately, but the phase-down schedule starts in 2028 and runs on a hard clock. Contracts that need to be renegotiated before that clock expires require lead time. Start identifying them now.",[12,492,493,496],{},[29,494,495],{},"Audit your claims adjudication for disenrollment lag risk."," Run an analysis of current members with low or zero encounter activity over the past 90 days. Cross-reference against your most recent state eligibility file reconciliation. Members appearing capitated with no encounters over an extended period are a proxy for potential phantom members or eligibility edge cases. That baseline audit tells you how clean your data is before the disenrollment wave starts.",[12,498,499,502],{},[29,500,501],{},"Prepare your customer service infrastructure."," State outreach begins July 1. Members who receive a work requirement notice from the state will call your customer service line, not the state agency. They will have questions your current scripts may not cover accurately. Update your knowledge base now. Identify the specific exemptions applicable in your state. Make sure your call center staff can correctly explain what the 30-day notice period means and what documentation members need to submit.",[12,504,505,508],{},[29,506,507],{},"Model your financial exposure at reduced enrollment."," Run three scenarios: 10%, 20%, and 30% reduction in expansion adult enrollment by end of 2027. At each scenario, calculate the effect on your PMPM administrative cost, your MLR, and your cash flow if state capitation payments lag the enrollment changes by 60 to 90 days. The cash flow lag is real — states pay capitation on prior-period enrollment files, and corrections take time. Plans that hit a disenrollment spike without a liquidity reserve will feel it in operations.",[19,510,512],{"id":511},"reconciliation-workflows-must-exist-before-2027","Reconciliation Workflows Must Exist Before 2027",[12,514,515],{},"The reconciliation problem is not a technology problem. It is a workflow problem — one that requires a defined owner, a documented escalation path, and a measurement cadence.",[12,517,518],{},"Before January 1, 2027, your plan needs documented answers to three questions. Who is responsible for comparing your enrollment roster against the state eligibility file, at what frequency, and within what resolution timeframe? What is the threshold that triggers a manual review of a member record versus an automated correction? And what is the audit trail for a disenrollment transaction — start to finish — that demonstrates compliance with your data integrity obligations?",[12,520,521],{},"Plans that don't have documented answers to those questions will be building the workflow in real time during a disenrollment spike. That is the worst possible moment to be improvising.",[12,523,524],{},"The enrollment volatility coming from HR1's Medicaid provisions is not a future problem. States are already in planning mode. CMS guidance is being finalized. Some states — Nebraska, for example — are targeting early implementation in advance of the federal deadline. The plans that operationalize their response in the next 90 days will handle the 2027 transition as a managed workflow. The plans that don't will spend 2027 explaining enrollment discrepancies to state agencies and auditors.",[158,526],{},[12,528,529],{},[163,530,531,532,179],{},"If your plan is assessing whether your enrollment infrastructure and reconciliation workflows are ready for the HR1 implementation timeline, ",[167,533,535],{"href":534},"\u002Fcontact","Ayin's team works specifically with small and mid-sized Medicaid plans on back-office operations",{"title":181,"searchDepth":182,"depth":182,"links":537},[538,539,540,541,542],{"id":414,"depth":182,"text":415},{"id":439,"depth":182,"text":440},{"id":455,"depth":182,"text":456},{"id":468,"depth":182,"text":469},{"id":511,"depth":182,"text":512},"2026-06-05","HR1's Medicaid provisions — work requirements, FMAP reductions, and provider tax restrictions — are the largest administrative disruption in a decade. The policy debate is settled. Here's what small plans must operationalize in the next 90 days.","Healthcare administrator reviewing compliance documents",{},"\u002Farticles\u002Fhr1-medicaid-cuts-operationalize",{"title":406,"description":544},"articles\u002Fhr1-medicaid-cuts-operationalize",[551,552,401,189,390],"Medicaid","HR1","3wzu_3l3Nit8UjLXP5b51aMyGkmS7B_2sAGcw6qol4o",{"id":555,"title":556,"author":7,"body":557,"category":774,"date":775,"description":776,"extension":192,"featured":193,"image":777,"imageAlt":778,"meta":779,"navigation":197,"path":780,"seo":781,"stem":782,"tags":783,"__hash__":787},"articles\u002Farticles\u002Fcapitation-administration-reconciliation.md","Capitation Administration: The Reconciliation Problems Plans Don't See Coming",{"type":9,"value":558,"toc":766},[559,562,565,568,572,575,578,581,585,588,591,594,597,600,616,619,623,626,629,632,635,638,655,658,662,665,668,671,677,683,689,695,699,702,705,708,714,720,726,732,738,741,745,748,751,754,756],[12,560,561],{},"It's month two. The capitation check arrives. It's $47,000 less than you expected.",[12,563,564],{},"You call the plan. They say the payment reflects your current attributed membership: 1,214 members at your contracted PMPM rate. Your team pulls the roster you've been tracking internally. You show 1,347 members. The delta is 133 people — patients your providers are actively seeing, who are generating cost, who you are clinically responsible for, but who are not generating capitation revenue this month.",[12,566,567],{},"This is not a billing error. It is a reconciliation problem. And it is one of the most common shocks that ACOs, IPAs, and provider-sponsored organizations face in their first quarter of capitation operations.",[19,569,571],{"id":570},"why-capitation-is-harder-than-the-contract-suggests","Why Capitation Is Harder Than the Contract Suggests",[12,573,574],{},"More provider organizations are taking on capitation risk than at any point in the last decade. As of 2025, the Medicare Shared Savings Program includes 476 ACOs serving more than 11.2 million Traditional Medicare beneficiaries. The ACO REACH model — which requires participating organizations to accept either 50% or 100% of financial risk — covers an additional 2.5 million aligned beneficiaries across 103 ACOs. Nationally, roughly 14% of provider reimbursement is now tied to some form of delegated or capitated risk.",[12,576,577],{},"The contract negotiations are usually sophisticated. Legal reviews the risk corridor language. Finance models the PMPM at different utilization scenarios. Actuaries bless the rate.",[12,579,580],{},"What gets less attention is the operational engine required to make the contract work month after month. By the time month two arrives, most organizations discover that capitation administration is not a finance function with a simpler payment model. It is a mini-payer operation — with all of the roster, eligibility, and reporting requirements that implies.",[19,582,584],{"id":583},"the-roster-to-eligibility-reconciliation-problem","The Roster-to-Eligibility Reconciliation Problem",[12,586,587],{},"The foundational issue is that your attributed membership list and the plan's eligibility file are maintained separately, updated on different schedules, and reconciled — if at all — after the fact.",[12,589,590],{},"Here is what typically happens. A patient sees one of your PCPs in January. The plan attributes that patient to your organization based on their historical claim pattern and PCP assignment. But the patient lost and regained Medicaid eligibility in December. The reinstatement processed in the plan's system on January 18. Your roster file, delivered on February 1, doesn't reflect the January activity. You provided care for someone in January who will not appear on your attributed list until March — if they appear at all.",[12,592,593],{},"Multiply this by a population that churns. Medicaid members gain and lose eligibility an average of multiple times per year. Commercial and Medicare populations are more stable, but they are not static. Members move. PCPs change. Plan assignments shift. Every one of these events is a potential misalignment between your clinical reality and the plan's financial reality.",[12,595,596],{},"The OIG has documented this problem from the plan side: a 2025 nationwide audit identified over $207 million in unallowable Medicaid capitation payments made on behalf of deceased enrollees — payments that continued because state eligibility systems hadn't been updated. The problem runs in both directions. Plans overpay for members who should be off the roster. Provider organizations are underpaid for members who should be on it.",[12,598,599],{},"The administrative answer is a roster reconciliation workflow that runs continuously, not monthly. You need a process that:",[601,602,603,607,610,613],"ul",{},[604,605,606],"li",{},"Pulls eligibility files from the plan at minimum weekly, ideally daily",[604,608,609],{},"Flags discrepancies between your attributed roster and the plan's active eligibility file",[604,611,612],{},"Tracks the disposition of each discrepancy — was it resolved in your favor, the plan's favor, or is it pending?",[604,614,615],{},"Creates a financial reserve for unresolved members whose attribution status is in dispute",[12,617,618],{},"Without this workflow, you are flying blind. Your PMPM revenue figure is accurate only by accident.",[19,620,622],{"id":621},"downstream-cap-distribution-and-the-audit-trail-problem","Downstream Cap Distribution and the Audit Trail Problem",[12,624,625],{},"An IPA or MSO taking global capitation rarely delivers all covered services itself. The more common structure: the IPA receives the full capitation check and then distributes sub-capitation to delegated specialists, facility partners, or carve-out vendors who cover defined service categories.",[12,627,628],{},"This is where administrative complexity compounds.",[12,630,631],{},"Every sub-capitation payment you make downstream creates a contractual obligation and a regulatory exposure. If you are distributing $18 PMPM to a behavioral health carve-out based on 1,214 attributed members, but your roster shows 1,347, you have a choice: pay on the plan's count and absorb the difference yourself, or pay on your count and document the discrepancy. Neither is simple. Both require documentation.",[12,633,634],{},"Delegated entities operating under CMS or state Medicaid contracts are not just responsible for their own performance — they are responsible for demonstrating that their downstream subcontractors are operating within the terms of the primary contract. California's DMHC, for example, has been explicit: plans are ultimately accountable for the actions and failures of their downstream providers. When a single IPA or medical group contracts with multiple payers, it may face ten or more separate annual audits from those plans — each looking at sub-delegation documentation, financial controls, and compliance with the primary contract terms.",[12,636,637],{},"The audit trail for downstream cap distribution needs to show:",[601,639,640,643,646,649,652],{},[604,641,642],{},"The attributed membership count used to calculate each downstream payment",[604,644,645],{},"The PMPM rate applied, and its contractual basis",[604,647,648],{},"Reconciliation of any month-over-month count changes and how the distribution was adjusted",[604,650,651],{},"Any amounts held in reserve pending roster dispute resolution",[604,653,654],{},"The timing of each payment relative to your receipt of the upstream capitation",[12,656,657],{},"This is not a spreadsheet problem. It is an accounting system problem. Plans that are managing downstream distribution in Excel are one audit away from an extended and expensive reconciliation exercise with their payer.",[19,659,661],{"id":660},"stop-loss-triggering-and-accumulation-tracking","Stop-Loss Triggering and Accumulation Tracking",[12,663,664],{},"Stop-loss coverage exists precisely because capitation creates catastrophic risk exposure for provider organizations. A single high-cost member — a premature neonate, a trauma case, a new cancer diagnosis requiring aggressive treatment — can consume a disproportionate share of a small population's risk pool.",[12,666,667],{},"Stop-loss for risk-bearing provider groups typically operates as specific stop-loss: once an individual member's costs exceed a defined threshold (often in the range of $75,000 to $200,000 per year, depending on the contract and carrier), the stop-loss policy reimburses the excess. The catch is that triggering stop-loss is not automatic. You have to accumulate and document the claim spend, notify the carrier at the right interval, and submit supporting documentation in the format the carrier requires.",[12,669,670],{},"Most provider organizations entering capitation for the first time underestimate the operational overhead of stop-loss tracking. The core workflow requirements are:",[12,672,673,676],{},[29,674,675],{},"Member-level cost accumulation."," You need a system that tracks cumulative claim cost by member, within the stop-loss contract year, across all service categories covered under your capitation agreement. If your claims data is incomplete — because some services are carved out, or because encounter data from delegated providers lags — your accumulation will be inaccurate.",[12,678,679,682],{},[29,680,681],{},"Threshold proximity monitoring."," You cannot wait until a member crosses the threshold to begin the notification process. Most stop-loss contracts require advance notification when a member approaches the attachment point. Missing this window can result in a denied claim.",[12,684,685,688],{},[29,686,687],{},"Stop-loss contract year vs. calendar year alignment."," Your capitation contract year, your stop-loss policy year, and the calendar year may not be the same. A member who generates $140,000 in claims that straddle two policy years may not trigger your $100,000 attachment point under either year. Understanding how costs accumulate against the correct contract period is not a minor technical detail — it directly affects your reinsurance recovery.",[12,690,691,694],{},[29,692,693],{},"Documentation quality."," Stop-loss carriers audit claims. Medical records, claim-level detail, and authorization documentation need to be accessible and organized at the member level. Organizations that cannot produce this documentation on request are organizations that do not recover money they are owed.",[19,696,698],{"id":697},"what-good-capitation-reporting-actually-looks-like","What Good Capitation Reporting Actually Looks Like",[12,700,701],{},"Most plans provide capitation summary reports. Most of those reports are insufficient for managing the contract.",[12,703,704],{},"A typical plan-generated cap report tells you: total attributed members this month, total PMPM paid, total capitation received. That is a check stub. It is not financial management information.",[12,706,707],{},"A CFO managing a capitation contract needs a materially different data set:",[12,709,710,713],{},[29,711,712],{},"Variance analysis, not just totals."," Month-over-month change in attributed membership, decomposed by the reason for the change — new attributions, disenrollments, eligibility changes, attribution methodology changes. If your attributed count dropped by 80 members this month, you need to know whether those were members who terminated, members who switched PCPs, or members the plan re-attributed to a different ACO because of a methodology update.",[12,715,716,719],{},[29,717,718],{},"Revenue-to-cost ratio by service category."," Total capitation received versus total claim cost incurred, broken out by service category. If your PMPM for behavioral health services is $22 but your actual behavioral health cost per attributed member is running at $31, you have a structural problem that needs to be quantified and acted on.",[12,721,722,725],{},[29,723,724],{},"Incurred but not reported (IBNR) reserve tracking."," Capitation revenue is received in the current period. The claims that consume that revenue will lag by 60 to 120 days. A CFO who looks at capitation income and believes it represents current profit is misreading the financial position. Maintaining an actuarially supportable IBNR reserve is not optional — it is the difference between knowing your margin and guessing it.",[12,727,728,731],{},[29,729,730],{},"Stop-loss accumulation by member."," Which members are tracking toward attachment points? What is the expected reinsurance recovery this contract year? What is the net capitation position after anticipated stop-loss offsets?",[12,733,734,737],{},[29,735,736],{},"Downstream distribution reconciliation."," Total sub-capitation paid versus total sub-capitation owed, with open items by delegated entity.",[12,739,740],{},"If your current reporting does not include these elements, you are managing the contract on incomplete information. The risk is not just operational — it is financial. Provider organizations have entered capitation arrangements and discovered significant losses only because they lacked the reporting infrastructure to see them developing in real time.",[19,742,744],{"id":743},"building-the-infrastructure-before-you-need-it","Building the Infrastructure Before You Need It",[12,746,747],{},"The organizations that manage capitation well treat it as a payer function from the first day of the contract. They invest in eligibility feeds, reconciliation workflows, and claims accumulation systems before the first check arrives — not after the first discrepancy surfaces.",[12,749,750],{},"The organizations that struggle treat capitation as a payment model change and assume that existing administrative infrastructure will adapt. By month three, they are doing retroactive reconciliation on month one, managing downstream distribution disputes, and trying to reconstruct stop-loss documentation they should have been building all along.",[12,752,753],{},"The contract does not change this dynamic. The operational readiness you bring on day one does.",[158,755],{},[12,757,758],{},[163,759,760,761,179],{},"Ayin Health Solutions works with ACOs, IPAs, and provider-sponsored organizations on the administrative and financial infrastructure capitation contracts require — roster reconciliation, downstream distribution, stop-loss tracking, and CFO-grade financial reporting. Learn more at ",[167,762,765],{"href":763,"rel":764},"https:\u002F\u002Fayin.com\u002Fsolutions\u002Fcapitation",[171],"ayin.com\u002Fsolutions\u002Fcapitation",{"title":181,"searchDepth":182,"depth":182,"links":767},[768,769,770,771,772,773],{"id":570,"depth":182,"text":571},{"id":583,"depth":182,"text":584},{"id":621,"depth":182,"text":622},{"id":660,"depth":182,"text":661},{"id":697,"depth":182,"text":698},{"id":743,"depth":182,"text":744},"Value-Based Care","2026-05-27","Signing a capitation contract is the easy part. By month two, most provider organizations discover that roster mismatches, attribution churn, downstream distribution requirements, and stop-loss tracking demand payer-grade administrative infrastructure they don't have.","\u002Fphotography\u002FAyin_still_13.png","Healthcare finance and operations",{},"\u002Farticles\u002Fcapitation-administration-reconciliation",{"title":556,"description":776},"articles\u002Fcapitation-administration-reconciliation",[784,774,785,390,786],"Capitation","Provider Risk","Finance","YjW8UqthZ6Q7s74ExyRttV0gAlwAfOOvNKsg6M312JI",{"id":789,"title":790,"author":7,"body":791,"category":402,"date":945,"description":946,"extension":192,"featured":193,"image":947,"imageAlt":948,"meta":949,"navigation":197,"path":950,"seo":951,"stem":952,"tags":953,"__hash__":958},"articles\u002Farticles\u002Fmedicare-advantage-risk-adjustment-operations.md","Risk Adjustment for Regional MA Plans: The Operational Gaps Costing You Revenue",{"type":9,"value":792,"toc":937},[793,796,799,803,806,812,818,821,825,828,831,834,837,841,844,847,850,853,857,860,866,872,878,884,890,894,897,900,903,906,909,913,916,919,921],[12,794,795],{},"Risk adjustment is a revenue problem before it is a clinical problem. CMS calculates your plan's monthly capitation payment based on the risk scores of your enrolled members. Those scores are built from diagnosis codes submitted through encounter data. If your encounter data is incomplete, your payment is lower than your population's actual acuity warrants — and no amount of clinical quality work corrects that.",[12,797,798],{},"For regional MA plans, this gap is not hypothetical. The Office of Inspector General estimates that CMS's improper payment rate for MA is 9.5 percent, driven primarily by unsupported diagnoses submitted by plans. The flip side of that finding is that plans with documentation failures are also missing compliant diagnoses that would have supported higher payments had the data been submitted correctly. Both problems originate in the same place: encounter data workflows that are not built to capture what the care actually was.",[19,800,802],{"id":801},"what-changed-in-2026","What Changed in 2026",[12,804,805],{},"Two regulatory shifts make this a now problem for plan operations.",[12,807,808,811],{},[29,809,810],{},"V28 is fully in effect."," CMS completed the phased transition to the CMS-HCC Risk Adjustment Model V28 in payment year 2026. The blend is gone — all RAF scores are now calculated exclusively under V28 rules, V28 HCC mappings, and V28 coefficients. CMS projected that the V28 transition would reduce average MA risk scores by 3.12 percent, representing approximately $11 billion in net payment reduction across the industry. V28 removed 2,294 ICD-10 codes from the crosswalk and added only 268. Codes that previously mapped to HCCs may no longer. Plans that have not updated their encounter data processes to reflect V28 mappings are likely submitting codes that no longer carry payment weight — while missing codes that do.",[12,813,814,817],{},[29,815,816],{},"RADV audits now cover every eligible contract."," In May 2025, CMS announced it would expand RADV audits from roughly 60 contracts per cycle to all eligible MA contracts — more than 550 — on an annual basis. CMS simultaneously grew its coding review workforce from 40 to approximately 2,000 reviewers and announced plans to deploy AI as a support tool for audit coders. In January 2026, CMS restored a five-month medical record submission window for audited plans, walking back a shorter window it had proposed in 2025.",[12,819,820],{},"The extrapolation question is not settled. A federal district court vacated CMS's rule that would have allowed it to extrapolate error rates from an audit sample across a plan's entire contract population — which would have multiplied financial exposure significantly. CMS appealed that ruling in November 2025. Plans should not treat the current legal uncertainty as a reason to deprioritize documentation quality. The underlying audit activity is expanding regardless of how extrapolation is ultimately resolved.",[19,822,824],{"id":823},"what-radv-actually-tests","What RADV Actually Tests",[12,826,827],{},"A RADV audit is a record validation exercise. CMS selects a sample of risk-adjustable diagnoses your plan submitted and asks for the medical records that support them. CMS's coders then review those records against a documented standard.",[12,829,830],{},"The standard is not complex, but it is specific. Every diagnosis submitted for risk adjustment must be supported by a medical record demonstrating that the condition was addressed during an encounter — not just listed in a problem list, not imported from a prior note, not documented only on a health risk assessment with no follow-up care. The standard typically used is MEAT: the record must show the condition was Monitored, Evaluated, Assessed, or Treated during the visit.",[12,832,833],{},"The most common audit failure is not fabrication. It is the absence of active management documentation for conditions the member genuinely has. A provider notes a chronic condition in a problem list and does not address it in the visit note. A specialist encounter is never submitted as an encounter record. A diagnosis is coded from a health risk assessment that generated no additional care. In each case, the condition may be real, but the documentation does not meet the standard CMS applies.",[12,835,836],{},"The OIG's October 2024 report on health risk assessments found that HRAs with no linked additional care spending led to $7.5 billion in increased MA payments in 2023. CMS and OIG have flagged in-home HRAs specifically as a high-risk documentation source. Using HRAs as a primary diagnosis capture mechanism — without ensuring those diagnoses are also documented in subsequent care encounters — is both a compliance risk and a RADV audit failure waiting to happen.",[19,838,840],{"id":839},"the-compliance-line","The Compliance Line",[12,842,843],{},"This is worth stating directly: a compliant risk adjustment program and a revenue maximization scheme are not the same thing, and the distinction matters operationally.",[12,845,846],{},"Compliant risk adjustment captures diagnoses that are supported by contemporaneous clinical documentation, submitted through proper encounter data channels, and reflect care that actually occurred. When a plan closes diagnosis gaps by ensuring that documented conditions appear in encounter data submissions, that is compliant revenue recovery.",[12,848,849],{},"Upcoding is something different. Assigning higher-severity codes than the documentation supports, using HRAs as the sole documentation source for conditions that receive no treatment, coaching providers to add diagnoses not reflected in the clinical record — these are the practices that generate OIG referrals and False Claims Act exposure. The OIG has been explicit about this distinction in its reporting on the HRA overpayment issue.",[12,851,852],{},"The plans with the largest compliance exposure are not always the ones with the most aggressive coding programs. They are often regional plans that have neither: no systematic upcoding, but also no systematic process for capturing diagnoses that are legitimately present and documented. The revenue loss from the second problem is just as real, and it carries none of the legal risk associated with the first.",[19,854,856],{"id":855},"where-encounter-data-breaks-down","Where Encounter Data Breaks Down",[12,858,859],{},"Diagnosis capture gaps in regional MA plans almost always trace back to encounter data workflow failures, not clinical documentation failures. The care is documented. The data does not reach the submission system in a form that supports risk adjustment.",[12,861,862,865],{},[29,863,864],{},"Provider encounter submission gaps."," Smaller regional plans typically contract with independent practices, community health centers, and single-specialty groups that do not have dedicated billing staff oriented toward MA encounter data requirements. Fee-for-service claims may be submitted accurately. MA encounter records — which require more complete data elements than a standard claim — may be submitted late, submitted with missing required fields, or not submitted at all. A specialist encounter that never reaches the plan's encounter data processor never contributes to risk adjustment.",[12,867,868,871],{},[29,869,870],{},"EDPS transition errors."," As of 2025, the Encounter Data Processing System (EDPS) is the primary source for risk adjustment calculations. RAPS-based submission pathways are largely phased out. Plans that have not fully transitioned their encounter data pipelines to meet EDPS requirements — or that have delegated encounter data submission to vendors without verifying data quality — are likely losing diagnoses to submission failures that do not generate obvious error flags.",[12,873,874,877],{},[29,875,876],{},"V28 crosswalk misalignment."," Plans or vendors that have not updated ICD-10-to-HCC mapping tables to reflect V28 may be submitting codes that no longer carry payment weight. This is a systems configuration problem, not a coding problem. It requires a deliberate audit of the crosswalk logic in your encounter data processing system against the current V28 mapping.",[12,879,880,883],{},[29,881,882],{},"Late or missing supplemental data submissions."," CMS allows supplemental data sources — pharmacy data, lab data, prior authorization records — to support risk adjustment, but these require timely submission within defined windows. Plans that rely on supplemental data to fill encounter gaps but do not have automated submission processes miss deadlines at a rate that scales with volume and organizational complexity.",[12,885,886,889],{},[29,887,888],{},"Reconciliation failures."," After submission, CMS's system generates acceptance and rejection responses. Plans that process encounter data without a systematic reconciliation workflow do not know which records were rejected and why. Rejections may stem from invalid member IDs, missing NPIs, duplicate submission flags, or data formatting errors. Without a process to catch and resubmit rejected records, legitimate diagnoses are lost.",[19,891,893],{"id":892},"what-a-compliant-capture-operation-looks-like","What a Compliant Capture Operation Looks Like",[12,895,896],{},"Operationally, the difference between plans that consistently leave money on the table and plans that do not comes down to a few process structures.",[12,898,899],{},"A complete encounter data submission process covers the full provider network — not just large hospital systems and multispecialty groups, but independent practices, behavioral health providers, and specialists. Each contract with a downstream provider should include encounter data submission obligations with defined timelines.",[12,901,902],{},"A V28-aligned crosswalk audit is a one-time operational task that should have been completed before payment year 2026 began. If it has not been done, it needs to happen now. Map your current ICD-10 submission volume against V28 HCC assignments. Identify codes you have been submitting that no longer carry weight, and identify conditions with supporting documentation that may map to HCCs you are not currently capturing.",[12,904,905],{},"A RADV-ready documentation standard means that every risk-adjustable diagnosis in your encounter data can be matched to a medical record that shows active management of the condition — not just a problem list entry. This does not require changing how providers practice. It requires knowing, before CMS asks, whether the records exist and where they are.",[12,907,908],{},"A closed-loop rejection management process means someone sees every EDPS rejection, every record fails for a documented reason, and every correctable rejection is resubmitted within the relevant window. This is a workflow design problem, not a technology problem, though technology can make it significantly easier to operate at scale.",[19,910,912],{"id":911},"the-audit-exposure-assessment","The Audit Exposure Assessment",[12,914,915],{},"Before the next audit cycle, regional MA plans should know the answer to three questions. First: what percentage of your encounter records are accepted by EDPS on first submission, and what is happening to the rejections? Second: have your encounter data crosswalk tables been updated to reflect V28 mappings, and do you have documentation to verify that? Third: for the diagnoses driving your highest RAF contributions, do you have medical records demonstrating active management at an encounter — not just a health risk assessment or a problem list?",[12,917,918],{},"If the answer to any of those is unclear, the audit risk is real. The record submission window CMS provides in a RADV audit is finite. Documentation assembled reactively during that window is harder to defend and less likely to be complete than documentation that exists as a natural output of a functioning encounter data process.",[158,920],{},[12,922,923],{},[163,924,925,926,931,932,936],{},"If your plan is assessing encounter data workflow gaps or preparing for RADV audit activity, ",[167,927,930],{"href":928,"rel":929},"https:\u002F\u002Fayin.com\u002Fsolutions\u002Fmedicare-advantage",[171],"Ayin works with regional MA plans on risk adjustment operations"," — or ",[167,933,935],{"href":176,"rel":934},[171],"contact us"," to talk through where the gaps are.",{"title":181,"searchDepth":182,"depth":182,"links":938},[939,940,941,942,943,944],{"id":801,"depth":182,"text":802},{"id":823,"depth":182,"text":824},{"id":839,"depth":182,"text":840},{"id":855,"depth":182,"text":856},{"id":892,"depth":182,"text":893},{"id":911,"depth":182,"text":912},"2026-05-13","CMS has expanded RADV audits to all eligible MA contracts and completed the V28 model transition. Regional plans are leaving revenue on the table — not because of clinical failures, but because of preventable gaps in encounter data workflows and diagnosis capture operations.","\u002Fphotography\u002FAyin_still_11.png","Healthcare data analysis",{},"\u002Farticles\u002Fmedicare-advantage-risk-adjustment-operations",{"title":790,"description":946},"articles\u002Fmedicare-advantage-risk-adjustment-operations",[402,954,955,956,957],"Risk Adjustment","HCC","RADV","Revenue","PYyE4c59oZMJSQZp-IWESWqw0ZiBsuWtuT1mQZfDVEs",{"id":960,"title":961,"author":7,"body":962,"category":189,"date":1079,"description":1080,"extension":192,"featured":193,"image":1081,"imageAlt":1082,"meta":1083,"navigation":197,"path":1084,"seo":1085,"stem":1086,"tags":1087,"__hash__":1090},"articles\u002Farticles\u002Fdsnp-integration-operations.md","D-SNP Integration Operations: Running Medicare and Medicaid on One Spine",{"type":9,"value":963,"toc":1072},[964,967,970,974,977,980,983,986,989,993,996,999,1002,1005,1008,1012,1015,1018,1021,1025,1028,1031,1034,1037,1040,1044,1047,1050,1053,1056,1058],[12,965,966],{},"More than 6 million people are enrolled in Dual Eligible Special Needs Plans. That number grew from 2.2 million in 2018, and CMS is not done expanding the program's scope. What has changed faster than enrollment is the regulatory obligation attached to every one of those members.",[12,968,969],{},"If your plan runs Medicare and Medicaid administration on separate platforms connected by a middleware bridge or a batch-file handshake, you already have a compliance problem. CMS has made the direction of travel clear: integration is not aspirational — it is now a contract requirement, with hard deadlines attached.",[19,971,973],{"id":972},"what-cms-actually-requires-now","What CMS Actually Requires Now",[12,975,976],{},"The Bipartisan Budget Act of 2018 permanently authorized D-SNPs and directed CMS to unify Medicare and Medicaid appeals and grievance procedures. That directive has been landing in State Medicaid Agency Contract (SMAC) requirements and final rules ever since.",[12,978,979],{},"For contract year 2025, applicable integrated plans — D-SNPs affiliated with a Medicaid MCO in the same service area — must operate unified appeals and grievance procedures under 42 CFR §§ 422.629–422.634. That means a single intake point, a single tracking system, and a single acknowledgment to the member regardless of which program the issue touches. As of January 1, 2025, enrollees have 65 calendar days from the date on a coverage decision letter to file an integrated reconsideration. Both clocks run on one track.",[12,981,982],{},"FIDE-SNPs face the highest bar. Starting January 2025, fully integrated plans must operate with exclusively aligned enrollment — meaning they can no longer enroll partial-benefit dual-eligible individuals. A FIDE-SNP holds capitated contracts covering essentially all Medicaid services, including long-term services and supports. The administrative footprint is substantial.",[12,984,985],{},"HIDE-SNPs occupy the middle tier. They carry a Medicaid managed care contract but may not cover the full Medicaid benefit. CMS still requires them to meet unified grievance procedures and integrated care coordination standards where the SMAC mandates it.",[12,987,988],{},"The 2027 mandate, codified at § 422.514(h) in the CY2025 final rule, closes the biggest remaining gap. Where an MA organization — or its parent, or any entity sharing that parent — also holds a Medicaid MCO contract in the same service area, enrollment must be exclusively aligned by 2027. By 2030, the D-SNP can only enroll individuals already in, or actively enrolling in, the affiliated Medicaid plan. Plans that have been treating their MA and Medicaid lines as separate businesses are now on a countdown.",[19,990,992],{"id":991},"where-two-systems-break-down","Where Two Systems Break Down",[12,994,995],{},"The operational failure mode is predictable. A member has a hospital admission. The Medicare claim adjudicates under your MA platform. The Medicaid cost-sharing liability goes to a separate Medicaid system. The crossover claim moves sequentially: Medicare adjudicates first, generates an EOB, and that EOB becomes the input for Medicaid secondary adjudication — often via batch file, often overnight, sometimes via manual re-entry.",[12,997,998],{},"At every handoff, things go wrong.",[12,1000,1001],{},"Cost-sharing is miscalculated because the Medicaid system did not receive the updated Medicare payment in time for the adjudication window. A prior authorization approved on the Medicare side is not visible to the care manager working in the Medicaid platform. The member's care plan in the MA system reflects a primary care provider who changed three months ago on the Medicaid side. The health risk assessment completed in January sits in one system; the social determinants screening required under the 2024 D-SNP rule — housing, transportation, food security — lives in another.",[12,1003,1004],{},"Each of these is not just an operational nuisance. Each is a compliance exposure. CMS requires D-SNPs to maintain procedures for care coordination activities following HRAs. OIG has an active work plan project — OEI-03-25-00211, opened June 2025 — specifically examining D-SNP compliance with care coordination requirements, with particular attention to whether plans are using HRAs to generate risk-adjustment revenue without fulfilling the corresponding care coordination obligations.",[12,1006,1007],{},"Quality measures compound the problem. HEDIS and Star Rating measures that span both Medicare and Medicaid — HbA1c control, medication adherence, follow-up after hospitalization — require data from both systems to score accurately. Plans running two systems often cannot produce a clean denominator for dual-eligible members. They reconcile manually at the end of the measurement year, which introduces both error and delay.",[19,1009,1011],{"id":1010},"what-states-are-adding-on-top","What States Are Adding on Top",[12,1013,1014],{},"Federal floors are not the ceiling. California's Department of Health Care Services now limits new D-SNP enrollment in all counties to plans affiliated with a Medi-Cal managed care plan. If your D-SNP does not have an affiliated Medi-Cal contract, you cannot grow your California book. The state has effectively made integration a market-access requirement, not just a compliance requirement.",[12,1016,1017],{},"New York's 2026 SMAC introduced specific provisions for MLTCP-aligned HIDE-SNP plans and clarified the path for plans converting between D-SNP types. The state's requirements around care coordination documentation, network adequacy for long-term services and supports, and Medicaid-side grievance tracking are written into the SMAC — which means CMS and the state can both audit against them.",[12,1019,1020],{},"Plans with members in multiple states are navigating a patchwork of SMAC terms that vary in integration depth, grievance timelines, and care management documentation standards. A two-system architecture cannot accommodate that variation without a proliferation of custom interfaces that each carry their own maintenance burden and failure risk.",[19,1022,1024],{"id":1023},"what-a-single-member-spine-looks-like","What a Single Member Spine Looks Like",[12,1026,1027],{},"A genuinely integrated D-SNP administration model does not mean a single technology vendor owns everything. It means a single authoritative member record that both the MA and Medicaid functions read from and write to in real time.",[12,1029,1030],{},"On the eligibility side, that record reflects the member's dual-eligible status, their Medicaid aid category, their Medicare entitlement type, and their enrollment in both plans — updated on the same cycle. When CMS processes a Low Income Subsidy status change or a state Medicaid agency updates a member's LTSS authorization, that change propagates to the care management team and the claims adjudication engine without a batch delay.",[12,1032,1033],{},"On the claims side, crossover processing should not require a separate system handshake. The adjudication engine knows the member is dual-eligible, knows the Medicare payment, and calculates the Medicaid cost-sharing liability in a single pass or in a tight, same-day sequential process with a shared claim record — not a batch EOB export to a disconnected platform.",[12,1035,1036],{},"On the care management side, the care manager sees a single longitudinal record: the HRA, the care plan, the social determinants screening, the open authorizations on both sides, the recent claims regardless of program, and the open grievances regardless of which intake channel received them. There is no \"Medicare care manager\" and \"Medicaid care manager\" working from different records for the same member.",[12,1038,1039],{},"On grievances and appeals, a single intake queue routes and tracks everything. The integrated reconsideration timeline — 65 days from the coverage decision letter — is system-enforced, not calendar-managed by a compliance analyst.",[19,1041,1043],{"id":1042},"the-operational-debt-calculation","The Operational Debt Calculation",[12,1045,1046],{},"The honest question for a COO is not \"can we pass the next audit with our current architecture?\" It is \"what does it cost us per year to maintain the seam, and what does it cost us if the seam fails at audit?\"",[12,1048,1049],{},"The maintenance cost is real: custom interfaces, reconciliation staff, parallel data quality reviews, manual quality measure reconciliation, duplicate training curricula for teams working two systems. The compliance cost of failure is also real: CMS has authority to impose civil monetary penalties, suspend enrollment, and terminate contracts for D-SNPs that cannot demonstrate integrated care coordination. OIG's new audit project signals that care coordination documentation will receive scrutiny, not just claims accuracy.",[12,1051,1052],{},"The 2027 exclusively aligned enrollment requirement makes the stakes concrete. If your Medicare enrollment system and your Medicaid enrollment system cannot confirm, in real time, that a prospective D-SNP enrollee is also enrolled in the affiliated Medicaid plan, you will either enroll ineligible members or turn away eligible ones. Neither outcome is acceptable at scale.",[12,1054,1055],{},"Plans that start the architecture work now — before the 2027 deadline, before the next SMAC cycle, before the OIG audit findings publish — will spend that investment once. Plans that wait will spend it under pressure, on a compressed timeline, while simultaneously managing member disruption and regulatory scrutiny.",[158,1057],{},[12,1059,1060],{},[163,1061,1062,1063,173,1068,179],{},"To learn how Ayin Health Solutions supports D-SNP integration at the operational level, visit ",[167,1064,1067],{"href":1065,"rel":1066},"https:\u002F\u002Fayin.com\u002Fsolutions\u002Fdual-eligible",[171],"ayin.com\u002Fsolutions\u002Fdual-eligible",[167,1069,1071],{"href":176,"rel":1070},[171],"contact our team",{"title":181,"searchDepth":182,"depth":182,"links":1073},[1074,1075,1076,1077,1078],{"id":972,"depth":182,"text":973},{"id":991,"depth":182,"text":992},{"id":1010,"depth":182,"text":1011},{"id":1023,"depth":182,"text":1024},{"id":1042,"depth":182,"text":1043},"2026-04-29","CMS is tightening FIDE-SNP and HIDE-SNP requirements every contract year. Plans still running dual-eligible populations across two separate systems are accumulating operational debt they will eventually have to repay — here is what integrated D-SNP administration actually requires at the workflow level.","\u002Fphotography\u002FAyin_still_5.png","Healthcare operations and coordination",{},"\u002Farticles\u002Fdsnp-integration-operations",{"title":961,"description":1080},"articles\u002Fdsnp-integration-operations",[1088,1089,551,402,390],"Dual-Eligible","D-SNP","ezmkq1pOyowfWH_Ty2f-BW6NSWOgt3HRWtbT__ai5nM",{"id":1092,"title":1093,"author":7,"body":1094,"category":1278,"date":1279,"description":1280,"extension":192,"featured":193,"image":1281,"imageAlt":1282,"meta":1283,"navigation":197,"path":1284,"seo":1285,"stem":1286,"tags":1287,"__hash__":1290},"articles\u002Farticles\u002Fai-health-plan-back-office.md","AI in the Health Plan Back Office: What's Real, What's Not, and What to Build First",{"type":9,"value":1095,"toc":1267},[1096,1099,1102,1106,1109,1112,1117,1120,1123,1126,1130,1133,1139,1145,1151,1154,1158,1161,1164,1167,1170,1191,1195,1198,1201,1204,1208,1211,1214,1220,1226,1232,1236,1239,1242,1245,1248,1251,1253],[12,1097,1098],{},"If you run operations at a small or mid-sized health plan, you've been pitched AI at least a dozen times in the last 18 months. The pitch usually sounds the same: efficiency gains, cost reduction, faster decisions. The specifics are vague. The demos look good. The proof is thin.",[12,1100,1101],{},"This is an attempt to be more honest about what's actually working, what isn't, and where a three-person ops team should focus first.",[19,1103,1105],{"id":1104},"separate-the-old-from-the-new","Separate the old from the new",[12,1107,1108],{},"Most of what vendors call \"AI\" in health plan back office falls into one of two categories: automation that has existed for years and is now being rebranded, and genuinely new capability made possible by machine learning and large language models.",[12,1110,1111],{},"Both matter. But conflating them causes real problems. It leads plans to overpay for existing functionality, underprepare for new tooling requirements, and miss the actual opportunity.",[1113,1114,1116],"h3",{"id":1115},"where-automation-has-a-long-track-record","Where automation has a long track record",[12,1118,1119],{},"Claims edit packages — the logic that checks whether a submitted claim meets coding and billing rules before it pays — have been around for decades. Vendors like ClaimLogic, Optum's ClaimCheck, and built-in edit suites in most core admin systems do this at scale. Industry auto-adjudication rates for commercial and managed care plans run in the 80–85% range for clean electronic claims. The cost differential is significant: auto-adjudicated claims cost cents to process; claims requiring manual review cost roughly $20 each.",[12,1121,1122],{},"Duplicate detection is similarly mature. Pattern-matching logic that flags same-member, same-date, same-provider claims has existed since the 1990s. It's effective. Most well-configured systems catch the obvious cases.",[12,1124,1125],{},"These aren't AI. They're rule-based automation. That doesn't make them less valuable — a plan running below 80% auto-adjudication is leaving real money on the table. But if a vendor is pitching you \"AI-powered duplicate detection,\" ask what's new about it.",[1113,1127,1129],{"id":1128},"where-machine-learning-actually-adds-something","Where machine learning actually adds something",[12,1131,1132],{},"A few use cases represent genuine capability advances worth your attention:",[12,1134,1135,1138],{},[29,1136,1137],{},"Coding suggestion for complex claims."," Natural language processing applied to clinical notes can suggest HCC codes that weren't captured on a claim. For Medicare Advantage plans, where risk-adjusted revenue depends on accurate diagnosis capture, this is material. A missed chronic condition code can mean underpayment that compounds year over year.",[12,1140,1141,1144],{},[29,1142,1143],{},"Denial prediction before adjudication."," ML models trained on historical claims data can score incoming claims for denial probability based on payer-specific patterns, flagging high-risk claims for review before they're submitted. Early results from payers deploying these tools show meaningful reductions in initial denial rates — though the gains depend entirely on training data quality.",[12,1146,1147,1150],{},[29,1148,1149],{},"Member risk flagging from claims patterns."," Predictive models that identify members trending toward high-cost utilization — based on claim sequences, ER visit patterns, prescription lapses — can surface care management candidates that rule-based logic misses. This is one of the cleaner use cases for smaller plans, because the output is actionable and the human decision is preserved.",[12,1152,1153],{},"None of these are plug-and-play. Each requires clean data, thoughtful implementation, and ongoing monitoring.",[19,1155,1157],{"id":1156},"the-data-quality-problem-most-plans-skip","The data quality problem most plans skip",[12,1159,1160],{},"Here's the part of the AI conversation that vendors consistently underemphasize: your results will be bounded by your data quality, and most plans overestimate where they stand.",[12,1162,1163],{},"AI models learn from historical data. If your eligibility files have processing lag, your provider directory has stale NPIs, your COB logic produces inconsistent outcomes, or your encounter data is incomplete — the model trains on those errors. It will reproduce them, confidently, at scale.",[12,1165,1166],{},"One telling signal: plans that run below 80% auto-adjudication typically have a data problem, not a technology problem. The same underlying issues that create claims suspense — credentialing mismatches, eligibility gaps, missing coordination of benefits data — will undermine any AI tool you layer on top. The automation reveals where you've been compensating for complexity through manual work. In that environment, AI has limited room to deliver real efficiency.",[12,1168,1169],{},"Before deploying any machine learning tool, audit three things:",[1171,1172,1173,1179,1185],"ol",{},[604,1174,1175,1178],{},[29,1176,1177],{},"Eligibility file currency."," For Medicaid populations with high enrollment churn, eligibility reconciliation needs to run continuously, not on batch cycles. If your system is running daily or weekly eligibility updates, the AI will make confident decisions based on stale member status.",[604,1180,1181,1184],{},[29,1182,1183],{},"Provider directory completeness."," A 2025 analysis found that provider data problems are among the most common root causes of auto-adjudication failure. Missing taxonomy codes, incorrect group affiliations, and outdated credentialing status collectively suppress your automation rate more than any algorithmic limitation.",[604,1186,1187,1190],{},[29,1188,1189],{},"Encounter data completeness for managed care."," If you're on a capitated or value-based contract, incomplete encounter submission means your risk scores are built on partial information. Any AI tool you use for risk stratification will inherit those gaps.",[19,1192,1194],{"id":1193},"the-regulatory-environment-is-moving-fast","The regulatory environment is moving fast",[12,1196,1197],{},"Prior authorization has attracted the most regulatory attention on AI. CMS launched its WISeR model in 2025, a pilot using AI and ML to screen prior authorization requests for select Medicare services across six states beginning January 2026. It signals CMS's interest in the technology — and the conditions it attaches are instructive.",[12,1199,1200],{},"At the same time, state legislatures have been moving in the opposite direction. Arizona, Maryland, and others passed laws in 2025 prohibiting AI from serving as the sole basis for medical necessity denials. A class action lawsuit against UnitedHealth over its nH Predict algorithm — which plaintiffs alleged was used to deny Medicare Advantage post-acute care claims with a 90% error rate — is still in litigation.",[12,1202,1203],{},"For smaller plans, the practical implication is narrow: don't build workflows where an AI system issues an adverse determination without human review. That exposure isn't worth the efficiency gain at your scale, and regulators are watching. Use AI to triage, flag, and surface — keep a human in the decision on anything clinical or coverage-determinative.",[19,1205,1207],{"id":1206},"build-vs-buy","Build vs. buy",[12,1209,1210],{},"Nearly 80% of health plans now prefer vendor-built AI over in-house development, according to a 2026 Innovaccer survey. For a plan with a small ops team, this is almost always the right call. Building and maintaining ML models requires data engineering, model validation, and ongoing retraining capacity that doesn't exist in most sub-100,000-member plans.",[12,1212,1213],{},"The real question isn't build vs. buy — it's which vendors are worth evaluating. A few criteria worth applying:",[12,1215,1216,1219],{},[29,1217,1218],{},"Transparency on training data."," Ask specifically what data the model was trained on and whether it includes plans with similar demographics to yours. A model trained predominantly on commercial populations may underperform on Medicaid or dually eligible members.",[12,1221,1222,1225],{},[29,1223,1224],{},"Integration depth."," Many AI vendors operate as overlays on your existing system, requiring data exports and manual imports. That creates lag, introduces error, and limits how actionable the outputs actually are. Integration that connects directly to your adjudication engine or care management platform is worth the higher price.",[12,1227,1228,1231],{},[29,1229,1230],{},"Governance and audit trail."," For anything touching clinical or coverage decisions, you need clear documentation of how a recommendation was generated. If you can't explain the AI's output to a regulator or a member on appeal, the tool isn't ready for that use case.",[19,1233,1235],{"id":1234},"where-to-focus-first","Where to focus first",[12,1237,1238],{},"For a resource-constrained ops team, the best starting point is usually the same: close the auto-adjudication gap before adding new AI capability.",[12,1240,1241],{},"If your plan is auto-adjudicating below 85%, fix the underlying data issues that are creating suspense. Update your edit library. Tighten eligibility reconciliation. Clean your provider directory. These aren't exciting projects, but they have the clearest ROI — and they build the data foundation that any AI tool you add later will depend on.",[12,1243,1244],{},"Once you're at or above 85%, the highest-return next move for most small plans is a denial prediction tool connected to your claims intake, and risk stratification on your most complex members. Both have enough track record now to make vendor selection tractable, and both produce outputs your team can act on without restructuring how you work.",[12,1246,1247],{},"What to avoid: generative AI tools for anything in the claims adjudication chain, any vendor that can't show you validation data from plans like yours, and any workflow where AI issues a coverage decision without a human checkpoint.",[12,1249,1250],{},"The plans getting real value from AI right now aren't the ones that deployed the most tools. They're the ones that got the data right first.",[158,1252],{},[12,1254,1255],{},[163,1256,1257,1258,1262,1263,179],{},"If you're evaluating your current automation baseline or thinking through where AI fits in your operations, ",[167,1259,1261],{"href":169,"rel":1260},[171],"Ayin's platform"," is built around the data infrastructure that makes these decisions tractable — and our team is available to work through the specifics with you at ",[167,1264,1266],{"href":176,"rel":1265},[171],"ayin.com\u002Fcontact",{"title":181,"searchDepth":182,"depth":182,"links":1268},[1269,1274,1275,1276,1277],{"id":1104,"depth":182,"text":1105,"children":1270},[1271,1273],{"id":1115,"depth":1272,"text":1116},3,{"id":1128,"depth":1272,"text":1129},{"id":1156,"depth":182,"text":1157},{"id":1193,"depth":182,"text":1194},{"id":1206,"depth":182,"text":1207},{"id":1234,"depth":182,"text":1235},"Technology","2026-04-15","Every vendor is selling AI to health plans. This cuts through it: where automation has a proven track record, where AI adds new value, the data quality prerequisite most plans skip, and where to focus first if you're resource-constrained.","\u002Fphotography\u002FAyin_still_2.png","Healthcare data and technology",{},"\u002Farticles\u002Fai-health-plan-back-office",{"title":1093,"description":1280},"articles\u002Fai-health-plan-back-office",[1288,1289,390,205,1278],"AI","Automation","OHsZl0PCt-4aQlNV8f2aU4DrLxrEq4x2ziBuniC6cko",{"id":1292,"title":1293,"author":7,"body":1294,"category":390,"date":1454,"description":1455,"extension":192,"featured":193,"image":194,"imageAlt":1456,"meta":1457,"navigation":197,"path":1458,"seo":1459,"stem":1460,"tags":1461,"__hash__":1465},"articles\u002Farticles\u002Fmedicaid-margin-compression-playbook.md","The Margin Compression Playbook: How Small Medicaid Plans Cut Administrative Costs Without Cutting Corners",{"type":9,"value":1295,"toc":1442},[1296,1299,1302,1306,1309,1312,1316,1319,1322,1326,1329,1332,1335,1339,1342,1345,1349,1352,1355,1359,1362,1365,1368,1372,1375,1378,1381,1384,1388,1391,1397,1403,1409,1415,1419,1422,1425,1428,1431,1433],[12,1297,1298],{},"Oregon's Coordinated Care Organizations got a 3.4% average rate increase in 2024. Their per-member costs grew by more than 10%. The result: an average net operating margin of essentially zero — 0.001% statewide — with seven of the sixteen CCOs posting outright losses. This isn't an Oregon story. It's a national pattern playing out in nearly every Medicaid market. The Milliman data is stark: across 184 Medicaid MCOs nationally, aggregate underwriting margins went from +2.4% in 2023 to -1.0% in 2024 — a $9.9 billion swing in a single year. More than half of all plans lost money on their Medicaid book. If you're running a small or mid-sized Medicaid plan right now, you already know this in your bones. The question isn't whether the pressure is real. The question is what you can actually do about it.",[12,1300,1301],{},"You cannot renegotiate your capitation rates on a Tuesday afternoon. You cannot change your member population's acuity. You cannot restructure your provider network fast enough to move the needle this fiscal year. What you can control — often with more impact than plans realize — is how efficiently your back office operates.",[19,1303,1305],{"id":1304},"where-administrative-cost-actually-lives","Where Administrative Cost Actually Lives",[12,1307,1308],{},"The first problem with most administrative efficiency discussions is that they stay at the level of the org chart. \"Reduce headcount.\" \"Consolidate functions.\" That's not a strategy. It's a budget cut dressed up in management language.",[12,1310,1311],{},"Real administrative cost lives in specific workflows. Here's where to look.",[1113,1313,1315],{"id":1314},"claims-touches","Claims Touches",[12,1317,1318],{},"Every time a claim requires human intervention — a human opens it, looks at it, routes it, corrects it, or makes a decision about it — that's a \"touch.\" Each touch costs money. For a plan processing 500,000 claims annually, reducing average touches from 1.8 to 1.2 per claim is not a rounding error. At even $8–12 of labor cost per touch, the math gets significant fast.",[12,1320,1321],{},"The plans with high touch rates share common root causes: incomplete or stale provider data causing routing failures, authorization mismatches that create pend queues, member eligibility that isn't reconciled in real time, and claims editing logic that hasn't been updated to reflect current contract terms. None of these are glamorous problems. All of them are fixable.",[1113,1323,1325],{"id":1324},"enrollment-churn","Enrollment Churn",[12,1327,1328],{},"Medicaid populations churn faster than any other market segment. Members gain and lose eligibility constantly — and every eligibility change creates downstream administrative work if your enrollment reconciliation isn't running continuously.",[12,1330,1331],{},"The cost of enrollment churn isn't just the enrollment transaction itself. It's the claims that adjudicate against the wrong eligibility status. It's the member services calls from people who think they're covered but aren't — or vice versa. It's the encounter data submissions that reflect a member who shouldn't have been on your roster. Phantom member problems — where a member has technically disenrolled but hasn't been cleanly removed from your operational systems — are more common than plans admit, and they propagate errors across claims, analytics, and quality reporting.",[12,1333,1334],{},"Plans that treat enrollment as a solved problem and batch-reconcile weekly or monthly are carrying this cost invisibly. The work still happens — it just shows up as downstream exception handling, rework, and corrected submissions.",[1113,1336,1338],{"id":1337},"call-volume-as-a-cost-symptom","Call Volume as a Cost Symptom",[12,1340,1341],{},"Your member services call volume isn't just a staffing problem. It's a diagnostic signal. High call volume on eligibility questions usually traces back to enrollment reconciliation gaps. High call volume on claims status usually means you have a claims pend backlog or a slow adjudication cycle. High call volume on referrals or authorizations often means your member-facing materials are out of date or your network directory has errors.",[12,1343,1344],{},"Most plans look at call volume and ask: how do we answer these calls more efficiently? The better question is: why are members calling in the first place? Resolving the upstream issue — the enrollment error, the claims delay, the stale provider data — eliminates the call entirely. That's a different math than hiring faster call center staff.",[1113,1346,1348],{"id":1347},"manual-workarounds","Manual Workarounds",[12,1350,1351],{},"Every manual workaround in your operation has a cost that's rarely measured directly. A staff member who exports data from your claims system into Excel to do a calculation that should happen automatically. A monthly report that requires someone to pull from three systems and reconcile by hand. A state submission that requires manual reformatting because your platform doesn't natively support the required format.",[12,1353,1354],{},"These workarounds accumulate over years. They're rarely documented. When the person who built them leaves, institutional knowledge walks out the door. And they consume staff time that could be spent on work that actually requires human judgment.",[19,1356,1358],{"id":1357},"benchmarking-theres-more-variation-than-you-think","Benchmarking: There's More Variation Than You Think",[12,1360,1361],{},"Here's something that often surprises plan leaders: the administrative cost variation across similarly-sized Medicaid plans is substantial. The Medicaid MLR framework requires plans to spend at least 85% of capitation revenue on clinical services — leaving 15% for administration and margin. But what plans actually spend on administration within that envelope varies widely.",[12,1363,1364],{},"Composite data across Medicaid MCOs for 2023 showed an average Administrative Loss Ratio of 7.9%. But averages obscure a wide range. Plans running lean, well-integrated administrative operations can land materially below that figure. Plans with fragmented systems, heavy manual workflows, and high staff-to-member ratios can run substantially above it — sometimes while also delivering worse service quality, because the administrative burden is distributed inefficiently rather than effectively.",[12,1366,1367],{},"If your administrative costs are above 10% of premium equivalents, that's worth examining seriously. If you don't know where you land, that's the first problem to solve.",[19,1369,1371],{"id":1370},"automation-vs-staffing-the-size-dependent-tradeoff","Automation vs. Staffing: The Size-Dependent Tradeoff",[12,1373,1374],{},"Small plans — say, under 40,000 members — face a specific dilemma. The automation investments that make large plans efficient (a mature claims editing engine, a real-time eligibility integration, an automated encounter data validation pipeline) require upfront capital and technical capacity to implement and maintain. You may not have the IT team to build and sustain them internally.",[12,1376,1377],{},"This creates a real temptation to staff around the gaps instead. Hire someone to manually check eligibility before each claims run. Hire someone to manage the encounter data exception queue. Hire a coordinator to handle the state reporting format conversions. These are real jobs, and for a time, they work.",[12,1379,1380],{},"The problem is that staffing around system gaps doesn't scale, and it doesn't improve. As your membership grows, the manual workload grows with it. The automation investment required to eliminate those roles doesn't get smaller — it gets more complicated because you've built operational habits around the workarounds.",[12,1382,1383],{},"The question for plans under 100,000 members isn't whether to automate versus staff. It's whether to build the automation internally, buy a point solution, or operate on a platform that handles it as part of an integrated back-office model. The honest answer depends on your growth trajectory, your internal technical capacity, and how many of these problems you're trying to solve simultaneously.",[19,1385,1387],{"id":1386},"what-to-stop-doing","What to Stop Doing",[12,1389,1390],{},"Sometimes the most valuable administrative efficiency move is subtraction. A few common candidates:",[12,1392,1393,1396],{},[29,1394,1395],{},"Stop running eligibility reconciliation on a weekly batch cycle."," Real-time or daily reconciliation costs more to implement once but eliminates a class of downstream rework that's expensive and ongoing. The break-even point arrives faster than most plans expect.",[12,1398,1399,1402],{},[29,1400,1401],{},"Stop manually building state submission files."," If your team is spending hours each month reformatting encounter data, prior authorization reports, or quality metric submissions to match state specifications, you're paying for a translation layer that should be automated. This is solved infrastructure, not custom work.",[12,1404,1405,1408],{},[29,1406,1407],{},"Stop treating your claims pend queue as a normal operating condition."," A large pend queue is a symptom of upstream data problems — provider file gaps, authorization mismatches, coordination of benefits issues. Clearing pends manually is treating the symptom. Finding why claims are pending in the first place is treating the disease.",[12,1410,1411,1414],{},[29,1412,1413],{},"Stop accepting that your member services team will \"just figure it out.\""," When member services staff are navigating multiple systems, interpreting inconsistent data, and improvising because they don't have clean eligibility and claims information at their fingertips, you're paying for their time while also delivering worse member experience. That's the worst of both.",[19,1416,1418],{"id":1417},"identifying-your-highest-cost-manual-workflows","Identifying Your Highest-Cost Manual Workflows",[12,1420,1421],{},"The practical starting point for any administrative efficiency effort is a workflow audit — not a high-level process map, but a ground-level inventory of where staff time actually goes.",[12,1423,1424],{},"Ask your operations leads to track, for two weeks, every task that involves opening more than one system, copying data between systems, reformatting data for a submission, or manually reviewing exceptions that should have been auto-adjudicated. You'll find patterns quickly. The highest-cost manual workflows almost always cluster around the same root causes: data that doesn't flow cleanly between systems, eligibility information that isn't current at the point of claims adjudication, and submission requirements that your platform doesn't natively support.",[12,1426,1427],{},"These are solvable problems. Not overnight, and not without investment — but with a clear return, because the manual cost is recurring and the fix is one-time (or at least amortized over years).",[12,1429,1430],{},"The plans that are navigating this margin environment without cutting clinical programs or member services quality are largely the ones that did this audit two or three years ago and made the infrastructure investments. The plans that are cutting corners now are the ones that didn't.",[158,1432],{},[12,1434,1435],{},[163,1436,1437,1438,1441],{},"If you're trying to understand where your administrative cost is concentrated and what it would take to address it, ",[167,1439,1440],{"href":534},"Ayin works with small and mid-sized Medicaid plans on exactly these problems"," — enrollment, claims, encounter data, and the integrations that tie them together.",{"title":181,"searchDepth":182,"depth":182,"links":1443},[1444,1450,1451,1452,1453],{"id":1304,"depth":182,"text":1305,"children":1445},[1446,1447,1448,1449],{"id":1314,"depth":1272,"text":1315},{"id":1324,"depth":1272,"text":1325},{"id":1337,"depth":1272,"text":1338},{"id":1347,"depth":1272,"text":1348},{"id":1357,"depth":182,"text":1358},{"id":1370,"depth":182,"text":1371},{"id":1386,"depth":182,"text":1387},{"id":1417,"depth":182,"text":1418},"2026-03-11","Medicaid rates rose 3.4% in 2024 while costs jumped over 10%. The only lever small plans can actually control right now is administrative efficiency — here's what that means operationally.","Administrative operations team reviewing health plan data",{},"\u002Farticles\u002Fmedicaid-margin-compression-playbook",{"title":1293,"description":1455},"articles\u002Fmedicaid-margin-compression-playbook",[551,390,1462,1463,1464],"Cost Reduction","Back Office","Financial Sustainability","0llIiqEtTcTUkiGpRFu0Qa8ezU8U6jOc4l7RPo91YXE",{"id":1467,"title":1468,"author":7,"body":1469,"category":390,"date":1724,"description":1725,"extension":192,"featured":193,"image":194,"imageAlt":1726,"meta":1727,"navigation":197,"path":1728,"seo":1729,"stem":1730,"tags":1731,"__hash__":1734},"articles\u002Farticles\u002Fback-office-build-hire-partner.md","Build, Hire, or Partner? A Decision Framework for Health Plan Back-Office Operations",{"type":9,"value":1470,"toc":1714},[1471,1474,1478,1481,1484,1487,1491,1494,1500,1506,1512,1518,1524,1528,1531,1630,1633,1637,1640,1643,1646,1649,1653,1656,1659,1662,1665,1669,1672,1675,1678,1681,1685,1688,1691,1694,1698,1701,1704,1706],[12,1472,1473],{},"You have a three-person ops team, a state audit on the calendar, and a backlog of enrollment reconciliation that nobody has had time to touch since the last redetermination wave. At the same time, your COO is asking whether it makes more sense to hire a claims supervisor, license a new platform, or hand the whole function to an outside vendor. Every small community health plan faces this question — repeatedly, across multiple functions, often without a structured way to answer it. Most of the content written on the topic either argues for full outsourcing or treats insourcing as the default without examining the tradeoffs honestly. This article tries to do something more useful: give you a real decision framework.",[19,1475,1477],{"id":1476},"start-with-the-right-question","Start With the Right Question",[12,1479,1480],{},"The instinct is usually to ask, \"Can we afford to outsource this?\" That's the wrong starting point. The better question is: \"What is this function actually costing us today — fully loaded — and what does it cost to do it to standard?\"",[12,1482,1483],{},"Many plans are carrying significant hidden costs in functions they assume are cheap because they're internal. A single enrollment specialist handling Medicaid redeterminations earns a base salary of $50,000–$65,000. Add benefits (typically 25–30% of salary), employer payroll taxes, training time, turnover cost (which runs 50–150% of annual salary in healthcare operations roles), and the management overhead of a supervisor whose time is split across five other issues. A function you think costs $70,000 a year may actually cost $110,000–$130,000 fully burdened — before accounting for errors, rework, and the compliance exposure from a team that's stretched thin.",[12,1485,1486],{},"That's not an argument for outsourcing. It's an argument for knowing your actual number before you make any decision.",[19,1488,1490],{"id":1489},"the-five-variables-that-should-drive-the-decision","The Five Variables That Should Drive the Decision",[12,1492,1493],{},"There is no universal answer to build-hire-partner. But five variables tend to determine the right path for most small community health plans:",[12,1495,1496,1499],{},[29,1497,1498],{},"1. Plan size and volume."," Some back-office functions have real economies of scale. Claims adjudication, encounter data submission, and eligibility reconciliation all get meaningfully cheaper per transaction as volume increases — but only if you have the infrastructure to support volume. A 25,000-member Medicaid plan processing 150,000 claims per year will almost never achieve the per-claim cost of a partner that processes 10 million claims annually across multiple customers. If you're below roughly 50,000 members, the math on internal claims infrastructure is almost always unfavorable.",[12,1501,1502,1505],{},[29,1503,1504],{},"2. Growth trajectory."," If you're in active growth — adding members, expanding geographically, launching a new program line — internal staffing is a liability. You hire for current volume, volume spikes, you scramble to hire again, and the new hires take 3–6 months to reach full productivity. If you're stable or contracting, a well-structured internal team may be more cost-efficient than a partner relationship sized for growth you're not experiencing.",[12,1507,1508,1511],{},[29,1509,1510],{},"3. Regulatory complexity."," Some functions are operationally routine once you understand the rules. Others require ongoing specialization that's genuinely hard to maintain internally. Encounter data submission for PACE organizations, CMS risk adjustment for Medicare Advantage, and Oregon Health Plan quality metric reporting all fall in the latter category. The regulatory requirements change frequently, the penalty for error is real, and maintaining current expertise internally requires dedicated investment in staff development. Regulatory-intensive functions favor external partners whose entire business is built around staying current.",[12,1513,1514,1517],{},[29,1515,1516],{},"4. Internal capacity to manage a vendor."," This is the variable that gets overlooked most often. Outsourcing does not eliminate management burden — it transforms it. You go from managing staff to managing a contract, a service level agreement, and a relationship. That requires someone with enough operational knowledge to evaluate performance, enough authority to push back when standards aren't met, and enough bandwidth to do both without dropping something else. Plans that lack this capacity often find their outsourcing relationships drift — the vendor delivers mediocre results because no one is holding them to account.",[12,1519,1520,1523],{},[29,1521,1522],{},"5. Capital availability."," Building internal capability requires upfront investment: systems, training, process documentation, and hiring lead time. Partnering typically converts capital expenditure to operating expense — predictable monthly costs in exchange for not owning the infrastructure. For plans under financial pressure from rate compression or enrollment volatility, the operating expense model often makes more sense even when the long-run cost would be lower with internal investment.",[19,1525,1527],{"id":1526},"the-decision-matrix","The Decision Matrix",[12,1529,1530],{},"Run each major back-office function through this set of questions:",[1532,1533,1534,1550],"table",{},[1535,1536,1537],"thead",{},[1538,1539,1540,1544,1547],"tr",{},[1541,1542,1543],"th",{},"Question",[1541,1545,1546],{},"Points toward Build\u002FHire",[1541,1548,1549],{},"Points toward Partner",[1551,1552,1553,1565,1575,1585,1594,1603,1612,1621],"tbody",{},[1538,1554,1555,1559,1562],{},[1556,1557,1558],"td",{},"Volume above 50,000 members and growing?",[1556,1560,1561],{},"Build\u002FHire",[1556,1563,1564],{},"—",[1538,1566,1567,1570,1572],{},[1556,1568,1569],{},"Function requires specialized expertise that changes frequently?",[1556,1571,1564],{},[1556,1573,1574],{},"Partner",[1538,1576,1577,1580,1583],{},[1556,1578,1579],{},"You have internal capacity to manage a vendor relationship?",[1556,1581,1582],{},"Either",[1556,1584,1582],{},[1538,1586,1587,1590,1592],{},[1556,1588,1589],{},"Function is core to your competitive differentiation?",[1556,1591,1561],{},[1556,1593,1564],{},[1538,1595,1596,1599,1601],{},[1556,1597,1598],{},"Rate of regulatory change is high?",[1556,1600,1564],{},[1556,1602,1574],{},[1538,1604,1605,1608,1610],{},[1556,1606,1607],{},"You need to scale up or down quickly?",[1556,1609,1564],{},[1556,1611,1574],{},[1538,1613,1614,1617,1619],{},[1556,1615,1616],{},"Capital is constrained and you need predictable costs?",[1556,1618,1564],{},[1556,1620,1574],{},[1538,1622,1623,1626,1628],{},[1556,1624,1625],{},"You have current staff who can own this function fully?",[1556,1627,1561],{},[1556,1629,1564],{},[12,1631,1632],{},"No single question is decisive. The pattern across questions is what matters. A function where five of seven arrows point toward \"Partner\" is probably not worth staffing internally, regardless of what feels more comfortable.",[19,1634,1636],{"id":1635},"what-end-to-end-support-actually-means-and-why-it-matters","What \"End-to-End Support\" Actually Means — and Why It Matters",[12,1638,1639],{},"There is a meaningful difference between point-solution outsourcing and end-to-end operational partnership. Understanding that difference matters before you sign anything.",[12,1641,1642],{},"A point-solution vendor handles one function — claims adjudication, or member services calls, or eligibility verification — and hands the output back to you. You still own integration, exception handling, reporting, and coordination across functions. For a three-person ops team, that coordination burden can easily consume whatever efficiency you were hoping to gain.",[12,1644,1645],{},"An end-to-end partner takes responsibility for a complete operational domain: intake through resolution, including the handoffs between functions, the exception workflows, and the reporting that tells you how the domain is performing. You get a single relationship, a single SLA, and one throat to grab when something goes wrong.",[12,1647,1648],{},"Point solutions make sense when your internal team is strong and you need to augment one specific area of capacity or expertise. End-to-end support makes sense when the coordination burden itself is a significant part of your problem. Most small community health plans have coordination problems — they just don't always recognize them as such until a claims error traces back to an enrollment gap that was itself triggered by an eligibility reconciliation failure no one caught.",[19,1650,1652],{"id":1651},"the-hybrid-model","The Hybrid Model",[12,1654,1655],{},"The realistic answer for most plans is neither full insourcing nor full outsourcing — it's a deliberate hybrid. The question is where to draw the line.",[12,1657,1658],{},"A workable starting framework: staff internally for functions that require deep institutional knowledge of your member population, your provider relationships, and your clinical priorities. Partner externally for functions that require technical depth in regulatory compliance, systems integration, or high-volume transaction processing.",[12,1660,1661],{},"For a Medicaid plan, that might mean keeping your clinical quality team and your provider relations function internal while partnering for claims administration, encounter data, and enrollment reconciliation. Your internal team retains the relationships and the program knowledge. The partner handles the infrastructure and the regulatory-compliance heavy lifting.",[12,1663,1664],{},"This model only works if the boundary between internal and external is clearly defined in the contract, the data flows between them are automated and reliable, and someone on your team owns the relationship actively.",[19,1666,1668],{"id":1667},"transition-risk-the-cost-that-doesnt-show-up-in-the-proposal","Transition Risk: The Cost That Doesn't Show Up in the Proposal",[12,1670,1671],{},"Any decision to shift a function — whether inward or outward — carries transition risk. Plans consistently underestimate this cost.",[12,1673,1674],{},"Moving from internal to partner: expect a 60–120 day period where both teams are running the function in parallel. Historical data migration takes longer than anyone projects. Institutional knowledge that was never documented will surface as gaps after the transition. Build this into your cost comparison and your timeline expectations.",[12,1676,1677],{},"Moving from partner to internal: this is harder, not easier. You are rebuilding capability that your team hasn't operated in years, often during a contract wind-down when the outgoing vendor's cooperation is limited. The plans that execute this successfully do so because they maintained enough internal operational knowledge to supervise the partner — which reinforces the earlier point about vendor management capacity.",[12,1679,1680],{},"The risk isn't a reason to avoid transitions. It is a reason to build a realistic transition plan before you sign, not after.",[19,1682,1684],{"id":1683},"when-building-internally-is-the-right-answer","When Building Internally Is the Right Answer",[12,1686,1687],{},"It bears saying clearly, because most of what gets written on this topic tilts toward outsourcing: there are real scenarios where building internal capability is the better call.",[12,1689,1690],{},"If you are a growing plan approaching 100,000 members with stable program structure, sufficient capital, and strong operational leadership, the long-run economics of internal infrastructure can favor insourcing — particularly for functions like customer service where member relationship quality is part of your value proposition. If your market differentiation is built around local program integration and community relationships, handing those functions to a vendor that serves dozens of plans nationally is a real strategic tradeoff, not just a cost decision.",[12,1692,1693],{},"If you have experienced staff who know your programs deeply and are currently doing the work well — don't fix what isn't broken. The best reason to partner is a genuine capability or capacity gap, not an assumption that external is always more efficient.",[19,1695,1697],{"id":1696},"make-the-decision-function-by-function","Make the Decision Function by Function",[12,1699,1700],{},"The most common mistake is treating this as a binary organizational question — \"should we outsource our back office?\" — rather than a function-by-function operational analysis. Your claims operation may be a strong candidate for partnering. Your member services team may be your biggest retention asset. Encounter data submission may require external expertise your team simply doesn't have time to maintain. Each function deserves its own analysis against the variables above.",[12,1702,1703],{},"Do that analysis with honest numbers, including the fully loaded internal cost and a realistic read on transition risk. The right answer will be different for every plan — and probably different from the answer you arrived at intuitively before you ran the numbers.",[158,1705],{},[12,1707,1708],{},[163,1709,1710,1711,1713],{},"If you're working through this decision for your plan, ",[167,1712,7],{"href":534}," works through exactly this kind of analysis with health plans before recommending any path forward — including when the right answer is to build internally.",{"title":181,"searchDepth":182,"depth":182,"links":1715},[1716,1717,1718,1719,1720,1721,1722,1723],{"id":1476,"depth":182,"text":1477},{"id":1489,"depth":182,"text":1490},{"id":1526,"depth":182,"text":1527},{"id":1635,"depth":182,"text":1636},{"id":1651,"depth":182,"text":1652},{"id":1667,"depth":182,"text":1668},{"id":1683,"depth":182,"text":1684},{"id":1696,"depth":182,"text":1697},"2026-01-20","Every small community health plan faces the same question: staff up internally, build your own systems, or partner with an outside firm? Here is an honest framework for making that call — including when internal is the right answer.","Health plan operations team reviewing workflows",{},"\u002Farticles\u002Fback-office-build-hire-partner",{"title":1468,"description":1725},"articles\u002Fback-office-build-hire-partner",[1463,390,1732,1278,1733],"BPO","Strategy","yhzk7bKhJSx2phhCS11gJCv97sZyS7IZuIZMyqLIhog",{"id":1736,"title":1737,"author":7,"body":1738,"category":390,"date":1917,"description":1918,"extension":192,"featured":193,"image":194,"imageAlt":1919,"meta":1920,"navigation":197,"path":1921,"seo":1922,"stem":1923,"tags":1924,"__hash__":1928},"articles\u002Farticles\u002Foregon-health-plan-operations-guide.md","Oregon Health Plan Operations: A Practical Guide for CCO Administrative Teams",{"type":9,"value":1739,"toc":1909},[1740,1743,1746,1750,1753,1756,1759,1762,1768,1774,1780,1784,1787,1790,1793,1796,1799,1803,1806,1809,1812,1832,1835,1838,1842,1845,1851,1857,1863,1869,1872,1876,1879,1885,1891,1895,1898,1900],[12,1741,1742],{},"If you've worked in Medicaid administration in another state and then moved into an Oregon CCO, the learning curve is real. The Oregon Health Plan isn't just a differently-branded version of standard managed Medicaid. It has structural features — the Prioritized List of Health Services, a state-specific quality incentive program with its own reporting infrastructure, and a DHS foster care population with distinct coordination requirements — that don't have direct equivalents anywhere else. For administrative and operations teams, understanding those features at a working level isn't optional. They affect claims adjudication, revenue, compliance exposure, and how your team spends its time every week.",[12,1744,1745],{},"This is a practical guide for CCO administrative directors and ops managers who need to operate inside OHP fluently, not just understand it from a policy perspective.",[19,1747,1749],{"id":1748},"the-prioritized-list-what-it-actually-means-for-claims-adjudication","The Prioritized List: What It Actually Means for Claims Adjudication",[12,1751,1752],{},"The Oregon Health Evidence Review Commission (HERC) publishes a ranked list of condition-treatment pairs — what OHA calls the Prioritized List of Health Services. The Oregon Legislature sets a funding line each biennium. Services ranked above the line are covered. Services ranked below the line are generally not.",[12,1754,1755],{},"As of January 1, 2024, OHP covers lines 1 through 469. Adult coverage extends to funded conditions at line 472 or above on the current 2026 list. The practical consequence for your claims operation: coverage determination requires knowing both the procedure code and the diagnosis code being billed. That pairing — condition and treatment together — determines where a claim falls on the list. You can't evaluate coverage from the procedure code alone.",[12,1757,1758],{},"This is the Line-Condition-Treatment (LCT) logic that OHP claims staff and systems have to implement. Standard Medicaid benefit packages in most states let you adjudicate coverage from the procedure code and the member's eligibility. OHP requires a third variable: the diagnosis. Adjudicating without it, or with an incomplete code pairing, will produce incorrect coverage determinations — both false denials and false approvals.",[12,1760,1761],{},"A few operational realities that catch teams off guard:",[12,1763,1764,1767],{},[29,1765,1766],{},"The same procedure code can produce different coverage outcomes."," A specific CPT code paired with one diagnosis may land above the line (covered); the same CPT code paired with a different diagnosis may land below (not covered). Your claims system needs to handle this correctly or it generates errors in bulk.",[12,1769,1770,1773],{},[29,1771,1772],{},"Below-the-line isn't the same as never covered."," Ancillary and diagnostic services can be covered even when the primary condition treatment is below the line. And members under 21 receive EPSDT coverage — all medically necessary services, regardless of line placement. Effective January 1, 2025, that EPSDT-equivalent protection extended to members under 26 who qualify for Young Adults with Special Health Care Needs (YSHCN) benefits. If your system is denying services for these populations based on line placement, it's denying incorrectly.",[12,1775,1776,1779],{},[29,1777,1778],{},"OHA operates a code pairing hotline."," The OHP Code Pairing and Prioritized List Hotline (800-336-6016) exists for a reason. Your clinical and claims staff should know it exists and know when to use it. Borderline determinations happen, and getting them wrong in either direction has downstream consequences.",[19,1781,1783],{"id":1782},"a-major-structural-change-is-coming-the-prioritized-list-is-going-away","A Major Structural Change Is Coming: The Prioritized List Is Going Away",[12,1785,1786],{},"Here is the single most important policy development Oregon CCO administrative teams need to be planning for right now: CMS has directed OHA to stop using the Prioritized List by January 1, 2027.",[12,1788,1789],{},"That deadline is less than nine months away.",[12,1791,1792],{},"OHA convened a planning workgroup that met from August through December 2025. The replacement structure moves OHP from a ranked list model to a category-based system — federally-defined benefit categories, some mandatory and some optional, with coverage applying to all medically necessary services within covered categories. This aligns Oregon with standard Medicaid practices used in other states.",[12,1794,1795],{},"What this means operationally: the LCT adjudication logic that your claims system currently applies will need to be reconfigured. The code-pairing infrastructure your team relies on will be replaced by a different coverage determination framework. OHA has stated that members will not lose covered services in the transition — the intent is continuity — but the administrative mechanics of how your system evaluates coverage will change substantially.",[12,1797,1798],{},"If your claims system is configured with hard-coded OHP prioritized list logic, that configuration has a hard expiration date. If you're running manual workarounds for edge cases, document them now, because those same edge cases will need to be re-evaluated under the new framework. CCOs that wait until late 2026 to begin reconfiguration will be processing claims manually during the transition.",[19,1800,1802],{"id":1801},"oha-quality-metric-reporting-the-administrative-calendar-your-team-owns","OHA Quality Metric Reporting: The Administrative Calendar Your Team Owns",[12,1804,1805],{},"The CCO Quality Incentive Program (QIP) ties a meaningful portion of CCO revenue to performance on 13 incentive measures. To receive 100 percent of eligible Quality Pool funds, a CCO must meet or exceed the benchmark or improvement target on at least 10 of those 13 measures. The financial stakes are real — the quality pool represents funds that smaller CCOs cannot afford to leave on the table.",[12,1807,1808],{},"What administrative teams need to understand is that this isn't just a clinical performance function. The reporting mechanics are administrative, and the deadlines are fixed.",[12,1810,1811],{},"For measurement year 2025, here is the operative timeline your operations team needs to own:",[601,1813,1814,1820,1826],{},[604,1815,1816,1819],{},[29,1817,1818],{},"December 2025",": OHA provides preliminary sample for the Prenatal and Postpartum Care (PPC) hybrid measure",[604,1821,1822,1825],{},[29,1823,1824],{},"January 2026",": OHA delivers final PPC sample and the CCO Enrollment by Plan Type report used to identify total CCO physical health membership",[604,1827,1828,1831],{},[29,1829,1830],{},"March 31, 2026",": Final deadline for PPC and Social Determinants of Health (SDOH) template submissions to OHA; also the deadline for EHR-based data proposals and data submission fields",[12,1833,1834],{},"Missing the March 31 deadline isn't a recoverable error for that measurement year. OHA uses administrative claims and enrollment data to generate denominator populations for hybrid measures — which means data quality problems upstream (enrollment errors, claims coding gaps) directly affect your denominator accuracy and, ultimately, your quality scores.",[12,1836,1837],{},"The quality reporting calendar also intersects with your encounter data obligations. Encounter data that doesn't flow correctly into OHA's systems creates gaps in the administrative data OHA uses to calculate your measures. Clean encounter data isn't just a CMS compliance requirement — it's a direct input into OHP quality revenue.",[19,1839,1841],{"id":1840},"dhs-foster-care-why-this-population-is-operationally-distinct","DHS Foster Care: Why This Population Is Operationally Distinct",[12,1843,1844],{},"Children in DHS custody are a prioritized population under OHP rules, and they come with administrative requirements that differ from general CCO membership in several concrete ways.",[12,1846,1847,1850],{},[29,1848,1849],{},"The coordination mandate is explicit."," CCOs are required to provide Intensive Care Coordination (ICC) for foster care members — spanning physical health, behavioral health, and oral health — including for members placed outside the CCO's service area. Placement instability is a defining feature of this population. A child can move from one county to another, cross CCO service area boundaries, and still remain your member administratively. Your ICC team has to be able to reach and coordinate care for members who aren't geographically proximate to your network.",[12,1852,1853,1856],{},[29,1854,1855],{},"DHS is a required coordination partner."," CCO care coordinators are required to have a direct method of contact with the member's DHS case manager — whether that's through Area Agency on Aging, Aging and People with Disabilities, or the local Developmental Disability services provider. This isn't optional and it isn't just best practice. It's a contractual requirement that OHA reviews during quality assurance processes.",[12,1858,1859,1862],{},[29,1860,1861],{},"The EPSDT obligation applies at full strength."," Foster children are almost always under 21, which means all medically necessary services are covered regardless of Prioritized List line placement. This matters for claims adjudication: your system should not be applying standard below-the-line denial logic to foster care members. It also means behavioral health, dental, and developmental services that might otherwise require coverage determinations are covered on a medical necessity standard.",[12,1864,1865,1868],{},[29,1866,1867],{},"Electronic health record continuity is a documented obligation."," DHS maintains electronic health records for foster children to preserve medical history through placement changes. CCOs are expected to support continuity of care across those transitions. Practically, this means your care coordination and customer service teams need to be equipped to handle member transitions that aren't triggered by standard enrollment events — they're triggered by DHS placement decisions that happen on DHS's timeline, not yours.",[12,1870,1871],{},"The administrative load for this population is disproportionate to its size. Foster care members represent a small share of total CCO enrollment but generate care coordination, customer service, and claims adjudication complexity that requires specific staff training and workflow configuration.",[19,1873,1875],{"id":1874},"what-else-is-changing-in-2026-and-2027","What Else Is Changing in 2026 and 2027",[12,1877,1878],{},"Beyond the Prioritized List transition, CCO administrative teams need to be tracking two other near-term operational changes.",[12,1880,1881,1884],{},[29,1882,1883],{},"CCO payment rates increased 10.2% for 2026."," OHA increased capitation payments to CCOs by an average of 10.2%, reflecting both inflationary pressures and the financial strain documented across Oregon CCOs. This provides some operational room, but it doesn't change the compliance obligations or reporting requirements — it just means the revenue at risk from quality penalties and encounter data errors is proportionally larger.",[12,1886,1887,1890],{},[29,1888,1889],{},"Federal work and activity requirements take effect January 1, 2027."," Starting in 2027, many adult OHP members aged 19-64 will need to demonstrate 80 hours per month of qualifying work, volunteer, education, or training activity — or qualify for an exemption. Renewals for affected adults will move from annual to semi-annual. The federal government has not yet released all implementing guidance, but the enrollment processing volume implications are significant. CCOs that rely on manual renewal workflows are looking at a workload problem. This is not an abstract 2027 concern — it requires enrollment system configuration work that should be starting now.",[19,1892,1894],{"id":1893},"operating-in-ohp-is-a-specialized-discipline","Operating in OHP Is a Specialized Discipline",[12,1896,1897],{},"Oregon has built one of the most ambitious managed Medicaid programs in the country. The Prioritized List, quality incentive structure, DHS coordination requirements, and now the benefit structure transition add up to an administrative environment that requires program-specific expertise — not just general Medicaid ops experience. The teams that operate effectively in OHP are the ones who treat these Oregon-specific features as first-class operational concerns, not edge cases.",[158,1899],{},[12,1901,1902],{},[163,1903,1904,1905,1908],{},"If your CCO is working through the Prioritized List transition, the 2026 quality reporting cycle, or DHS foster care coordination requirements, ",[167,1906,1907],{"href":534},"Ayin's team has deep operational experience with OHP-specific workflows"," — and we're happy to talk through where you are.",{"title":181,"searchDepth":182,"depth":182,"links":1910},[1911,1912,1913,1914,1915,1916],{"id":1748,"depth":182,"text":1749},{"id":1782,"depth":182,"text":1783},{"id":1801,"depth":182,"text":1802},{"id":1840,"depth":182,"text":1841},{"id":1874,"depth":182,"text":1875},{"id":1893,"depth":182,"text":1894},"2025-10-28","The Oregon Health Plan has structural complexities — the prioritized list, OHA quality reporting, DHS foster care workflows — that differ from every other state Medicaid program. This guide covers what CCO administrative teams need to operate within it fluently.","Administrative operations team reviewing Oregon Health Plan workflows",{},"\u002Farticles\u002Foregon-health-plan-operations-guide",{"title":1737,"description":1918},"articles\u002Foregon-health-plan-operations-guide",[1925,1926,551,1927,189],"Oregon","OHP","CCO","V9TM4sDykBG3wGJmwOOa7_a3vErzHa07_hAK6cHtr8Q",{"id":1930,"title":1931,"author":7,"body":1932,"category":774,"date":2064,"description":2065,"extension":192,"featured":197,"image":194,"imageAlt":2066,"meta":2067,"navigation":197,"path":2068,"seo":2069,"stem":2070,"tags":2071,"__hash__":2075},"articles\u002Farticles\u002Fvalue-based-care-medicaid-2025.md","Value-Based Care in Medicaid: What Provider-Sponsored Plans Need to Know in 2025",{"type":9,"value":1933,"toc":2053},[1934,1937,1941,1944,1947,1951,1954,1958,1961,1965,1968,1972,1975,1979,1982,1985,1989,1992,2012,2016,2019,2039,2042,2044],[12,1935,1936],{},"The landscape of Medicaid managed care is shifting rapidly. As states push deeper into value-based payment models, provider-sponsored plans are uniquely positioned—but only if they have the infrastructure to execute. Here's what the data and our experience supporting over a million enrollees tells us.",[19,1938,1940],{"id":1939},"the-accelerating-shift-to-value","The Accelerating Shift to Value",[12,1942,1943],{},"Over the past three years, more than 35 states have expanded value-based care requirements in their Medicaid contracts. These arrangements go beyond simple pay-for-performance bonuses—they now include shared savings models, global capitation, and in some markets, full financial risk for defined populations.",[12,1945,1946],{},"For provider-sponsored health plans, this is familiar territory in one sense: the clinical expertise is already there. The gap, consistently, is on the operational and data side.",[19,1948,1950],{"id":1949},"where-plans-struggle-most","Where Plans Struggle Most",[12,1952,1953],{},"In our work with Medicaid, Medicare Advantage, and PACE plans, we see three recurring pain points:",[1113,1955,1957],{"id":1956},"_1-claims-data-latency","1. Claims Data Latency",[12,1959,1960],{},"Value-based care contracts require near-real-time visibility into utilization patterns. Plans that are still processing claims in batch cycles of 24–48 hours are working with data that's already stale when risk stratification decisions need to be made.",[1113,1962,1964],{"id":1963},"_2-care-management-gaps","2. Care Management Gaps",[12,1966,1967],{},"Even plans with strong clinical teams hit capacity ceilings when their care management tools aren't integrated with enrollment, authorization, and claims workflows. A care manager who has to check three separate systems to confirm a member's current status loses time that could be spent on outreach.",[1113,1969,1971],{"id":1970},"_3-enrollment-volatility","3. Enrollment Volatility",[12,1973,1974],{},"Medicaid populations churn. Members gain and lose eligibility faster than in commercial markets, creating a constant operational burden. Plans that lack automated eligibility verification and enrollment reconciliation routinely carry phantom members on their books—skewing both risk scores and per-member-per-month reporting.",[19,1976,1978],{"id":1977},"the-infrastructure-answer","The Infrastructure Answer",[12,1980,1981],{},"The plans we see performing well in value-based contracts share a common characteristic: their technology, administrative services, and analytics are integrated—not siloed.",[12,1983,1984],{},"When claims adjudication feeds directly into care management alerts, and enrollment data flows automatically into both, you get a closed loop. The result isn't just efficiency—it's the ability to intervene before a gap in care becomes a gap in quality measure performance.",[19,1986,1988],{"id":1987},"what-2025-looks-like","What 2025 Looks Like",[12,1990,1991],{},"Several trends are worth watching closely this year:",[601,1993,1994,2000,2006],{},[604,1995,1996,1999],{},[29,1997,1998],{},"HEDIS measure expansion",": CMS continues to broaden the quality measure set for Medicare-Medicaid integration programs. Plans that aren't tracking these measures in real time will be reactive, not proactive.",[604,2001,2002,2005],{},[29,2003,2004],{},"PACE program growth",": The Program of All-Inclusive Care for the Elderly is expanding nationally, and state PACE organizations face many of the same infrastructure gaps as larger Medicaid plans—often with smaller administrative teams.",[604,2007,2008,2011],{},[29,2009,2010],{},"AI-assisted utilization management",": Early adopters are using machine learning to flag high-risk prior authorization requests for expedited clinical review. The technology is ready; the integration question is whether UM workflows can actually act on the output.",[19,2013,2015],{"id":2014},"starting-points-that-move-the-needle","Starting Points That Move the Needle",[12,2017,2018],{},"If you're evaluating where to invest, we'd suggest prioritizing in this order:",[1171,2020,2021,2027,2033],{},[604,2022,2023,2026],{},[29,2024,2025],{},"Clean enrollment data first."," Everything downstream—claims, care management, analytics—is only as good as your member roster.",[604,2028,2029,2032],{},[29,2030,2031],{},"Integrate claims and care management."," Even a basic integration that pushes high-cost claims into a care management worklist delivers measurable ROI.",[604,2034,2035,2038],{},[29,2036,2037],{},"Build your quality measure dashboard before your contract renews."," Understanding your HEDIS and CAHPS performance gaps 12 months before a contract renewal gives you time to actually close them.",[12,2040,2041],{},"Value-based care rewards organizations that can connect the dots between clinical intent and operational execution. For provider-sponsored plans, the clinical foundation is already there. The work now is building the infrastructure to support it.",[158,2043],{},[12,2045,2046],{},[163,2047,2048,2049,2052],{},"Ayin Health Solutions supports provider-sponsored health plans across Medicaid, Medicare Advantage, and PACE programs with integrated technology, administrative services, and analytics. ",[167,2050,2051],{"href":534},"Connect with our team"," to discuss your specific situation.",{"title":181,"searchDepth":182,"depth":182,"links":2054},[2055,2056,2061,2062,2063],{"id":1939,"depth":182,"text":1940},{"id":1949,"depth":182,"text":1950,"children":2057},[2058,2059,2060],{"id":1956,"depth":1272,"text":1957},{"id":1963,"depth":1272,"text":1964},{"id":1970,"depth":1272,"text":1971},{"id":1977,"depth":182,"text":1978},{"id":1987,"depth":182,"text":1988},{"id":2014,"depth":182,"text":2015},"2025-06-12","As state Medicaid programs accelerate their shift toward value-based care arrangements, provider-sponsored health plans face both new opportunities and operational challenges. Here's what you need to know.","Clinician reviewing data on a tablet",{},"\u002Farticles\u002Fvalue-based-care-medicaid-2025",{"title":1931,"description":2065},"articles\u002Fvalue-based-care-medicaid-2025",[551,774,2072,2073,2074],"Health Plans","PACE","Care Management","dkQQh_2p4b0YpV_-r7neELJHBeiNXTW1PEd2drEvOoc",{"id":2077,"title":2078,"author":2079,"body":2080,"category":2079,"date":2079,"description":181,"extension":192,"featured":193,"image":2079,"imageAlt":2079,"meta":2269,"navigation":197,"path":2270,"seo":2271,"stem":2272,"tags":2079,"__hash__":2273},"articles\u002Farticles\u002Fbehavioral-health-claims-analytics-infrastructure.md","Behavioral Health Claims Analytics Infrastructure",null,{"type":9,"value":2081,"toc":2261},[2082,2084,2093,2096,2100,2103,2109,2115,2121,2127,2133,2137,2140,2146,2152,2158,2164,2170,2174,2177,2183,2189,2195,2201,2207,2211,2214,2220,2226,2232,2238,2244,2247,2249],[158,2083],{},[19,2085,2087,2088,2092],{"id":2086},"title-what-behavioral-health-cost-growth-means-for-your-claims-and-analytics-infrastructuredescription-behavioral-health-is-now-one-of-the-fastest-growing-cost-categories-in-medicaid-managed-care-and-most-small-plans-lack-the-claims-infrastructure-and-analytics-to-see-it-clearly-heres-what-you-need-to-fix-thatdate-2025-12-09author-ayin-health-solutionscategory-technologytags-behavioral-health-claims-analytics-operations-dataimage-photographyayin_still_7pngimagealt-healthcare-operations-and-data-analytics-workspacefeatured-false","title: \"What Behavioral Health Cost Growth Means for Your Claims and Analytics Infrastructure\"\ndescription: \"Behavioral health is now one of the fastest-growing cost categories in Medicaid managed care — and most small plans lack the claims infrastructure and analytics to see it clearly. Here's what you need to fix that.\"\ndate: 2025-12-09\nauthor: \"Ayin Health Solutions\"\ncategory: \"Technology\"\ntags: ",[2089,2090,2091],"span",{},"\"Behavioral Health\", \"Claims\", \"Analytics\", \"Operations\", \"Data\"","\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Healthcare operations and data analytics workspace\"\nfeatured: false",[12,2094,2095],{},"Behavioral health has quietly become one of the fastest-growing cost categories in Medicaid managed care, and most small plans are watching it happen without the infrastructure to understand why. Managed care organizations reported elevated behavioral health utilization as a driver of margin pressure throughout 2024, with multiple insurers flagging BH spend as a primary factor in capitation rate misalignment during Q3 and Q4 earnings cycles. Total Medicaid managed care spending grew 6.4% from FFY 2024 to FFY 2025 — more than three times the prior year's growth rate — and behavioral health, alongside pharmaceuticals and long-term services, was consistently cited as a top driver. The cost growth itself is only part of the problem. The other part is that the systems most plans use to track and understand claims were not built with behavioral health in mind. If you're a COO or analytics lead at a community plan, you probably know BH costs are up. What you may not know is why your standard reports can't tell you the full story.",[19,2097,2099],{"id":2098},"why-bh-claims-are-operationally-different-from-medicalsurgical","Why BH Claims Are Operationally Different from Medical\u002FSurgical",[12,2101,2102],{},"Behavioral health claims are not just medical claims with different diagnosis codes. The underlying transaction structure, coding logic, and adjudication rules differ in ways that create real operational friction.",[12,2104,2105,2108],{},[29,2106,2107],{},"837P versus 837I transaction mix."," Most behavioral health services are billed on the 837P (professional) transaction format — individual therapy, psychiatric evaluation, medication management. But higher-acuity services like partial hospitalization programs (PHP) and inpatient psychiatric stays use the 837I (institutional) format. Plans that process a lot of BH volume end up managing a mixed transaction environment with different field requirements, different remittance logic, and different adjudication rules for each. A claims system tuned primarily for 837I medical\u002Fsurgical inpatient will often mishandle 837P behavioral health claims in ways that don't trigger obvious errors — they just adjudicate incorrectly or incompletely.",[12,2110,2111,2114],{},[29,2112,2113],{},"Place-of-service logic."," BH services are delivered in a wide range of settings — outpatient offices, community mental health centers, residential facilities, crisis stabilization units, member homes via telehealth. Each place-of-service code carries different reimbursement rules and different authorization requirements. Telehealth alone created a permanent complexity layer: by 2022, behavioral health telehealth had grown from roughly 1% of visits pre-pandemic to more than 32%, and coverage rules, modifier requirements, and rate schedules vary significantly by payer and state contract. If your claims system doesn't have explicit logic for BH place-of-service combinations, you're either over-paying, under-paying, or generating a denial queue that never gets fully worked.",[12,2116,2117,2120],{},[29,2118,2119],{},"Authorization workflows that don't match medical\u002Fsurgical patterns."," Outpatient BH services often don't require prior authorization for initial sessions but trigger continued-stay reviews after a defined visit threshold. PHP and intensive outpatient programs (IOP) almost always require authorization. Residential treatment requires authorization and ongoing clinical review. These are not the same authorization workflows as a surgical prior auth, and managed care platforms that weren't purpose-built for BH often handle them inconsistently — missing the visit-count trigger, failing to link the authorization to the correct service line, or accepting claims against an expired auth without flagging the discrepancy.",[12,2122,2123,2126],{},[29,2124,2125],{},"CPT code complexity and bundling rules."," BH coding has expanded significantly, including add-on codes for complexity, codes for collaborative care models, medication-assisted treatment billing that spans pharmacy and medical, and crisis intervention codes that may be billed by multiple provider types for the same episode. Bundling and unbundling rules for BH are genuinely complex, and the opportunity for coding errors — in both directions — is substantial.",[12,2128,2129,2132],{},[29,2130,2131],{},"Carve-in versus carve-out dynamics."," This one matters more than most plans realize. Historically, many states managed BH benefits through separate carve-out contracts with behavioral health managed care organizations (BH-MCOs). As states shift toward carve-in models — where the comprehensive Medicaid MCO is responsible for both medical and BH benefits — small plans that were previously insulated from BH claims complexity are now seeing it land in their core adjudication workflow. As of 2024, states including North Carolina and New Jersey were actively transitioning to or expanding carve-in structures. If your plan recently absorbed a carved-out BH benefit, your claims infrastructure may not be ready for the volume or the coding complexity.",[19,2134,2136],{"id":2135},"why-standard-analytics-miss-bh-cost-drivers","Why Standard Analytics Miss BH Cost Drivers",[12,2138,2139],{},"Even if your claims system adjudicates BH reasonably well, your analytics stack is likely giving you an incomplete picture. Several structural issues combine to create blind spots.",[12,2141,2142,2145],{},[29,2143,2144],{},"Encounter data completeness problems."," BH encounter data in Medicaid managed care has historically had significant completeness gaps. Community mental health centers, solo-practice therapists, and peer support organizations often have weaker EDI infrastructure than medical\u002Fsurgical providers. Claims get submitted on paper, get rejected and not resubmitted, or arrive through clearinghouses with translation errors that result in incomplete records. CMS has flagged BH encounter data quality as a persistent challenge for states. The practical result for a plan: your BH utilization in your analytics platform is probably understated, which means your trend analysis is understated too.",[12,2147,2148,2151],{},[29,2149,2150],{},"Date-of-service lags."," BH providers — particularly smaller outpatient practices — tend to have longer lag times between service delivery and claim submission than medical\u002Fsurgical providers. A busy medical\u002Fsurgical provider might submit within 5–10 days; a solo therapist might submit monthly or quarterly. For a plan trying to monitor BH cost trends in near real-time, this creates a systematic delay. Your November data doesn't reflect November activity — it reflects claims submitted against November dates of service, which won't be complete until January or February. If your analytics don't account for this lag and build in appropriate run-out buffers, your trend lines will look flat right up until they spike.",[12,2153,2154,2157],{},[29,2155,2156],{},"Provider taxonomy gaps."," BH providers span an unusually wide range of taxonomy codes: psychiatrists, psychologists, licensed clinical social workers, marriage and family therapists, peer support specialists, community health workers, substance use disorder counselors, and others. If your provider master data doesn't accurately tag BH provider taxonomy, your analytics can't reliably segment BH spend from general medical spend. You'll see cost increases but won't be able to attribute them correctly. This matters especially when you're trying to isolate which service categories or provider types are driving the trend.",[12,2159,2160,2163],{},[29,2161,2162],{},"Carve-out data gaps."," If any portion of your BH benefit is or was managed under a carve-out arrangement, you may not have complete claims data for that population in your primary data environment. The carved-out entity holds the claims history. When states transition to carve-in models, the data handoff is often incomplete — you inherit a member population whose BH utilization history you can't see. That makes baseline trend analysis and cost modeling significantly harder.",[12,2165,2166,2169],{},[29,2167,2168],{},"Episode-level analysis is nearly impossible without configuration work."," A single BH episode of care might involve outpatient therapy, a prescription, a crisis intervention, and a brief inpatient stay. Each of those is a separate claim, potentially submitted by different providers on different timelines. Standard episode groupers are designed for medical\u002Fsurgical episodes and don't handle BH well. Without BH-specific episode grouping logic, you can't tell whether a high-cost member has one expensive episode or many routine ones — and those require very different responses.",[19,2171,2173],{"id":2172},"what-data-infrastructure-you-actually-need","What Data Infrastructure You Actually Need",[12,2175,2176],{},"Getting visibility into BH cost trends isn't a massive rebuild. It's a set of targeted additions to your existing data environment.",[12,2178,2179,2182],{},[29,2180,2181],{},"BH-specific claims segmentation."," Your data warehouse needs a reliable, maintained logic layer that tags claims as behavioral health based on a combination of diagnosis code, procedure code, provider taxonomy, and place of service. No single field is sufficient on its own. A psychiatric evaluation billed by a psychiatrist at an outpatient office is clearly BH. The same procedure code billed by an internist in a primary care setting may or may not be. Build the segmentation logic, document it, and apply it consistently.",[12,2184,2185,2188],{},[29,2186,2187],{},"Provider taxonomy normalization."," Audit your provider master for BH taxonomy accuracy. NUCC taxonomy codes for BH providers are specific and numerous. Plans that imported provider data from credentialing systems or state directories often have gaps or errors. A provider listed as \"individual practice\" rather than \"licensed clinical social worker\" won't sort correctly into BH analytics.",[12,2190,2191,2194],{},[29,2192,2193],{},"Run-out-adjusted trend monitoring."," Build your BH trend dashboards with explicit run-out assumptions — typically 90 to 180 days for BH, depending on your provider mix. Report incurred-but-not-reported (IBNR) estimates for BH separately from medical\u002Fsurgical, because the lag patterns differ. Without this, you'll systematically misread the trend.",[12,2196,2197,2200],{},[29,2198,2199],{},"Authorization utilization reports."," If your authorization system tracks BH auths separately, build a report that crosses authorizations against paid claims by service type. This tells you which authorized services are being used, which are authorized but not yet billed (a potential future liability), and which claims came in without a matching authorization. All three categories matter for cost management.",[12,2202,2203,2206],{},[29,2204,2205],{},"Carve-out data reconciliation."," If you have any members whose BH history lives outside your primary claims environment, prioritize getting that data into your analytics platform — even if it's in a separate mart. You need it for baseline modeling and for identifying members whose total cost of care is higher than your medical claims alone would suggest.",[19,2208,2210],{"id":2209},"operational-levers-at-the-plan-level","Operational Levers at the Plan Level",[12,2212,2213],{},"Cost trend management in behavioral health is heavily constrained for a plan without clinical staff — you can't set clinical criteria, you can't run utilization management programs, and you shouldn't try to. But there are real operational levers that don't cross into clinical territory.",[12,2215,2216,2219],{},[29,2217,2218],{},"Claims accuracy review."," BH claims have higher denial and reprocessing rates than medical\u002Fsurgical claims in most plans. A regular review of BH claim denial patterns — by denial code, provider type, and service category — often surfaces systematic adjudication errors that are costing the plan money in both directions. Duplicate payments and incorrect rate application are common. Fixing adjudication logic doesn't require any clinical judgment.",[12,2221,2222,2225],{},[29,2223,2224],{},"Authorization-to-claim matching."," Building tighter workflows that match paid BH claims to existing authorizations is a purely administrative function. Claims paid without a matching authorization — or against an authorization for a different service type — are a recoverable cost category for many plans.",[12,2227,2228,2231],{},[29,2229,2230],{},"Encounter data submission quality."," If your BH encounter data submissions to the state are incomplete or inaccurate, you're at regulatory risk and potentially affecting capitation rate calculations. Encounter data completeness audits for BH are a legitimate plan-level operational function, and most plans that do them find significant gaps.",[12,2233,2234,2237],{},[29,2235,2236],{},"Provider billing education."," Small BH providers often have persistent billing errors — wrong place-of-service codes, missing modifier combinations for telehealth, incorrect taxonomy on claims. Targeted outreach and billing guidance to high-volume BH providers isn't utilization management; it's claims accuracy work. It reduces denial rework for both the provider and the plan.",[12,2239,2240,2243],{},[29,2241,2242],{},"Network adequacy monitoring."," If your BH network has capacity gaps, you'll see it in your claims data as members seeking out-of-network care or in non-emergency situations that escalate because routine care was unavailable. Monitoring this is an administrative function, and the data signal is in your claims.",[12,2245,2246],{},"None of these levers require a clinical program. They require clean data, consistent adjudication logic, and someone who is actually looking at the numbers.",[158,2248],{},[12,2250,2251],{},[163,2252,2253,2254,2258,2259,179],{},"If you're building out BH claims monitoring or need help closing gaps in your encounter data and analytics infrastructure, ",[167,2255,2257],{"href":2256},"\u002Fsolutions","Ayin's analytics and encounter data services"," are built for exactly this kind of operational challenge — reach out at ",[167,2260,534],{"href":534},{"title":181,"searchDepth":182,"depth":182,"links":2262},[2263,2265,2266,2267,2268],{"id":2086,"depth":182,"text":2264},"title: \"What Behavioral Health Cost Growth Means for Your Claims and Analytics Infrastructure\"\ndescription: \"Behavioral health is now one of the fastest-growing cost categories in Medicaid managed care — and most small plans lack the claims infrastructure and analytics to see it clearly. Here's what you need to fix that.\"\ndate: 2025-12-09\nauthor: \"Ayin Health Solutions\"\ncategory: \"Technology\"\ntags: \"Behavioral Health\", \"Claims\", \"Analytics\", \"Operations\", \"Data\"\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Healthcare operations and data analytics workspace\"\nfeatured: false",{"id":2098,"depth":182,"text":2099},{"id":2135,"depth":182,"text":2136},{"id":2172,"depth":182,"text":2173},{"id":2209,"depth":182,"text":2210},{},"\u002Farticles\u002Fbehavioral-health-claims-analytics-infrastructure",{"description":181},"articles\u002Fbehavioral-health-claims-analytics-infrastructure","miuK5XNeGbzHemUPNIXC-aLuFRSOMVmsQv7GT90-dss",{"id":2275,"title":2276,"author":2079,"body":2277,"category":2079,"date":2079,"description":181,"extension":192,"featured":193,"image":2079,"imageAlt":2079,"meta":2426,"navigation":197,"path":2427,"seo":2428,"stem":2429,"tags":2079,"__hash__":2430},"articles\u002Farticles\u002Fclaims-processing-accuracy-guide.md","Claims Processing Accuracy Guide",{"type":9,"value":2278,"toc":2414},[2279,2281,2289,2292,2296,2299,2302,2308,2314,2320,2324,2327,2331,2334,2340,2344,2347,2352,2356,2359,2364,2368,2371,2391,2395,2398,2401,2403],[158,2280],{},[19,2282,2284,2285,2288],{"id":2283},"title-the-claims-accuracy-imperative-how-processing-errors-undermine-value-based-caredescription-claims-processing-errors-dont-just-create-administrative-headachesthey-corrupt-the-data-foundation-that-value-based-care-depends-on-heres-how-to-identify-and-address-the-most-costly-error-patternsdate-2025-04-03author-ayin-health-solutionscategory-operationstags-claims-operations-data-quality-health-plansimage-photographyayin_still_7pngimagealt-healthcare-administrator-reviewing-claims-datafeatured-false","title: \"The Claims Accuracy Imperative: How Processing Errors Undermine Value-Based Care\"\ndescription: \"Claims processing errors don't just create administrative headaches—they corrupt the data foundation that value-based care depends on. Here's how to identify and address the most costly error patterns.\"\ndate: 2025-04-03\nauthor: \"Ayin Health Solutions\"\ncategory: \"Operations\"\ntags: ",[2089,2286,2287],{},"\"Claims\", \"Operations\", \"Data Quality\", \"Health Plans\"","\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Healthcare administrator reviewing claims data\"\nfeatured: false",[12,2290,2291],{},"At 10 million claims processed annually, we've developed a precise view of where claims errors originate, how they propagate, and what they ultimately cost plans. The short answer: more than most finance teams realize, and in ways that extend far beyond direct payment errors.",[19,2293,2295],{"id":2294},"the-hidden-costs-of-claims-inaccuracy","The Hidden Costs of Claims Inaccuracy",[12,2297,2298],{},"Most plans track claims accuracy as a percentage of clean claims on first submission. That's a useful metric, but it understates the total cost because it only captures direct rework.",[12,2300,2301],{},"The downstream effects are harder to see:",[12,2303,2304,2307],{},[29,2305,2306],{},"Quality measure distortion."," If a diabetes management visit is coded incorrectly and the claim denies, that member appears to have a gap in care. Your HEDIS numerator takes a hit—not because the care didn't happen, but because the claim didn't process correctly.",[12,2309,2310,2313],{},[29,2311,2312],{},"Risk score erosion."," In managed care, your risk-adjusted revenue depends on accurate diagnosis capture. Claims that don't close out correctly can suppress HCC (Hierarchical Condition Category) codes, leading to underpayment that has nothing to do with actual member risk.",[12,2315,2316,2319],{},[29,2317,2318],{},"Care management blind spots."," When care managers rely on claims as a proxy for recent utilization (a common workflow), missing or incorrect claims mean they may not know a member was recently hospitalized, or that a specialist visit occurred.",[19,2321,2323],{"id":2322},"the-three-most-common-error-sources","The Three Most Common Error Sources",[12,2325,2326],{},"After processing claims across dozens of plan implementations, these are the patterns we see most consistently:",[1113,2328,2330],{"id":2329},"provider-credentialing-mismatches","Provider Credentialing Mismatches",[12,2332,2333],{},"Claims that arrive with a billing NPI that doesn't match the provider's credentialing status in the plan's system will either suspend or deny—often with a generic error code that gives the provider no useful information. The root cause is usually a lag between when a provider is credentialed and when that status is updated in the claims system.",[12,2335,2336,2339],{},[29,2337,2338],{},"The fix:"," Real-time credentialing status feeds between your provider management system and your claims adjudication engine. The data exists; the integration is the work.",[1113,2341,2343],{"id":2342},"eligibility-at-date-of-service-errors","Eligibility at Date of Service Errors",[12,2345,2346],{},"This is the most avoidable error category. A member who was eligible on the date of service should never receive a denial due to eligibility—but it happens when eligibility files aren't reconciled in time for the adjudication cycle to pick up the current status.",[12,2348,2349,2351],{},[29,2350,2338],{}," Eligibility reconciliation that runs continuously, not on batch cycles. For Medicaid populations with high churn, this is particularly important.",[1113,2353,2355],{"id":2354},"coordination-of-benefits-cob-failures","Coordination of Benefits (COB) Failures",[12,2357,2358],{},"For dual-eligible members (Medicare and Medicaid), COB logic is complex enough that many plans handle it manually for exception cases. Manual handling means volume limits, turnaround time variability, and inconsistent outcomes.",[12,2360,2361,2363],{},[29,2362,2338],{}," Automated COB logic with clear exception escalation paths. Manual review should be the exception, not the default.",[19,2365,2367],{"id":2366},"what-accuracy-looks-like-in-practice","What Accuracy Looks Like in Practice",[12,2369,2370],{},"Plans that are performing well on claims accuracy tend to share a few characteristics:",[601,2372,2373,2379,2385],{},[604,2374,2375,2378],{},[29,2376,2377],{},"Edit libraries that are regularly updated."," CMS, AMA, and state Medicaid programs release code updates continuously. Plans whose edit logic is 6–12 months behind are systematically generating errors on current-year codes.",[604,2380,2381,2384],{},[29,2382,2383],{},"Provider-facing portals that explain denials clearly."," When providers can self-service status checks and understand denial reasons, resubmission turnaround drops significantly.",[604,2386,2387,2390],{},[29,2388,2389],{},"Claims analytics that flag unusual patterns proactively."," A sudden spike in denials for a specific provider or service type is a signal that something has changed upstream—and it's better to catch it at 50 claims than 5,000.",[19,2392,2394],{"id":2393},"the-data-quality-foundation","The Data Quality Foundation",[12,2396,2397],{},"The reason we spend so much time on claims accuracy isn't operational efficiency alone—it's that every analytics and care management capability a plan has is built on top of claims data. If that foundation is unreliable, the insights built on top of it are unreliable too.",[12,2399,2400],{},"For plans operating in value-based care contracts, where quality measure performance directly affects revenue, the stakes are high. Getting claims accuracy right is the infrastructure investment that makes everything else work.",[158,2402],{},[12,2404,2405],{},[163,2406,2407,2408,173,2411,179],{},"Ayin's claims administration team processes over 10 million claims annually for Medicaid, Medicare Advantage, and PACE programs. ",[167,2409,2410],{"href":2256},"Learn more about our claims services",[167,2412,2413],{"href":534},"connect with our team",{"title":181,"searchDepth":182,"depth":182,"links":2415},[2416,2418,2419,2424,2425],{"id":2283,"depth":182,"text":2417},"title: \"The Claims Accuracy Imperative: How Processing Errors Undermine Value-Based Care\"\ndescription: \"Claims processing errors don't just create administrative headaches—they corrupt the data foundation that value-based care depends on. Here's how to identify and address the most costly error patterns.\"\ndate: 2025-04-03\nauthor: \"Ayin Health Solutions\"\ncategory: \"Operations\"\ntags: \"Claims\", \"Operations\", \"Data Quality\", \"Health Plans\"\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Healthcare administrator reviewing claims data\"\nfeatured: false",{"id":2294,"depth":182,"text":2295},{"id":2322,"depth":182,"text":2323,"children":2420},[2421,2422,2423],{"id":2329,"depth":1272,"text":2330},{"id":2342,"depth":1272,"text":2343},{"id":2354,"depth":1272,"text":2355},{"id":2366,"depth":182,"text":2367},{"id":2393,"depth":182,"text":2394},{},"\u002Farticles\u002Fclaims-processing-accuracy-guide",{"description":181},"articles\u002Fclaims-processing-accuracy-guide","sVh1g9jOnD8TklO2DvARRKxPqbNRnKx7gt2YLpF_gPI",{"id":2432,"title":2433,"author":2079,"body":2434,"category":2079,"date":2079,"description":181,"extension":192,"featured":193,"image":2079,"imageAlt":2079,"meta":2582,"navigation":197,"path":2583,"seo":2584,"stem":2585,"tags":2079,"__hash__":2586},"articles\u002Farticles\u002Fcredentialing-lag-claims-adjudication.md","Credentialing Lag Claims Adjudication",{"type":9,"value":2435,"toc":2573},[2436,2438,2446,2449,2452,2456,2459,2462,2465,2468,2472,2475,2478,2481,2484,2487,2491,2494,2497,2500,2506,2512,2518,2521,2525,2528,2531,2534,2537,2540,2544,2547,2550,2553,2556,2559,2561],[158,2437],{},[19,2439,2441,2442,2445],{"id":2440},"title-the-hidden-cost-of-credentialing-lag-in-claims-adjudicationdescription-when-credentialing-decisions-dont-reach-the-claims-system-in-time-clean-claims-deny-this-article-explains-the-data-flow-gap-the-downstream-cost-cascade-and-what-a-real-fix-requires-at-the-system-leveldate-2025-09-16author-ayin-health-solutionscategory-operationstags-claims-provider-credentialing-operations-data-quality-denialsimage-photographyayin_still_7pngimagealt-back-office-operations-team-reviewing-claims-datafeatured-false","title: \"The Hidden Cost of Credentialing Lag in Claims Adjudication\"\ndescription: \"When credentialing decisions don't reach the claims system in time, clean claims deny. This article explains the data flow gap, the downstream cost cascade, and what a real fix requires at the system level.\"\ndate: 2025-09-16\nauthor: \"Ayin Health Solutions\"\ncategory: \"Operations\"\ntags: ",[2089,2443,2444],{},"\"Claims\", \"Provider Credentialing\", \"Operations\", \"Data Quality\", \"Denials\"","\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Back-office operations team reviewing claims data\"\nfeatured: false",[12,2447,2448],{},"A provider gets credentialed. The credentialing committee approves, the contract is executed, and the provider starts seeing members. Three weeks later, claims start denying. The billing NPI doesn't match an active, credentialed provider in the claims system. The provider calls your network relations team. Someone opens a ticket. Someone else manually updates a record. The claim gets resubmitted. The whole sequence — start to finish — takes four to six weeks and costs your plan somewhere between $118 and $181 per reworked claim. Multiply that by the number of providers you onboard or re-credential in a given quarter, and you're looking at a recurring, avoidable operational tax that most plans have simply learned to absorb.",[12,2450,2451],{},"The problem isn't that credentialing is slow. It's that credentialing and claims adjudication operate as disconnected systems — and the gap between them is where money disappears.",[19,2453,2455],{"id":2454},"where-the-data-flow-breaks-down","Where the Data Flow Breaks Down",[12,2457,2458],{},"Credentialing at a health plan involves a specific sequence: application receipt, primary source verification, committee review, approval, and contract execution. At the end of that sequence, a provider is approved to bill your plan. But that approval doesn't automatically propagate to your claims adjudication system. It has to get there through a separate data update.",[12,2460,2461],{},"In most small-to-midsized plans, that update happens one of three ways: a manual entry by a credentialing or network ops staff member, a batch file export from the credentialing system that loads into the claims platform on a scheduled basis (often nightly or weekly), or a semi-automated workflow that requires someone to trigger the update. All three introduce lag. Manual entry depends on staffing bandwidth and accuracy. Batch processing introduces a time window — a provider approved Thursday afternoon may not be active in the claims system until the following Monday's batch. Semi-automated workflows depend on no one skipping the step.",[12,2463,2464],{},"The NPI is the bridge between these two systems. The billing NPI on a claim has to match an active, credentialed record in the adjudication system. When it doesn't — because the update hasn't been made yet, because the wrong NPI type was entered (Type 1 individual vs. Type 2 organizational), or because a re-credentialing update closed a record that should have stayed open — the claim denies. A 2024 MGMA report found that 62% of claim denials were linked to provider identification errors, with NPIs among the most common culprits.",[12,2466,2467],{},"The lag window is the core problem. It can be as short as 24 hours or as long as several weeks depending on your update cadence and staffing. During that window, every claim the provider submits is at risk.",[19,2469,2471],{"id":2470},"the-downstream-cascade","The Downstream Cascade",[12,2473,2474],{},"A credentialing-lag denial isn't a single event. It's the start of a cascade.",[12,2476,2477],{},"The immediate effect is the denial itself and the rework it creates. The average administrative cost to rework a denied claim is $118. Healthcare organizations that haven't addressed this problem systematically report losing more than $500,000 annually to credentialing-related denials — and that figure covers more than 20% of organizations surveyed in a Plutus Health analysis. Hospitals collectively spend nearly $20 billion annually fighting denied claims across all categories; credentialing errors are a consistent, preventable slice of that total.",[12,2479,2480],{},"Beyond the direct rework cost, there's provider dissatisfaction. When a newly onboarded provider's first experience with your plan is a wave of denials and delayed payment, your network relations team spends time managing fallout instead of managing relationships. For smaller plans operating lean network ops functions, that's a real capacity drain.",[12,2482,2483],{},"There are also downstream data errors. A claim that denies and gets resubmitted — or adjusted — creates duplicate records, split payment trails, and encounter data that requires reconciliation. For Medicaid managed care plans, encounter data accuracy is a compliance requirement. Credentialing-lag denials that generate corrected claims and resubmissions introduce noise into encounter submissions. If those submissions hit CMS with errors or gaps, you're managing a data quality problem that started as a workflow timing issue.",[12,2485,2486],{},"Risk adjustment is the less-obvious exposure. If providers billing under specific specialties — behavioral health, complex chronic care, specific procedure categories — are delayed in the claims system, the associated diagnoses and services don't flow into your risk score calculations in time. For Medicare Advantage and PACE plans, that can affect premium revenue. For Medicaid plans moving toward value-based arrangements, incomplete encounter data distorts the picture.",[19,2488,2490],{"id":2489},"what-real-time-integration-actually-requires","What Real-Time Integration Actually Requires",[12,2492,2493],{},"\"Real-time credentialing integration\" sounds like a large technology project. For some plans, it is. But the core requirement is more specific than it sounds.",[12,2495,2496],{},"The goal is reducing the lag between a credentialing approval event and an active, accurate record in the claims adjudication system. You don't need to replace your credentialing platform to do this. What you need is a reliable, low-latency data pathway between the two systems.",[12,2498,2499],{},"In practice, this usually means one of three things:",[12,2501,2502,2505],{},[29,2503,2504],{},"API-based event triggers."," When the credentialing system marks a provider as approved, it fires an event that updates the claims system directly. No batch window, no manual step. This requires that both systems support the integration and that someone has built and maintains the connection. Most modern credentialing platforms and claims systems support API connectivity. The gap is usually the integration build and ongoing maintenance.",[12,2507,2508,2511],{},[29,2509,2510],{},"Shortened batch cycles with validation."," If real-time API integration isn't feasible, moving from weekly batch updates to nightly — and adding validation logic that flags mismatches before they hit adjudication — reduces the exposure window significantly. This is achievable without a new platform. It requires process redesign and testing, but not a system replacement.",[12,2513,2514,2517],{},[29,2515,2516],{},"Workflow checkpoints before claims go live."," For providers newly added to your network, a pre-activation hold that verifies the billing NPI is active in the claims system before the provider starts submitting can catch the gap before it becomes a denial. This is a workflow control, not a technology one. It requires coordination between credentialing, network ops, and claims — and a shared checklist that gets completed before the provider is \"live.\"",[12,2519,2520],{},"The 73% of healthcare organizations still running credentialing on legacy systems — spreadsheets, shared drives, email-based approvals — face a harder path to integration. The fix in those cases often involves credentialing platform modernization alongside claims integration work. But even in those environments, manual verification checkpoints and shortened batch cycles can reduce lag substantially while a longer-term platform decision gets made.",[19,2522,2524],{"id":2523},"the-cost-math","The Cost Math",[12,2526,2527],{},"The question plans ask is whether integration investment is worth it. The math is straightforward.",[12,2529,2530],{},"If your plan credentials 80 providers per year — a reasonable figure for a 50,000-member Medicaid managed care organization with active network growth — and even 15% of those onboardings produce a credentialing-lag denial event, that's 12 provider-level denial clusters annually. Each cluster typically involves multiple claims across the lag window. If each cluster generates an average of 10 denied claims requiring rework, you're at 120 reworked claims per year at $118 each. That's roughly $14,000 in direct rework cost.",[12,2532,2533],{},"Add the staff time for network relations calls, manual system updates, resubmission tracking, and encounter data reconciliation, and the real cost is substantially higher. Plans that have measured this fully typically report total operational costs — including staff time — running 3x to 5x the direct rework cost per claim.",[12,2535,2536],{},"The integration investment to close this gap — whether through API development, batch process optimization, or workflow redesign — typically runs $15,000 to $60,000 depending on system complexity and scope. For most plans, the breakeven is under two years. For plans with higher provider turnover or faster network growth, it's often within the first year.",[12,2538,2539],{},"The more important math is what's not counted in the rework figure: provider dissatisfaction, encounter data errors, risk score gaps, and the staff capacity consumed by manual exception handling instead of higher-value work.",[19,2541,2543],{"id":2542},"what-the-fix-looks-like-in-practice","What the Fix Looks Like in Practice",[12,2545,2546],{},"The fix doesn't require ripping out your credentialing system or claims platform. It requires treating the credentialing-to-claims data pathway as an integration problem rather than a workflow afterthought.",[12,2548,2549],{},"That means auditing the current lag: how long, on average, between a credentialing approval and an active record in the claims system. For most plans, no one has measured this. The audit itself surfaces the problem in terms that justify the investment.",[12,2551,2552],{},"It means mapping where the update fails or gets delayed — is it a batch timing issue, a manual step with no accountability, or a data translation problem between systems? Each root cause has a different fix.",[12,2554,2555],{},"And it means building a monitoring layer: a regular review of denials coded to provider identification or credentialing status, so that lag events are visible as a metric rather than invisible as individual tickets.",[12,2557,2558],{},"For plans that don't have the internal capacity to build and maintain this integration, the alternative is a partner who already has the plumbing — claims administration infrastructure that keeps credentialing data and claims adjudication logic synchronized without requiring your ops team to manage the connection.",[158,2560],{},[12,2562,2563],{},[163,2564,2565,2566,2569,2570,2572],{},"If credentialing-lag denials are a recurring issue for your plan, Ayin's ",[167,2567,2568],{"href":2256},"claims administration services"," include integrated provider data management designed to close the gap between credentialing decisions and adjudication accuracy — ",[167,2571,935],{"href":534}," to talk through what that looks like for your program.",{"title":181,"searchDepth":182,"depth":182,"links":2574},[2575,2577,2578,2579,2580,2581],{"id":2440,"depth":182,"text":2576},"title: \"The Hidden Cost of Credentialing Lag in Claims Adjudication\"\ndescription: \"When credentialing decisions don't reach the claims system in time, clean claims deny. This article explains the data flow gap, the downstream cost cascade, and what a real fix requires at the system level.\"\ndate: 2025-09-16\nauthor: \"Ayin Health Solutions\"\ncategory: \"Operations\"\ntags: \"Claims\", \"Provider Credentialing\", \"Operations\", \"Data Quality\", \"Denials\"\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Back-office operations team reviewing claims data\"\nfeatured: false",{"id":2454,"depth":182,"text":2455},{"id":2470,"depth":182,"text":2471},{"id":2489,"depth":182,"text":2490},{"id":2523,"depth":182,"text":2524},{"id":2542,"depth":182,"text":2543},{},"\u002Farticles\u002Fcredentialing-lag-claims-adjudication",{"description":181},"articles\u002Fcredentialing-lag-claims-adjudication","6OtJpQY9TN9g417txKYdPiKJlOL-y6oDAWcZ8qqoWOo",{"id":2588,"title":2589,"author":2079,"body":2590,"category":2079,"date":2079,"description":181,"extension":192,"featured":193,"image":2079,"imageAlt":2079,"meta":2736,"navigation":197,"path":2737,"seo":2738,"stem":2739,"tags":2079,"__hash__":2740},"articles\u002Farticles\u002Fcustomer-service-quality-metric.md","Customer Service Quality Metric",{"type":9,"value":2591,"toc":2728},[2592,2594,2602,2605,2608,2612,2615,2621,2627,2633,2639,2645,2649,2652,2655,2661,2667,2673,2679,2683,2686,2691,2696,2701,2705,2708,2711,2714,2716],[158,2593],{},[19,2595,2597,2598,2601],{"id":2596},"title-customer-service-as-a-quality-metric-what-your-call-volume-is-telling-youdescription-member-services-call-data-is-one-of-the-best-leading-indicators-of-upstream-operational-failures-enrollment-errors-claims-denials-network-gaps-pharmacy-issues-heres-how-to-read-itdate-2025-11-18author-ayin-health-solutionscategory-operationstags-customer-service-member-experience-quality-operations-analyticsimage-photographyayin_still_7pngimagealt-health-plan-operations-team-reviewing-member-services-datafeatured-false","title: \"Customer Service as a Quality Metric: What Your Call Volume Is Telling You\"\ndescription: \"Member services call data is one of the best leading indicators of upstream operational failures — enrollment errors, claims denials, network gaps, pharmacy issues. Here's how to read it.\"\ndate: 2025-11-18\nauthor: \"Ayin Health Solutions\"\ncategory: \"Operations\"\ntags: ",[2089,2599,2600],{},"\"Customer Service\", \"Member Experience\", \"Quality\", \"Operations\", \"Analytics\"","\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Health plan operations team reviewing member services data\"\nfeatured: false",[12,2603,2604],{},"Your member services call volume is not a staffing problem. It is a diagnostic tool — and most plans are not using it that way. Every spike in call volume, every recurring call reason, every call that ends without resolution is a signal from inside your operations. The question is whether anyone is listening.",[12,2606,2607],{},"Most health plans treat their call center as a cost center to be minimized: shorter handle times, faster wrap-up, lower headcount per thousand members. That framing is not wrong, exactly, but it misses the larger point. The calls coming in are a continuous, real-time audit of your enrollment accuracy, your claims adjudication logic, your network adequacy, and your pharmacy benefit management. When those systems break down, members call. They always do. The call center picks up the cost — and the signal — that the upstream failure generated.",[19,2609,2611],{"id":2610},"what-your-most-common-call-reasons-are-actually-telling-you","What Your Most Common Call Reasons Are Actually Telling You",[12,2613,2614],{},"Call reason categorization is the most underused analytical tool in a plan's member services operation. When you look past the surface-level category and ask what the call actually represents, a different picture emerges.",[12,2616,2617,2620],{},[29,2618,2619],{},"\"I can't find a doctor in my network.\""," This is not a call about provider directories. It is a signal about network adequacy — and often about network data quality. If members are calling because their primary care physician isn't showing as in-network, the first question is whether the directory is wrong, the credentialing is stale, or the member's enrollment is on the wrong product. All three are common. A spike in these calls after an open enrollment period almost always traces back to auto-assignment logic or plan-of-record errors in the enrollment file.",[12,2622,2623,2626],{},[29,2624,2625],{},"\"My claim was denied.\""," Claims denial calls are the most expensive calls in your queue — high handle time, high escalation rate, and often a second or third call to follow up. But denial calls are also precise operational intelligence. When you break down denial reasons at the call level, you find patterns: a specific provider billing under the wrong NPI, an authorization workflow that isn't capturing the right codes, a coordination-of-benefits logic error for members with dual coverage. One call is noise. Fifty calls in the same category over four weeks is a process failure.",[12,2628,2629,2632],{},[29,2630,2631],{},"\"My prescription isn't covered.\""," Pharmacy calls spike predictably at formulary change dates, at the start of a new plan year, and when a prior authorization workflow breaks down. They also spike when a member has been re-enrolled on a different plan variant after a redetermination — and the new formulary didn't follow them. That second pattern is a pure enrollment data problem wearing pharmacy clothes. Plans that don't connect their pharmacy call volume to their enrollment reconciliation records will spend months managing the symptom without addressing the cause.",[12,2634,2635,2638],{},[29,2636,2637],{},"\"I just enrolled and my coverage isn't showing.\""," Enrollment confirmation calls are a leading indicator — they arrive before problems become claims. A member calling on day three of coverage because their pharmacy can't verify eligibility is telling you that your enrollment transaction to your pharmacy benefits manager didn't transmit, or transmitted with an error, or transmitted correctly but the effective date logic is wrong. That member will generate a second call when the claim rejects. Fix it now and you prevent three more touch points downstream.",[12,2640,2641,2644],{},[29,2642,2643],{},"\"I got a bill for something that should be covered.\""," These calls are the tail end of a claims adjudication failure, often with weeks of lag between the original service and the member contact. By the time a member calls about an unexpected bill, the claim has already been processed, the provider has already billed, and the member has already lost confidence in the plan. These calls are late-arriving evidence of problems that happened weeks earlier.",[19,2646,2648],{"id":2647},"call-data-as-an-early-warning-system","Call Data as an Early-Warning System",[12,2650,2651],{},"The operational value of member services data is highest when you use it prospectively rather than retrospectively. That requires treating call volume trends the way you treat any other operational metric — with thresholds, trend lines, and assigned ownership.",[12,2653,2654],{},"A few specific applications that work in practice:",[12,2656,2657,2660],{},[29,2658,2659],{},"Volume spikes by call reason, not just overall volume."," Total call volume tells you when something is wrong. Call reason breakdowns tell you what is wrong. If your overall volume is flat but pharmacy calls are up 40% in a two-week window, that is an actionable signal. Build reporting that surfaces call reason trends on a weekly basis, not monthly.",[12,2662,2663,2666],{},[29,2664,2665],{},"Abandon rate as a stress indicator."," CMS holds Medicare Advantage and Part D plans to an abandonment rate threshold of under 5% and average hold times under two minutes for their call center monitoring standards. When abandonment rate climbs above that threshold, it usually means call volume spiked faster than staffing could absorb — which means something upstream broke. Abandonment rate spikes and call reason spikes together tell you what broke and how badly.",[12,2668,2669,2672],{},[29,2670,2671],{},"First-call resolution by issue category."," Low first-call resolution on a specific issue category is a workflow problem, not a staffing problem. If your CSRs cannot resolve pharmacy coverage questions on first contact, the issue is usually that they don't have access to real-time eligibility and formulary data in the same screen. That is a technology and integration problem. Fixing it reduces handle time, reduces repeat contacts, and improves the member experience simultaneously.",[12,2674,2675,2678],{},[29,2676,2677],{},"Enrollment-period call monitoring."," In the weeks immediately following open enrollment, auto-assignment changes, or a Medicaid redetermination cycle, your call center data becomes your most accurate real-time view of enrollment accuracy. Plans that don't actively monitor call reason trends during these windows routinely discover enrollment errors at claims adjudication — weeks later, at much higher cost to resolve.",[19,2680,2682],{"id":2681},"what-good-looks-like-by-population","What Good Looks Like — By Population",[12,2684,2685],{},"Member services benchmarks are not one-size-fits-all. The appropriate targets differ meaningfully across Medicaid, Medicare Advantage, and PACE.",[12,2687,2688,2690],{},[29,2689,551],{}," populations generate structurally higher call volume than commercial or Medicare populations. Medicaid members are more likely to have unstable housing, limited health literacy, and no prior experience navigating managed care. They call more frequently, require longer handle times, and are more likely to need non-clinical assistance — transportation, eligibility confirmation, understanding their benefits. For Medicaid plans, call volume per thousand members is less useful as a benchmark than call reason distribution and first-call resolution rate. A plan doing Medicaid well is not necessarily one with the lowest call volume — it is one where calls are resolved on first contact and escalations are rare.",[12,2692,2693,2695],{},[29,2694,402],{}," populations generate lower raw call volume but are more sensitive to service quality. MA CAHPS surveys ask directly about plan customer service — whether the plan's customer service gave members the information they needed, and whether staff were helpful and treated them with courtesy. These survey responses feed directly into Star Ratings. CMS has historically weighted CAHPS member experience measures at 4x in the Star Rating calculation (reduced to 2x for 2026 Stars), meaning a low customer service score creates a disproportionate impact on a plan's overall rating. For MA plans, the operational discipline is ensuring that member service quality is consistent enough to show up positively when the survey arrives — which means the daily work of the call center is effectively Star Rating work.",[12,2697,2698,2700],{},[29,2699,2073],{}," programs serve a frail elderly population with complex, multi-service needs. Call patterns in PACE look very different from Medicaid or MA — members or their caregivers are calling about care coordination, transportation to the day center, medication changes, and after-hours urgency. Call volume per participant is lower, but the stakes per call are higher. PACE organizations should monitor their member services data primarily for care coordination gaps — calls that signal a participant is falling through the handoffs between medical, social, and transportation services.",[19,2702,2704],{"id":2703},"the-cahps-connection","The CAHPS Connection",[12,2706,2707],{},"CAHPS surveys do not ask members about their claims adjudication accuracy. They ask about their experience — whether they got the information they needed, whether the plan was easy to deal with, whether their care was coordinated. But those experiential outcomes are downstream of operational performance. A member whose claim was denied incorrectly and then corrected after a 30-minute call does not rate the plan's customer service highly in a survey taken three months later. The CAHPS score is the lag indicator. The call data is the leading indicator.",[12,2709,2710],{},"Plans that achieve strong CAHPS customer service scores are not doing anything magical. They are running clean enrollment operations so members' coverage is right from day one. They are adjudicating claims accurately so members are not calling to dispute incorrect bills. They are maintaining network data quality so members can find care without calling first. Member services performance, in the end, is a summary score for the entire back-office operation. If your CSRs are busy, your upstream systems are failing somewhere.",[12,2712,2713],{},"The practical implication is straightforward: the plan that reviews its call reason trends weekly, connects those trends to specific upstream systems, and assigns operational owners to resolve the underlying issues will see its CAHPS scores improve — not because it changed its survey strategy, but because it fixed the problems that were generating calls in the first place.",[158,2715],{},[12,2717,2718],{},[163,2719,2720,2721,2724,2725,2727],{},"If you want help building the operational infrastructure to turn your member services data into an early-warning system, ",[167,2722,2723],{"href":2256},"Ayin's customer service and operations teams"," work alongside plan administrators to connect call data to enrollment, claims, and analytics workflows — or ",[167,2726,178],{"href":534}," to talk through your current gaps.",{"title":181,"searchDepth":182,"depth":182,"links":2729},[2730,2732,2733,2734,2735],{"id":2596,"depth":182,"text":2731},"title: \"Customer Service as a Quality Metric: What Your Call Volume Is Telling You\"\ndescription: \"Member services call data is one of the best leading indicators of upstream operational failures — enrollment errors, claims denials, network gaps, pharmacy issues. Here's how to read it.\"\ndate: 2025-11-18\nauthor: \"Ayin Health Solutions\"\ncategory: \"Operations\"\ntags: \"Customer Service\", \"Member Experience\", \"Quality\", \"Operations\", \"Analytics\"\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Health plan operations team reviewing member services data\"\nfeatured: false",{"id":2610,"depth":182,"text":2611},{"id":2647,"depth":182,"text":2648},{"id":2681,"depth":182,"text":2682},{"id":2703,"depth":182,"text":2704},{},"\u002Farticles\u002Fcustomer-service-quality-metric",{"description":181},"articles\u002Fcustomer-service-quality-metric","kdPqA4R0_krcUTs7RSMO7KEKl59qneghlriW4RXIxy4",{"id":2742,"title":2743,"author":2079,"body":2744,"category":2079,"date":2079,"description":181,"extension":192,"featured":193,"image":2079,"imageAlt":2079,"meta":2925,"navigation":197,"path":2926,"seo":2927,"stem":2928,"tags":2079,"__hash__":2929},"articles\u002Farticles\u002Fmedicaid-enrollment-management-clean-data.md","Medicaid Enrollment Management Clean Data",{"type":9,"value":2745,"toc":2916},[2746,2748,2756,2759,2763,2766,2769,2772,2775,2779,2782,2788,2794,2800,2806,2809,2813,2816,2819,2822,2825,2828,2832,2835,2841,2847,2853,2859,2865,2869,2872,2898,2901,2903],[158,2747],{},[19,2749,2751,2752,2755],{"id":2750},"title-enrollment-management-for-high-churn-medicaid-populations-what-clean-data-actually-requiresdescription-medicaid-populations-churn-faster-than-any-other-market-plans-that-treat-enrollment-as-a-solved-problem-are-carrying-phantom-members-generating-incorrect-claims-and-creating-risk-score-errors-heres-what-a-truly-clean-enrollment-operation-requiresdate-2026-01-06author-ayin-health-solutionscategory-operationstags-enrollment-medicaid-data-quality-eligibility-operationsimage-photographyayin_still_7pngimagealt-operations-team-reviewing-enrollment-datafeatured-false","title: \"Enrollment Management for High-Churn Medicaid Populations: What Clean Data Actually Requires\"\ndescription: \"Medicaid populations churn faster than any other market. Plans that treat enrollment as a solved problem are carrying phantom members, generating incorrect claims, and creating risk score errors. Here's what a truly clean enrollment operation requires.\"\ndate: 2026-01-06\nauthor: \"Ayin Health Solutions\"\ncategory: \"Operations\"\ntags: ",[2089,2753,2754],{},"\"Enrollment\", \"Medicaid\", \"Data Quality\", \"Eligibility\", \"Operations\"","\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Operations team reviewing enrollment data\"\nfeatured: false",[12,2757,2758],{},"A member disenrolls in March. The state transmits the termination file. Your enrollment system processes it — eventually. In the meantime, a claim comes in for that member dated March 15th. Your system adjudicates it against an active record because the termination hasn't posted yet. The claim pays. Six weeks later you find the discrepancy during a reconciliation run. Now you're chasing a recovery, correcting your encounter data submission, and explaining the gap to your finance team. That sequence — in some variation — plays out dozens of times a month in plans that haven't built their enrollment operation around the reality of Medicaid churn. It's not an edge case. It's the baseline condition of running Medicaid.",[19,2760,2762],{"id":2761},"the-churn-reality-is-structural-not-incidental","The Churn Reality Is Structural, Not Incidental",[12,2764,2765],{},"Medicaid churn is different from anything you'll find in commercial or Medicare Advantage enrollment. In commercial markets, members change plans at open enrollment, maybe once a year. In Medicare Advantage, the annual election period drives most activity with a predictable calendar. In Medicaid, eligibility changes continuously — and for reasons that have nothing to do with member choice.",[12,2767,2768],{},"Income fluctuates. A member picks up a second job for two months and crosses the FPL threshold. A life event creates a household change. A renewal notice gets sent to an address that's six months stale. The state system processes the termination. Three months later, circumstances change again and the member re-enrolls. According to KFF analysis, approximately 10.3% of full-benefit Medicaid enrollees experience a coverage gap of less than one year — and about 4.2% re-enroll within just three months of disenrolling. Among adults specifically, the rate climbs to 12.1%.",[12,2770,2771],{},"These aren't members leaving and coming back by choice. They're cycling through administrative processes driven by income volatility, procedural barriers, and enrollment system timing. Research on the 2023–2024 Medicaid unwinding reinforced this at scale: of the roughly 25 million people disenrolled when pandemic-era continuous enrollment ended, nearly seven in ten lost coverage for procedural reasons — outdated contact information, missed notices, incomplete paperwork — not because they were ineligible.",[12,2773,2774],{},"State variation makes it worse. Churn rates across states range from under 5% in states like Hawaii and North Carolina to over 15% in Texas, Wisconsin, and Pennsylvania. If you operate across multiple states, you're managing multiple churn regimes simultaneously, each with different redetermination schedules, file formats, and timing windows.",[19,2776,2778],{"id":2777},"the-phantom-member-problem","The Phantom Member Problem",[12,2780,2781],{},"\"Phantom member\" is operational shorthand for an enrollee who appears active in your system but shouldn't be — because a termination was delayed, a disenrollment file wasn't processed, or a reconciliation gap let an outdated record persist. They're invisible from the outside but they're causing damage in several specific places.",[12,2783,2784,2787],{},[29,2785,2786],{},"Claims adjudication."," An active enrollment record is what authorizes a claim to pay. If a termination hasn't posted, a claim for a disenrolled member will clear adjudication. You pay. The member wasn't enrolled. Now you have a liability, a potential recovery situation, and an audit flag.",[12,2789,2790,2793],{},[29,2791,2792],{},"Encounter data submissions."," You're required to submit encounter data to the state reflecting actual services delivered to enrolled members. A phantom member inflates your denominator, distorts utilization patterns, and creates discrepancies that regulators notice. Encounter data accuracy reviews are getting more rigorous, not less — and enrollment errors are one of the most common root causes of submission failures.",[12,2795,2796,2799],{},[29,2797,2798],{},"Risk score calculations."," In managed Medicaid with risk-adjusted rates, your member roster directly affects your risk profile. Phantom members can skew acuity calculations. Conversely, members who churn off your roster but whose historical claims data was used in risk stratification create analytic noise that misleads population health reporting.",[12,2801,2802,2805],{},[29,2803,2804],{},"Member-level analytics."," If you're running any care management or quality reporting, phantom members corrupt your denominators. You can't measure gaps in care for a member who isn't enrolled. You can't attribute outcomes correctly when the roster doesn't match reality.",[12,2807,2808],{},"The cost compounds. A phantom member who generates a single improperly paid claim may cost $300 to $3,000 to identify, recover, and correct in your data systems. Multiply that by the frequency of the underlying enrollment errors, and you're looking at a material operational loss that never shows up as a line item — it's just absorbed as friction.",[19,2810,2812],{"id":2811},"why-batch-reconciliation-isnt-enough","Why Batch Reconciliation Isn't Enough",[12,2814,2815],{},"Most plans run monthly or weekly enrollment reconciliation. You get the state file, compare it to your internal roster, post differences. This is the standard. It's also insufficient for a population that moves as fast as Medicaid.",[12,2817,2818],{},"The gap between state file transmission and your system update is where errors accumulate. If the state sends a termination file on the first of the month and you process it on the tenth, you have a nine-day window where your roster is wrong. A busy practice seeing Medicaid members several times a week will generate claims in that window. They adjudicate against bad data.",[12,2820,2821],{},"Continuous eligibility reconciliation closes that gap. Instead of waiting for a monthly batch, you're checking eligibility in real time — or as close to real time as the state's system allows — at the point of adjudication. Before a claim processes, the system verifies current enrollment status. If the state's eligibility API shows the member as inactive, the claim holds for review rather than auto-paying.",[12,2823,2824],{},"This requires more than just intent. It requires a system architecture that can query state eligibility sources at transaction time, not just at batch time. It requires workflow rules that route eligibility exceptions to staff rather than auto-adjudicating past them. And it requires that your enrollment system and claims system are actually integrated — not just adjacent.",[12,2826,2827],{},"The distinction matters operationally. Many plans run separate enrollment and claims platforms that share data through nightly files. That file-based integration introduces a 24-hour lag by design. Any eligibility change that happens between file runs creates an exposure window. If you're adjudicating tens of thousands of claims per month, that window generates errors.",[19,2829,2831],{"id":2830},"what-clean-enrollment-data-actually-requires","What Clean Enrollment Data Actually Requires",[12,2833,2834],{},"Clean enrollment data isn't a state you achieve and maintain. It's an ongoing operational standard you either hit or miss each day. Here's what hitting it actually requires.",[12,2836,2837,2840],{},[29,2838,2839],{},"A defined accuracy standard, measured consistently."," \"Clean data\" means nothing unless you've defined it in measurable terms. What percentage of your active roster matches the state's eligibility file at any given point? What's your tolerance for lag between state-reported events and system updates? Plans that measure this typically find their match rate is lower than they expect — 95% sounds good until you understand that 5% of a 50,000-member plan is 2,500 records with some form of discrepancy.",[12,2842,2843,2846],{},[29,2844,2845],{},"Automated alerts on enrollment events."," Terminations, suspensions, retroactive disenrollments — each one should trigger an automated workflow, not a manual reconciliation queue item. The workflow should include claim holds on any pending adjudication for that member, notification to care management if the member was active in any programs, and a data correction task if the termination is retroactive.",[12,2848,2849,2852],{},[29,2850,2851],{},"Retroactive enrollment management."," Retroactive disenrollments are the hardest case. The state determines a member was ineligible as of a past date. You may have paid claims during that period. Now you need to identify every claim that adjudicated against that enrollment record, determine recovery obligations, and correct your encounter data submissions. Without a system that can trace the claim-to-enrollment dependency chain, this is manual and slow.",[12,2854,2855,2858],{},[29,2856,2857],{},"State file monitoring and exception handling."," State enrollment files aren't always clean or timely. Format errors, missing fields, duplicate records — any of these can cause your enrollment system to silently skip a transaction rather than posting the change. Exception reports need to be reviewed daily, not weekly. A missed termination that sits in an exception queue for a week generates a week of exposure.",[12,2860,2861,2864],{},[29,2862,2863],{},"The enrollment-to-claims data dependency chain."," Every claim adjudication depends on enrollment status at the date of service. That dependency chain should be explicit in your system — auditable, traceable, and testable. When you identify a claims error, you should be able to trace it back to the enrollment event that caused it. When you correct an enrollment record, your system should identify all claims that may be affected.",[19,2866,2868],{"id":2867},"measuring-what-you-actually-have","Measuring What You Actually Have",[12,2870,2871],{},"Most plans don't have a clear picture of their enrollment data quality until something breaks. By then the damage is done. A few specific metrics will tell you more than any audit:",[601,2873,2874,2880,2886,2892],{},[604,2875,2876,2879],{},[29,2877,2878],{},"Roster match rate:"," What percentage of your active members match state eligibility files at time of check? Anything below 98% warrants investigation.",[604,2881,2882,2885],{},[29,2883,2884],{},"Termination lag:"," How many days on average between state-reported disenrollment and system update? The goal is under 24 hours for standard terminations.",[604,2887,2888,2891],{},[29,2889,2890],{},"Claims on inactive members:"," How many claims per month adjudicate successfully against member records that were inactive at date of service? Even a handful per month signals a process gap.",[604,2893,2894,2897],{},[29,2895,2896],{},"Retroactive correction volume:"," How many enrollment corrections per month involve a retroactive effective date? High volume here means your upstream reconciliation is catching too little, too late.",[12,2899,2900],{},"None of these metrics require sophisticated analytics infrastructure. They require that your enrollment and claims systems expose the data to generate them, and that someone is accountable for watching them.",[158,2902],{},[12,2904,2905],{},[163,2906,2907,2908,2911,2912,2915],{},"If enrollment volatility is creating claims errors, phantom member issues, or encounter data problems for your plan, ",[167,2909,2910],{"href":2256},"Ayin's enrollment management services"," are built specifically for the operational reality of Medicaid. ",[167,2913,2914],{"href":534},"Reach out"," to talk through what clean data requires for your program.",{"title":181,"searchDepth":182,"depth":182,"links":2917},[2918,2920,2921,2922,2923,2924],{"id":2750,"depth":182,"text":2919},"title: \"Enrollment Management for High-Churn Medicaid Populations: What Clean Data Actually Requires\"\ndescription: \"Medicaid populations churn faster than any other market. Plans that treat enrollment as a solved problem are carrying phantom members, generating incorrect claims, and creating risk score errors. Here's what a truly clean enrollment operation requires.\"\ndate: 2026-01-06\nauthor: \"Ayin Health Solutions\"\ncategory: \"Operations\"\ntags: \"Enrollment\", \"Medicaid\", \"Data Quality\", \"Eligibility\", \"Operations\"\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Operations team reviewing enrollment data\"\nfeatured: false",{"id":2761,"depth":182,"text":2762},{"id":2777,"depth":182,"text":2778},{"id":2811,"depth":182,"text":2812},{"id":2830,"depth":182,"text":2831},{"id":2867,"depth":182,"text":2868},{},"\u002Farticles\u002Fmedicaid-enrollment-management-clean-data",{"description":181},"articles\u002Fmedicaid-enrollment-management-clean-data","9L2MwJPUFJoQy9RR41ahGlArrlv7p5tVtKxpWVCJfqQ",{"id":2931,"title":2932,"author":2079,"body":2933,"category":2079,"date":2079,"description":181,"extension":192,"featured":193,"image":2079,"imageAlt":2079,"meta":3104,"navigation":197,"path":3105,"seo":3106,"stem":3107,"tags":2079,"__hash__":3108},"articles\u002Farticles\u002Fmedicaid-work-requirements-2027.md","Medicaid Work Requirements 2027",{"type":9,"value":2934,"toc":3087},[2935,2937,2945,2948,2952,2955,2959,2962,2966,2969,2973,2976,2979,2983,2986,2989,2992,2996,2999,3001,3004,3007,3011,3014,3017,3021,3024,3027,3031,3034,3040,3046,3052,3058,3064,3067,3071,3074,3077,3079],[158,2936],{},[19,2938,2940,2941,2944],{"id":2939},"title-medicaid-work-requirements-what-small-plans-need-to-operationalize-before-january-2027description-the-january-1-2027-cms-deadline-for-medicaid-work-requirements-is-closer-than-it-looks-and-the-back-office-burden-falls-squarely-on-health-plans-heres-what-it-actually-takes-to-operationalize-work-verification-manage-eligibility-churn-and-protect-your-enrollment-datadate-2026-04-01author-ayin-health-solutionscategory-compliancetags-medicaid-work-requirements-enrollment-compliance-operationsimage-photographyayin_still_7pngimagealt-ayin-health-solutions-back-office-operationsfeatured-false","title: \"Medicaid Work Requirements: What Small Plans Need to Operationalize Before January 2027\"\ndescription: \"The January 1, 2027 CMS deadline for Medicaid work requirements is closer than it looks — and the back-office burden falls squarely on health plans. Here's what it actually takes to operationalize work verification, manage eligibility churn, and protect your enrollment data.\"\ndate: 2026-04-01\nauthor: \"Ayin Health Solutions\"\ncategory: \"Compliance\"\ntags: ",[2089,2942,2943],{},"\"Medicaid\", \"Work Requirements\", \"Enrollment\", \"Compliance\", \"Operations\"","\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Ayin Health Solutions back-office operations\"\nfeatured: false",[12,2946,2947],{},"January 1, 2027 is eight months away. Under H.R. 1, signed into law on July 4, 2025, most Medicaid expansion adults ages 19–64 will be subject to community engagement requirements — 80 hours per month of work, job training, education, or community service. States that can't get there by January can apply for an extension to December 31, 2028, but the operative word is \"can't,\" not \"plan to.\" The default is go-live in eight months. CMS is still issuing guidance — an interim final rule is due by June 1, 2026 — which means the operational window for small plans is shorter than the calendar makes it look. If your enrollment team isn't already mapping what this change requires at the workflow level, you are behind.",[19,2949,2951],{"id":2950},"what-the-rule-actually-requires-operationally","What the Rule Actually Requires — Operationally",[12,2953,2954],{},"The policy summary is simple: work-capable adults must demonstrate 80 hours per month of qualifying activity or lose coverage. The operational reality is considerably more complex.",[1113,2956,2958],{"id":2957},"verification-before-enrollment","Verification Before Enrollment",[12,2960,2961],{},"Before a member is enrolled or re-enrolled, states must conduct a look-back review covering at least one and up to three months prior. States are required to check existing data sources first — payroll data, wage records, Medicaid payment and encounter data — before asking applicants to self-report. That data-first requirement sounds helpful. In practice, it means your eligibility systems need to be connected to state data feeds that may not exist yet, feeding into workflows that states are still designing.",[1113,2963,2965],{"id":2964},"ongoing-redeterminations-every-six-months","Ongoing Redeterminations Every Six Months",[12,2967,2968],{},"Once enrolled, members must demonstrate compliance for at least one month within each six-month eligibility review period. That is two redetermination cycles per year, per member, layered on top of your existing annual renewal workflow. For a plan with 50,000 expansion-eligible members, that is 100,000 compliance verification events annually — each one requiring intake, documentation review, and a disposition.",[1113,2970,2972],{"id":2971},"_30-day-notice-and-grace-period","30-Day Notice and Grace Period",[12,2974,2975],{},"When a member fails to demonstrate compliance, the state must send notice by mail plus at least one other channel. The member then has 30 days to show compliance before disenrollment. Those 30 days are not a buffer — they are an active workflow window. Someone has to track who received a notice, when, and whether they responded. Someone has to manage the queue of members in that grace period. And someone has to process the disenrollments for those who don't respond in time.",[12,2977,2978],{},"None of that is happening automatically. It is staff-hours and system logic that either exist in your operation or they don't.",[19,2980,2982],{"id":2981},"the-staffing-math-nobody-wants-to-do","The Staffing Math Nobody Wants to Do",[12,2984,2985],{},"States are already short the workers needed to implement this. Pennsylvania has nearly 400 open positions across county human services offices. Indiana has 94 open Medicaid agency positions. Missouri is running its Medicaid operation with 1,000 fewer front-line workers than it had a decade ago — while managing more than twice the enrollment. These aren't just capacity problems; they are baseline problems. States don't have enough staff to run the existing eligibility workload cleanly, let alone absorb a new compliance verification layer on top of it.",[12,2987,2988],{},"That strain flows downstream to managed care plans. When state eligibility determinations are delayed or inconsistent — and they will be — plans receive bad enrollment transactions. Members show up on your roster who shouldn't be there. Members who should be there disappear. Your team is left reconciling a state file that reflects not reality, but the current backlog status of an understaffed eligibility office.",[12,2990,2991],{},"That is not a hypothetical. During the post-pandemic redetermination wave, call center wait times at state Medicaid agencies hit three hours in Hawaii, nearly an hour in Oklahoma, more than an hour in Nevada. Application processing rates cratered — 30 percent of applications in Washington, D.C. and Georgia exceeded the 45-day processing window. Your members will be calling you when they can't get through to the state. Your enrollment team will be manually resolving transactions the state system generated incorrectly.",[19,2993,2995],{"id":2994},"what-happens-to-your-enrollment-data","What Happens to Your Enrollment Data",[12,2997,2998],{},"The CBO projects that approximately 4.8 million people will lose Medicaid coverage specifically due to work requirements over the next decade. That number doesn't land uniformly — it lands in waves, tied to redetermination cycles. Plans with high concentrations of expansion-eligible adults will see disenrollment spikes that stress every downstream system.",[1113,3000,2778],{"id":2777},[12,3002,3003],{},"Phantom members — individuals who appear on your enrollment roster but are no longer eligible — are the predictable output of a high-churn environment with slow state transaction processing. When disenrollments are delayed or fail to transmit cleanly, plans continue to receive capitation for members who should be off the rolls. Claims keep adjudicating. Risk scores carry inaccurate data. You may not know a member disenrolled for three billing cycles.",[12,3005,3006],{},"This is expensive and it creates compliance exposure. CMS is explicit that work requirement enforcement cannot be delegated to managed care entities — states own the eligibility determination. But plans own their data. You are responsible for what your enrollment file says and what you do with it.",[1113,3008,3010],{"id":3009},"reconciliation-burden-at-scale","Reconciliation Burden at Scale",[12,3012,3013],{},"Clean enrollment management in a work requirement environment means continuous reconciliation against state eligibility files — not monthly batch processing. It means exception workflows that flag anomalies quickly: members with no encounter activity after the grace period window closed, members who appear disenrolled by the state but remain on your capitation file, members who re-enrolled after a short gap that may indicate a failed disenrollment transaction.",[12,3015,3016],{},"Plans that are running enrollment as a manual or semi-manual process are going to find that cadence unsustainable in a high-churn environment. The volume of exception events will outpace staff capacity.",[19,3018,3020],{"id":3019},"member-outreach-is-your-problem-too","Member Outreach Is Your Problem Too",[12,3022,3023],{},"CMS guidance requires states to conduct outreach to affected members between June 30 and August 31, 2026 — before implementation. That outreach must include compliance information, exemption explanations, consequences of non-compliance, and reporting instructions. States will send it. That does not mean members will understand it, or act on it, or not call your customer service line with questions about it.",[12,3025,3026],{},"If your plan has 20,000 expansion-eligible members and even 15 percent of them call with work requirement questions in August and September 2026, that is 3,000 calls your team needs to handle correctly — with accurate information about a rule that is still being finalized by CMS. Your customer service scripts, your member portal language, your IVR routing — none of that is updated yet. It needs to be.",[19,3028,3030],{"id":3029},"what-to-start-building-now","What to Start Building Now",[12,3032,3033],{},"You don't need to wait for the interim final rule in June to start planning. The operational requirements are clear enough to begin.",[12,3035,3036,3039],{},[29,3037,3038],{},"Map your affected population."," Identify how many of your current members are expansion-eligible adults ages 19–64. Segment by exemption categories — pregnant individuals, medically frail members, full-time students. The exempt population reduces your verification workload, but you need to know who is in it.",[12,3041,3042,3045],{},[29,3043,3044],{},"Audit your eligibility transaction workflow."," How are you currently receiving and processing 834 transactions from your state? How quickly do you reconcile against the state file? If the answer is \"monthly batch,\" that cadence won't hold. You need near-real-time exception monitoring.",[12,3047,3048,3051],{},[29,3049,3050],{},"Document your phantom member exposure."," Run an analysis of your current enrollment data against recent claim activity. Members who have been capitated with no encounters over an extended period are a proxy for potential phantom members. That baseline tells you how clean your data is right now — before the churn starts.",[12,3053,3054,3057],{},[29,3055,3056],{},"Build your outreach infrastructure."," Start drafting member communications for August 2026 now. Coordinate with your state Medicaid agency on messaging alignment. Update your customer service team's knowledge base as CMS guidance becomes final.",[12,3059,3060,3063],{},[29,3061,3062],{},"Assess your reconciliation staffing."," Do an honest count of how many additional enrollment transactions you will need to process under biannual redeterminations. If your current team can't absorb it, you need to decide now whether you are adding staff, automating more of the workflow, or both.",[12,3065,3066],{},"The $200 million CMS allocated to states for implementation support in FY2026 is intended for systems and infrastructure — not plan-level operations. Your plan does not get a line item from that fund. You are building your own capacity with your existing budget.",[19,3068,3070],{"id":3069},"the-window-is-narrow","The Window Is Narrow",[12,3072,3073],{},"CMS will release an interim final rule by June 2026. States are required to start member outreach by July 1, 2026. Implementation goes live January 1, 2027. That is a six-month operational window from final federal guidance to go-live — for changes that touch your enrollment system, your reconciliation workflows, your customer service operation, and your member data.",[12,3075,3076],{},"Small plans that treat this as a compliance checkbox rather than an operational build will be managing the fallout in 2027. The enrollment volatility from even a partial implementation will expose every weakness in a manual or batch-based back-office operation. The plans that handle it cleanly will be the ones that started building the infrastructure before the deadline arrived.",[158,3078],{},[12,3080,3081],{},[163,3082,3083,3084,179],{},"If your plan is assessing whether your current enrollment infrastructure can absorb the demands of work requirement implementation, ",[167,3085,3086],{"href":2256},"talk to Ayin's team about what enrollment management looks like at scale",{"title":181,"searchDepth":182,"depth":182,"links":3088},[3089,3091,3096,3097,3101,3102,3103],{"id":2939,"depth":182,"text":3090},"title: \"Medicaid Work Requirements: What Small Plans Need to Operationalize Before January 2027\"\ndescription: \"The January 1, 2027 CMS deadline for Medicaid work requirements is closer than it looks — and the back-office burden falls squarely on health plans. Here's what it actually takes to operationalize work verification, manage eligibility churn, and protect your enrollment data.\"\ndate: 2026-04-01\nauthor: \"Ayin Health Solutions\"\ncategory: \"Compliance\"\ntags: \"Medicaid\", \"Work Requirements\", \"Enrollment\", \"Compliance\", \"Operations\"\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Ayin Health Solutions back-office operations\"\nfeatured: false",{"id":2950,"depth":182,"text":2951,"children":3092},[3093,3094,3095],{"id":2957,"depth":1272,"text":2958},{"id":2964,"depth":1272,"text":2965},{"id":2971,"depth":1272,"text":2972},{"id":2981,"depth":182,"text":2982},{"id":2994,"depth":182,"text":2995,"children":3098},[3099,3100],{"id":2777,"depth":1272,"text":2778},{"id":3009,"depth":1272,"text":3010},{"id":3019,"depth":182,"text":3020},{"id":3029,"depth":182,"text":3030},{"id":3069,"depth":182,"text":3070},{},"\u002Farticles\u002Fmedicaid-work-requirements-2027",{"description":181},"articles\u002Fmedicaid-work-requirements-2027","2T53yVKqnuPNTWMKwxOhfJQ_DbkuZI6cia-PeYIHs7E",{"id":3110,"title":3111,"author":2079,"body":3112,"category":2079,"date":2079,"description":181,"extension":192,"featured":193,"image":2079,"imageAlt":2079,"meta":3277,"navigation":197,"path":3278,"seo":3279,"stem":3280,"tags":2079,"__hash__":3281},"articles\u002Farticles\u002Fmedicare-advantage-enrollment-compliance.md","Medicare Advantage Enrollment Compliance",{"type":9,"value":3113,"toc":3266},[3114,3116,3124,3127,3131,3134,3140,3146,3152,3158,3162,3165,3168,3171,3175,3178,3181,3187,3193,3199,3205,3211,3215,3218,3221,3224,3228,3231,3234,3237,3240,3243,3247,3250,3253,3255],[158,3115],{},[19,3117,3119,3120,3123],{"id":3118},"title-medicare-advantage-enrollment-compliance-for-regional-plans-getting-the-basics-rightdescription-cms-audit-findings-consistently-cite-enrollment-operations-as-a-source-of-compliance-exposure-for-small-ma-plans-this-article-explains-what-compliant-ma-enrollment-actually-requires-election-periods-sep-documentation-marx-submission-timelines-and-where-manual-processes-break-downdate-2025-10-07author-ayin-health-solutionscategory-medicare-advantagetags-medicare-advantage-enrollment-compliance-cms-operationsimage-photographyayin_still_7pngimagealt-administrative-operations-team-reviewing-enrollment-compliance-documentationfeatured-false","title: \"Medicare Advantage Enrollment Compliance for Regional Plans: Getting the Basics Right\"\ndescription: \"CMS audit findings consistently cite enrollment operations as a source of compliance exposure for small MA plans. This article explains what compliant MA enrollment actually requires — election periods, SEP documentation, MARx submission timelines, and where manual processes break down.\"\ndate: 2025-10-07\nauthor: \"Ayin Health Solutions\"\ncategory: \"Medicare Advantage\"\ntags: ",[2089,3121,3122],{},"\"Medicare Advantage\", \"Enrollment\", \"Compliance\", \"CMS\", \"Operations\"","\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Administrative operations team reviewing enrollment compliance documentation\"\nfeatured: false",[12,3125,3126],{},"Medicare Advantage enrollment looks straightforward on paper. Members elect coverage during defined windows, plans submit transactions to CMS, and enrollment is confirmed. In practice, the regulatory framework governing when elections are valid, what documentation must support them, and how quickly transactions must be submitted is dense enough that even experienced plans carry more compliance exposure here than they realize. For regional and small MA plans running lean ops teams, enrollment is one of the places where manual workarounds accumulate quietly — until an audit makes the risk visible.",[19,3128,3130],{"id":3129},"the-ma-enrollment-calendar","The MA Enrollment Calendar",[12,3132,3133],{},"CMS defines four primary enrollment windows that an MA plan must manage correctly for every transaction it processes.",[12,3135,3136,3139],{},[29,3137,3138],{},"Annual Enrollment Period (AEP)"," runs October 15 through December 7 each year. Elections made during AEP take effect January 1 of the following year. This is the highest-volume window for most plans and the period where processing backlogs are most likely.",[12,3141,3142,3145],{},[29,3143,3144],{},"Medicare Advantage Open Enrollment Period (OEP)"," runs January 1 through March 31. During this window, members already enrolled in an MA plan can switch to a different MA plan or return to Original Medicare. New enrollments into MA from Original Medicare are not permitted during OEP — a distinction that trips up plans processing requests from members who don't fully understand their options.",[12,3147,3148,3151],{},[29,3149,3150],{},"Initial Coverage Election Period (ICEP)"," is the window a new Medicare beneficiary has to choose their coverage when they first become eligible. Timing is tied to the individual's Part B effective date, and errors here often surface as enrollment effective date discrepancies.",[12,3153,3154,3157],{},[29,3155,3156],{},"Special Enrollment Periods (SEPs)"," are where complexity concentrates. CMS recognizes more than a dozen distinct SEP types — involuntary loss of coverage, plan area moves, institutional placements, loss of Medicaid eligibility, and others. Each SEP has its own eligibility criteria, documentation requirements, and effective date rules. Using the wrong SEP code, or processing an election under an SEP without adequate supporting documentation, is one of the most consistent sources of CMS audit findings in enrollment operations.",[1113,3159,3161],{"id":3160},"the-dual-eligible-sep-changes-every-plan-should-know","The Dual-Eligible SEP Changes Every Plan Should Know",[12,3163,3164],{},"Effective January 1, 2025, CMS restructured the SEP rules for dually eligible individuals — members enrolled in both Medicare and Medicaid. The previous quarterly SEP that allowed dual eligible and Low-Income Subsidy (LIS) recipients to switch MA plans has been replaced with a monthly SEP that only permits disenrollment into Original Medicare (plus enrollment in a standalone Part D plan). Switching between MA plans using this pathway is no longer permitted.",[12,3166,3167],{},"CMS simultaneously created a new Integrated Care SEP allowing full-benefit dual eligible individuals to switch between integrated D-SNPs — specifically Fully Integrated Dual Eligible Special Needs Plans (FIDE SNPs), Highly Integrated Dual Eligible Special Needs Plans (HIDE SNPs), and Applicable Integrated Plans (AIPs) — on a monthly basis. The purpose is to align Medicare and Medicaid managed care enrollment.",[12,3169,3170],{},"For plans serving dual eligible populations, this is a material operational change. The new rules require plans to track which SEP a member used and when — because when a member uses multiple SEPs in the same month, the last-in-time election controls. That sequencing requirement demands enrollment transaction logging that is real-time, not end-of-day batch.",[19,3172,3174],{"id":3173},"where-small-plans-fail-common-audit-findings","Where Small Plans Fail: Common Audit Findings",[12,3176,3177],{},"CMS conducted 39 program audits in 2024 covering 36 parent organizations and 494 contracts. The audit universe is broad, and CMS has refined its approach to smaller plans — using samples of 35 to 200 enrollees calibrated to plan size. Smaller plans are not exempt from audit exposure; they are just audited with samples sized to their population.",[12,3179,3180],{},"Enrollment-related audit findings in small MA plans tend to cluster in a few predictable areas.",[12,3182,3183,3186],{},[29,3184,3185],{},"SEP documentation gaps."," Plans process a member's election under an SEP but cannot produce the documentation that verifies SEP eligibility at the time of the election. Retrospective documentation requests generate denial letters and complaints. CMS expects contemporaneous documentation — the evidence should exist when the election is processed, not assembled afterward.",[12,3188,3189,3192],{},[29,3190,3191],{},"Incorrect effective dates."," Each election type carries specific effective date rules. An AEP election is January 1. An OEP election is the first of the month following the election request. SEP effective dates vary by SEP type. Plans processing elections manually — or using systems that require a coordinator to select effective dates rather than calculating them automatically — generate errors at a rate that scales with transaction volume.",[12,3194,3195,3198],{},[29,3196,3197],{},"Eligibility transaction failures."," CMS receives enrollment transactions through the MARx system. When a plan submits a transaction for a member who does not meet basic eligibility requirements — no Part A and Part B, not living within the service area, not a U.S. citizen or lawfully present — the transaction fails, but the failure must be caught, resolved, and resubmitted within the plan's processing window. Plans without automated transaction validation end up with enrollment records that don't match CMS's system, creating downstream issues for claims and member communications.",[12,3200,3201,3204],{},[29,3202,3203],{},"Delegated entity oversight failures."," CMS's 2024 audit report specifically flagged plans for inadequate oversight of subcontractors handling enrollment-related functions. If a plan delegates enrollment intake to a broker, vendor, or downstream partner, the plan remains accountable for that entity's compliance with enrollment requirements. This is a straightforward regulatory obligation that plans frequently underinvest in monitoring.",[12,3206,3207,3210],{},[29,3208,3209],{},"Eligibility file errors causing benefit access issues."," CMS imposed civil monetary penalties in 2024 specifically for plans that \"inappropriately rejected enrollees' access to medications due to errors with eligibility files.\" Enrollment data errors — wrong effective dates, mismatched member IDs, incomplete record updates — propagate directly into benefits administration. The enrollment record is the source of truth for everything downstream.",[19,3212,3214],{"id":3213},"marx-submission-requirements","MARx Submission Requirements",[12,3216,3217],{},"MARx is the CMS system that processes Medicare Advantage enrollment and disenrollment transactions. Every election — whether from AEP, OEP, ICEP, or SEP — must be submitted to MARx within the CMS-defined processing window. CMS updated its MA and Part D Enrollment and Disenrollment Guidance in August 2025 for contract year 2026, and plans are required to apply the updated guidance to all requests received on or after January 1, 2026.",[12,3219,3220],{},"Plans must transmit transactions with correct plan contract and PBP codes, accurate election period codes, and member data that matches Medicare's records. Rejected transactions must be worked within the same processing cycle. CMS does not hold elections open indefinitely — if a transaction misses its cycle, the election may be treated as not received, and the member remains in their prior status until the next valid election window.",[12,3222,3223],{},"For a three-person ops team processing transactions manually against MARx deadlines, the margin for error is narrow. A missed weekly transaction file means a member's election doesn't take effect when they expect, generating a member complaint, a possible SEP invocation, and a compliance documentation trail that needs to be managed carefully.",[19,3225,3227],{"id":3226},"automated-enrollment-management-vs-manual-processes","Automated Enrollment Management vs. Manual Processes",[12,3229,3230],{},"The difference between automated and manual MA enrollment management is not primarily about speed. It is about error rate at scale and the ability to demonstrate compliance during an audit.",[12,3232,3233],{},"A manual enrollment process typically looks like this: election requests come in by phone, fax, or online form; a coordinator reviews them, assigns an election period code, calculates an effective date, checks eligibility against a list, and enters the transaction into MARx. SEP documentation is collected and stored — sometimes in a shared drive, sometimes in the member's file in a claims system, sometimes in both, sometimes inconsistently. When CMS requests documentation for an audit sample, staff spend time locating records across multiple systems.",[12,3235,3236],{},"An automated enrollment management process does this instead: transactions enter through defined intake channels; eligibility verification runs against Medicare's data automatically; election period and effective date logic is applied by the system, not a human; MARx submissions are generated and transmitted on schedule with automated reconciliation against CMS responses; and SEP documentation is linked to the enrollment record at the time of intake, not appended later.",[12,3238,3239],{},"The compliance advantage is not just accuracy — it is auditability. When CMS pulls a sample of 50 enrollments and asks for election documentation, plans with automated systems can produce a complete record for each one in minutes. Plans with manual systems spend days reconstructing files and often find gaps.",[12,3241,3242],{},"The transition is not trivial. Automating enrollment management requires clear data flows from intake channels into the enrollment system, integration with MARx's transaction formats, and workflow rules that encode CMS's election period logic correctly. Plans that have grown their MA membership over time — and layered process on top of process to manage volume — often find that the cost of the workarounds exceeds the cost of the automation they've been deferring.",[19,3244,3246],{"id":3245},"a-note-on-the-work-ahead","A Note on the Work Ahead",[12,3248,3249],{},"CMS has signaled continued attention to MA plan compliance. The 2024 audit cycle covered 87.6 percent of Medicare Part C enrollees. RADV audit activity is expanding. The structural reforms to dual-eligible SEPs create new tracking obligations that take effect immediately. And the CY 2026 enrollment and disenrollment guidance update in August 2025 means plans are already operating under revised requirements this calendar year.",[12,3251,3252],{},"For a regional MA plan with a small ops team, the practical question is not whether CMS will audit enrollment practices — it is whether the documentation and system infrastructure exist to demonstrate compliance when they do. That assessment is worth making before the audit cycle starts, not after a notice arrives.",[158,3254],{},[12,3256,3257],{},[163,3258,3259,3260,3262,3263,3265],{},"If your team is evaluating enrollment management infrastructure or working through CMS compliance gaps, ",[167,3261,2910],{"href":2256}," are built specifically for regional and community-driven MA plans — or ",[167,3264,178],{"href":534}," to talk through your situation.",{"title":181,"searchDepth":182,"depth":182,"links":3267},[3268,3270,3273,3274,3275,3276],{"id":3118,"depth":182,"text":3269},"title: \"Medicare Advantage Enrollment Compliance for Regional Plans: Getting the Basics Right\"\ndescription: \"CMS audit findings consistently cite enrollment operations as a source of compliance exposure for small MA plans. This article explains what compliant MA enrollment actually requires — election periods, SEP documentation, MARx submission timelines, and where manual processes break down.\"\ndate: 2025-10-07\nauthor: \"Ayin Health Solutions\"\ncategory: \"Medicare Advantage\"\ntags: \"Medicare Advantage\", \"Enrollment\", \"Compliance\", \"CMS\", \"Operations\"\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Administrative operations team reviewing enrollment compliance documentation\"\nfeatured: false",{"id":3129,"depth":182,"text":3130,"children":3271},[3272],{"id":3160,"depth":1272,"text":3161},{"id":3173,"depth":182,"text":3174},{"id":3213,"depth":182,"text":3214},{"id":3226,"depth":182,"text":3227},{"id":3245,"depth":182,"text":3246},{},"\u002Farticles\u002Fmedicare-advantage-enrollment-compliance",{"description":181},"articles\u002Fmedicare-advantage-enrollment-compliance","BIfY69feZlSh9THHoofNvDuOw3VVplIW5LdnoVVfs4M",{"id":3283,"title":3284,"author":2079,"body":3285,"category":2079,"date":2079,"description":181,"extension":192,"featured":193,"image":2079,"imageAlt":2079,"meta":3438,"navigation":197,"path":3439,"seo":3440,"stem":3441,"tags":2079,"__hash__":3442},"articles\u002Farticles\u002Fpace-administrative-mistakes-2025.md","Pace Administrative Mistakes 2025",{"type":9,"value":3286,"toc":3429},[3287,3289,3297,3300,3304,3307,3310,3313,3316,3319,3322,3326,3329,3335,3341,3347,3350,3354,3357,3360,3366,3372,3378,3381,3385,3388,3391,3394,3397,3400,3404,3407,3410,3413,3416,3418],[158,3288],{},[19,3290,3292,3293,3296],{"id":3291},"title-pace-in-2025-what-growing-organizations-are-getting-wrong-administrativelydescription-for-profit-pace-expansion-is-accelerating-faster-than-back-office-infrastructure-can-keep-up-here-are-the-specific-administrative-failure-modes-showing-up-in-growing-pace-organizations-from-encounter-data-gaps-to-enrollment-process-breakdowns-to-new-cms-compliance-requirements-that-many-organizations-are-not-ready-fordate-2026-02-25author-ayin-health-solutionscategory-pacetags-pace-operations-compliance-enrollment-encounter-dataimage-photographyayin_still_7pngimagealt-administrative-team-reviewing-health-plan-compliance-documentationfeatured-false","title: \"PACE in 2025: What Growing Organizations Are Getting Wrong Administratively\"\ndescription: \"For-profit PACE expansion is accelerating faster than back-office infrastructure can keep up. Here are the specific administrative failure modes showing up in growing PACE organizations — from encounter data gaps to enrollment process breakdowns to new CMS compliance requirements that many organizations are not ready for.\"\ndate: 2026-02-25\nauthor: \"Ayin Health Solutions\"\ncategory: \"PACE\"\ntags: ",[2089,3294,3295],{},"\"PACE\", \"Operations\", \"Compliance\", \"Enrollment\", \"Encounter Data\"","\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Administrative team reviewing health plan compliance documentation\"\nfeatured: false",[12,3298,3299],{},"The PACE market is growing faster than it has in decades. According to NORC's March 2025 market assessment, for-profit PACE organizations grew their contracts by 182% and their enrollment by 173% between 2016 and 2022 — while nonprofits grew by 6% and 44%, respectively. Private equity and venture capital-backed PACE organizations alone grew by 300% over the same period. As of mid-2025, there are 196 PACE programs operating across 33 states, with for-profits now accounting for more than a quarter of total enrollment. That growth trajectory is not slowing down. States are actively issuing RFPs — Georgia, Pennsylvania, New Jersey, Oregon, Louisiana, Tennessee — and new entrants are moving fast to operationalize. The problem is that operational speed and administrative readiness rarely travel together. And in PACE, the gap between the two creates specific, measurable, and often expensive problems.",[19,3301,3303],{"id":3302},"the-encounter-data-transition-is-not-optional-and-most-organizations-are-behind","The Encounter Data Transition Is Not Optional — And Most Organizations Are Behind",[12,3305,3306],{},"CMS is in the middle of a multi-year transition requiring PACE organizations to submit risk adjustment data through the Encounter Data System (EDS) rather than the legacy Risk Adjustment Processing System (RAPS). The January 2024 HPMS memo made clear that CMS expects comprehensive diagnosis data submitted via EDS, and the transition is now embedded in the CY 2025 and CY 2026 compliance calendar.",[12,3308,3309],{},"For CY 2026, CMS is blending risk scores using a 10% weight on the updated 2024 CMS-HCC model and a 90% weight on the 2017 model. The full transition — where PACE risk scores will be calculated exclusively from encounter data and FFS claims, aligned with the standard Medicare Advantage HCC model — is targeted for CY 2029.",[12,3311,3312],{},"That timeline sounds like runway. It is not.",[12,3314,3315],{},"Getting encounter data right requires accurate, complete, and timely submission of clinical diagnoses tied to actual services rendered. In PACE, that means capturing everything from PACE center visits to home health to behavioral health to transportation — across an IDT-driven care model that doesn't naturally generate a claim. Many PACE organizations are still submitting incomplete encounter records or relying on chart reviews to close diagnosis gaps rather than building the underlying documentation practices that produce clean encounter data from the start.",[12,3317,3318],{},"The downstream risks are concrete: inaccurate risk scores, revenue that doesn't reflect true member acuity, and audit exposure when CMS scrutinizes encounter submission quality. The 2026 audit protocol introduced by CMS explicitly identifies \"universe accuracy\" — meaning the accuracy and completeness of the data populations organizations submit for audit — as the foundational audit risk factor. An organization that can't produce clean encounter universes will trigger expanded review.",[12,3320,3321],{},"For new PACE entrants in particular, this is where under-investment in back-office technology shows up first. There is no shortcut to accurate encounter data. It requires the right system configuration, the right submission workflows, and regular validation before data leaves the organization.",[19,3323,3325],{"id":3324},"the-cy-2025-compliance-calendar-has-real-teeth","The CY 2025 Compliance Calendar Has Real Teeth",[12,3327,3328],{},"The April 2024 CMS final rule introduced a batch of policy changes with a January 1, 2025 applicability date. Many PACE organizations were still adjusting operational processes well into 2025. Several of these changes create new administrative exposure if the workflows to support them aren't in place.",[12,3330,3331,3334],{},[29,3332,3333],{},"IDT reassessment timelines."," IDTs must now reevaluate care plans within 180 days of the prior plan's finalization and within 14 days of any identified change in health or psychosocial status. If a hospitalization occurs within 14 days of a status change, reassessment must happen within 14 days of discharge. Tracking these triggers across a complex, high-acuity population is not manageable in a spreadsheet. It requires a care management platform integrated with enrollment and clinical data that surfaces the trigger in time to act.",[12,3336,3337,3340],{},[29,3338,3339],{},"Service scheduling requirements."," Approved services must be scheduled within 7 calendar days of IDT approval. Medications must be arranged within 24 hours of provider orders. These are not aspirational standards — they are compliance requirements. An organization without workflow automation supporting these timelines will create documentation gaps that show up in audits.",[12,3342,3343,3346],{},[29,3344,3345],{},"Grievance resolution."," PACE organizations must now resolve grievances within 30 days of receipt, with formal written procedures. The rule also clarifies who can submit grievances and requires that resolution notifications include participant rights information. This is operationally straightforward if you have a grievance tracking system. It is not straightforward if grievances are being tracked in email threads or shared folders.",[12,3348,3349],{},"The CY 2026 audit protocol compounds all of this. CMS has introduced new standardized templates for Requests for Additional Information (RAIs) and Corrective Action Plans (CAPs), and compliance program effectiveness is now evaluated through quarterly calls rather than a separate audit session. Organizations that haven't stress-tested their documentation practices against the updated protocol will learn about the gaps at the worst possible time — during fieldwork.",[19,3351,3353],{"id":3352},"enrollment-process-gaps-in-a-population-that-doesnt-tolerate-them","Enrollment Process Gaps in a Population That Doesn't Tolerate Them",[12,3355,3356],{},"PACE enrollment is structurally different from Medicare Advantage or Medicaid managed care. The frailty of the population means enrollment processes must move quickly and accurately. The average PACE enrollment tenure is two to three years, with death as the primary reason for disenrollment. This is not a population where enrollment errors self-correct over time.",[12,3358,3359],{},"What tends to go wrong:",[12,3361,3362,3365],{},[29,3363,3364],{},"Eligibility and assessment coordination."," PACE enrollment requires nursing home level of care certification, Medicaid eligibility, Medicare eligibility (for dual-eligible participants), and geographic service area confirmation — all of which must be validated before enrollment is finalized. When any of these are mismatched, the downstream effects touch claims, risk adjustment, and capitation payments simultaneously.",[12,3367,3368,3371],{},[29,3369,3370],{},"Enrollment timing errors."," PACE capitation payments are tied to enrollment effective dates. Delays or errors in reporting enrollment to CMS and the state Medicaid agency create reconciliation problems that are time-consuming and sometimes irrecoverable. New organizations often underestimate how much manual reconciliation is required before automated enrollment workflows are configured correctly.",[12,3373,3374,3377],{},[29,3375,3376],{},"Disenrollment documentation."," When a participant dies, is hospitalized long-term, or voluntarily disenrolls, that transition must be documented and reported promptly. Lagging disenrollment reporting creates phantom capitation payments that will be recouped — often months later, after revenue has already been recognized.",[12,3379,3380],{},"Growing PACE organizations often understaff enrollment operations relative to their clinical build-out. The IDT, the PACE center, the transportation network — those get resourced first. Enrollment gets three people and a spreadsheet. That equation doesn't hold as census grows.",[19,3382,3384],{"id":3383},"rural-expansion-is-creating-operational-problems-that-werent-in-the-business-plan","Rural Expansion Is Creating Operational Problems That Weren't in the Business Plan",[12,3386,3387],{},"The NORC data on for-profit rural expansion is striking: for-profit PACE enrollment in rural areas grew by 493% between 2016 and 2022, compared to 58% for nonprofits. That's largely a story of investor-driven market entry into underserved geographies. It's also a story of organizations discovering, after entry, that rural PACE creates specific administrative complications that urban program models don't prepare you for.",[12,3389,3390],{},"Transportation cost and documentation is the first problem that surfaces. PACE transportation is a covered service and a significant cost driver — and it's also encounter data that has to be captured and submitted. Rural programs run longer routes, use more non-emergency medical transportation vendors, and generate more variation in service delivery than urban programs. Capturing that accurately and consistently is harder.",[12,3392,3393],{},"Provider network adequacy documentation becomes more difficult when specialty providers are hours away. When a PACE participant requires specialist services outside the immediate area, the coordination documentation, authorization records, and encounter submission requirements don't change — but the volume of exceptions does.",[12,3395,3396],{},"And the enrollment ramp-up problem is more acute. PACE programs are typically not financially sustainable until enrollment reaches a critical threshold, often cited in the range of 100 to 200 participants. In a low-density rural market, reaching that threshold takes longer. The administrative infrastructure has to sustain the program during the ramp-up period, which requires careful cash flow management and operational efficiency from day one — not month eighteen.",[12,3398,3399],{},"California's 2025 moratorium on new PACE applications and service area expansions is a different kind of warning signal. When a major state effectively stops processing PACE applications because it has run out of regulatory bandwidth, it reflects how demanding new program oversight has become. The compliance burden on state agencies mirrors the compliance burden on organizations. Both are real.",[19,3401,3403],{"id":3402},"technology-gaps-that-pace-specific-operations-expose","Technology Gaps That PACE-Specific Operations Expose",[12,3405,3406],{},"PACE organizations frequently start with health plan administration platforms that were designed for MA or Medicaid managed care — and then discover that PACE workflows don't map cleanly. The IDT structure, the all-inclusive service model, the encounter data requirements for center-based services without a claim, the care plan trigger tracking — these aren't standard features in most platforms.",[12,3408,3409],{},"The practical result is workarounds. A system that wasn't built for IDT-driven care planning gets a custom module. Encounter data gets captured in a separate system and manually reconciled. Care plan reassessment triggers get tracked in a spreadsheet. Each workaround creates a compliance risk and a data quality problem.",[12,3411,3412],{},"Organizations that are new to PACE sometimes recognize this gap and invest in purpose-built PACE platforms early. More often, they discover the gap after go-live, when the workarounds are already load-bearing.",[12,3414,3415],{},"The check isn't whether you have a system. It's whether your system can produce a clean encounter data universe, track IDT reassessment triggers against the new CY 2025 timelines, and generate grievance documentation that meets the updated resolution requirements — without manual intervention at every step.",[158,3417],{},[12,3419,3420],{},[163,3421,3422,3423,3426,3427,936],{},"If your organization is navigating the encounter data transition, building out PACE enrollment operations, or preparing for a CMS audit, ",[167,3424,3425],{"href":2256},"Ayin's encounter data and enrollment management services"," are built to support exactly this kind of operational complexity — or ",[167,3428,935],{"href":534},{"title":181,"searchDepth":182,"depth":182,"links":3430},[3431,3433,3434,3435,3436,3437],{"id":3291,"depth":182,"text":3432},"title: \"PACE in 2025: What Growing Organizations Are Getting Wrong Administratively\"\ndescription: \"For-profit PACE expansion is accelerating faster than back-office infrastructure can keep up. Here are the specific administrative failure modes showing up in growing PACE organizations — from encounter data gaps to enrollment process breakdowns to new CMS compliance requirements that many organizations are not ready for.\"\ndate: 2026-02-25\nauthor: \"Ayin Health Solutions\"\ncategory: \"PACE\"\ntags: \"PACE\", \"Operations\", \"Compliance\", \"Enrollment\", \"Encounter Data\"\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Administrative team reviewing health plan compliance documentation\"\nfeatured: false",{"id":3302,"depth":182,"text":3303},{"id":3324,"depth":182,"text":3325},{"id":3352,"depth":182,"text":3353},{"id":3383,"depth":182,"text":3384},{"id":3402,"depth":182,"text":3403},{},"\u002Farticles\u002Fpace-administrative-mistakes-2025",{"description":181},"articles\u002Fpace-administrative-mistakes-2025","v6Ht827QkdUV8f1V4Zuf0lyB66zK68geozK7nHB-k3A",{"id":3444,"title":3445,"author":2079,"body":3446,"category":2079,"date":2079,"description":181,"extension":192,"featured":193,"image":2079,"imageAlt":2079,"meta":3606,"navigation":197,"path":3607,"seo":3608,"stem":3609,"tags":2079,"__hash__":3610},"articles\u002Farticles\u002Fpace-encounter-data-compliance.md","Pace Encounter Data Compliance",{"type":9,"value":3447,"toc":3595},[3448,3450,3458,3461,3465,3468,3471,3474,3478,3481,3484,3487,3490,3494,3497,3500,3504,3507,3510,3516,3522,3528,3532,3535,3541,3547,3553,3559,3565,3569,3572,3575,3578,3581,3583],[158,3449],{},[19,3451,3453,3454,3457],{"id":3452},"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: ",[2089,3455,3456],{},"\"PACE\", \"Encounter Data\", \"CMS\", \"Compliance\", \"Risk Adjustment\"","\nimage: \"\u002Fphotography\u002FAyin_still_7.png\"\nimageAlt: \"Administrative team reviewing compliance documentation\"\nfeatured: false",[12,3459,3460],{},"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.",[19,3462,3464],{"id":3463},"what-cms-is-actually-requiring","What CMS Is Actually Requiring",[12,3466,3467],{},"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.",[12,3469,3470],{},"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.",[12,3472,3473],{},"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.",[19,3475,3477],{"id":3476},"how-errors-propagate-into-risk-adjustment-and-revenue","How Errors Propagate Into Risk Adjustment and Revenue",[12,3479,3480],{},"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.",[12,3482,3483],{},"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.",[12,3485,3486],{},"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.",[12,3488,3489],{},"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.",[1113,3491,3493],{"id":3492},"the-raps-trap","The RAPS Trap",[12,3495,3496],{},"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.",[12,3498,3499],{},"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.",[19,3501,3503],{"id":3502},"the-validation-workflow-gaps-most-pace-plans-have","The Validation Workflow Gaps Most PACE Plans Have",[12,3505,3506],{},"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.",[12,3508,3509],{},"Most PACE organizations are missing three things:",[12,3511,3512,3515],{},[29,3513,3514],{},"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.",[12,3517,3518,3521],{},[29,3519,3520],{},"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.",[12,3523,3524,3527],{},[29,3525,3526],{},"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.",[19,3529,3531],{"id":3530},"what-a-compliant-submission-process-looks-like","What a Compliant Submission Process Looks Like",[12,3533,3534],{},"A PACE organization with a defensible encounter data submission workflow has several things in place that most currently don't.",[12,3536,3537,3540],{},[29,3538,3539],{},"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.",[12,3542,3543,3546],{},[29,3544,3545],{},"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.",[12,3548,3549,3552],{},[29,3550,3551],{},"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.",[12,3554,3555,3558],{},[29,3556,3557],{},"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.",[12,3560,3561,3564],{},[29,3562,3563],{},"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.",[19,3566,3568],{"id":3567},"the-timeline-and-what-it-means-for-data-collection-now","The Timeline and What It Means for Data Collection Now",[12,3570,3571],{},"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.",[12,3573,3574],{},"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.",[12,3576,3577],{},"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.",[12,3579,3580],{},"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.",[158,3582],{},[12,3584,3585],{},[163,3586,3587,3588,3591,3592,3594],{},"If your organization is working through encounter data submission gaps or preparing for the risk adjustment model transition, ",[167,3589,3590],{"href":2256},"Ayin's encounter data services"," are built specifically for PACE and Medicare Advantage plans — or ",[167,3593,178],{"href":534}," to talk through where your current workflow stands.",{"title":181,"searchDepth":182,"depth":182,"links":3596},[3597,3599,3600,3603,3604,3605],{"id":3452,"depth":182,"text":3598},"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":3463,"depth":182,"text":3464},{"id":3476,"depth":182,"text":3477,"children":3601},[3602],{"id":3492,"depth":1272,"text":3493},{"id":3502,"depth":182,"text":3503},{"id":3530,"depth":182,"text":3531},{"id":3567,"depth":182,"text":3568},{},"\u002Farticles\u002Fpace-encounter-data-compliance",{"description":181},"articles\u002Fpace-encounter-data-compliance","sABN2Qoj3TRdmUGPqbH9l608URVmd2PPWcjTMrQzZBg",1790973089386]