For Minnesota CFSS agencies
Every verified visit becomes a paid claim.
MinnAI puts scheduling, EVV, care notes, MHCP billing and payroll in one place, so the hours your support workers log are the hours you bill and the hours you pay. Built in Minnesota for the CFSS transition. We do the switch with you, in 30 days.
- Built for CFSS
- We do the switch with you, in 30 days
- Founding agency pricing, locked for [24] months
Already a customer? Sign in.
What a broken visit costs
A denied claim is not a billing problem. It is a cash flow problem.
Every unresolved visit is work your caregivers already did, sitting in a queue instead of in your account.
30 days
The window Minnesota Health Care Programs has to process a clean claim. A claim that comes back unclean starts that clock over.
Source: Minnesota DHS, MHCP Provider Manual
Every visit
Minnesota designates HHAeXchange as its EVV aggregator. A personal care visit needs a resolved record there before the claim can be processed.
Source: Minnesota DHS
After payment
DHS reviews EVV data post-payment. A claim that was already paid, but that the aggregator cannot support, can still be recouped.
Source: Minnesota DHS
These describe how Minnesota Medicaid works. They are not MinnAI performance figures. We do not publish results we cannot show you in your own data.
How the money arrives
Clean at the source, not corrected three weeks later.
Every visit passes the same six checks before it can become a claim. What fails does not go out. It lands in a queue with the reason attached to the visit that caused it.
EVV captured
In the mode this visit requires. Five modes, not one shape.
Signatures present
Caregiver and client, on the device at the point of care.
Authorization live
On the date of service. Not live today, live on the day the work happened.
Client eligible
Checked against the payer before the claim is built.
Unit limits
Per day and per week, enforced when the shift is scheduled.
The 8-minute rule
A visit too short to bill is caught here, not in a remittance file.
Ready to bill
Everything that passed. Generate and submit the batch to HHAeXchange without opening a spreadsheet.
Not billable, with the reason
Everything that did not, each item naming the check it failed and linking to the visit that caused it. Fix it while the caregiver still remembers the shift.
The console
One tenant, four screens, no export in between.
Scheduling, EVV, care plans, credentials, billing and reporting in one database behind one permission model.
Who it's for
The same record, whichever chair you sit in.
The owner
“Am I getting paid for last week, and what is at risk?”
- Unbilled visit alerts
- Authorization utilization
- Expiry at 90, 60 and 30 days
The scheduler
“Who can cover Tuesday, and are they still credentialed?”
- Swimlane week grid
- Conflicts flagged as you assign
- An expired credential blocks it
The QP
“Is the care plan current, signed, and matched to the authorization?”
- Versioned care plans
- Signed on the device
- Documents virus-scanned
Billing
“What can go out today, and why did that one come back?”
- Ready-to-bill queue
- Denials by reason code
- Payment reconciliation
Why now
The CFSS transition is a billing change before it is a software change.
Three dates, in the order they hit your revenue.
In force now
EVV is a condition of payment
A personal care visit without conformant EVV data is not a billable visit. Minnesota routes all of it through HHAeXchange to MMIS.
September 30, 2026
Extended PCA services end
An agency still running on PCA needs its CFSS billing working, not planned.
September 30, 2027
The CFSS transition closes
Two employment models, new authorization formats, and banked hours that roll forward inside an authorization period.
The person doing the clock-in
A failed clock-in is an unbilled visit.
Your EVV users are caregivers in their sixties and seventies. If the clock-in screen needs training, the visit does not get verified, and an unverified visit does not get paid.
16px body text on mobile
With a 13px floor, and it survives the system font set to Large without truncating a primary action.
48dp minimum touch targets
56 for the button that starts a shift.
Mobile body text clears 7:1
A floor set for a cheap Android screen in direct sunlight, not an office monitor.
Every colour pair is measured
By a test that fails the build below 4.5:1, in both themes, on every commit.
Getting started
Parallel billing, then live.
You will not get a login and a help center. You get a person on the phone and a 30-day plan. Here is exactly what we commit to.
Week 1
Your data comes over.
Clients, workers, authorizations and service codes, checked with you line by line.
Week 2
Your workers learn it in one visit.
On their own phones, on the shifts they already have booked.
Week 3
We bill one cycle in parallel.
Old process and MinnAI side by side, compared claim by claim.
Week 4
You go live when the two agree.
Then we check in every day for 30 days, until you tell us to stop.
Security
Built for the review you hope never comes.
Client records stay in the United States, encrypted in transit and at rest. Access is limited by role, down to the individual worker. Every edit is stamped with who made it and when. Your data is yours. We do not sell it and we do not train on it.
- HIPAA-aligned safeguards
- BAA before any data
- HHAeXchange aggregator integration in progress
Founding agencies
Be one of our first five.
We are onboarding five Minnesota CFSS agencies this [fall]. Founding agencies get the switch done with them by the people who built MinnAI, pricing locked for [24] months, and a direct line to the team for a year. In return we ask for a 30-minute call every two weeks while we get it right.
Not ready to switch? Bring us one week of visits. We will show you what it should have collected.