Telehealth documentation requirements determine whether your claims get paid or denied. Coders must validate specific documentation elements before submitting telehealth claims: patient consent, originating and distant site locations, technology platform used, and service modality. Without these elements clearly documented, payers will reject claims even when the service was medically appropriate and properly delivered. This guide walks through exactly what coders need to verify in the medical record to prevent telehealth claim denials.
Core documentation elements coders must verify
Every telehealth claim requires four foundational documentation elements. Missing any one of them creates denial risk.
Patient consent and acknowledgment
The medical record must show the patient agreed to receive care via telehealth. This doesn't need to be a separate signed form in most states, but the documentation must prove consent occurred.
Acceptable consent documentation includes a note stating "patient verbally consented to telehealth visit" or a checkbox in the EHR indicating consent was obtained. Some payers require documentation of the risks and benefits explained to the patient, particularly for behavioral health services.
Several states mandate written consent for specific service types. Coders should flag encounters missing any consent documentation for provider query before claim submission.
Location documentation for both sites
CMS requires documentation of where the patient was located during the encounter (originating site) and where the provider was located (distant site). This matters because payment rules vary based on geography.
The originating site determines whether facility fees apply. Patients in their homes typically generate professional fees only. Patients at a clinic or hospital may generate both professional and facility fees depending on the service type.
Documentation should include city and state at minimum. "Patient at home in Columbus, Ohio" and "Provider at Cleveland Clinic main campus" satisfies the requirement. Vague documentation like "patient at home" without a geographic identifier creates compliance risk during audits.
Technology platform and modality
The record must specify what technology was used. Audio-only telephone visits, audio-video visits, and asynchronous store-and-forward services have different coding and coverage rules.
Documentation should name the platform ("visit conducted via Zoom for Healthcare") or describe it functionally ("two-way interactive video with audio"). This proves the service met the real-time interactive communication standard most payers require.
Audio-only visits expanded during the COVID-19 public health emergency, but many payers have since restricted coverage again. When the record only documents a phone call without video, coders must verify current payer policy before assigning standard telehealth codes.
Modifier and place of service code requirements
Correct modifier and place of service (POS) code selection depends on the documentation elements above. Get these wrong and the claim will deny even if the service documentation is perfect.
When to append modifier 95 vs modifier GT
Modifier 95 indicates services rendered via real-time interactive audio and video telecommunication. This is the current standard modifier for most commercial payers and Medicare for telehealth services.
Modifier GT served the same function but has been largely replaced by modifier 95. Some Medicaid programs and a shrinking number of commercial plans still require GT. Coders need to reference current payer policy or clearinghouse edits.
The documentation must support real-time audio-video interaction to use either modifier. Audio-only services require different codes or modifiers depending on the payer and service date.
Place of service code selection rules
POS 02 designates telehealth services. Use this code when the patient is at home or another non-clinical location receiving synchronous telehealth services.
POS 10 (patient's home) was temporarily allowed for telehealth during the public health emergency. Most payers now require POS 02 instead, but documentation showing the patient was at home supports either code depending on payer instructions.
When the patient is physically in a clinic or hospital receiving telehealth from a distant provider, use the POS code matching the physical location (like POS 11 for office or POS 22 for outpatient hospital) along with the appropriate telehealth modifier. Physician coding teams must cross-reference the documented originating site with current payer POS requirements.
Documentation gaps that trigger denials
Certain documentation patterns create predictable claim denials. Coders should query these before claim submission.
Missing time documentation for time-based codes
When providers bill time-based CPT codes for telehealth visits, the record must document start and stop times or total time spent. "45-minute video visit" satisfies the requirement. "Video visit completed" does not.
Without time documentation, coders cannot select the appropriate code level. Querying the provider after the encounter risks delayed responses and claim submission backlogs.
Incomplete evaluation and management documentation
Telehealth doesn't change the core E/M documentation requirements. History, examination, medical decision making, or time must still support the code level selected.
Some providers assume telehealth visits automatically qualify as lower-level codes. The opposite is often true. Complex decision making via video still supports high-level E/M codes when documented appropriately.
Coders must apply the same documentation standards to telehealth encounters as in-person visits. A 99215 requires the same level of complexity whether delivered face-to-face or via video.
Unsigned or auto-generated notes
Many telehealth platforms auto-generate encounter notes. These templates often lack specificity and contain placeholder text that was never customized.
Notes stating "patient tolerated procedure well" when no procedure occurred, or copy-forward documentation that doesn't match the current encounter, create fraud risk. Coders should flag template language that clearly wasn't individualized.
Unsigned notes cannot be coded. Telehealth encounters move fast, and providers sometimes forget to finalize the documentation. Establish a holding queue for unsigned encounters rather than submitting claims for incomplete records.
Payer-specific policy variations
No single set of telehealth documentation requirements applies across all payers. Coders need current policy references.
Medicare maintains detailed telehealth coverage policies on the CMS telehealth webpage. The list of covered services, geographic restrictions, and originating site requirements updates regularly.
Commercial payers set their own rules. Some mirror Medicare. Others cover broader service lists or maintain audio-only coverage that Medicare discontinued. A few require prior authorization for telehealth that isn't required for in-person delivery of the same service.
Medicaid telehealth policies vary by state. Some states expanded telehealth permanently post-pandemic. Others reverted to pre-2020 restrictions. Coders working with multi-state provider groups need to track policies for each state separately.
When documentation meets CMS standards but the payer denies the claim, the issue is usually a coverage policy difference, not a documentation deficiency. Appeals should focus on payer policy interpretation rather than requesting additional documentation from the provider.
Special scenarios requiring additional documentation
Certain telehealth situations require documentation beyond the four core elements.
Behavioral health telehealth
Many states require additional consent elements for telepsychiatry and teletherapy. Documentation should show the provider discussed emergency procedures, explained limitations of remote care, and confirmed the patient has access to in-person crisis services if needed.
Some payers restrict behavioral health telehealth to established patients only. The record should clearly indicate whether this is an initial or follow-up visit.
Remote patient monitoring and asynchronous services
Asynchronous telehealth (store-and-forward) requires documentation of the images or data transmitted, when they were sent, when the provider reviewed them, and what clinical decision resulted.
Remote patient monitoring codes require documentation of the monitoring period, device used, time spent analyzing data, and communication with the patient about findings. These services have specific time thresholds. Without documented minutes, coders cannot assign the codes.
Hospital-based telehealth (tele-stroke, tele-ICU)
When a remote specialist provides consultation to a hospital patient via telehealth, documentation must show who was present at the bedside, what the consulting specialist evaluated, and what recommendations were made.
Both the bedside provider and remote consultant may bill separately depending on service type and payer rules. The documentation must support distinct contributions from each provider. Inpatient coding teams should verify each provider's documentation before assigning consultation or critical care codes.
Building a telehealth documentation audit process
Random manual review of every telehealth claim isn't sustainable. Targeted audits catch problems faster.
Flag encounters for pre-bill review when the claim includes modifier 95 or POS 02 combined with high-level E/M codes. These represent the highest dollar-value denial risk.
Run monthly reports showing telehealth claims by provider. Outliers billing significantly more telehealth visits at higher code levels than peers warrant documentation review.
Track denial reasons specifically for telehealth claims. If a particular payer consistently denies for "documentation does not support place of service," that signals a systematic documentation or coding issue that education can fix.
Build pre-bill edits into your coding workflow. When a coder assigns a telehealth modifier, the system should prompt verification that consent, location, and technology are documented. This takes seconds per claim but prevents hours of rework later.
MedCodex Health embeds these telehealth-specific audits into routine quality reviews, catching documentation gaps before claims go out. Our coders flag incomplete records for provider queries as part of the standard workflow, not as a separate post-denial process.
Frequently asked questions
What happens if telehealth consent is documented verbally but not in writing?
Verbal consent is acceptable for most payers and services as long as it's documented in the encounter note. The note should state "patient provided verbal consent for telehealth" or similar language. Written consent is only mandatory when state law specifically requires it, which applies primarily to certain behavioral health and reproductive health services. Coders should verify state requirements for the patient's location, not the provider's location.
Can coders assign telehealth codes if the provider didn't specify the technology platform?
No. The record must document whether the service used audio-video, audio-only, or asynchronous communication. Generic phrases like "remote visit" or "virtual care" don't satisfy payer requirements. Coders should query the provider to document the specific modality used before assigning telehealth codes or modifiers. Guessing the technology based on the appointment type creates compliance risk.
Do telehealth documentation requirements apply to telephone E/M codes?
No. Telephone E/M codes (99441-99443) are not telehealth services and don't require telehealth-specific documentation like originating site or consent. However, these codes have their own requirements: they must be for established patients, cannot relate to a visit in the past 7 days or lead to a visit in the next 24 hours, and require time documentation. Many payers stopped covering these codes after pandemic-era policies ended, so verify coverage before coding telephone visits.
How should coders handle documentation that says "patient at home" without specifying which state?
Query the provider for the specific location. The patient's state determines licensure requirements, coverage policies, and sometimes tax implications. Without a state documented, you cannot verify the provider was licensed to practice in the patient's jurisdiction or that the payer covers telehealth for that location. Some payers deny claims when the originating site state is missing or doesn't match their coverage area.
What documentation proves a telehealth platform met HIPAA requirements?
The medical record doesn't need to prove HIPAA compliance of the technology platform. That's a compliance department function, not a coding documentation requirement. The record should name or describe the platform used, which allows auditors to verify it was on the organization's approved list. Coders should not assign telehealth codes if the documented platform was a non-secure consumer application like FaceTime or Skype, unless temporary enforcement discretion was in effect during the public health emergency.
What this means for your revenue cycle
Telehealth documentation deficiencies create a specific type of revenue loss. The service was delivered and medically appropriate, but poor documentation makes it uncodable or leads to denial.
Pre-bill audits focused on the four core telehealth documentation elements prevent these denials. Coders catch the gaps, providers fix them quickly, and claims go out clean the first time.
If your telehealth denial rate is climbing or your coders are spending excessive time on provider queries for basic documentation elements, MedCodex Health can help. Our telemedicine documentation services include pre-bill reviews that catch missing consent, location, and modality documentation before claims submission. We work with your existing EHR and coding workflow, flagging only the encounters that need provider attention. Contact us for a workflow assessment and sample audit of your current telehealth documentation quality.