Telehealth Claims Begin With the Right Visit Record

Telehealth visit documentation and billing is the process of recording remotely delivered care and translating that record into a claim that meets the patient’s payer requirements. For pediatric practices, this includes identifying who participated, where the child was located, how the encounter occurred, and what supported the clinical decisions and billed service.

A remote visit can be clinically appropriate yet incorrectly billed. Conversely, a correctly formatted claim can lack documentation supporting the service. The safest workflow connects scheduling, the clinical note, and claim preparation without treating any one of them as a substitute for the others.

Start with the payer’s rule for that service

“Telehealth covered” is not a complete benefit determination. Coverage may depend on the service, clinician type, patient location, communication method, and date of service. A plan that covers video follow-ups may apply different rules to audio-only encounters or preventive visits.

Pediatric teams should distinguish Medicaid fee-for-service, Medicaid managed care, and commercial plan policies. Medicare guidance can explain familiar billing conventions, but it is not a universal rulebook for children’s coverage.

Maintain a small payer reference table with these fields:

The Medicaid telehealth resource provides federal context, but the applicable state program and managed care plan remain essential sources. Do not assume a temporary coverage policy continues indefinitely.

Capture the facts that an ordinary office template misses

A telehealth note should describe the actual encounter, not simply add “seen virtually” to a standard office note.

Record the following when applicable:

• Identity and participants: Identify the child, participating parent or guardian, relationship to the patient, and other participants such as an interpreter. Verify authority to consent under applicable rules.
• Location: Record the child’s physical location during the encounter, including enough detail to support emergency response. Capture the clinician’s location when required by policy or organizational procedure.
• Encounter method: State whether the visit used synchronous audio-video or audio-only communication. Document interruptions and any change in method.
• Consent: Record telehealth consent in the form and at the frequency required by applicable law and payer policy. General registration consent should not automatically be treated as sufficient.
• Clinical evidence: Separate clinician observations from caregiver reports, patient statements, and home measurements.
• Limitations and disposition: Explain what could not be assessed remotely and whether those limitations required testing, an office visit, or urgent evaluation.

For adolescent visits, also address privacy and confidential discussion when appropriate. A parent’s presence may help with history while limiting sensitive screening. Consent, confidentiality, and proxy-access rules are related but distinct responsibilities.

A parent on the call does not answer every billing question

For pediatric clinicians, coders, and front-desk teams, a practical condition is that the child’s participation and the payer’s requirements must be established before a parent-led call is treated as a billable patient visit. A caregiver can supply important history, but that fact alone does not establish coverage, medical necessity, or the appropriate service category.

1. Hypothetical example: A parent joins a scheduled video follow-up for a child’s eczema, but the child is at school. The clinician discusses treatment response and reviews photographs uploaded earlier. The team should document that the child was absent, identify the information reviewed, and check whether the payer covers the service actually delivered. It should not describe a live examination of the child or automatically submit the usual video E/M claim. If the intended assessment requires seeing the child, arranging an appropriate follow-up may be necessary. Any billing decision should reflect the completed service rather than the appointment label.

Make the assessment support the code—not the reverse

Remote care does not lower the documentation standard for medical necessity. The note should connect the presenting problem, available findings, assessment, treatment decision, and follow-up plan.

Hypothetical example: During a video asthma follow-up, a caregiver reports nighttime cough and increased rescue inhaler use. The clinician observes the child speaking comfortably, reviews adherence and inhaler technique, and changes treatment. Document those distinct sources of information and decisions; do not insert normal auscultation findings that were never obtained.

When the applicable E/M code permits selection by medical decision-making or total time, use the chosen method correctly:

• Medical decision-making: Support the problems addressed, qualifying data, and management risk under the applicable code’s rules. Prescription drug management alone does not automatically establish the overall level.
• Time: Document the qualifying clinician time on the date of service. Exclude staff time and time for separately reported services. Connection duration alone may not represent the code’s required time.

Use current code definitions and payer instructions. Do not assume every payer accepts the same telemedicine code family, or that an older telephone code remains valid for the date of service.

Keep location, modality, and modifiers separate

These claim elements answer different questions. Place of service describes the relevant setting; a telehealth modifier identifies an encounter characteristic under the payer’s instructions. One does not replace the other.

CMS defines POS 10 for telehealth provided in the patient’s home and POS 02 for telehealth provided somewhere other than the patient’s home. Whether a particular plan requires those codes must still be checked. The clinician working from an office does not, by itself, establish the patient’s telehealth place of service.

Modifier 95 commonly identifies synchronous audio-video services, while 93 identifies qualifying synchronous audio-only services. Neither should be appended automatically: code-specific instructions and payer requirements determine their use, and some payers specify different conventions. Consult CMS telehealth guidance when Medicare rules apply.

Hypothetical example: A video connection fails before clinical assessment, and the encounter proceeds by telephone. The note should describe the change, and billing staff should evaluate the completed audio-only service against the payer’s policy—not bill video merely because video was scheduled.

Stop unsupported claims before submission

A short reconciliation step can catch mismatches that a technically valid claim will not reveal:

• Does the billed modality match the completed encounter?
• Does the place of service match the documented patient location and payer instructions?
• Were required participants present?
• Does the record support the selected service and level?
• Were other same-day services checked for bundling or duplicate billing?
• Are any required consent or authorization details missing?

For pediatric preventive care, do not assume a remote conversation fulfills every component of a comprehensive well-child service. Check coverage and completion requirements, and arrange necessary in-person measurements, examinations, screenings, or immunizations without duplicating charges.

For practices using IKON EMR, an AI-powered EMR/EHR, the governing principle is straightforward: documentation assistance must preserve encounter facts rather than manufacture completeness. Any generated note should be checked for unsupported examination findings, inaccurate participant details, and time statements that do not match the clinician’s work.

The final claim should tell the same story as the clinical record: the service actually delivered, to the documented patient, through the documented method, under the rules applicable on that date.