Technology & Data
Telehealth in Home Health
Definition
Telehealth in home health is the use of telecommunications technology, including real-time audio-video and audio-only interactions, to deliver services under a Medicare home health plan of care. Medicare permits telehealth as a supplement when it is included on the plan of care, but telecommunications encounters cannot substitute for ordered in-person visits and do not count as visits for payment purposes.
What Medicare actually allows
Under 42 CFR 409.43(a), which CMS made permanent in the CY 2021 home health final rule, the plan of care must include any remote patient monitoring or other services furnished via telecommunications technology or audio-only technology. Those services must be tied to the patient-specific needs in the comprehensive assessment and cannot substitute for a home visit ordered as part of the plan of care. The regulation also says they cannot be considered a home visit for patient eligibility or payment.
How telehealth is reported on claims
CMS created three G-codes for reporting telecommunications technology on home health claims. Reporting was voluntary for periods of care starting on or after January 1, 2023, and mandatory for periods of care starting on or after July 1, 2023:
- G0320: services furnished via synchronous audio-video telecommunications
- G0321: services furnished via synchronous audio-only telecommunications (telephone or another real-time interactive audio-only system)
- G0322: collection of physiologic data digitally stored or transmitted by the patient, meaning remote patient monitoring
These lines do not affect payment: CMS excludes them from the visit amounts, the outlier amounts and the LUPA calculation sent to the pricer. CMS says the data lets it analyze the characteristics of the beneficiaries who use services furnished remotely.
The payment reality
Telehealth encounters do not count toward the LUPA (Low Utilization Payment Adjustment) visit threshold, do not generate per-visit payment, and do not change the 30-day period payment. A 30-day period with fewer visits than its LUPA threshold is paid per visit under 42 CFR 484.230(b), and telecommunications services are not counted as visits. The plan of care must state the frequency and duration of all visits (42 CFR 409.43(a)(3)(i)(A)), and the practitioner's orders must state how often each service will be furnished (42 CFR 409.43(b)).
Where telehealth works well in practice
CMS tells agencies to report each service on the claim as a separately dated line under the revenue code for the discipline that furnished it. Remote patient monitoring that spans several days is one line, with the start date and the number of days in the units field.
Frequently asked questions
No. Only in-person visits count toward the LUPA threshold and per-visit payment. A telecommunications encounter, whether audio-video or audio-only, never counts as a visit for Medicare home health payment purposes.
Yes. Medicare requires that any services furnished via telecommunications technology be included on the plan of care, tied to patient-specific needs, and unable to substitute for a home visit ordered as part of the plan of care.
No. Reporting with G0320, G0321, and G0322 became mandatory for home health periods of care starting on or after July 1, 2023, whenever telecommunications technology is used when furnishing home health services. The codes do not affect payment.
CMS defines remote patient monitoring as the collection of physiologic data, such as ECG, blood pressure or glucose readings, that the patient or caregiver digitally stores or transmits to the home health agency. It has to be on the plan of care like any other telecommunications service. On the claim, the agency reports it with HCPCS code G0322.
No. A service furnished by telecommunications technology can be on the plan of care, but it cannot substitute for a home visit ordered as part of the plan of care. It also cannot be considered a home visit for patient eligibility or payment (42 CFR 409.43(a)(3)(i)(B)).
Related terms
The EHR that does the work for you.
See how Enzo drafts the documentation, catches the errors, and closes the episode.