Summary
Home care software selection goes wrong when agencies evaluate platforms on surface features instead of the architecture, implementation, and support realities that determine whether the system actually works once the demo is over. The two questions that reveal the most about a platform’s true fit are how it handles your state’s specific EVV configuration and whether it can produce real-time billing, scheduling, and clinical reports from a unified data source without manual assembly. If you’re looking for home care software built specifically for home care workflows — with purpose-built EVV, multi-payer billing, and unified reporting — myEZcare is worth adding to your evaluation list.
Introduction
The demo looked flawless. The sales rep knew the product cold, the interface was clean, and the pricing fit the budget. Three months after go-live, the billing team was still manually reconciling EVV records because the integration the vendor had described as “seamless” turned out to require a custom configuration that was never included in the contract.
That story has a version at almost every agency that’s been through a home care software selection process at least once.
Choosing home care software is one of the highest-stakes operational decisions an agency makes — not because the technology is especially mysterious, but because the wrong platform embeds itself into every clinical, scheduling, billing, and compliance workflow your team runs every day. A home care software evaluation that goes well saves your agency years of workarounds, staff frustration, and revenue cycle friction. One that goes badly does the opposite, and switching again means absorbing the migration cost twice. The seven questions in this guide are designed to get past the demo and into the architecture, implementation, and support realities that actually determine whether a home care software platform works for your agency.
Question 1: Was This Platform Built for Home Care Specifically — or Adapted From Something Else?
This is the first question in any home care software evaluation and the one most agencies skip because it feels too basic. It isn’t. A significant portion of the platforms marketed to home care agencies were originally built for hospitals, skilled nursing facilities, or general outpatient settings and then adapted for home-based care through additional modules, rebranded interfaces, and integration layers that connect systems that weren’t designed to talk to each other.
Home care software built from the ground up for home-based care workflows has a fundamentally different architecture than a platform that was adapted. The scheduling module in a purpose-built home care software system was designed around caregiver-to-client matching, geographic routing, and real-time availability from the start — not retrofitted onto a template built for clinic appointment management. The EVV module captures point-of-care visit data and routes it to state aggregators because that’s what the system was designed to do, not because a third-party integration was bolted on after the core platform was built.
Ask the vendor directly: when was this platform first built, what care setting was it originally designed for, and which modules were added later versus built into the original architecture? The answers tell you whether you’re buying a home care software platform or a general healthcare platform wearing home care clothing.
Question 2: How Does Your Platform Handle My State’s Specific EVV Requirements?
EVV compliance is a non-negotiable operational requirement for any Medicaid-funded home care agency, and the technical implementation varies enough between states that a home care software platform that handles EVV correctly in one state may fail in another. Before choosing home care software, you need a specific, detailed answer to this question — not a general assurance that the platform is “EVV-compliant.”
The specific questions inside this question are: Which state aggregators does your platform have validated, active integrations with? What happens when my state changes its aggregator or EVV model? How does your system handle manual visit entries when a caregiver has a connectivity issue in the field, and how does it flag entries that exceed my state’s manual entry threshold? If the vendor gives you a fluent answer to all three, the EVV integration is real. If they defer to a technical team or pivot to general compliance language, the integration may be less robust than the demo suggested.
Home care software that treats EVV as a core function rather than a compliance checkbox handles these questions with specificity because the team that built the platform has worked through them. The $27.50-per-day NOA penalty and the hard-edit claim rejections that come from failed EVV data transmission are the business consequences of choosing home care software whose EVV capability doesn’t match your state’s actual requirements.
Question 3: What Does the Data Migration Process Actually Look Like?
Every home care software vendor will tell you that data migration is straightforward. What you actually want to know is how many agencies similar to yours in size and payer mix they’ve migrated in the past year, what their validation process is for confirming that migrated records match the source system, and what happens when discrepancies surface after go-live.
A reputable home care software vendor has a structured migration protocol that specifies which data fields transfer automatically, which require manual verification, and what the parallel-run period looks like before the old system is switched off. If the migration plan you’re shown is a generic data import checklist rather than a workflow that accounts for your specific payer configuration, authorization history, and caregiver profile structure, that’s a signal that the implementation team hasn’t migrated many agencies from a system like yours.
Ask for the migration documentation in writing before you sign. Ask which team member will own your migration specifically. Ask what the escalation path is if a billing cycle is affected by a data discrepancy during the parallel-run period. The answers to those questions tell you more about the home care software vendor’s implementation maturity than anything in the demo.
Question 4: How Does Your Platform Handle Multi-Payer Billing?
Most home care agencies serve clients across multiple funding sources — Medicaid fee-for-service, Medicaid managed care plans, Medicare, private pay, VA programs, and sometimes commercial insurance — each with its own rate structure, authorization requirements, documentation standards, and billing code set. Home care software that handles multi-payer billing natively keeps all of that configuration inside a single billing workflow. Home care software that handles it partially leaves your billing team managing the gaps manually, which is exactly the source of claim errors that compound over time.
The specific version of this question to ask during a home care software evaluation is: show me what happens when a single client transitions from one payer to another mid-authorization period. That scenario — a Medicaid waiver client whose coverage changes to a managed care plan at the start of a new month — is a routine billing event that exposes how well the platform actually handles payer transitions. If the demo shows a clean, automated transition, the multi-payer architecture is real. If it requires a workaround or a manual update in two separate modules, you’re looking at a home care software system that will cost your billing team time on every payer change.
If you’ve been running an agency for more than a year with a mixed payer caseload, you already know that payer transitions are where most billing errors originate. Choosing home care software that handles them natively isn’t a nice-to-have.
Question 5: What Does Implementation Support Actually Include — and for How Long?
Implementation support is the most underspecified component of any home care software agreement, and it’s the one that determines whether your go-live is smooth or chaotic. “Implementation support” can mean anything from a six-week dedicated onboarding team to a library of self-serve training videos and a shared support inbox. Those are categorically different levels of help, and which one you’re getting should be defined in writing before you sign.
The specific questions that distinguish real implementation support from nominal support are: Do you have a dedicated implementation manager assigned to my agency, or do I work with a general support queue? Is your implementation team present in real time during my first payroll cycle and first billing run, or available by ticket? What’s your policy when a configuration issue surfaces during go-live that wasn’t identified during the setup period? Home care software vendors who have run enough implementations to know that first-cycle billing issues happen routinely will have a clear, specific answer to that last question. Vendors who haven’t will give you a general assurance.
Ask for the implementation timeline in writing, with specific milestones for data migration completion, caregiver training rollout, EVV aggregator validation, and first billing cycle completion. A home care software vendor who can’t produce that timeline before you sign is telling you something about how structured their implementation process actually is.
Question 6: Can I Talk to Three References From Agencies Similar to Mine?
This question should be non-negotiable in any home care software evaluation, and the follow-through matters as much as the ask. Every vendor will provide references — the question is whether those references are for agencies that match your profile in size, payer mix, state EVV requirements, and care setting. A reference from a 400-client non-medical personal care agency in a provider-choice EVV state doesn’t tell you much about how the platform performs for a 60-client Medicare-certified home health agency in a state-mandated aggregator model.
When you speak with references, ask them three specific questions: What did the vendor get wrong during implementation, and how did they respond? What’s the one thing about the home care software you wish you’d known before you signed? If you were choosing home care software again today, would you choose this vendor — and why? The third question is the most revealing, because it forces a direct current assessment rather than a historical narrative that may have softened over time.
Question 7: What Does the Reporting Tell Me — and How Fast Can I Get It?
Reporting capability is the feature that agencies underweight during home care software evaluation and overweight after they’re three months into using a system that can’t answer basic operational questions without a manual export. Before choosing home care software, ask the vendor to pull three specific reports live during the demo: a real-time authorization utilization report for a single client, a caregiver overtime risk report for the current week, and a claim denial rate summary by payer for the prior month. Those three reports touch scheduling, clinical, and billing data — and the speed and completeness with which the home care software produces them tells you exactly how unified the underlying data architecture is.
Home care software with genuinely integrated data produces all three reports from a single platform in under two minutes without anyone switching screens or running a manual export. Home care software that stores scheduling data separately from billing data and clinical data separately from both produces those reports slowly, incompletely, or not at all without someone assembling pieces from multiple modules. The reporting question isn’t about features — it’s the clearest diagnostic test of whether the home care software you’re evaluating is a unified platform or a collection of connected tools pretending to be one.
See how myEZcare answers all seven of these questions with specifics built into the platform — from EVV aggregator integration and multi-payer billing through implementation support and real-time reporting. Schedule a free demo today and bring your three biggest pain points into the conversation.
