Telehealth & Virtual Care Frequently Asked Questions
What should a provider evaluate before launching or expanding a telehealth program?
A provider should evaluate compliance requirements, reimbursement, staffing, workflows, policies, provider compensation, service pricing, cybersecurity, and electronic medical record capabilities before moving forward. Reviewing these areas together helps determine whether the program can operate effectively, support care delivery, and fit within the organization’s broader financial and operational model.
Why are coding, documentation, and medical necessity reviews important for virtual care?
Virtual care services must be supported by documentation that reflects the care provided, the reason the service was necessary, and the code submitted for payment. Reviewing these areas can identify gaps between clinical practice, billing, and compliance expectations before they affect reimbursement or create broader program risk.
How can rate analysis and revenue cycle review support a telehealth program?
Rate analysis can help an organization understand how telehealth services are reimbursed under its payer arrangements, while revenue cycle review examines whether those services are documented, billed, and collected effectively. Together, they can reveal where payment expectations and actual financial results are not aligned.
When might a telehealth arrangement require valuation or pricing analysis?
Valuation or pricing analysis may be appropriate when a telehealth program involves provider compensation, management or professional services agreements, business ownership interests, or fees for virtual care services. The analysis should reflect the responsibilities of each party, the structure of the arrangement, and the proposed economic terms.
What technology risks should be addressed in virtual care delivery?
Virtual care programs should evaluate cybersecurity, risk management, regulatory compliance, and the ability of electronic medical record systems to support care delivery. These technology considerations should be coordinated with staffing, policies, operational workflows, and compliance oversight so the program is not built around systems that cannot support its intended use.
