documenting-telemedicine-visits
Structures telehealth encounter documentation with technology modality, clinical limitations, and follow-up planning. Use when documenting virtual visits, recording telemedicine encounters, or managing remote patient care.
Best use case
documenting-telemedicine-visits is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Structures telehealth encounter documentation with technology modality, clinical limitations, and follow-up planning. Use when documenting virtual visits, recording telemedicine encounters, or managing remote patient care.
Teams using documenting-telemedicine-visits should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/documenting-telemedicine-visits/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How documenting-telemedicine-visits Compares
| Feature / Agent | documenting-telemedicine-visits | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Structures telehealth encounter documentation with technology modality, clinical limitations, and follow-up planning. Use when documenting virtual visits, recording telemedicine encounters, or managing remote patient care.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Documenting Telemedicine Visits Structures telehealth encounter documentation with technology modality, clinical limitations, and follow-up planning. ## Why This Skill Exists Telehealth visits now account for 20-30% of primary care encounters and have become a permanent component of ambulatory medicine. CMS established telehealth billing parity through the COVID-19 Public Health Emergency flexibilities, many of which have been codified into permanent policy. However, telemedicine documentation must meet specific requirements beyond standard office visit documentation: technology modality, patient location, clinical limitations of remote assessment, and informed consent. Inadequate documentation exposes practices to audit recoupment and malpractice liability. State medical boards increasingly regulate telemedicine practice standards, including establishing a patient-provider relationship, prescribing limitations (especially controlled substances per Ryan Haight Act), and cross-state licensure requirements. This skill ensures every telehealth encounter is documented with the elements required for billing compliance, medicolegal protection, and clinical completeness, while explicitly addressing the inherent limitations of remote assessment. --- ## Checkpoint A: Pre-Draft Intake (Mandatory) 1. What is the telehealth modality (synchronous video, audio-only, store-and-forward, remote patient monitoring)? **Default: synchronous video** 2. What is the patient's physical location during the visit (home, workplace, state)? **Default: [REQUIRED]** 3. What is the provider's location and state of licensure? **Default: per credentialing** 4. Has the patient provided informed consent for telehealth (documented or on file)? **Default: verify** 5. What is the reason for the visit (follow-up, acute complaint, chronic disease management, medication refill)? **Default: [REQUIRED]** 6. Is this visit appropriate for telehealth, or does it require in-person evaluation? **Default: assess** 7. What E/M code level is anticipated (99211-99215, or telehealth-specific codes)? **Default: based on MDM** 8. Does the patient have any technology issues affecting the visit (poor video quality, connectivity)? **Default: assess during visit** ### Documents to Request - Telehealth consent form (signed or verbal consent documentation) - Patient's stated physical location (address and state) - Technology platform used (HIPAA-compliant platform name) - Patient-provided vital signs if available (home BP monitor, glucometer, pulse oximeter, thermometer, weight) - Current medication list - Recent labs or imaging results relevant to visit - Prior visit notes for continuity of care - Remote patient monitoring (RPM) data if enrolled (BP trends, glucose logs, weight trends) --- ## Step 1: Telehealth Visit Header Documentation Every telemedicine encounter note MUST contain these elements in the header or visit metadata: | Required Element | Documentation Example | |---|---| | Visit type | "Telehealth visit — synchronous audio-video" | | Technology platform | "Visit conducted via [platform name], HIPAA-compliant video conferencing" | | Patient location (originating site) | "Patient located at home residence in [City, State]" | | Provider location (distant site) | "Provider at [clinic name, City, State]" | | Consent | "Patient provided verbal consent for telehealth visit, documented in chart" OR "Written telehealth consent on file dated [date]" | | Participants | "Present: patient, [caregiver/interpreter name if applicable]" | | Technology adequacy | "Audio and video quality adequate for clinical assessment" OR "Audio only due to [reason]; limitations acknowledged" | | Visit start and end time | "Visit began at [time], ended at [time]; total time [X] minutes" | --- ## Step 2: Clinical Assessment with Telehealth-Specific Documentation **History of Present Illness (HPI):** Standard documentation applies; telehealth does not reduce HPI requirements. **Physical Exam — Telehealth Adaptations:** | Exam Component | Telehealth Capability | Documentation Approach | |---|---|---| | General appearance | Full capability via video | "Patient appears well-nourished, in no acute distress, seated comfortably" | | Skin | Limited (resolution-dependent) | "Visible skin without obvious rashes or lesions via video" or "Patient directed phone camera to [area]; [findings]" | | HEENT | Partial (oropharynx limited) | "Conjunctivae clear bilaterally via video; oropharynx assessment limited by video resolution" | | Respiratory | Limited to observation | "No visible use of accessory muscles; respiratory rate appears normal; auscultation not possible via telehealth" | | Cardiovascular | Not assessable remotely | "Heart auscultation not performed — telehealth limitation; patient reports no chest pain, palpitations, or edema" | | Abdomen | Not assessable remotely | "Abdominal exam not performed — telehealth limitation; patient denies tenderness on self-palpation" | | Musculoskeletal | Partial (observation + guided ROM) | "Patient demonstrates [ROM] of [joint] via video; [observed findings]" | | Neurologic | Partial (cranial nerves, gait, coordination observable) | "Cranial nerves grossly intact via video; patient demonstrates [gait/coordination] on camera" | | Psychiatric/behavioral | Full via video | "Affect appropriate; speech normal rate and rhythm; thought process linear" | **Critical documentation principle:** Explicitly state what CANNOT be assessed and how limitations were mitigated. --- ## Step 3: Patient-Reported Vitals and Remote Monitoring Data | Vital Sign | Patient-Reported Source | Documentation Standard | |---|---|---| | Blood pressure | Home BP monitor (validated device preferred) | "Patient-reported BP [value] via home monitor [brand if known]; [seated/standing]; [time of reading]" | | Heart rate | Wearable device or pulse oximeter | "Patient-reported HR [value] via [device]" | | Temperature | Home thermometer | "Patient-reported temp [value] [oral/temporal]" | | Weight | Home scale | "Patient-reported weight [value] on home scale" | | Blood glucose | Glucometer or CGM | "Patient-reported fasting glucose [value] via [device]" | | SpO2 | Home pulse oximeter | "Patient-reported SpO2 [value] via home pulse oximeter" | **Documentation requirement:** Always note the source as "patient-reported" to distinguish from clinician-measured values. If patient does not have monitoring equipment, document: "Home vitals not available; [recommendation for in-person vitals or device provision]." **RPM integration:** If enrolled in Remote Patient Monitoring (CPT 99453-99458), reference RPM data trends: "RPM data reviewed: [X]-day average BP [value], [trend description]." --- ## Step 4: Medical Decision-Making and Plan MDM documentation for telehealth follows standard E/M guidelines (2021 AMA E/M framework): **MDM elements are identical to in-person visits:** - Number and complexity of problems addressed - Amount and complexity of data reviewed (labs, imaging, external records, RPM data) - Risk of complications, morbidity, or mortality of management decisions **Telehealth-specific plan elements to document:** 1. **In-person follow-up need:** "Patient should be seen in-person if [symptoms worsen / specific trigger] or at [date] for [exam component not possible via telehealth]" 2. **Diagnostic limitations:** "Assessment limited by inability to perform [specific exam/test]; clinical diagnosis is [presumptive/working]; differential includes [list]" 3. **Safety net instructions:** "Patient instructed to go to ED / call 911 if [specific red flag symptoms]. Return precautions reviewed." 4. **Prescriptions:** Document medical necessity for any medications prescribed, especially if controlled substances (note: DEA requires Ryan Haight Act compliance for Schedule II-V via telehealth) 5. **Referrals:** Note if in-person specialist evaluation is needed vs. telehealth-capable specialist --- ## Step 5: Billing and Compliance Documentation **Telehealth billing codes (CMS):** | Scenario | Code | Modifier | Key Requirements | |---|---|---|---| | Synchronous audio-video, established patient | 99211-99215 | Place of Service (POS) 10 (telehealth in patient home) or 02 (telehealth other) | Modifier -95 or POS code per payer | | Audio-only (telephone) | 99441-99443 | N/A | Time-based: 99441 (5-10 min), 99442 (11-20 min), 99443 (21-30 min) | | E-visit (patient-initiated portal message) | 99421-99423 | N/A | Cumulative time over 7 days; non-face-to-face | | Virtual check-in | G2012 (video), G2010 (image) | N/A | Brief, 5-10 minutes; patient-initiated | | Remote patient monitoring | 99453-99458 | N/A | Device setup, data review, clinical management | | Transitional care management (telehealth face-to-face) | 99495-99496 | POS 10 or 02 | Face-to-face component can be telehealth post-COVID flexibilities | **State-specific requirements to verify:** - Patient must be in a state where the provider holds an active license (or interstate compact applies) - Controlled substance prescribing via telehealth: initial in-person visit may still be required per Ryan Haight Act (temporary DEA flexibilities may expire) - Some states require specific telehealth consent language in writing - Medicaid telehealth coverage varies significantly by state --- ## Checkpoint B: Post-Draft Alignment (Mandatory) 1. Is the telehealth modality, platform, and consent documented in the visit header? 2. Are patient and provider locations (including states) documented? 3. Are telehealth limitations explicitly stated for each physical exam component not assessable? 4. Is the plan documented with clear in-person follow-up triggers and safety net instructions? 5. Is the billing code appropriate for the modality with correct place-of-service and modifiers? --- ## Quality Audit - [ ] Visit type (telehealth) and modality (video, audio-only, asynchronous) documented - [ ] HIPAA-compliant platform identified by name - [ ] Patient location (city and state) documented for licensure and billing compliance - [ ] Provider location documented - [ ] Informed consent for telehealth documented (verbal or written, with date) - [ ] Technology adequacy noted (audio/video quality sufficient or limitations documented) - [ ] HPI documented at same standard as in-person visit - [ ] Physical exam documents what WAS assessed and what COULD NOT be assessed via telehealth - [ ] Patient-reported vitals labeled as patient-reported with source device noted - [ ] MDM documented at standard E/M level (not reduced because of telehealth) - [ ] Safety net instructions provided with specific red flag symptoms for escalation - [ ] In-person follow-up recommendation documented when telehealth assessment is insufficient - [ ] Prescribing compliance documented (especially for controlled substances — Ryan Haight Act) - [ ] Billing code and POS/modifier are correct for the telehealth modality - [ ] Visit duration (start/end time) documented to support time-based coding if applicable --- ## Guidelines - Never perform a telehealth visit for conditions requiring hands-on examination that cannot be safely deferred (acute abdomen, chest pain requiring auscultation, new neurologic deficits requiring full exam) - Always explicitly document what physical exam components could NOT be performed remotely and how this limitation was managed - Patient-reported vitals must always be labeled as such; do not enter patient-reported BP into vital signs as if clinician-measured - The standard of care for documentation is identical for telehealth and in-person visits; telehealth does NOT lower documentation requirements - Controlled substance prescribing via telehealth requires Ryan Haight Act compliance; an in-person exam has historically been required for initial Schedule II-V prescriptions (DEA flexibilities may be temporary) - Cross-state telehealth requires active licensure in the patient's state unless an interstate compact (IMLC) applies; verify before each visit - Audio-only visits (telephone) are billed differently from audio-video visits; do not use E/M codes 99211-99215 for telephone-only encounters - HIPAA applies fully to telehealth; never use non-compliant platforms (personal Zoom, FaceTime, SMS) for clinical encounters unless covered under a public health emergency waiver
Related Skills
managing-telemedicine-technology
Evaluates and implements telemedicine technology platforms with clinical workflow integration. Use when selecting telehealth platforms, integrating virtual care technology, or managing telemedicine infrastructure.
managing-pediatric-well-visits
Structures well-child visits with age-appropriate milestones, immunization tracking, and anticipatory guidance. Use when conducting pediatric checkups, tracking development, or documenting well-child exams.
documenting-ultrasound-obstetric
Structures obstetric ultrasound reporting with biometry, anatomy survey, and growth assessment. Use when reporting OB ultrasounds, documenting fetal anatomy, or tracking fetal growth.
documenting-tumor-board-presentations
Structures multidisciplinary tumor board case presentations with radiology, pathology, and treatment synthesis. Use when preparing tumor board cases, presenting MDT discussions, or documenting consensus recommendations.
documenting-trauma-surgery
Creates trauma surgery documentation with injury severity scoring and damage control principles. Use when documenting trauma operations, calculating ISS, or recording damage control sequences.
documenting-surgical-pathology-requests
Structures surgical pathology requisitions with clinical history, specimen description, and specific diagnostic questions. Use when submitting pathology specimens, writing pathology requisitions, or requesting special studies.
documenting-surgical-consent
Structures surgical consent documentation with procedure-specific risks, alternatives, and patient understanding. Use when obtaining surgical consent, documenting risk discussions, or verifying consent elements.
documenting-resuscitation-events
Creates structured code documentation with timestamps, interventions, and ROSC criteria. Use when documenting cardiac arrests, recording resuscitation timelines, or completing code sheets.
documenting-psychotherapy-notes
Structures psychotherapy documentation meeting billing and clinical requirements. Use when documenting therapy sessions, writing progress notes, or recording psychotherapy interventions.
documenting-procedure-notes
Creates structured procedure documentation with indications, technique, findings, and complications. Use when documenting inpatient procedures, recording procedural details, or writing procedure notes.
documenting-nursing-notes
Structures nursing progress notes with SBAR communication and clinical narrative documentation. Use when writing nursing notes, documenting patient updates, or creating SBAR communications.
documenting-mental-status-exams
Creates structured MSE documentation covering appearance, behavior, speech, mood, thought, cognition, and insight. Use when documenting mental status, writing MSE sections, or describing psychiatric findings.