Skip to content

When regulatory change hits your bottom line.

Six-month Medi-Cal redeterminations start December 31, 2026. Roughly two million California members are at risk of losing coverage, most of them for paperwork reasons, not eligibility reasons. Every one is a patient who stops showing up and a claim that never gets paid.

We codify redetermination and CalAIM billing requirements into a deterministic rules engine that checks every patient record before a renewal date passes or a claim goes out. Your team gets a prioritized list of what needs attention, and why, in plain language.

The deadline is fixed. The paperwork is not.

  • Dec 31, 2026Six-month redeterminations begin, no option to delay
  • ~2MMedi-Cal members at risk of losing coverage
  • 74%Of prior disenrollments were procedural, not eligibility
  • 2×The administrative surface area, starting immediately

Under H.R. 1, Medicaid expansion adults move from annual to six-month eligibility renewals effective December 31, 2026. California DHCS published its implementation plan in January 2026. There is no state option to delay this provision.

For behavioral health providers and FQHCs, this doubles the number of times each year a patient can fall out of coverage because a form did not get returned, and the population least equipped to manage paperwork is the population you serve.

Sources: H.R. 1 §71107; CMS SMD #26-001; California DHCS H.R. 1 Implementation Plan (January 30, 2026).

Three places revenue leaks, and none of them are clinical.

  1. 01

    The renewal nobody tracked

    A patient’s redetermination date passes. Nobody flagged it. Nobody knew their address on file was stale. Coverage lapses mid-treatment, the patient stops coming, and sessions you already delivered become unbillable.

  2. 02

    The claim that was almost right

    The ECM documentation was thorough. The care coordination happened. But the modifier did not match the managed-care plan’s requirement, and the claim came back denied weeks later, when reworking it costs more than it recovers.

  3. 03

    The audit you can’t answer

    DHCS asks how a service met medical necessity. The documentation exists somewhere across three systems and a shared drive. Assembling the answer takes a week of staff time you did not budget.

A rules engine for the requirements. A copilot for your team.

We take the requirements your organization actually operates under (H.R. 1 redetermination rules, CalAIM ECM and Community Supports billing standards, and your managed-care plan’s specific modifier requirements) and codify them into deterministic rules that evaluate every record before it matters.

01

Redetermination risk monitoring

Every patient scored against their renewal date, contact information currency and documentation completeness. Your care coordination team gets a weekly prioritized outreach list: who needs attention, what is missing and how many days remain.

02

Pre-submission claim evaluation

Every claim checked against the documentation, coding and modifier requirements for that service, that payer and that program, before it is submitted, not after it is denied.

03

Plain-language guidance

When something fails a check, your billing specialist sees what failed, why it matters and the steps to fix it, with a citation to the exact DHCS or plan requirement behind it. No decoder ring required.

04

An audit trail that already exists

Every evaluation is timestamped and immutable. When DHCS or a managed-care plan asks how a determination was made, the answer is already assembled: data, rule, reasoning step, outcome.

Built for the organizations carrying the most exposure.

  • Behavioral health providers

    SUD treatment programs, outpatient mental health practices and community behavioral health agencies where Medi-Cal is the majority of revenue. Your patients are disproportionately affected by redetermination churn, and CalAIM documentation requirements are the most complex in the state.

  • Federally Qualified Health Centers

    FQHCs managing renewal navigation across large patient panels, with community health worker teams doing it patient by patient. We turn that into a systematic, prioritized weekly workflow.

  • County and managed-care behavioral health plans

    Organizations responsible for network-wide compliance performance, where a provider’s documentation gap becomes your DHCS contract problem.

Luveo HealthEnterprise pharmacy operations platform

Different regulations. Same architecture.

For Luveo Health we codified 28 compliance rules across 7 operational workflows (DEA, DSCSA, HIPAA, USP 797 and state Board of Pharmacy) and layered a governed copilot that translated every outcome into cited, plain-language guidance for pharmacy technicians.

Across a 30-scenario structured evaluation: zero hallucinated rule keys, zero fabricated regulatory citations and zero guardrail violations. Delivered in two four-week cycles.

Read the case study →
  • 28Compliance rules codified
  • 97%Explanation accuracy · 100% on chat
  • 0Fabricated citations
  • 35/sEvents validated under load

Reasonable questions.

We already have a billing company. Doesn’t this overlap?
Your billing company submits claims. This evaluates whether a claim will survive submission before it goes out, and whether a patient’s record supports continued eligibility before their renewal date. Most billing partners welcome it: fewer denials to rework is good for both of you.
Our documentation is already good. Is this solving a real problem?
Documentation quality and documentation compliance are different problems. A thorough note can still fail a plan-specific modifier requirement. The question is not whether your clinicians document well; it is whether anything systematically checks that documentation against the requirement for that specific claim, payer and program.
Does this touch PHI?
Yes, and it is built for that. We execute a BAA before any data access, work in isolated environments in your cloud, and tokenize PHI at the ingestion boundary so protected data never reaches the AI layer directly. More on security & PHI →
December 2026 is close. Is four weeks realistic?
That is exactly why the cycle is four weeks. A cycle started this quarter is in production well before the first six-month renewal wave. A cycle started in November is not.

Find out in 30 minutes whether this fits.

If we can scope it into a four-week cycle, we will tell you exactly what that includes and what it costs. If we cannot, we will tell you that too.

Book a 30-minute scoping call →
  1. We’ll ask three questions
  2. 01Which workflow is leaking?
  3. 02What data sits behind it?
  4. 03What does “fixed” look like to you?