Tennessee home-care margin recovery: when the visit is real and CareBridge never let the claim build.

Tennessee runs its home-care benefit in a way that puts a checkpoint in front of the claim rather than behind it. TennCare delivers long-term services and supports entirely through managed care, so there is no fee-for-service path to fall back on. Personal and attendant care reach members through the CHOICES programs, and every member sits with one of three managed-care organizations. On top of that, since August 2025 the state routes EVV through a single aggregator that validates the visit before the claim is allowed to build at all. A visit that does not pass that pre-billing check never becomes a claim, which means it never shows up in your denied bucket. It just quietly fails to exist.

This page is about where that money leaks in Tennessee specifically, and why catching it means reading your CareBridge visit data against the authorization rather than trusting that a delivered visit turned into a paid claim.

Managed care, three plans, one CareBridge aggregator

Because TennCare is fully managed care, an agency in Tennessee is not billing the state directly. It is billing whichever managed-care organization the member belongs to: BlueCare, UnitedHealthcare Community Plan, or Wellpoint. Each plan carries its own authorization process and service-coordinator workflow, so an agency contracted across all three is reconciling three rule sets at once.

What ties them together on the EVV side is CareBridge. Effective August 1, 2025, TennCare, its MCOs, and CareBridge implemented an Open EVV Model for personal care services. An agency can use CareBridge's own EVV at no cost, or it can run a third-party EVV vendor that integrates with CareBridge as the shared aggregator. So there is one aggregator across all three plans, but each plan still owns its own authorizations, and the visit has to reconcile to the right one.

Pre-billing validation: the claim that never gets built

Here is the Tennessee-specific mechanism, and it is different from a back-end denial. CareBridge runs pre-billing validation. When it receives visit data, it compares that data against the member and authorization information it gets from the MCO and state partners, and it returns a response file listing the validation errors that must be corrected before the visit can be submitted for claims. The claim does not build until the visit passes.

That changes where the money hides. In a back-end model, you see a denial on a remittance and you can work it. In Tennessee, a visit that fails pre-billing validation does not produce a denial, because it never reached the payer as a claim. It sits in an error file. If nobody clears that file, the visit ages out silently, and on a 120-day filing clock the window to fix it is short. Tennessee also requires GPS coordinates on at least 90 percent of scheduled services submitted for payment to keep an acceptable compliance score, so visits with location gaps create their own exposure. The state publishes the validation mechanism and that compliance metric rather than a single tidy denial code, so the way to find these is to reconcile the visit data, not to wait for a remittance reason.

Where the margin actually leaks in Tennessee

From the way Tennessee wires managed care, CareBridge, and pre-billing validation together, the recoverable losses cluster in a few predictable places:

• Visits stuck in pre-billing validation. Delivered visits that failed the CareBridge check and never became claims. This is the most Tennessee-specific leak, because it never appears in a denial report.
• No matching accepted EVV record. Claims rejected because the EVV visit did not reconcile to the claim on service code, date, member, or authorization.
• Plan-by-plan authorization mismatches. The same agency reconciling against BlueCare, UnitedHealthcare, and Wellpoint authorizations, each with its own process, so a visit can be fine for one plan's rules and out of bounds for another.
• GPS and compliance-score gaps. Visits missing location data that drag the compliance score below the threshold and put payment at risk.
• Silent underpayments. Claims that pay below the contracted amount, never flagged as a denial, visible only when payment received is compared against payment expected, line by line.

None of these are visible from inside the scheduling view. The schedule says the visit happened. The EVV system says the caregiver clocked in. It is only when you reconcile the CareBridge visit data against the authorization and the paid claims that the gap appears.

Why a read-only recovery layer is the right tool for this

Reeve sits read-only over whatever EMR and EVV export an agency already runs, whether that is WellSky, AxisCare, HHAeXchange, AlayaCare, or anything else, and compares what was delivered with what was authorized and what was actually paid. For a Tennessee agency, that means lining up the CareBridge visit data, the claim lines, and the plan authorizations, then surfacing every place they fail to reconcile: the visits stuck in pre-billing validation, the unmatched EVV records, the plan-by-plan authorization mismatches, and the silent underpayments.

Because Reeve is read-only and neutral across every EMR, it never writes to your billing workflow without your control, and it has no reason to look past a finding that implicates a billing module. It hands you a ranked list of recoverable dollars with the reason attached. The ones still inside the 120-day window are the ones you can rebill now, and in Tennessee that window closes fast.

This is the same engine described across the rest of the site. For the broader map of revenue loss in home care, see where home-care margin leaks. For the filing-window side specifically, see home-care timely filing limits. For the full playbook on getting uncollected revenue back, see home care revenue recovery.

What the free Tennessee Margin Teardown does

The way to find out whether CareBridge pre-billing validation and plan authorization mismatches are draining your margin is to look at a real, de-identified slice of your own data, before you spend a dollar. The Margin Teardown is a one-time, read-only read of where margin is leaking in your book: the stuck visits, the unmatched EVV records, the authorization gaps, and the underpayments. It is free, and it is yours to keep whether or not you ever work with Reeve. It carries the same 3×-or-free guarantee the rest of the engine does. If Reeve does not surface at least three times its monthly fee in recoverable margin you agree is real, you do not pay.