The document that outlines the criteria for services from a telehealth facility or hub is the Centers for Medicare & Medicaid Services (CMS) Conditions of Participation (CoP) framework — specifically the hospital CoP Interpretive Guidelines in Appendix A of the State Operations Manual, where "telehealth" is treated as a distinct provider type with its own facility, interfacility, and intrafacility requirements. The originating-site facility criteria sit in the hospital CoP at 42 CFR §482.12 (governing body), §482.13 (patients' rights), and §482.24 (medical records), read together with the telehealth-specific guidance CMS adds to Appendix A. The contingency and emergency handoff procedures — the part most readers actually need — live in the emergency preparedness CoP at 42 CFR §482.15 and in the transfer and discharge requirements at §482.43.

That answer needs one boundary stated up front: the exact document title and section numbers change as CMS revises Appendix A and as individual states embed telehealth rules in their own licensure codes. Confirm the current Appendix A revision on the CMS website and your state health department's telehealth page before you cite anything in a policy document. Nothing here is legal or compliance advice — it is a map to the right source.

Why the telehealth facility criteria aren't in a single stand-alone rule

There is no dedicated federal "telehealth facility CoP" document with that exact name. This is the misconception that sends administrators hunting for a phantom regulation. CMS regulates telehealth as a mode of delivering services inside an existing provider type — hospital, critical access hospital, rural health clinic, or federally qualified health center — so the criteria are distributed across that provider's CoP.

The practical effect is that a hospital-based telehealth hub must meet the host hospital's CoP in full, then layer telehealth-specific interpretive guidance on top. The Joint Commission's hospital accreditation standards mirror this structure, which is why accredited facilities often cite Joint Commission standard language rather than raw CFR text in their internal policies.

A worked example makes the distribution concrete. Suppose a 200-bed hospital runs a telehealth hub serving 14 rural clinics. Its governing-body documentation must show oversight of the hub (§482.12), its patient-rights notice must address telehealth consent and privacy (§482.13), and its medical records policy must define what the distant-site provider documents versus the originating site (§482.24). Three sections, one provider, one document set.

State law can add a fourth layer. Several states require a separate telehealth facility licensure or registration for hubs that serve patients across state lines, and those requirements are not in the federal CoP at all. Check your state's medical board and health facility licensing office, because a hub compliant federally can still be out of compliance locally.

What Appendix A of the State Operations Manual actually says about originating and distant sites

Appendix A is CMS's interpretive guidance for surveyors — the document that translates each CFR section into surveyable expectations. For telehealth, it distinguishes the originating site (where the patient is) from the distant site (where the provider is), and it places facility-condition obligations on both.

For the originating site, the guidance expects documented patient identification, a private and clinically appropriate space, and functioning technology verified before each encounter. For the distant site, it expects credentialing and privileging under the applicable CoP provisions, including the telemedicine credentialing-by-proxy pathway that CMS permits when certain written agreements exist.

The "hub" concept maps most cleanly to the distant site when the hub employs the clinicians. If your hub also functions as an originating site for specialist consults, it carries both sets of obligations simultaneously — a frequent survey finding.

CMS's own surveyor training materials, rather than the CFR text alone, are where the handoff and contingency expectations get spelled out in operational terms. That is why a policy built only from the CFR reads as compliant but fails survey: the interpretive layer adds the "show me your downtime procedure" expectation that the regulation implies but does not itemize.

The interfacility provisions: transfers between hub and spoke

Interfacility care means a patient moving between two separately certified facilities — hub to spoke, spoke to hub, or either to a third hospital. The controlling requirements are the transfer and discharge CoP at 42 CFR §482.43 and the emergency preparedness CoP at §482.15.

§482.43 requires that the hospital have a written transfer agreement or documented transfer process, that the receiving facility accept the transfer, and that the patient's medical records travel with the patient in a form the receiving facility can use. For telehealth, that means the hub must be able to transmit the encounter record, not just a verbal report.

Here is the failure case that trips most programs. A spoke clinic initiates a telehealth consult, the hub determines the patient needs emergency transfer, and the record system cannot export the consult note to the receiving hospital's EHR. The patient arrives with a verbal handoff only. That is a §482.43 documentation gap even though the clinical care was sound.

Build the transfer packet as a checklist rather than a paragraph:

1: Confirm the receiving facility has accepted the patient and record the accepting clinician's name and time. 2: Export the telehealth encounter note, imaging, and orders in a format the receiving facility can open. 3: Complete the transfer summary with reason for transfer, current condition, and interventions given. 4: Transmit the packet before or with the patient, and log the transmission time. 5: Document the verbal handoff separately if the packet cannot travel in real time.

Step 2 is where hub-and-spoke programs most often fail audit. Test the export once per quarter with a real record, not a test file, and record the result.

The intrafacility provisions: moving patients inside one certified entity

Intrafacility care covers movement within a single certified facility — for example, a patient in the emergency department receiving a telehealth consult from a specialist physically located in the same hospital but a different unit. Because no certification boundary is crossed, the transfer CoP does not apply, but the patient-rights and medical-records CoPs still do.

The intrafacility handoff expectation is continuity of the same record. If the ED physician and the remote specialist are in the same hospital, the consult note must land in the same medical record the ED is using. Splitting the record across two systems creates a §482.24 gap.

A concrete comparison shows why this matters:

Handoff type Governing requirement Record obligation Survey exposure
Intrafacility (same entity) §482.13, §482.24 Single medical record, consult note filed in same EHR Missing consult note in record
Interfacility (hub to spoke) §482.43, §482.15 Transfer summary plus transmittable encounter record Verbal-only handoff, no export
Emergency contingency §482.15 Documented downtime procedure and activation log No written downtime plan

The table's third row is the one most programs underbuild. Read it as a warning, not a checkbox.

For intrafacility telehealth, the practical control is a single patient identifier that both the originating unit and the consulting clinician use. Test it by pulling a random consult note and confirming it appears in the patient's chart under the same encounter, not a parallel one.

Contingency procedures: the downtime plan §482.15 requires

The emergency preparedness CoP at 42 CFR §482.15 requires every hospital, including one operating a telehealth hub, to have an all-hazards emergency preparedness plan, policies and procedures, a communication plan, and training and testing. For telehealth, the contingency that matters most is technology downtime — the connection fails mid-consult.

Your downtime procedure needs four named elements to survive survey. First, a defined trigger: what specifically counts as downtime (loss of video for more than a set number of minutes, total platform outage, network failure). Second, an alternate pathway: telephone-only consult, redirect to another hub, or transfer to in-person care. Third, an activation log: who declared downtime, when, and what pathway was used. Fourth, a return-to-service check before resuming normal operations.

Pick your trigger number deliberately and write it into policy. A common choice is loss of video exceeding five minutes with no restoration, but the right number depends on your clinical service lines — behavioral health tolerates audio-only longer than telestroke does.

Train and test on the schedule §482.15 sets: at least two exercises per year, one of which must be a full-scale community-based exercise, plus an annual review of the plan. A tabletop exercise that walks through a mid-consult platform failure satisfies the testing requirement and surfaces gaps a desk review misses.

Document the exercise with the scenario, participants, timeline, findings, and corrective actions. Surveyors ask for the after-action report, and a plan without one reads as untested.

Emergency handoff procedures: what happens when the consult becomes an emergency

An emergency handoff is a distinct event from a routine transfer. The patient's condition deteriorates during or because of the telehealth encounter, and care must pass immediately to a local clinician or emergency department. The requirements that apply are §482.43 for the transfer and §482.15 for the communication failure if technology is involved.

Write the emergency handoff as a sequence with named roles. The distant-site clinician declares the emergency and states it aloud on the record. The originating-site clinician assumes physical care and calls local emergency services if needed. A third person — often the hub coordinator — documents the time, the declaration, and the handoff recipient.

The failure case to plan around is the "silent handoff": the distant clinician believes the local clinician has taken over, the local clinician believes the consult is still running, and no one is managing the patient. Prevent it with a verbal read-back — the receiving clinician repeats the patient's condition and immediate plan back to the sending clinician, and that read-back is documented.

Run a quarterly drill of the emergency handoff with a scripted deterioration scenario, timed from declaration to documented handoff. Track the elapsed time and set an internal target. There is no federal numeric target for this interval, so set your own and defend it clinically.

What the document must contain to survive a survey

A compliant telehealth facility policy is a stack, not a page. It needs the governing-body oversight statement, the patient-rights and consent provisions, the medical-records rule for both sites, the transfer process under §482.43, the emergency preparedness plan under §482.15, and the downtime and emergency handoff procedures described above.

Each element should name an owner, a review cycle, and an evidence location. Surveyors do not accept "we do that" — they ask to see the document, the log, or the after-action report. If your policy names an owner who has left the organization, that is a finding.

Version control matters more than most teams expect. Appendix A and the CFR are revised periodically, and a policy citing a superseded section number signals an unmaintained program. Record the revision date of every source you cite and re-verify against the CMS website at least annually.

Keep the policy readable. A 90-page binder that no clinician opens is worse than a 20-page policy with a one-page quick-reference card at each spoke site. The quick-reference card should carry the downtime trigger, the emergency handoff read-back script, and the transfer packet checklist — the three things a clinician needs under pressure.

State licensure, accreditation, and the layers above the federal floor

Federal CoP compliance is the floor, not the ceiling. State licensure rules, payer credentialing requirements, and accreditation standards each add criteria that the CMS document does not contain.

State telehealth licensure rules vary widely. Some states require the distant-site provider to be licensed in the patient's state; others have registration pathways or interstate compacts. A hub serving patients across three state lines may need three licenses or compact registrations, and that requirement appears nowhere in Appendix A.

Accreditation adds its own survey layer. The Joint Commission, DNV, and other accreditors publish telehealth standards that interpret the CoP for their surveyed organizations. If your facility is accredited, cite both the CFR section and the accreditor's standard in your policy so a surveyor from either body can follow the trail.

Payer rules sit on top of both. Medicare telehealth coverage and originating-site rules have shifted repeatedly, and commercial payers set their own. For coverage questions, check the CMS telehealth policy page and each payer's provider manual — the rules change, and a policy written to last year's coverage rules will be wrong this year.

The practical takeaway is a layered checklist: federal CoP first, state licensure second, accreditation third, payer rules fourth. Build the policy from the bottom up and record which layer each requirement comes from.

FAQ

Is there a single federal document literally titled for telehealth facility criteria?

No — CMS regulates telehealth inside existing provider-type CoPs, so the criteria appear across the hospital CoP sections and Appendix A interpretive guidance rather than one stand-alone rule. If someone hands you a document with that exact title, verify its source on the CMS website before relying on it. The closest official sources are the CFR sections and Appendix A of the State Operations Manual.

Does the transfer CoP apply when a patient moves from a hub to a spoke in the same health system?

It applies whenever the two locations hold separate certifications, even inside one health system. Two separately certified hospitals are two facilities under §482.43, so the written transfer process and record transmittal requirements apply. If both locations operate under one certification, the intrafacility record rules govern instead.

How often must the telehealth downtime plan be tested?

§482.15 requires at least two emergency preparedness exercises per year, one of which is a full-scale community-based exercise, plus an annual plan review. A telehealth-specific downtime drill can be counted toward that testing if it is documented with a scenario, timeline, and after-action report. Quarterly drills are common practice but exceed the federal minimum.

What is the most common survey finding in hub-and-spoke telehealth programs?

Verbal-only handoffs during interfacility transfers, where the consult record cannot be transmitted to the receiving facility. It is a §482.43 documentation gap even when clinical care was appropriate. Test your record export quarterly with a real patient record to catch it before a surveyor does.

Does an audio-only fallback satisfy the contingency requirement?

It can, if your written downtime procedure names audio-only as an approved alternate pathway and defines which service lines may use it. Behavioral health programs typically permit it; telestroke and other time-critical services usually require immediate transfer to in-person care instead. The key is that the choice is written down and trained, not improvised mid-consult.

Do I need a separate telehealth license to run a hub across state lines?

Possibly — it depends on each patient's state. Some states require full licensure in the patient's state, some offer registration or compact pathways, and the requirement is not in the federal CoP. Check each state medical board and health facility licensing office, and confirm the current rules before launching cross-border service.

Who owns the telehealth policy in a hospital that both originates and receives consults?

The governing body owns it under §482.12, but operational ownership usually sits with a named telehealth director or compliance officer. Assign one accountable owner and a backup, and record both in the policy. A policy naming a departed owner is itself a survey finding.

This article is general educational information about regulatory structure, not legal, compliance, or clinical advice, and it promises no survey outcome. Telehealth rules vary by jurisdiction, accreditation body, and payer, and they change; confirm current requirements with CMS, your state licensing authority, your accreditor, and qualified local counsel before relying on anything here. If a patient is in immediate danger, contact local emergency services right away.