EVV Requirements in a Home Care Business Sale

Identify the services and reporting systems

Build an inventory by program, payer, service, location and provider ID. List the tools used for scheduling, electronic visit verification, payroll and claims. An agency may use several tools or a mix of private-pay and Medicaid services. A single software subscription does not explain which rules apply to each service.

Medicaid.gov describes federal EVV requirements for specified personal care and home-health services involving an in-home visit. Review the actual state and payer implementation next. Do not assume that all home care or all home health activity has one reporting path. (Source: Medicaid.gov EVV overview)

Keep the home-care model distinct from home health. Record who confirmed each service's scope and which current guidance was used. A list of unanswered questions is more useful than a general assurance that the agency uses EVV software.

Understand the six information categories

Section 1903(l)(5) identifies the service type, recipient, date, location, worker and start and end time. Those are information categories, not proof that all payment conditions have been met. Confirm how the actual program requires the information to be captured and sent. (Source: Social Security Act section 1903(l))

Ask about approved methods for correcting an error and preserving its history. The federal definition does not require one vendor, a particular device or continuous location tracking. State and payer instructions may specify further details. Use those instructions for the actual service rather than carrying settings from another program into the new account.

The federal funding mechanism concerns payments to states. Do not describe it as a standard percentage removed from each provider claim. Determine the applicable claim edits, correction process and consequences separately. Keep unresolved policy questions with the person responsible for obtaining an answer.

Follow the visit through to cash

The authorized-hours definition explains why approval and delivery are separate. Check the service, provider, dates and units covered by the authorization where required. Then follow the completed work through its records, claim response and receipt. A status at one stage should not stand in for the others.

An accepted data transmission may only show that a system received a file. It does not prove a claim is valid. Use the same service-period definitions across the review so that timing differences are visible. Keep unbilled work apart from invoices already included in receivables to avoid counting an amount twice.

Interpret exception counts with a defined sample

Choose service periods that include routine work and known problems. Record the sample boundary and the time of the status export. Match records through approved identifiers and investigate differences. Expand the sample when findings justify it. Do not infer the condition of the whole business from a convenient clean week.

In this fictional sample, 100 completed visits are reviewed at one snapshot. Twelve needed an EVV correction; eight of those are now resolved. Each visit appears in exactly one row below. These invented counts describe correction status only, with no national pass threshold or claim-payment conclusion.

The status total is 88 + 8 + 4 = 100. The open corrections are 12 − 8 = 4. The 96 visits outside the open category are not necessarily payable claims. Eligibility, authorization, other records and payer conditions still need review. The sample does not establish that the work itself was adequately documented.

Assign the open work and its cost

For each unresolved item, list the cause, evidence needed, responsible person and next action. Separate a missed check-in from a service-code mismatch or rejected transmission. Manual correction is not automatically misconduct, and a completed correction is not automatically sufficient support. The reason and history matter.

Check the staff time required to clear issues and maintain the process. If the seller keeps old receivables, the buyer may still be asked to help with records or corrections. Set duties, access limits and payment for that work. The working-capital guide connects these tasks with cash ownership and timing.

Do not manufacture visit evidence to clear a dashboard. Follow the authorized correction process and preserve the original entry, support and approval trail. Repeated issues may require training or configuration changes. Assign the underlying fix as well as the individual correction.

Check ownership dependencies with the program and payer

Separate operating authority, payer enrollment, provider identifiers and software access. An asset sale, entity sale or management change can raise different questions. Obtain instructions for the actual transaction through authorized contacts. Record what must happen first and what evidence will show that the next step is ready.

Wisconsin offers a specific example. Its DHS FAQ says Medicaid-enrolled providers complete the ownership-change process and receive a new provider ID. They then follow the remaining EVV setup steps and notify payers. Payers must create service authorizations with the new ID so those records can flow to Sandata and connect with claims. (Source: Wisconsin DHS EVV FAQ, revised November 20, 2025)

That is a Wisconsin dependency, not a national ID rule or a complete state closing checklist. Confirm the current instructions for the actual payer and program. The example shows why a working login alone cannot establish readiness. A needed authorization may still refer to the wrong provider.

Map the systems and prove the handoffs

Draw the route from scheduling to EVV and onward to payroll, billing and remittance review. Identify manual files as well as automated connections. Record service-code mappings, time settings and the credentials used by each connection. Confirm which agreements or integrations depend on the seller's account.

Visit logs can support a work-history review without deciding employment status. Use the caregiver classification evidence guide to connect those records with contracts, assignment choices and pay practices. Its review separates missing facts from the legal conclusion that the applicable adviser must assess.

Build a test with the vendor, operator and payer as appropriate. Define the test environment, permitted data, expected response and person who accepts the result. Confirm that the receiving system shows the intended provider, service and period. A vendor's successful integration test may not cover every agency configuration.

A parallel comparison must not create duplicate claims or unauthorized live submissions. Label test activity and keep it separate from billable work. Compare results, resolve gaps and retain the evidence. If a test fails, keep the dependency open rather than assuming that staff can correct the data after closing.

Preserve privacy and historical access

Start diligence with aggregate exception and payer reports where they answer the question. Review any deeper access under the actual privacy rules and participant roles. Where the HIPAA minimum necessary standard applies, limit the information to the approved need. An NDA does not create authority to release protected visit details. (Source: HHS minimum necessary guidance)

Assign custody for past visits, attachments and correction histories. Confirm export formats, search tools, costs and lawful access after closing. HHS explains that its Privacy Rule does not set a general medical-record retention term. Determine other applicable duties and legal holds separately. (Source: HHS retention FAQ)

Use the records-custody guide to test a historical lookup and a request for supporting records. Do not retire the only usable archive while a duty remains unresolved. EVV history may need to remain accessible even when the buyer changes vendors.

Prepare staff and an approved fallback

Have staff demonstrate how to capture a visit, report a problem and seek help through approved methods. Include the people who manage exceptions, schedules and claims. Record coverage for absences and after-hours problems. A training invitation alone does not show that the people doing the work can use the process.

Plan how to respond if the new connection fails. Establish who can pause the cutover, restore permitted access and alert the operator. HHS's Security Rule summary addresses safeguards and continuity for covered electronic information. Use the relevant framework with the privacy and technology teams. (Source: HHS Security Rule summary)

Follow the actual program's approved contingency instructions; do not invent records or bypass claim controls. Keep payroll obligations in a separate review from reimbursement. An unpaid claim does not by itself establish that compensation for work may be withheld. The operating budget needs a supported plan for collection delays.

Record a specific readiness decision

Review service scope, provider configuration, staff readiness, test evidence, historical access and remaining exceptions together. Name the person responsible for every open task and the evidence needed to close it. When the closing date or payer instructions change, reassess the dependencies. An earlier successful test may no longer cover the proposed handoff.

Use the home-care diligence checklist or home-health diligence checklist for the wider acquisition. EVV work supports the operating transition. It does not replace other approvals, required care records or claim review, and it cannot guarantee future payment.

The EVV definition introduces the six visit-data categories and a fictional time mismatch. Use it to separate the visit record from authorization, a claim and payment before reviewing the ownership handoff.