EVV IT support at a home care agency divides along one line: the EVV vendor supports its own platform, and the agency’s IT provider supports everything that platform runs on. Neither one takes responsibility for EVV compliance or the accuracy of visit data. That stays with the agency, and specifically with the agency’s EVV administrator.
The line sounds clean until a caregiver’s clock-in fails at a client’s front door. Then the question of whose problem it is decides whether the visit gets recorded or becomes a manual entry someone has to justify later. For Medi-Cal personal care and home health agencies across the San Francisco Bay Area, that question comes up every week, and most agencies have never written down the answer.
This post lays out where each party’s support stops, where issues fall between them, and how to close the gap without taking on either party’s job.
Why Is EVV a Stack and Not a Single App?
EVV is a stack. The EVV platform is the part everyone sees, but it runs on caregiver phones, office workstations, the Wi-Fi and cellular connections those devices use, and the user accounts the agency creates and maintains. A failure in any one layer looks the same to the caregiver standing in a client’s kitchen: the visit will not record.
That is why “EVV is down” is rarely a complete diagnosis. The app may be fine while the phone’s operating system blocks it. The portal may load while the office network drops it. Each layer has a different owner, which is the whole reason the support question exists. Our overview of IT for home care agencies treats EVV as one of six core activities an agency runs on technology; this post goes a level deeper into who supports what.
What Does the EVV Vendor Support?
The EVV vendor supports its own platform: the mobile app caregivers clock in with, the web portal office staff use, the server-side processing that turns clock-ins into visit records, and the transmission of those records to the state. If the app fails for every caregiver at once, the portal will not load, or verified visits are not arriving where they should, that is the vendor’s problem to solve.
In California, that platform is one of two things. Agencies record visits either in CalEVV, the state-sponsored system Sandata operates under contract with DHCS, or in a certified Alternate EVV system, which for many agencies is the EVV function built into the scheduling platform they already use. Either way, the visit data ends up in the CalEVV Aggregator, the state’s repository.
EVV vendor responsibilities end at the platform boundary. Vendor support does not troubleshoot a phone that will not update, a router in the office, or a Microsoft 365 password. In our experience across agencies running HHAeXchange, AxisCare, Axxess, and WellSky, vendor support stops precisely at that boundary, and device, network, and account problems come straight back to the agency to solve.
What Does the Agency’s IT Provider Support?
The agency’s IT provider supports everything EVV runs on: caregiver phones and office workstations, the operating systems on them, the office network and the connectivity field devices depend on, the accounts that live outside the EVV platform, and core systems such as Microsoft 365. A phone that will not install an app update, office Wi-Fi that drops during morning scheduling, and a coordinator’s email login that fails are all IT provider problems.
For a field workforce, the biggest piece of that scope is the phone itself. A managed phone, enrolled in a platform such as Intune, is a known quantity: the IT provider can see its OS version, push the update the EVV app needs, and confirm the app is installed. Our mobile device management guide for home care agencies explains what enrollment gives an agency. The short version is that it turns “something is wrong with the phone” into a question the IT provider can answer in minutes rather than a guess.
Who Owns EVV Compliance When Both Parties Are Involved?
The agency does. Neither the EVV vendor nor the IT provider takes EVV compliance or data accuracy off the agency. DHCS directs its requirements at the provider agency, and the agency’s EVV administrator is the person accountable for visit data being logged, reviewed, and corrected. That accountability stays in-house no matter how much of the surrounding technology is outsourced.
This matters for the support question because it puts a third role above the other two. The vendor keeps the platform running. The IT provider keeps the devices and network running. The EVV administrator decides whether a visit record is right and fixes it when it is not.
Where Do EVV IT Support Issues Stall?
EVV IT support issues stall in the gray zones, where a problem crosses the platform boundary and neither party’s scope clearly covers it. Three come up constantly:
- An app update on a managed phone. The vendor released the update; the IT provider controls whether the phone installs it. If the new version breaks clock-in, each side can reasonably point at the other.
- A cellular dead zone inside a client’s home. The app works, the phone works, and the visit still will not record from a hillside house on the Peninsula where signal drops at the front door. Neither party’s ticket queue is built for this.
- A user account that lives inside the EVV portal. The IT provider cannot reset a password it does not control, and the vendor may reasonably treat the agency’s own portal administrator as the right person to do it.
None of these is anyone’s fault, which is exactly why they sit unresolved. A caregiver reports the problem, the scheduler opens a ticket with whichever party she thinks of first, and the ticket comes back with “not ours” while the visit goes unrecorded.
What the OIG Colorado Audit Shows About Platform Defects
A platform defect can be fixed by the vendor and still land on the program that relied on the data. In HHS-OIG’s audit of Colorado’s Medicaid personal care EVV program, issued July 17, 2026, auditors found 16 sampled claim lines with no service location recorded. The state traced the gap to a system logic defect, coordinated with its EVV vendor, and deployed corrective updates on July 31, 2025.
The vendor fixed the platform. The finding still appeared in the report, directed at the state agency. Two cautions apply: this is Colorado, not California, and Colorado disputed most of the audit’s findings. The mechanism is what matters for an agency. When a platform fails, the record that failed is still yours.
“Most agencies have no idea what technology problems are things that fall under their EVV vendor’s, their EMR vendor’s, or their IT provider’s domain. Most IT providers have never heard of EVV or most EMR’s and instantly say no when an issue is related to an application they’re unaware of. We have seen repeatedly how helpful it is for an agencies team to be able to come to us and either have their problem be solved right then and there or pointed to the right vendor to bring the problem to.”
Brendan Duebner, President of IT Total Care
What About HIPAA at a Home Health Agency?
HIPAA enters the picture only for home health agencies delivering Medi-Cal HHCS, which are covered entities under the Security Rule. Home care agencies delivering non-medical PCS are generally not covered entities, so this section does not apply to them by default.
At an HHCS home health agency, a caregiver’s phone running an EMR app such as Axxess or WellSky carries ePHI, electronic protected health information, between visits. Securing that device falls to the agency’s IT provider as part of helping support the agency’s Security Rule obligations: encryption, screen lock, remote wipe, and enrollment so the work profile can be removed when the clinician leaves. The EVV vendor’s responsibility for that phone ends at its own app.
DHCS separately publishes EVV-specific guidance on identifying, handling, and safeguarding PII and PHI within CalEVV, which belongs alongside the agency’s own Security Rule work. And because the EVV vendor and the IT provider both handle patient information on the agency’s behalf, both belong on the agency’s business associate list. Our post on which vendors are business associates of a home health agency walks through the examples.
How Can a Home Care Agency Sort Out EVV IT Support on Its Own?
An agency can define its own EVV IT support boundaries in an afternoon by listing what EVV depends on, getting both parties’ scope in writing, and naming the person who sits above both. The steps below are the work. None of them require new technology, and all of them survive staff turnover if they are written down.
Map every piece EVV depends on
Start by listing every piece EVV depends on: the EVV app and portal, caregiver phones (agency-issued and personal), office workstations, the office network and each caregiver’s cellular plan, and the accounts staff use to reach all of it. The list is usually longer than expected. It is the foundation for everything else, because a support scope written without it will have holes exactly where the gray zones are.
Get both scopes in writing
Ask the EVV vendor to confirm in writing what its support covers: platform availability, app behavior, portal functions, and transmission of visit data to the state. Then ask the IT provider the same question in the other direction: which devices, networks, and accounts are in its scope, and which are not. Lay the two answers next to the list from the first step. Whatever is on the list and in neither answer is a gap the agency now knows about instead of discovering at 7 a.m.
Decide what happens to personal phones
Picture a caregiver clocking in through the EVV app on a personal phone between visits. The vendor supports the app. But an unmanaged personal phone can fall outside everyone’s support scope: the vendor will not troubleshoot the phone, and an IT provider cannot support a device it cannot see. DHCS’s CalEVV FAQ places responsibility for equipping staff with appropriate devices and data plans on the provider agency, so the choice between agency phones and personal phones is the agency’s to make, and it decides who can help when the phone fails.
Enrolling personal phones in a management platform, with a work profile that leaves personal content alone, is the middle path most agencies land on. The mobile device management guide covers what enrollment involves, and our post on caregiver technology adoption in the field covers getting caregivers to accept it.
Know which accounts live where
Accounts split two ways. In CalEVV, portal users are added and maintained by an agency administrator in the portal’s Security module. That is an agency role, not a vendor or IT provider role. The agency’s directory and email accounts, in Microsoft 365 or Google Workspace, sit with the IT provider.
Because the two sets of accounts are maintained by different people, EVV portal access belongs on the agency’s onboarding and offboarding checklists as its own line item, next to email and the EMR. Our employee onboarding and employee offboarding posts show where that line goes and who confirms it happened.
Name the gray zones before they happen
Take the three gray zones described above and write down, for each, who gets the first call and what that person checks before handing off. This is the step agencies skip, and it is the one that makes a live-issue procedure possible.
Give both parties one internal contact
The vendor and the IT provider both work better with one named internal contact, and that contact should be the agency’s EVV administrator. That person already owns the visit data under DHCS, so routing support through them means every fix ends with someone checking the record. It also stops the two outside parties from each hearing a different version of the same problem.
How Does IT Total Care Handle EVV IT Support for Bay Area Agencies?
IT Total Care supports everything EVV runs on for home care and home health agencies across the Bay Area, and is deliberate about what it does not support.
- Devices, networks, and accounts: We support caregiver and office devices, networks, Microsoft 365 and directory accounts, and security across the agency’s systems.
- Vendor-boundary experience: We work with agencies running HHAeXchange, AxisCare, Axxess, and WellSky, so we know where each vendor’s support stops and what it needs from us on a ticket.
- Not the platform, not the compliance: IT Total Care does not support the EVV platform itself and does not take on EVV compliance. The platform stays with the vendor. Compliance and data accuracy stay with the agency’s EVV administrator.
- Managed phones: We can manage agency-issued phones through an MDM platform such as Intune, so the EVV app runs on a known, updated device. Our guide to setting up mobile device management at a home care agency shows the process.
- Agency phone or personal phone: We help the agency decide which caregivers carry agency phones and which use personal phones, and what each choice means for support.
- First look on ambiguous issues: When a problem could be the device or the platform, we take the first look, rule out device and network causes, and hand platform problems to the vendor with the facts attached.
- HIPAA safeguards: For HHCS home health agencies, we help support Security Rule safeguards on devices carrying ePHI. The agency’s obligations stay with the agency, and our post on what you cannot hand over when outsourcing HIPAA compliance explains why.
- Month-to-month agreements: We work on month-to-month agreements.
The Line Only Works If Someone Draws It
EVV IT support is not a question of which party is better. It is a question of whether the agency has written down where one stops, where the other starts, and who stands above both. Agencies that map the stack, put both scopes in writing, and route everything through the EVV administrator stop losing visits in the gray zones. The ones that do not keep the list in a scheduler’s head, and lose it the day she leaves.
Ready to Draw the Line Between Your EVV Vendor and Your IT Provider?
IT Total Care helps home care and home health agencies throughout the San Francisco Bay Area, from the Peninsula to the South Bay, take ownership of the devices, networks, and accounts EVV depends on, and hand the platform back to the vendor with facts attached. Our EVV device and network support for home care agencies covers managed phones, connectivity, account management, and the first look on issues that cross the line. Learn more about our approach to healthcare IT.
Contact Us to talk through where your agency’s EVV support boundaries actually sit.
