Why Home Care Software Built for All 50 States Doesn’t Work for Your State

Home care agencies billing through state Medicaid programs operate under rules that are anything but uniform. The 21st Century Cures Act set federal EVV standards. Everything below that floor is up to the states. Arizona ALTCS runs differently from California IHSS, which runs differently from New York CDPAP. The rules around visit authorization, billing cycles, documentation requirements, and EVV vendor approval vary by program.

Most home care software platforms are built to work in all 50 states. That sounds like a strength. In practice, it means the platform is optimized for the common case and leaves the state-specific edge cases for you to handle manually.

What “Built for All 50 States” Actually Means

When a software vendor says their platform works nationwide, they mean it meets federal minimum requirements. It captures the six EVV data points. It generates the standard billing codes. It stores records securely.

What it doesn’t mean is that the platform is configured for how your state program actually runs. Arizona ALTCS has specific rules around who qualifies as a service provider, how visits must be authorized, and which EVV vendors the state accepts. California IHSS has its own rules around timesheets, overtime, and state payroll. CDPAP in New York treats the care recipient as the employer of record, which creates a completely different workflow structure.

None of these are obscure edge cases. They’re the core workflows of those programs. When your platform isn’t built around them, your staff builds workarounds. You hire people to bridge the gap.

The Hidden Cost of Generic Compliance

Generic platforms rarely advertise what they can’t do. The gap shows up in implementation. Your team spends weeks configuring the platform to match your state’s requirements, only to find certain workflows can’t be replicated. You end up with a hybrid approach: some processes in the software, some in spreadsheets, some in email.

For agencies with 100 or more caregivers billing through Medicaid, workflow gaps create direct revenue risk. Missed EVV data points mean rejected claims. Incomplete authorization tracking means audit exposure. Non-standard documentation means compliance risk during state reviews.

What a Configurable Platform Does Differently

Knack Health gives you the building blocks to construct the workflows your state program requires. If Arizona ALTCS requires a specific approval chain before a visit can be billed, you build that chain. If your state’s EVV rules require a specific data export format, you configure the export.

The security and compliance layer is handled for you: HIPAA-ready hosting, encrypted data, role-based access, and a signed BAA for covered entities. The operational logic is yours to define.

Knack Health home care platform → 

This is a meaningful distinction for agencies that have tried to force a generic platform to match their state’s rules. You’re not asking a vendor to build a state-specific module. You’re building it yourself, on infrastructure that meets every federal and state security requirement.

The Reseller Opportunity

There’s a secondary benefit worth noting. Agencies that build state-specific workflows for Arizona ALTCS, California IHSS, or other programs often discover they’ve created something valuable beyond their own operation. The system they built solves the same problem that every other agency in that state is dealing with.

Knack’s partner program lets agencies package and offer that solution to other operators in the same state, creating a revenue stream built on the operational investment they already made.

Knack Health partner program → 

Build your state-specific Medicaid workflows on Knack HealthKnack Health is a HIPAA-compliant platform built for home care agencies that need more than generic software provides. EVV workflows, multi-role portals, caregiver credentialing, guardian approval, and flat-rate pricing with no per-user fees. Learn more →

Home Care State Medicaid Software FAQs

Does every home care agency need state-specific software?

Not necessarily. Agencies doing purely private-pay non-medical care with straightforward workflows can often run on a generic platform. The need for state-specific configuration becomes significant when you’re billing through Medicaid, operating under a specific state program like ALTCS, IHSS, or CDPAP, or dealing with authorization workflows that vary by program type.

What’s the difference between EVV compliance and state-specific EVV compliance?

Federal EVV requirements specify six data points that must be captured at every qualifying visit: who provided care, who received it, what service was delivered, the location, the date, and the start and end times. State programs add requirements on top: which EVV vendors are approved, how the data must be transmitted, how visit verification connects to billing, and how exceptions are handled. A platform that’s federally compliant may not match your state’s transmission requirements.

Can Knack Health really be configured to match a specific state’s Medicaid rules?

Yes, with caveats. Knack Health lets you build the operational workflows that match your state’s requirements: intake, authorization, EVV data capture, billing export, reporting. It doesn’t handle Medicaid billing submission natively in most cases. Many agencies use Knack Health for operations and connect it to a billing-specific tool for claim submission. The two complement each other.

Talk to Knack Health about your state program → 

What does it cost to build a state-specific system on Knack Health?

Knack Health HIPAA plans start at $625 per month, flat-rate regardless of user count. Dedicated home care software for agencies with 100 or more users typically runs several thousand dollars a month on per-user pricing. The tradeoff is build time: you’ll spend more time on initial setup. For most agencies, the math still favors the configurable approach at scale.