Telehealth Coding Documentation 2026: Compliance Checklist
The pandemic-era telehealth flexibilities that gave providers wide latitude on documentation, site requirements, and covered services have expired. What remains is a stricter, more fragmented set of rules, and the compliance burden now falls squarely on the documentation captured at the point of care. Most telehealth claim denials in 2026 do not trace back to the wrong CPT code. They trace back to a missing or vague element in an otherwise correct record. Getting the documentation right, every time, is the practical challenge this checklist is designed to solve.
The Foundational Documentation Elements Every Telehealth Claim Needs
Compliant telehealth coding documentation begins with a consistent set of elements that must appear in the encounter record regardless of the code billed, the payer, or the clinical specialty.
Provider Location and Licensure
The record must state specifically where the rendering provider was physically located during the encounter, not just the practice address on file. It must also confirm that the provider holds an active license in the state where the patient was physically located at the time of service. Confirming licensure in the patient's state at the time of the visit, not just the provider's home state, is a compliance requirement that frequently goes undocumented.
Patient's Physical Location
Documenting "patient's home" is not sufficient. The record should capture the patient's specific location: city and state at minimum, because that location determines applicable state law, payer policy, and which modifiers and place-of-service codes apply. This distinction matters especially when patients travel, work in different states, or receive care while temporarily relocated.
Technology Platform and Communication Mode
Identify the platform used for the visit and explicitly confirm that two-way audio and video were both functional throughout the encounter. If the visit was audio-only because the patient lacked video capability or declined video, that must be clearly stated in the record. Audio-only visits carry a different code set and different modifier logic, and conflating the two creates both billing errors and audit exposure.
Patient Consent
Documented patient consent to receive care via telehealth is required by most payers and by many state regulations. The consent record should be retrievable and tied to the specific encounter or clearly noted as a standing consent obtained on a documented date. Verbal consent given at the time of the visit should be noted in the encounter record itself.
Clinical Rationale
The record should include a clinical reason why telehealth was appropriate for this specific encounter. For straightforward follow-up visits this may be brief, but it should be present. Payer reviewers and auditors look for evidence that telehealth was a deliberate clinical choice, not simply a default mode of delivery.
Why State Licensure Matters Mechanically
A provider generally needs to be licensed in the state where the patient is physically located at the time of the visit, not simply where the provider's practice is based. Interstate compacts exist to streamline multi-state licensure for certain provider types, but compact membership and the specific licenses it covers vary and change. Relying on a static list of compact states is a compliance risk. The operationally sound approach is to verify current compact status and individual state licensure requirements directly through the relevant licensing boards before scheduling telehealth encounters with out-of-state patients.
Solid telemedicine documentation practices should include a pre-visit workflow step that confirms licensure is active in the patient's state before the encounter is opened in the scheduling system.
Modifier and Place-of-Service Discipline
POS 02 Versus POS 10
Place-of-service code 02 indicates that the patient was located at a telehealth site other than the patient's home. POS 10 indicates that the patient was located at home during the telehealth visit. These are not interchangeable, and using the wrong code is a clean-claims failure that triggers either a denial or a payment differential, depending on the payer.
Modifier 95
Modifier 95 indicates a synchronous telehealth service delivered via interactive audio-video communication. It belongs on claims for visits that included live, two-way video. It does not belong on audio-only claims.
Modifier GT
Medicare has largely phased out modifier GT in favor of modifier 95 for its programs, but some commercial and Medicare Advantage contracts still reference GT. Reviewing each payer's current billing guidelines before assuming modifier 95 alone is sufficient is necessary for clean claims across a mixed payer mix.
Modifier GQ
Modifier GQ applies to asynchronous store-and-forward telehealth services, meaning services where the provider reviews recorded data or images without a live patient interaction. This modifier has a narrow application and is distinct from the synchronous modifiers above.
Audio-Only Visits: A Distinct Code Set
Audio-only telephone evaluation and management services are reported using CPT codes 99441, 99442, and 99443, which are differentiated by time. G2012 applies to brief communication technology-based services. These codes exist for visits where two-way video was not used. Modifier 95, which signals synchronous audio-video, must not appear on these codes. Applying modifier 95 to an audio-only visit misrepresents the service and creates a false claim exposure. The encounter record must clearly document why the visit was audio-only so that the code selection is defensible on review.
Documentation Templates for Common Telehealth Encounter Types
Established Patient E/M Follow-Up
The template should capture: provider name and physical location, patient name and physical location (city and state), date and start/end time, platform used, confirmation of two-way audio-video functionality or audio-only notation, consent status, clinical reason for telehealth delivery, the visit's medical decision-making elements or total time documented specifically, and the billing provider's active license state matching the patient's location.
New Patient Telehealth Visit
All elements above apply, with added attention to the consent process since this is the patient's first encounter. New patient visits carry heightened scrutiny under both E/M level documentation requirements and payer medical necessity review, making the clinical rationale for telehealth and the MDM or time documentation especially important.
Behavioral Health Visit
Behavioral health telehealth visits have received extended flexibilities in some federal programs, but documentation requirements remain. Templates should include the same location, consent, and technology elements, plus the specific psychotherapy or psychiatric service code being billed, time spent, and any interactive complexity add-on code if applicable. The patient's location is particularly important for behavioral health because state-specific practice laws govern what types of behavioral health services can be delivered across state lines.
Chronic Care Management Via Telehealth
CCM documentation must capture the cumulative time spent on care management activities during the calendar month, the staff members involved, the conditions being managed, and the care plan elements reviewed or revised. When CCM is delivered via telehealth rather than in-person, the record should also note the communication mode used for any synchronous contact with the patient.
A structured CDI program support framework can help standardize these templates across care settings and ensure that providers capture each required element without adding excessive documentation burden to the clinical workflow.
The Most Common Denial Triggers in Telehealth Coding
- Missing or non-specific patient location documentation, particularly when the patient's state cannot be confirmed from the record
- Missing originating-site documentation or incorrect POS code relative to where the patient actually was
- POS and modifier mismatches, including modifier 95 on audio-only codes
- Billing a CPT code that is not on the payer's covered telehealth services list for the date of service
- E/M documentation that does not support the billed level under either medical decision-making criteria or total time
- Absent or undocumentable patient consent
- No clinical rationale documented for telehealth as the delivery mode
Commercial and Medicare Advantage Payer Variation
Traditional Medicare's telehealth policies are published and updated through the annual physician fee schedule rulemaking process. Commercial payers and Medicare Advantage plans set their own telehealth coverage lists, modifier requirements, and originating-site rules, and those policies vary meaningfully from plan to plan and from traditional Medicare. Assuming that what Medicare covers applies uniformly across all payers is a systematic billing error waiting to surface in a denial trend.
The operational necessity is to maintain current, payer-specific telehealth policy references, updated at least annually and reviewed whenever a payer issues a bulletin, and to build payer-specific edits into the billing workflow. Effective physician coding operations treat payer telehealth policy management as an ongoing task, not a one-time setup.
A Practical Monthly Audit Approach
A workable telehealth audit process does not require reviewing every claim. Sample a defined number of telehealth encounters per provider each month, enough to identify patterns without creating an unsustainable review workload. For each sampled chart, check the record against the core documentation checklist: provider location, patient location, technology and communication mode, consent, clinical rationale, E/M level support, and correct modifier and POS code.
Track denial reasons by payer and by service type. When denials cluster around a specific element, such as missing patient location or POS mismatches on a particular visit type, that pattern points to a template gap or a workflow problem that can be corrected at the source. Monthly tracking allows systemic issues to surface early, before they accumulate into a significant revenue impact or a payer audit.
Frequently Asked Questions
What is the difference between POS 02 and modifier 95?
POS 02 is a place-of-service code that indicates the patient received telehealth services at a site other than their home. POS 10 indicates the patient was at home. Modifier 95 is a claim modifier that indicates the service was a synchronous telehealth visit using interactive audio-video. Both elements appear on a telehealth claim but they describe different things: POS describes where the patient was, and modifier 95 describes how the service was delivered.
Does consent need to be documented for every visit?
Requirements vary by state and by payer. Some states require documented consent at each telehealth encounter; others accept a standing consent documented once and noted in the chart as current. Because the rules vary and change, practices should verify the specific requirement for each state where they serve patients rather than applying a single policy uniformly.
Can a telehealth visit and an in-person visit be billed on the same day for the same patient?
In general, billing both a telehealth service and a face-to-face service for the same patient on the same day requires clear documentation that each encounter was a separate, distinct clinical event with its own medical necessity. Payer policies on this vary, and some payers restrict same-day billing in specific circumstances. The documentation must make the clinical distinction between the two encounters explicit.
How long must telehealth documentation be retained?
Telehealth encounter records are medical records and are subject to the same retention standards as any other medical record. Practices should follow applicable state medical record retention law, any payer contract requirements, and federal program requirements where relevant. There is no separate, shorter retention standard for telehealth records.
For a complete review of your telehealth documentation workflows and a customized compliance checklist for your practice or health system, visit MedCodex Health's telemedicine documentation services.