Home health ops · HCBS / EVV network platform
HHAeXchange
HHAeXchange connects homecare providers, payers, and caregivers for scheduling, EVV, visit confirmation, and Medicaid HCBS program integrity. It is a network platform, not a closed clinical agency EMR alone.
Strong fit
- Medicaid HCBS providers and MCOs that already sit inside HHAeXchange networks
- Agencies that need EVV confirmation, shift management, and payer connectivity together
- Programs measuring visit confirmation, compliance, and payment cycle time
Weak fit
- Medicare-only skilled home health shops outside HHAeXchange payer networks
- Buyers seeking a best-of-breed clinical EMR unrelated to Medicaid EVV rails
- Organizations that refuse to operate inside a payer-connected network model
Bottom line
HHAeXchange earns a Conditional for providers and payers already tied to Medicaid HCBS networks where the platform is the compliance and visit-confirmation rail. Outcomes matter when confirmed visits and cleaner payments move. Product strength is network connectivity more than a standalone clinical EMR story. Implementation friction rises when your payers and states are outside the network. Pricing is opaque. Score sits below pure agency EMR leaders because fit depends heavily on payer geography.
Score breakdown
Weights: Outcomes 35% · Product 30% · Implementation 20% · Pricing clarity 15%.
HHAeXchange connects homecare providers, payers, and caregivers around scheduling, EVV, visit confirmation, and program integrity for home and community-based services.
It is a different buy than a closed agency EMR like Alora or KanTime. Many agencies encounter it because Medicaid plans and states already run on the network.
Conditional score reflects strong network utility with weaker standalone EMR fit and opaque pricing outside those rails.
Competitor landscape
| Vendor | Overall | Ease of implementation |
|---|---|---|
| HHAeXchange | 6.9 | 6.6 |
| Axxess | 7.9 | 7.5 |
| Therap | 7.3 | 7.1 |
| AxisCare | 7.5 | 7.2 |
| KanTime | 7.6 | 7.3 |
Pricing
| Item | Detail |
|---|---|
| Model | Network and software packaging for providers, payers, and state programs; quote-based. |
| What usually drives cost | Provider versus payer seat, state programs in scope, visit volume, and mobile caregiver tooling. |
| What to ask in diligence | Whether your Medicaid MCOs and states already require or prefer HHAeXchange, and all-in cost at your visit volume. |
| Published pricing | Public list price: not published. Network participation often drives the buying decision as much as license math. |
Prerequisites for purchase
| Need | Why it matters |
|---|---|
| What you need to get HHAeXchange to function | |
| Confirmation that your Medicaid payers or states use the network | Outside those rails the platform may be the wrong buy. |
| Provider enrollment and caregiver roster ready for EVV | Incomplete rosters block visit confirmation. |
| Ops owner for shift and exception queues | Unowned queues create denials. |
| Clear path for caregiver mobile adoption | Paper timesheets break network compliance. |
| Billing coordination with MCO payment cycles | Visit confirmation without billing follow-through wastes the network. |
| What will maximize your value | |
| Measure confirmed visits and payment cycle time | Network value shows in those numbers. |
| Work exception queues daily at go-live | Aging exceptions become lost revenue. |
| Align agency EMR exports if you keep a separate clinical system | Double entry creates mismatches. |
| Train caregivers on clock-in discipline | Missed punches are a compliance event. |
| Review payer performance reports with your MCOs | Silent network issues compound. |
| Deal-breakers | |
| Your payers and states do not use HHAeXchange. | |
| You want a clinical EMR only, with no network EVV needs. | |
| Caregivers cannot use the mobile tools. | |
| No one will work visit-exception queues. | |
| You are Medicare-only skilled home health with no HCBS network requirement. | |
Value creation time frame
| # | Stage | Typical range |
|---|---|---|
| 1 | Contract signed → kickoff | 2-8 weeks (payer/network confirmation, enrollment, roster load) |
| 2 | Kickoff → first live workflow | 4-12 weeks for first programs confirming visits |
| 3 | First live workflow → steady value | 2-5 months before exception queues and payments feel routine |
Methodology
| Weight | Factor | What it measures |
|---|---|---|
| 35% | Customer outcomes | Whether buyers get measurable operational or clinical-workflow results after go-live |
| 30% | Product | Capability depth, reliability, and fit for the job the category actually buys |
| 20% | Implementation | How hard it is to stand up, integrate, train, and stabilize |
| 15% | Pricing clarity | Whether a buyer can model total cost without a mystery quote |
| Label | Meaning |
|---|---|
| Highly recommend | Strong outcomes and product with manageable caveats |
| Recommend | Solid fit for the right buyer; know the tradeoffs |
| Conditional | Only with a specific use case or heavy caveats |
| Not recommended | Avoid for most buyers in this category |
Read our full methodology for how we weight scores and assign recommend labels.