<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Implementation Challenges on Syam Adusumilli</title>
    <link>https://syamadusumilli.com/mrwr/series-13/</link>
    <description>Recent content in Implementation Challenges on Syam Adusumilli</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <copyright>© 2026 Syam Adusumilli</copyright>
    <lastBuildDate>Sun, 15 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://syamadusumilli.com/mrwr/series-13/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>The Documentation Gap</title>
      <link>https://syamadusumilli.com/mrwr/series-13/the-documentation-gap/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/the-documentation-gap/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Syam Adusumilli&lt;/strong&gt;&lt;br&gt;&#xA;&lt;em&gt;Chief Evangelist, GroundGame.Health&lt;/em&gt;&lt;/p&gt;&#xA;&#xA;&lt;h2 class=&#34;relative group&#34;&gt;The Shift That Never Starts&#xA;    &lt;div id=&#34;the-shift-that-never-starts&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;&#xA;    &#xA;    &lt;span&#xA;        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none&#34;&gt;&#xA;        &lt;a class=&#34;text-primary-300 dark:text-neutral-700 !no-underline&#34; href=&#34;#the-shift-that-never-starts&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;&#xA;    &lt;/span&gt;&#xA;    &#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Darnell Williams clocks in at 6:47 AM at the Wendy&amp;rsquo;s on Martin Luther King Boulevard, thirteen minutes before his shift officially begins because that&amp;rsquo;s when the morning manager needs help prepping the breakfast station. He&amp;rsquo;ll work until 2:00 PM, then walk three blocks to the Burger King on Commerce Street, where he picks up another five hours most days, sometimes six when someone calls in sick. Between the two jobs, he averages 35 to 40 hours per week. Sometimes more.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Summary: The Documentation Gap</title>
      <link>https://syamadusumilli.com/mrwr/series-13/the-documentation-gap-summary/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/the-documentation-gap-summary/</guid>
      <description>&lt;p&gt;Work requirements function primarily as documentation challenges rather than employment incentives. Arkansas 2018 data revealed that 97 percent of people who lost coverage were already working or qualified for exemptions, while the policy produced zero measurable increase in employment. The gap between what people are doing and what they can prove they are doing will determine whether work requirements under the One Big Beautiful Bill Act function as neutral verification or as barriers that transform working people into coverage casualties. For the 18.5 million expansion adults facing requirements beginning December 2026, documentation capacity rather than work activity will be the decisive factor in who keeps healthcare coverage.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>When December 2026 Won&#39;t Work</title>
      <link>https://syamadusumilli.com/mrwr/series-13/when-december-2026-wont-work/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/when-december-2026-wont-work/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Syam Adusumilli&lt;/strong&gt;&lt;br&gt;&#xA;&lt;em&gt;Chief Evangelist, GroundGame.Health&lt;/em&gt;&lt;/p&gt;&#xA;&#xA;&lt;h2 class=&#34;relative group&#34;&gt;The Timeline That Doesn&amp;rsquo;t Add Up&#xA;    &lt;div id=&#34;the-timeline-that-doesnt-add-up&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;&#xA;    &#xA;    &lt;span&#xA;        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none&#34;&gt;&#xA;        &lt;a class=&#34;text-primary-300 dark:text-neutral-700 !no-underline&#34; href=&#34;#the-timeline-that-doesnt-add-up&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;&#xA;    &lt;/span&gt;&#xA;    &#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Dr. Sandra Chen stares at the Gantt chart on her office wall, running her finger along the colored bars that represent her state&amp;rsquo;s work requirement implementation timeline. She&amp;rsquo;s been the Medicaid Director for six years, long enough to know the difference between aggressive timelines and impossible ones. This one is impossible.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Summary: When December 2026 Won&#39;t Work</title>
      <link>https://syamadusumilli.com/mrwr/series-13/when-december-2026-wont-work-summary/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/when-december-2026-wont-work-summary/</guid>
      <description>&lt;p&gt;The December 31, 2026 implementation deadline for Medicaid work requirements is unrealistic for a significant number of states. Major Medicaid IT procurements typically require 18 to 24 months from planning to deployment. States that began procurement in January 2026 face mid-2028 delivery under normal timelines. States that waited for CMS guidance before beginning face 2029 or later. The statute provides a pressure release valve allowing extensions up to December 31, 2028, but requesting an extension carries political implications that shape state behavior in ways that may not serve member interests. How states navigate the gap between the deadline and their actual readiness will determine whether 18.5 million expansion adults encounter functional systems or hastily assembled ones that produce the same documentation failures Arkansas experienced.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Article 13C: Behavioral Economics of Compliance</title>
      <link>https://syamadusumilli.com/mrwr/series-13/article-13c-behavioral-economics-of-compliance/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/article-13c-behavioral-economics-of-compliance/</guid>
      <description>&lt;p&gt;&lt;em&gt;Series 13: Special Topics in Work Requirements Implementation&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Opening Vignette: Maria&amp;rsquo;s Intention&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Maria has the documents. She knows the deadline. She has every intention of submitting her work verification by the 15th.&lt;/p&gt;&#xA;&lt;p&gt;She works Tuesday through Saturday at a hotel cleaning rooms. The hours vary, but she consistently hits 80-plus per month. Her employer provides pay stubs. She photographs them on her phone each payday. The submission portal is bookmarked. She has done this before.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Summary: Article 13C: Behavioral Economics of Compliance</title>
      <link>https://syamadusumilli.com/mrwr/series-13/article-13c-behavioral-economics-of-compliance-summary/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/article-13c-behavioral-economics-of-compliance-summary/</guid>
      <description>&lt;p&gt;Work requirement systems are designed as if people make decisions through rational cost-benefit analysis, weigh future consequences against present demands, and translate good intentions into timely action. Decades of behavioral science research demonstrate that none of these assumptions hold, particularly for populations under economic stress. The intention-action gap, where people consistently fail to do things they genuinely intend to do, is not a character flaw. It is a well-documented feature of human cognition that current compliance systems ignore entirely. Peter Gollwitzer&amp;rsquo;s research shows that people with strong goals fail to achieve them roughly half the time. When that failure rate is built into a healthcare system, the result is predictable: coverage loss among people who were working, had the documents, and intended to comply but could not close the gap between intention and action.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Article 13D: Gaming, Fraud, and Program Integrity</title>
      <link>https://syamadusumilli.com/mrwr/series-13/article-13d-gaming-fraud-and-program-integrity/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/article-13d-gaming-fraud-and-program-integrity/</guid>
      <description>&lt;p&gt;&lt;em&gt;Series 13: Special Topics in Work Requirements Implementation&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Opening Vignette: Three Cases on Jennifer&amp;rsquo;s Desk&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Jennifer has been a program integrity analyst for the state Medicaid agency for eleven years. This morning she has three flagged cases waiting for review. The fraud detection system treats all three the same way: probable cause for investigation, benefits suspended pending resolution.&lt;/p&gt;&#xA;&lt;p&gt;The first case is obvious. The system detected 47 separate work verification submissions originating from the same IP address within a six-hour window. The names are different, the employers are different, the documents look superficially different. But the metadata reveals they were created using the same software template, uploaded sequentially, and submitted by someone who forgot to mask their location. This is a document mill, someone selling verification services to people who cannot obtain legitimate documentation or who want to avoid work requirements entirely. Jennifer refers it to the fraud investigation unit with confidence.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Summary: Article 13D: Gaming, Fraud, and Program Integrity</title>
      <link>https://syamadusumilli.com/mrwr/series-13/article-13d-gaming-fraud-and-program-integrity-summary/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/article-13d-gaming-fraud-and-program-integrity-summary/</guid>
      <description>&lt;p&gt;Program integrity in work requirement systems faces a fundamental challenge: fraud and documentation failure produce identical administrative outcomes. A person whose work hours cannot be verified might be committing fraud by claiming hours they did not work, or they might be working exactly as claimed but unable to prove it. The verification system sees the same thing. The 2024 Medicaid improper payment rate was 5.09 percent, but 79 percent of those improper payments resulted from insufficient documentation rather than ineligibility or fraud. Systems calibrated to an imaginary epidemic of fraud will necessarily impose burdens on compliant populations that exceed any plausible fraud prevention benefit. For the 18.5 million expansion adults facing work requirements, the question is not whether fraud exists but whether anti-fraud measures will harm more eligible people than they protect.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Article 13E: Four Work Requirements, One Person</title>
      <link>https://syamadusumilli.com/mrwr/series-13/article-13e-four-work-requirements-one-person/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/article-13e-four-work-requirements-one-person/</guid>
      <description>&lt;h3 class=&#34;relative group&#34;&gt;Opening: Keisha&amp;rsquo;s Monthly Compliance Calendar&#xA;    &lt;div id=&#34;opening-keishas-monthly-compliance-calendar&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;&#xA;    &#xA;    &lt;span&#xA;        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none&#34;&gt;&#xA;        &lt;a class=&#34;text-primary-300 dark:text-neutral-700 !no-underline&#34; href=&#34;#opening-keishas-monthly-compliance-calendar&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;&#xA;    &lt;/span&gt;&#xA;    &#xA;&lt;/h3&gt;&#xA;&lt;p&gt;Keisha Davis maintains a spiral notebook with color-coded tabs. Blue for Medicaid. Green for SNAP. Yellow for childcare. Orange for her Section 8 housing voucher. Each section contains deadlines, documentation requirements, and contact numbers for caseworkers who never seem to be the same person twice.&lt;/p&gt;&#xA;&lt;p&gt;This month, her compliance schedule looks like this: By the 10th, she needs to submit her work verification to the housing authority, which wants employer letters on company letterhead confirming her hours for the past quarter. By the 15th, her SNAP recertification is due, requiring pay stubs from the last 30 days and a new statement about any changes in household composition. By the 20th, she must verify her childcare subsidy eligibility by providing her work schedule for the coming month, even though her manager rarely posts schedules more than a week in advance. And now, starting December 2026, Medicaid will require monthly verification of 80 hours of work or qualifying activities, with its own documentation standards and submission portal.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Summary: Article 13E: Four Work Requirements, One Person</title>
      <link>https://syamadusumilli.com/mrwr/series-13/article-13e-four-work-requirements-one-person-summary/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/article-13e-four-work-requirements-one-person-summary/</guid>
      <description>&lt;p&gt;A home health aide earning $14.50 an hour who receives SNAP, childcare subsidies, Section 8 housing, and Medicaid currently spends roughly eight hours each month proving she works so she can continue receiving the assistance that allows her to work. That is a full workday consumed by compliance, nearly equivalent to what she loses from her paycheck for taxes. Beginning December 2026, Medicaid work requirements add a fifth layer to what is already an unsustainable patchwork of duplicative verification obligations administered by four different federal agencies through four different state counterparts, each with its own rules, documentation standards, reporting cycles, and caseworkers. The people least equipped to manage administrative complexity face the most administrative complexity, and a missed deadline in one program can cascade across the entire safety net.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Article 13F: Technology Vendor Landscape</title>
      <link>https://syamadusumilli.com/mrwr/series-13/article-13f-technology-vendor-landscape/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/article-13f-technology-vendor-landscape/</guid>
      <description>&lt;p&gt;&lt;em&gt;Series 13: Special Topics&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;The spreadsheet on Janet Chen&amp;rsquo;s desk told a story of impossible arithmetic. As North Carolina&amp;rsquo;s Deputy Director for Medicaid Operations, she had spent three months assembling responses to the state&amp;rsquo;s Request for Information about work requirement verification systems. Three vendor categories had emerged, each with compelling arguments and disqualifying weaknesses.&lt;/p&gt;&#xA;&lt;p&gt;The incumbent eligibility system vendor, a major consultancy that had built the state&amp;rsquo;s current MMIS over a decade of incremental development, proposed a bolt-on module. Their pitch emphasized seamless integration with existing systems, established relationships with state IT staff, and proven experience navigating CMS certification requirements. The price: $47 million over five years, with a 24-month implementation timeline that would deliver the system three months before December 2026. Janet had been in government long enough to know that 24-month estimates typically became 30 months in practice, meaning they would likely miss the federal deadline.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Summary: Article 13F: Technology Vendor Landscape</title>
      <link>https://syamadusumilli.com/mrwr/series-13/article-13f-technology-vendor-landscape-summary/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/article-13f-technology-vendor-landscape-summary/</guid>
      <description>&lt;p&gt;No vendor category in the work requirement technology market offers both deep state implementation experience and purpose-built verification capability. States face a fragmented landscape where eligibility system incumbents understand government procurement but have troubled track records, SDOH platforms excel at member engagement but lack state integration experience, and specialized startups have purpose-built solutions but limited financial stability and customer bases. The $100 million Congress allocated for all fifty states to build verification systems roughly equals what Georgia spent to serve fewer than 8,000 enrollees. With procurement timelines of eight to fourteen months from initiation to signed contract, states that have not yet begun face near-certain deadline violations for December 2026.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Article 13G: The Marketplace Fallback Problem</title>
      <link>https://syamadusumilli.com/mrwr/series-13/article-13g-the-marketplace-fallback-problem/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/article-13g-the-marketplace-fallback-problem/</guid>
      <description>&lt;p&gt;Latisha reviews her options on healthcare.gov for the third time, hoping the numbers will somehow change. Three weeks ago, she lost Medicaid coverage after missing a work verification deadline during her daughter&amp;rsquo;s hospitalization. She had been working her usual 30 hours at the nursing home, but the chaos of caring for a sick child meant the verification documents sat unopened on the kitchen counter. Now she faces a coverage gap of her own.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Summary: Article 13G: The Marketplace Fallback Problem</title>
      <link>https://syamadusumilli.com/mrwr/series-13/article-13g-the-marketplace-fallback-problem-summary/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/article-13g-the-marketplace-fallback-problem-summary/</guid>
      <description>&lt;p&gt;Section 71119 of the One Big Beautiful Bill Act specifies that individuals who lose Medicaid eligibility due to failure to meet community engagement requirements are ineligible for premium tax credits on the ACA marketplace. This provision closes the coverage escape hatch for 18.5 million expansion adults, converting the marketplace from a bridge between coverage types into a dead end. A 40-year-old individual at 138 percent of the federal poverty level, earning approximately $20,800 annually, faces unsubsidized benchmark silver plan premiums of $500 to $650 monthly, consuming 30 to 40 percent of gross income before any healthcare is received. No rational economic actor makes this choice. The coverage is nominally available but functionally inaccessible, and CBO projections suggest work requirements will reduce Medicaid enrollment by 8 to 10 million over the decade following implementation, with most losses triggering this premium tax credit exclusion.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Series 13 Synthesis: When Compliance Systems Meet Implementation Reality</title>
      <link>https://syamadusumilli.com/mrwr/series-13/series-13-synthesis-when-compliance-systems-meet-implementation-reality/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/series-13-synthesis-when-compliance-systems-meet-implementation-reality/</guid>
      <description>&lt;p&gt;The seven articles in Series 13 were written to address &amp;ldquo;special topics&amp;rdquo; in work requirements implementation. What emerged instead was documentation of how policies designed on whiteboards collide with administrative realities that whiteboard models cannot capture. Each article examines a different fracture point where policy intent meets implementation capacity, and each reveals the same pattern: systems designed to verify compliance become systems that prevent compliance, not through malice but through structural mismatch between what the policy assumes and what the populations it affects can actually navigate.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Summary: Series 13 Synthesis: When Compliance Systems Meet Implementation Reality</title>
      <link>https://syamadusumilli.com/mrwr/series-13/series-13-synthesis-when-compliance-systems-meet-implementation-reality-summary/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://syamadusumilli.com/mrwr/series-13/series-13-synthesis-when-compliance-systems-meet-implementation-reality-summary/</guid>
      <description>&lt;p&gt;Series 13 set out to examine special topics in work requirements implementation. What emerged instead was documentation of a consistent pattern across seven different fracture points: systems designed to verify compliance become systems that prevent compliance, not through malice but through structural mismatch between what the policy assumes and what the populations it affects can actually navigate. The administrative architecture chosen by each state will determine outcomes far more than the policy goals motivating implementation. States can pursue identical policy objectives through systems generating 10 percent coverage loss or 30 percent coverage loss depending on verification design, navigation investment, technology choices, exemption pathways, and deadline flexibility. The debate over whether work requirements are justified policy turns out to be secondary to the administrative questions that determine who keeps coverage and who loses it.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
