How Home Health and Behavioral Health Agencies Should Document Telehealth Visits for EVV Compliance
The Documentation Gap Most Agencies Miss
When telehealth expanded across home health and behavioral health services, most agencies focused on the clinical side of the shift. They trained staff on video platforms, updated consent forms, and adjusted schedules. What did not get the same attention was the documentation side, specifically how remote visits get logged, timestamped, and verified for Medicaid billing purposes.
That gap is now a compliance liability.
Electronic Visit Verification (EVV) requirements under the 21st Century Cures Act apply to Medicaid-funded personal care and home health services. As telehealth became a standard delivery channel, the expectation that agencies maintain verifiable records for remote sessions followed. The question is whether your agency has documentation that can survive an audit or just a record that a call happened.
This article explains what compliant telehealth visit documentation looks like, why the standard matters operationally, and what agencies should have in place to meet it.
What EVV Requires for Remote Visits
The 21st Century Cures Act (Section 12006) mandated EVV for all Medicaid-funded personal care services starting January 1, 2020, and for home health care services starting January 1, 2023. The law requires that six core data elements be captured for every covered service visit:
- Type of service performed
- The individual receiving the service
- Date of the service
- Location of service delivery
- The individual providing the service
- Time the service begins and ends
For in-person visits, the location requirement is typically met through QR-based check-in or GPS confirmation at the client's address. For telehealth visits, location works differently. The caregiver is not physically present at the client's home, so the documentation requirement shifts toward verifiable time stamps and session records that confirm the session occurred, who was involved, and when it started and ended.
Managed care organizations (MCOs) are enforcing these standards with an 85% EVV auto-verification threshold. Agencies that fall below that threshold for three consecutive months face a Corrective Action Plan. Repeated non-compliance can lead to network termination. The threshold applies across your full visit volume, which means telehealth sessions that go undocumented or are logged manually without verifiable timestamps pull down your overall compliance rate.
Why Manual Logging Falls Short
Many agencies still rely on caregivers or clinicians to manually log telehealth sessions after the fact. A staff member completes a call, then enters the session time and duration into a spreadsheet, an EHR note, or a paper form. That record gets submitted with the billing claim.
The problem is that manual entry is inherently unverifiable. There is no system-generated timestamp confirming when the session actually started and ended. There is no record of whether the call connected or lasted as long as documented. If an auditor pulls that claim and asks for proof of service, a self-reported entry is not documentation. It is an assertion.
This is the same documentation vulnerability that has created liability exposure for agencies in the in-person visit context. Audit investigators look for patterns: sessions logged at unusual times, sessions with rounded durations, sessions documented hours after the billing date. Manual records create those patterns, not because staff are acting in bad faith, but because manual entry is imprecise by design.
The caregivers doing this work are following the process they were given. The issue is the process itself.
What Audit-Ready Telehealth Documentation Looks Like
Compliant telehealth session documentation has three characteristics that distinguish it from a manual log entry:
System-generated timestamps
The session start and end times are captured automatically at the moment the session occurs, not entered retrospectively. The timestamp is tied to the platform or verification system, not the clinician's memory or manual input.
Tamper-proof record creation
Once the session is logged, the record cannot be edited without creating an audit trail. This protects agencies from liability when a claim is reviewed months after the service date.
Same-day visibility for managers
Supervisors can see completed sessions on the day they occur. If a scheduled telehealth session does not generate a verification record, the gap is visible immediately rather than being discovered during a billing reconciliation or audit review.
The operational value of same-day visibility extends beyond compliance. When a remote session does not get logged, the issue could be a technical problem, a missed appointment, or a documentation error. Knowing which one within hours is different from finding out three weeks later during a billing cycle review.
The Compliance Rate Math
The 85% EVV auto-verification threshold applies to your total billable visit volume. If your agency handles 500 visits per month and 150 of those are telehealth sessions documented manually, you are starting with a documentation risk of 30% of your volume before anything else goes wrong.
Agencies that have built telehealth documentation into the same verification workflow as in-person visits do not carry that exposure. Remote sessions are logged automatically with the same timestamp integrity as field visits. The compliance rate reflects the actual delivery of services, and the audit record reflects the same.
This matters most during MCO audit cycles, OIG enforcement reviews, and any billing dispute that requires proof of service delivery. The agencies that have the documentation hold their ground. The ones relying on manual records are left to reconstruct a record that should have been built in real time.
How MyVisits Handles Telehealth Session Logging
MyVisits was built by Joseph Catan, who spent 18 years as a Clinical Director managing in-home service delivery for behavioral health agencies. The telehealth documentation feature exists because he ran into this exact problem before the software did.
When a caregiver completes a remote session through MyVisits, the platform automatically logs the visit with a verified timestamp. No manual entry. No after-the-fact documentation. The record is created at the moment the session occurs and is immediately visible in the manager dashboard.
Remote sessions are held to the same documentation standard as in-person visits. A telehealth call logged in MyVisits carries the same timestamp integrity and audit readiness as a QR-verified field visit. Managers see the full picture in one place, in-person visits and remote sessions together, without switching between platforms or reconciling separate records.
The platform runs on AWS infrastructure and provides direct technical support, so agencies do not need an IT department to maintain it. Setup takes less than a day.
What Agencies Should Review Now
If your agency delivers telehealth sessions as part of Medicaid-funded services, the following questions are worth reviewing before your next audit cycle:
- Are your telehealth session records generated automatically by a system, or entered manually by staff?
- Can you produce a timestamp-verified record of session start and end times for any specific date in the past 12 months?
- Is telehealth session documentation reflected in your EVV compliance rate, or is it tracked separately?
- Do managers see missed or incomplete telehealth sessions on the same day they occur?
If any of these questions expose a gap, the time to address it is before a Corrective Action Plan lands, not after.
The Practical Standard for Remote Visit Documentation
Agencies that have been through audits on telehealth billing often describe the same experience. The claim looked fine during billing. The session was completed. The documentation was there. The problem was that the documentation could not be independently verified because it had been entered manually after the fact.
The standard auditors apply is straightforward: can you demonstrate, through system-generated records, that the service occurred, when it occurred, and who was involved? If the answer depends on a staff member's manual entry, the record will not hold up under scrutiny the way a verified timestamp will.
Remote visits are no different from in-person visits in this regard. The delivery mechanism is different, but the documentation obligation is the same. Agencies that treat telehealth logging as a separate, lighter-weight process are carrying compliance risk they may not realize until it becomes a reimbursement problem.
See how MyVisits documents telehealth visits alongside in-person visits in a single verified record. Try the first 30 days on us.
