Electronic Visit Verification Requirements: What a Home Care App Must Capture

Federal law requires electronic visit verification for Medicaid personal care and home health visits, and leaves the system design to each state. A home care app has to capture six data elements, cover the right services, and follow what CMS says about GPS and privacy.

In short

  • Section 12006 of the 21st Century Cures Act requires states to use electronic visit verification for Medicaid personal care services and home health care services that need an in-home visit, from January 1, 2020 and January 1, 2023 respectively.
  • An EVV system must electronically verify six things: the type of service, the person receiving it, the date, the location, the person providing it, and the start and end times.
  • States choose the EVV model, so the detailed requirements for a home care app come from the state's specification, and CMS says GPS is not required and that capturing the location where the service starts and stops is enough.

Electronic visit verification (EVV) is a federal Medicaid requirement for personal care and home health visits made in a person's home. Section 12006 of the 21st Century Cures Act added section 1903(l) to the Social Security Act, which requires states to use EVV for personal care services from January 1, 2020 and for home health care services from January 1, 2023. Any EVV system must electronically verify six items: the type of service performed, the individual receiving it, the date, the location of service delivery, the individual providing it, and the time the service begins and ends. The law does not prescribe a system. Each state picks its model, so a home care app has to meet the federal minimum and then the state's own specification.

What does federal law require?

Section 1903(l) sets the six verification items and a few conditions on how states implement them. According to CMS's May 2018 informational bulletin, states must consult with providers, seek stakeholder input, consider best practices and EVV systems already in use in the state, give providers the opportunity for training, and make sure the system is minimally burdensome and compliant with HIPAA privacy and security requirements. The bulletin adds that nothing in section 1903(l) may be read to limit provider selection, constrain beneficiaries' choice of caregiver or impede the way care is delivered. States must also run a stakeholder process that includes providers, beneficiaries and family caregivers.

The enforcement lever is federal funding. States that do not implement EVV lose part of their federal medical assistance percentage (FMAP) for the affected services. The statute sets the schedule:

  • Personal care services: 0.25 percentage points in 2020, 0.5 in 2021, 0.75 in 2022, and 1 percentage point from 2023 onward.
  • Home health care services: 0.25 percentage points in 2023 and 2024, 0.5 in 2025, 0.75 in 2026, and 1 percentage point from 2027 onward.
  • A good faith exemption applied only to 2020 for personal care and 2023 for home health, for states that had taken steps to adopt EVV technology and met unavoidable system delays.

Which services need EVV?

CMS's FAQ defines the scope. Personal care services requiring an in-home visit are covered when provided under the state plan personal care benefit (section 1905(a)(24)), 1915(c) home and community-based services waivers, the 1915(i) state plan option, 1915(j) self-directed personal attendant care, 1915(k) Community First Choice, or section 1115 demonstrations. Home health services requiring an in-home visit are covered when described in section 1905(a)(7) and provided under the state plan or a waiver.

  • A renamed or bundled service is still covered. If a service includes personal care or home health services, even under a different name or alongside other services, it is subject to EVV, in managed care and fee-for-service alike.
  • Services to inpatients or residents of hospitals, nursing facilities, intermediate care facilities for individuals with intellectual disabilities and institutions for mental diseases are not covered.
  • CMS reads "in-home visit" to exclude personal care in congregate residential settings where 24-hour service is available, such as group homes.
  • CMS does not read the requirement to apply to PACE.
  • A medical supply mailed or picked up at a pharmacy does not need EVV. A supply that needs an in-home visit for setup does.

Does EVV require GPS?

No. CMS's FAQ says there is no requirement to use GPS, although GPS is one way to implement EVV. It names interactive voice response as a common alternative, where the caregiver checks in and out from a landline or a cellular device at the person's home. The Cures Act does not require states to capture each location as a person moves through the community. Capturing the location where the service starts and where it stops is enough to meet the federal minimum, though states may ask for more to control fraud, waste and abuse.

CMS also says an EVV system does not require the Medicaid beneficiary to have an internet connection, a cell phone or a landline. Options exist where the provider supplies a phone or an electronic device to staff or to the person receiving services. For an app, that means the caregiver's device does the work, and the person receiving care should never be asked to install anything.

Which EVV model does your state use?

CMS's bulletin describes five models. The model decides whether you may build or choose your own EVV software, and what you must send to the state.

  • Provider choice: providers pick and pay for their own EVV vendor under state standards. The state may need an aggregator to collect data from all of them. Under this model a provider's own app can be the EVV system, if it meets the state's specification.
  • Managed care plan choice: each plan selects its EVV vendor. Providers who work with several plans may have to use several systems.
  • State-mandated in-house system: the state builds and runs the system. Providers use it, and any other app has to work alongside it.
  • State-mandated external vendor: the state contracts with one vendor and everyone uses that system.
  • Open vendor: the state offers its own system or a contracted one, and lets providers and plans keep using their own systems, which then report standardized data to the state's aggregator.

Before you design anything, find the state's current EVV page and its technical specification for third-party systems, if it accepts them. That document lists the exact fields, formats, transfer method and certification steps. It also lists any items beyond the federal six, which CMS says states may require.

How do the six items map to app data?

  • Type of service performed: the service code from the person's authorization or care plan, picked from a list rather than typed.
  • Individual receiving the service: the person's Medicaid or plan member ID, linked to their profile in the app.
  • Date of the service: taken from the device clock and checked against the server time on sync.
  • Location of service delivery: captured at clock-in and clock-out, by GPS, a fixed device or a call from the home, depending on what the state accepts.
  • Individual providing the service: the caregiver's own login and ID, never a shared device account.
  • Begin and end times: clock-in and clock-out events, stored as recorded, with any later correction kept as a separate, reasoned edit.

What should the visit flow look like in the app?

  • Sign-in by the caregiver, then a list of today's visits from the schedule and authorizations.
  • Clock-in from the person's profile, capturing time and location.
  • The tasks or services planned for the visit, each checked off with what was done and how the person responded.
  • Clock-out, capturing time and location again, with a summary of the visit.
  • Offline capture with later sync, keeping the original timestamps.
  • An exception path for missed clock-ins, wrong locations or device failures, with a reason code and a supervisor's approval.

We built an app with this flow, Cx360 EVV, for medical workers who visit patients with behavioral health needs at home. It is a Flutter app for iOS and Android on the client's API. Workers sign in, see the list of clients with search, open a client's profile with date of birth, client ID, visit date and address, and start the visit. During the visit the app tracks location and shows the service and clock-in time, and the worker checks off each staff action and records whether the service was provided, how the client responded and what support was given. A report questionnaire and a visit summary close the visit, and the app works with the company's admin panel.

How does EVV data reach the claim?

CMS expects states to show that EVV data is used against provider claims, through their Medicaid Management Information System (MMIS) or an equivalent process. Its FAQ gives an example: for a personal care claim, the state can take the number of hours a person was authorized, verify the hours actually delivered in the EVV system, and match both to prior authorization and payment data. CMS expects this to help states validate that services were provided and detect potential fraud, waste and abuse.

Build the same check into your own system before claims go out. Compare each visit with the authorization and the schedule, flag visits with exceptions or edits, and hold claims for visits that have not been verified or approved.

What about self-directed services?

In self-directed programs, the person receiving services chooses and directs their own workers. CMS encourages states to pick EVV systems that keep the flexibilities of self-direction, such as fluid scheduling changes, choice of worker, participation in community activities and proper interaction with financial management services entities. An app for these programs should allow visits that were not on a fixed schedule and work for workers who are employed by the person, not by an agency.

How should an EVV app handle privacy?

  • Collect location only at clock-in and clock-out unless the state's specification asks for more, and say so in the app.
  • Explain to caregivers and to the people they serve what is recorded and why.
  • Restrict who can see visit locations and addresses, and keep each worker's view to their own clients.
  • Treat EVV data as PHI, because it links a person to the care they receive at a specific address.

We sign a BAA before anyone on the team sees PHI, and we run a penetration test before launch.

Building or fixing an EVV workflow?

Talk to an engineer at Onix Health about your state's EVV model, your visit flow and your billing. Our free five-day technical audit ends with a written report on gaps against the federal and state requirements and what to change first.