Log Into Your Account


Or Create an Account
Back to Blogs

Implementing Telehealth Visits

NAMAS
2020-03-20

The following is a step-by-step guide on how to convert office-based encounters to telehealth encounters during the current COVID-19 pandemic. These rules may change post-pandemic, as many changes relaxing existing rules were made on a temporary basis by CMS and commercial payers to facilitate patient access and minimize risk of infection.

Step 1: Telehealth Consent
In order to conduct a patient encounter as a telehealth service, the patient must consent to this modality. The consent should include the patient's explicit agreement to being treated via telehealth rather than in a face-to-face encounter.
Each consent form should include the following elements:
  • Patient name and date of birth
  • Date of service
  • Rendering provider
  • Elect services as a telehealth encounter
  • Instructions regarding the proper location for the patient during the telehealth encounter
  • Patient vs. provider responsibilities in case of technical difficulties
  • Payment considerations
  • Signature or verbal attestation by the patient
The consent form for each patient should be retained permanently in their record. Examples of Telehealth Consent Forms are found on the NAMAS COVID-19 Resource Page.
 
Step 2: Scheduling
The patient should be scheduled for their telehealth encounter. If transferring from an in-person visit to a telehealth visit, maintaining the same schedule maybe appropriate. Telehealth visits may be used to care for existing patients with acute concerns or ongoing management of chronic conditions. These services and associated relaxations of telehealth rules are not limited to patients with confirmed or suspected COVID-19. Prior to scheduling, front office staff should:
  • Prep charts as usual
  • Issue appointment reminders to each patient
  • Ensure telehealth consent is on file
Process copay/payment prior to scheduled appointment time (70% of monies not collected at the time of service go uncollected). Be sure to collect phone payments.
Step 3: Telehealth Encounter
 
The rendering provider should contact the patient through electronic means. The provider may use a HIPAA-compliant, secure telehealth service/program, such as Doxy.me or VSee, although HHS has stated they will not penalize physicians who use non-HIPAA compliant software such as Skype, FaceTime, or Google Meetings. 
The rendering provider should also take some extra steps for telehealth encounters:
  • While HIPAA guidelines have been "relaxed" during the pandemic, the provider should make every effort to ensure that the telehealth encounter is conducted in a secure area to maintain patient privacy.
  • Rendering providers should keep the telehealth interface open and ready for the patient to join the session.
  • Upon entering the telehealth "exam room," the provider should consider reminding the patient of the following:
    • During this telehealth encounter medical care may be impacted by communication and therefore, the patient is encouraged to be as transparent and blunt about their concerns and complaints as possible.
    • Remind the patient that while the provider is taking precautions to ensure privacy as required by HIPAA, the patient's surroundings also pose risks of a HIPAA breach for which the provider/organization cannot be responsible.
    • Inform the patient that active treatment and care is being provided during the encounter for their presenting problem, but further workup, testing, treatment, or aftercare is the responsibility of the patient. Non-urgent healthcare services at this time may not be a high priority for referral organizations and therefore the patient may have to make an increased effort to ensure treatment plans are followed. 
  • The provider should document the encounter as they would a normal, in-person office visit.
    • History, to include CC, HPI, ROS, and PFSH should be included as these are all subjective, obtainable through the online interview process with the patient.
    • Exams will be limited, but providers are encouraged to consider what is appropriate and medically indicated. Keep in mind that not every patient requires an 8-point organ system exam. Most telehealth patients will support E/M services represented by codes 99212, 99213, or 99214 and therefore the ONLY exam elements required per 1995 documentation guidelines are:
      • 99212 - 1 organ system (this could merely be a general statement of the patient's appearance)
      • 99213 - 2 organ systems
      • 99214 - 2 organ systems with the affected organ system including 3-4 findings. This level of exam may prove difficult in the telehealth setting
      • Assessment and plan, which includes the provider's clinical assessment of the complexity of the patient's condition, and a plan of treatment must be included and would not be compromised by the telehealth setting. If the assessment may be limited based on the need for additional workup, this should be noted in the documentation.
Step 4: Selecting the appropriate reportable service
Reporting the service varies by payer. It is advisable to have the providers focus on rendering and documenting the service, allowing the staff to choose the appropriate reportable codes.
 
ICD-10-CM diagnosis coding considerations:
Guidance from the American Academy of Family Practitioners (AAFP) calls for using either J12.89 (other viral pneumonia) or B97.29 (other coronavirus as cause) as the diagnosis code for confirmed COVID-19. Note B97.29 is a supplementary code to identify a primary manifestation of COVID-19 and should not be the first-listed code. For suspected COVID-19, report ICD-10 codes for the presenting signs and symptoms. For known exposure to COVID-19 without definitive diagnosis, report Z20.828; for suspected exposure that is ruled out after exam, report Z03.818.
  
(Click for larger image)

 

Modifiers for Consideration:
  • GQ: Asynchronous telehealth service.
  • 95: Synchronous telemedicine service rendered via real-time interactive audio and video telecommunications system.
  • GT: Critical Access Hospital (CAH) distant site providers billing under CAH Optional Method II*. This goes on an institutional claim and pays 80% of the professional fee schedule rate.
  • G0 (zero): Used to identify telehealth services furnished for purposes of diagnosis, evaluation, or treatment of symptoms of an acute stroke (see below).
  • GY: Notice of Liability Not Issued, Not Required Under Payer Policy. Used to report that an Advanced Beneficiary Notice (ABN) was not issued because item or service is statutorily excluded or does not meet definition of any Medicare benefit.
*CAH payment method II allows CAHs to receive cost-based payment for facility services, plus 115% of fee schedule payment amount for professional services.
CMS offers special rules for telehealth services furnished to patients who have suffered an acute stroke. Beginning on Jan. 1, 2019, telehealth services furnished for purposes of diagnosing, evaluating, or treating the symptoms of an acute stroke do not have the usual restrictions on geographic locations and the types of originating sites associated with normal telehealth services.
To indicate such a service, the new informational HCPCS modifier G0 should be appended to the reported codes. Modifier G0 is valid for all telehealth distant site codes billed with Place of Service (POS) code 02 or critical access hospitals, CAH method II (revenue codes 096X, 097X, or 098X). The modifier should also be reported with the telehealth originating site facility fee code Q3014 (see below).
 
Place of Service (POS) Codes for Consideration:
Use POS code "02" (telehealth) for all telehealth services reported to Medicare. For commercial payers, POS "02" may not be required, but the appropriate telehealth modifier is instead required. The most common telehealth modifier for commercial payers is -95.
 
Step 5: Keep it Simple
Most carriers are allowing relaxation for telehealth services to utilize the E&M services codes in lieu of the telehealth codes. This will make coding selections seamless for the provider and their coding team. The table below was published by CMS this week to provide such guidance.