Telehealth in Home Health Care

What is telehealth in home health care?

Telehealth in home health care is the use of video, audio-only calls or remote patient monitoring by a home health agency during a patient's episode. Under Medicare, each technology must be listed on the plan of care, supports the ordered visits rather than replacing them, and is reported on the claim without counting as a visit.

What does Medicare allow for home health telehealth?

Medicare allows agencies to use telecommunications technology inside a home health episode, with limits written into the regulations and claims instructions. These are the rules the software has to enforce.

• Plan of care: Under 42 CFR 409.43(a), the plan of care must include any remote patient monitoring or other services furnished through telecommunications technology, tied to needs found in the comprehensive assessment.
• No substitution: The same section says these services cannot substitute for a home visit ordered in the plan of care and cannot be considered a home visit for patient eligibility or payment.
• What counts as technology: 42 CFR 409.46(e) lists remote patient monitoring, teletypewriter (TTY), and 2-way audio-video technology that allows real-time interaction between patient and clinician.
• Claim reporting: CMS MLN Matters MM12805 requires agencies to report telecommunications services on home health claims from 1 July 2023, using G0320 for audio-video, G0321 for audio-only and G0322 for remote collection of physiologic data.
• Documentation: The same CMS instructions require the medical record to show how the technology helps achieve the goals in the plan of care.

The result is a reporting requirement, not a new payment. The G-codes give CMS data on how agencies use technology, while the episode payment still depends on the in-person care and the patient's case mix.

One later change matters for claim edits. CMS MLN Matters MM13812 allows G0320 to G0322 line dates to overlap an inpatient stay from 1 April 2025, because the lines are non-payable reporting items. A contact with a caregiver while the patient is in hospital can still be reported, so the claim builder should not block those dates.

How is a telehealth contact different from a home visit?

A telehealth contact supplements the visit schedule; it never fills a visit slot. Agency software should model each type separately so a scheduler cannot swap one for the other.

• Ordered home visit: An in-person visit by a skilled discipline, listed on the plan of care with a frequency. Missed visits stay missed even if a video call happens that day.
• Audio-video contact: A real-time video session with a clinician, such as a wound check between visits or medication teaching. Reported as G0320 under the discipline's revenue code.
• Audio-only contact: A phone call with clinical content, reported as G0321. A scheduling call with no clinical content is not a telecommunications service.
• Remote monitoring: Physiologic data such as blood pressure, weight or glucose sent by the patient or caregiver to the agency. Reported as G0322, with a span of days on one line.

Why this split matters for scheduling

If the scheduling system lets a coordinator mark a video call as completing a skilled nursing visit, the agency's visit counts and the claim will both be wrong. Keep telehealth contacts on their own calendar layer and their own note templates.

Which agency records does the software touch?

Home health telehealth writes into several regulated records. Each has its own timing rules, and the telehealth module must respect them.

• Initial assessment: Under 42 CFR 484.55(a)(1), the initial assessment visit must happen within 48 hours of referral, within 48 hours of the patient's return home, or on the ordered start of care date.
• Comprehensive assessment and OASIS: Under 484.55(b)(1), the comprehensive assessment, which incorporates the OASIS items, must be completed no later than 5 calendar days after the start of care. Telehealth needs identified here are what justify adding them to the plan of care.
• Plan of care: Under 42 CFR 484.60, the plan of care sets disciplines, visit frequency and goals. A telehealth or monitoring order is an amendment that needs the ordering practitioner's sign-off.
• Visit and contact notes: Each telehealth contact needs its own note with date, discipline, modality, who took part and how it served a plan-of-care goal.
• Medicaid visit verification: Section 12006 of the 21st Century Cures Act requires states to use electronic visit verification for Medicaid home health care services. Keep EVV records for in-person visits separate from telehealth contacts.

Fields a telehealth contact note should capture

A contact note template with fixed fields makes claim lines and surveys easier to support than free text. These fields cover both.

• Identity: Patient, clinician, discipline and the clinician's credential.
• Timing: Date, start time and end time, taken from the session rather than typed in.
• Modality: Audio-video, audio-only or monitoring review, which drives the G-code.
• Participants: Who else joined, such as a caregiver or interpreter.
• Goal link: The plan-of-care goal the contact supported and the finding.
• Action: Any change to the visit schedule, new order request or escalation.

Privacy in the patient's home

A home is not a clinic room. Other family members may be present, and the patient may not want them to hear. The app should prompt the clinician to confirm who is in the room and offer to move a sensitive part of the conversation to a private phone call.

How should the telehealth workflow run inside an agency?

The workflow below follows a telehealth contact from order to claim. Each step names the record that changes.

• 1. Order: The clinician identifies the need in the comprehensive assessment, and the plan of care is updated with the technology, the discipline and the goal it supports.
• 2. Setup: For monitoring, the agency ships and pairs the devices, records serial numbers and teaches the patient or caregiver. For video, it confirms the patient has a working device and a quiet space.
• 3. Contact: The clinician runs the video call or phone contact from the agency's app. The app records the start time, end time, modality and participants.
• 4. Note: The clinician completes a telehealth note template that asks which plan-of-care goal the contact addressed and what was found.
• 5. Escalation: If the contact shows a problem, the clinician schedules an extra in-person visit or contacts the ordering practitioner. The app should make that one action, not a separate system.
• 6. Review: For monitoring, a named clinician reviews incoming readings on a set schedule, and each review is logged with the reviewer and time.
• 7. Claim: At billing, each contact becomes a G-code line under the right revenue code, and monitoring spans become single G0322 lines.

Claim reporting checklist for G0320 to G0322

Claims edits reject G-code lines that break CMS rules. Build these checks into the claim builder before the file reaches the clearinghouse.

• Bill type: Report the G-codes only on home health type of bill 032x, which goes out on the institutional 837I.
• Revenue codes: Pair each G-code with the revenue code of the discipline that provided it: 042x, 043x, 044x, 055x, 056x or 057x.
• Line detail: Report each audio-video or audio-only service on its own dated line.
• Monitoring spans: Report remote monitoring that spans several days as one G0322 line with the start date and number of days.
• No charge logic: Treat the lines as reporting items. They should not change the expected payment the billing system calculates.
• Record match: Check that every G-code line has a matching contact note before the claim is released.

Where home health telehealth goes wrong

These failure points come from the gap between what a telehealth tool records and what Medicare expects an agency record to show.

• Video in place of a visit: Recording a video call as an ordered skilled visit conflicts with 409.43(a) and misstates the claim.
• Technology missing from the plan of care: A monitoring program started without a plan-of-care entry has no basis in the record.
• Monitoring data with no reviewer: Readings that arrive with no assigned clinician and no review time stamp show the agency collected data but did not act on it.
• Licensure shortcuts: A nurse calling a patient across a state line still needs a license valid where the patient is.
• Untracked vendors: A video or device vendor that stores recordings, readings or messages holds ePHI and needs a business associate agreement with the agency.
• No fallback: When the tablet fails, the clinician needs a phone path and a way to book an in-person visit the same day.

How Agnotic can help

Home health agencies need telehealth that respects plan-of-care rules and claim reporting, and Agnotic builds it into the agency's own tools. Agnotic Technologies adds video and phone contacts, device onboarding, telehealth note templates and G-code claim logic to agency EHR and scheduling systems, with escalation paths to in-person visits.

The engineering team also connects device readings to a review queue, keeps telehealth contacts off the visit calendar, and adds claim checks so every G-code line has a matching note before the 837I leaves the agency.

Sources

• 42 CFR 409.43: Plan of care requirements, including telecommunications services
• 42 CFR 409.46: Allowable administrative costs and telecommunications technology definition
• CMS MLN Matters MM12805: Telehealth home health services, new G-codes
• CMS MLN Matters MM13812: Allowing home health telehealth services during an inpatient stay
• 42 CFR 484.55: Comprehensive assessment of patients
• 42 CFR 484.60: Care planning, coordination of services and quality of care
• Medicaid.gov: Electronic visit verification