Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Medicaid Data Matching topic
No spam. Unsubscribe anytime.
Kansas Medicaid officials outline data‑matching rules and move to CMS Equifax hub to cut costs
Summary
KDHE told the Committee on Welfare Reform it runs electronic checks across income, citizenship, assets and residency for Medicaid eligibility and will shift Equifax income feeds to a CMS hub to reduce per‑transaction costs; KDHE also described new CMS multis tate files and a GainWell pilot to detect out‑of‑state enrollments.
Christine Osterlin, deputy secretary for agency integration and Kansas' state Medicaid director, told the Committee on Welfare Reform that the state performs a broad set of electronic matches when determining Medicaid eligibility, including wages, identity and citizenship, bank accounts, Social Security records, mortality and residency.
Osterlin said Kansas uses the Social Security Administration to verify Social Security numbers, the CMS citizenship hub for U.S. citizen verification and the Verify Lawful Presence hub for eligible noncitizen statuses. "If we do not receive a data match or there is some discrepancy, they are granted a 90‑day reasonable opportunity period to clear that up," she said.
Why it matters: These matches determine whether applicants must supply paper documentation or can be approved electronically. Osterlin emphasized that federal rules require states to use electronic matches first and prohibit denying or terminating benefits solely on an electronic match; KDHE must contact the consumer and allow time to provide documentation before discontinuing coverage.
KDHE described two primary income data sources: an automated interface with the Kansas Department of Labor and income verification currently obtained from Equifax. Osterlin said Kansas will continue to use Equifax data but obtain it via a CMS "hub," which uses the same underlying Equifax records at a lower per‑transaction price. She gave the example that a transaction that rose to about $11.54 when contracted directly could cost $7.08 through the hub, estimating roughly $7.5 million in savings over three years at the lower rate.
Asked about data quality, Osterlin said the hub returns essentially the same records; the main technical difference is the hub requires a tax ID on the record, meaning a "minuscule" number of records might be omitted compared with the direct Equifax feed. KDOL matching will remain the state's initial check, she said.
Osterlin also described new CMS files the state now receives. One file, TM SysData, lists members potentially enrolled in multiple states; KDHE reported that as of late January it had reviewed 9,075 records: 3,918 were already off Kansas rolls, 1,405 were pending residency verification, 70 did not meet Kansas residency, 3,521 were verified as Kansas residents, and 50 had return mail and were ended when appropriate. Separately, CMS began sending an immigration file to flag individuals whose status may no longer qualify them for Medicaid; KDHE said a small share of discontinuances from these files reflected immigration status changes or worker error and some reflected nonresponses to verification requests.
KDHE is also pursuing a pilot with GainWell, the state's Medicaid system vendor, to perform near‑real‑time checks with Missouri and Oklahoma. "The hope is because of the amount of data GainWell has that this could become almost a nationwide and almost a real time check," Osterlin said; Kansas is approved and awaiting signatures from Missouri and Oklahoma before the pilot begins.
KDHE described internal quality controls including production and targeted audits, sandbox audits for new hires and the federal MEQC/PERM audit process. Osterlin reported Kansas' most recent PERM payment error rate was below 1% for the reporting cycle she cited.
The presentation included questions from multiple committee members about how verification interacts with SNAP/DCF records, whether untaxed tip income counts for verification (KDHE said it will seek CMS guidance but currently expects untaxed tips not to appear on tax‑based verification), and the state's ability to follow up when data matches lag due to reporting delays. KDHE said unemployment records are auto‑updated and that renewals use previously verified income in the state's KEY system; if a data match differs from the KEY record by more than 20% the state will require documentation.
The committee did not vote on policy proposals during the presentation; members requested additional written materials and data tables KDHE said it would provide.
