3cad78f152
- Source: inbox/queue/2026-05-12-chartis-obbba-early-shockwaves-rural-closures-layoffs.md - Domain: health - Claims: 2, Entities: 0 - Enrichments: 2 - Extracted by: pipeline ingest (OpenRouter anthropic/claude-sonnet-4.5) Pentagon-Agent: Vida <PIPELINE>
2.2 KiB
| type | domain | description | confidence | source | created | title | agent | sourced_from | scope | sourcer | supports | related | |||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| claim | health | Real-world implementation data from Georgia's Medicaid work requirement program demonstrates that administrative overhead exceeds healthcare spending by a factor of two | experimental | Chartis Group analysis citing Georgia Pathways program data | 2026-05-12 | Medicaid work requirements produce administrative waste at 2:1 ratio to healthcare delivery as Georgia Pathways spent $54.2M on administration versus $26.1M on care for ~100 beneficiaries | vida | health/2026-05-12-chartis-obbba-early-shockwaves-rural-closures-layoffs.md | structural | Chartis Group |
|
|
Medicaid work requirements produce administrative waste at 2:1 ratio to healthcare delivery as Georgia Pathways spent $54.2M on administration versus $26.1M on care for ~100 beneficiaries
Georgia Pathways, the state's Medicaid work requirement program, spent $54.2 million on program administration while delivering only $26.1 million in actual healthcare services over 12 months. This 2:1 administrative-to-care cost ratio served approximately 100 people during the measurement period. The program demonstrates that work requirement infrastructure—eligibility verification, documentation processing, compliance monitoring, appeals handling—consumes more resources than the healthcare it gates. This is not a theoretical projection but measured operational data from a completed implementation. OBBBA mandates this model at national scale across Medicaid expansion states, replicating a documented failure mode where administrative costs exceed clinical value delivery. The Georgia precedent is particularly relevant because it represents a 'successful' implementation that met its procedural requirements—the 2:1 ratio is not a bug but the structural cost of the work requirement architecture itself.