Most clinic-based telehealth emergency handoffs fail before the video call connects, so the clinician's first steps happen before the visit starts: confirm the patient's identity and location, verify the callback number and device, activate the site's emergency escalation protocol, and have the on-site clinical contact and local EMS number ready. The handoff only works when those pre-visit checks are complete. This video-based emergency care model is still governed by state licensure, institutional policy, and emergency medical services (EMS) jurisdiction rules, so the steps below are the common backbone, not a substitute for your own protocol.
The Pre-Visit Handoff Is a Preparation Step, Not a Transfer of Care
A telehealth emergency handoff begins the moment the clinician recognizes that a synchronous video visit may involve an emergency, and the preparation happens before the visit starts. The handoff itself is not a transfer of care. The clinician on camera keeps responsibility for the patient until a local clinician or EMS crew takes over, and preparation exists to make that local takeover fast and unambiguous.
The preparation window matters because the patient may be alone, the connection may drop, and the local first responders do not know the patient. Anything that slows their arrival β a missing street address, an unknown gate code, a phone that does not accept calls β becomes a clinical risk, not an administrative annoyance. Treat the pre-visit checklist as the distance between recognition and response.
In a clinic setting, the clinician is often seeing a patient who joined from home or from a satellite site. This is the structural difference from an in-person emergency: the person who can physically intervene is not in the room, so the handoff must be routed through people the clinician cannot see. That reality shapes every step below.
Scope boundary: this article covers preparation and coordination, not diagnosis, dosing, or treatment decisions. Those belong to your local protocols and to a clinician who can examine the patient. The checklist is educational; your institution's emergency plan and your state's telehealth rules control.
Seven Steps to Run Before the Video Connects
These seven steps run in a short window, usually two to five minutes, and the order matters when the patient is at high risk. The steps mirror what the American Telemedicine Association and most clinic telehealth policies describe as the "patient safety" and "site readiness" elements of a virtual encounter.
1: Confirm the patient's identity and exact physical location. Ask for full name, date of birth, and the street address, building, floor, and room where the patient is sitting right now. A shared device or a hotel room makes the default address wrong. 2: Verify a callback number and a second device. Ask which phone can receive a call during the visit, and whether a second device is available if the video connection fails. 3: Activate your site's emergency escalation protocol. Know which button, phone line, or on-call pager reaches your emergency escalation contact, and know the expected response window stated in your policy. 4: Identify the on-site clinical contact. Designate the person physically present at the patient's location β a nurse, medical assistant, or site coordinator β and confirm their name and direct line. 5: Have the local EMS number ready. Use the emergency number for the patient's location, not your own. In the United States that is 911; in the United Kingdom, 999; in the European Union, 112. Confirm the number for your patient's jurisdiction if you practice across borders. 6: Pre-stage the chart and transfer package. Pull the patient's identifying details, allergies, current medications, and the reason for the visit into a single handoff note before the call starts, so you are not drafting during a crisis. 7: State the plan aloud at the start of the visit. Tell the patient what will happen if an emergency develops, who will call them, and what they should do if the video drops.
If any step fails, the default is to stop and escalate. A missing address is not a documentation gap to fix later; it is a reason to keep the patient on the line until a local contact can confirm the location. A callback number that rings to voicemail before the visit is a predictor of a failed handoff during the visit.
The Location Check You Cannot Skip: Addresses, Devices, and Callback Numbers
The location check is the highest-yield step, and it is also the one most often entered incorrectly. Clinic intake systems frequently store a billing address rather than the patient's current physical location, and a patient joining from work, a relative's house, or a hotel will pass a billing-address check while sitting somewhere else. Ask the patient to read the address aloud.
Device verification matters because the handoff often requires a phone call while the video visit is still open. If the patient is on a phone with no second line, the clinician cannot call a local contact and keep the video running at the same time. Ask directly: "Is there a second phone or device in the room?" If not, agree in advance that the video will be paused so the phone can be used.
Callback numbers fail in predictable ways. A patient may give a number that is a shared family phone, a work extension that routes to a receptionist, or a number with poor signal in the room. Confirm which number will actually reach the patient within sixty seconds, and record the second-best option. If the patient is a minor or a dependent adult, confirm the guardian or caregiver's number at the same time.
Documentation should be contemporaneous, not reconstructed. Write the confirmed address, callback number, second device, on-site contact, and EMS number into the chart before the video visit begins, not after an emergency occurs. If your platform supports a pre-visit note template, build those fields in so the step is one screen rather than five.
Build the Local Response Chain Before You Need It
The local response chain is the sequence of people who can physically reach the patient, and it should be named before the visit, not discovered during it. In a hospital-based clinic, the chain often runs from the telehealth clinician to a site coordinator to the on-site nurse to the facility's rapid response team or local EMS. In a community clinic, the chain may be shorter, ending with a designated staff member and a local ambulance service.
Name a single on-site contact, not a role. "The nurse on duty" is a role; "Jordan Reyes, site coordinator, direct line 555-0142" is a contact. During a handoff, the clinician should be able to say a name and a number without hunting through a directory. If the site has no on-site clinical staff, the chain should route directly to the patient's emergency contact and local EMS.
Confirm the response window for your escalation path. Many clinic telehealth protocols define a target for the clinician-to-local-contact handoff, but the specific target varies by institution and jurisdiction, so confirm the number in your own policy rather than assuming a standard. The point of the pre-visit step is to know what "fast enough" means at your site before you need it.
Test the chain on a schedule. A contact list that was accurate at onboarding drifts as staff change roles, and a stale number is worse than no number because it creates false confidence. Quarterly verification of on-site contacts and EMS numbers is a reasonable cadence for most clinics, and any change in site staffing should trigger an immediate update.
Prepare the Transfer Package: Identity, Allergies, Medications, Reason for Visit
The transfer package is the set of facts that local responders need in the first thirty seconds, and it should be assembled before the video visit, not during an emergency. At minimum it contains the patient's legal name, date of birth, current physical address, callback number, known allergies, current medications, relevant history, and the reason the visit is happening today. A concise package beats a comprehensive one.
The failure case is a chart that is complete but unsearchable. If the allergies are buried three tabs deep and the current medication list is a scanned fax, the clinician cannot read it aloud to a paramedic under time pressure. Build a one-page handoff note, either in the EHR or in a shared document, and keep it open during the visit. This is the same logic that drives structured handoff tools in hospital medicine.
Identity verification has a specific telehealth wrinkle: the patient may be using a device registered to someone else, and the video platform may display a different name than the chart. Confirm the name on the account and the person on camera match, and document the discrepancy if they do not. A mismatch is not automatically a problem, but it is a fact the local responders will need.
The reason for the visit should be written in plain language, not a billing code. "Chest tightness since this morning, worse with exertion" tells a paramedic more than a diagnosis code, and it gives the on-site clinician a starting point. Write it before the call if the intake note allows, and update it in the first minute of the visit.
Table: Pre-Visit Readiness Elements and What "Ready" Looks Like
Use this table as a self-audit before a high-risk virtual visit. Each row states the element, the evidence that it is ready, and the failure signal that means it is not.
| Readiness element | Evidence it is ready | Failure signal |
|---|---|---|
| Physical location | Patient reads the full street address, floor, and room aloud | Address matches billing record but patient cannot describe the room |
| Callback number | A test call or confirmed ring reaches the patient within 60 seconds | Number routes to voicemail, receptionist, or a shared family phone |
| Second device | A second phone or tablet is in the room and charged | Only one device, no speakerphone available |
| On-site contact | Named person with a direct line, confirmed present at the location | Role only ("the nurse"), or no one physically on site |
| EMS number | Number for the patient's jurisdiction confirmed and visible | Clinician relies on memory or the number for a different region |
| Transfer package | One-page note open with identity, allergies, medications, reason | Information scattered across tabs or scanned documents |
| Escalation path | Button or pager tested, response window known from policy | Clinician unsure which line reaches the on-call contact |
The verdict rule: if two or more rows show a failure signal, treat the visit as high-risk and complete the missing elements before continuing. One failure signal is a prompt to fix that element; three is a reason to pause and call the on-site contact first.
The First Sixty Seconds of the Call: Script, Confirmation, and Escalation Trigger
The first sixty seconds of the video visit should be scripted, because the clinician's opening words set the patient's expectations for what happens if something goes wrong. A short, plain-language opening works better than a formal disclosure. The clinician confirms identity and location, states that emergency help will be arranged if needed, and names what the patient should do if the call drops.
A usable script is short. "Before we start, I want to confirm you're at [address], and that this number reaches you if we get disconnected. If something urgent happens during our visit, I'll stay with you while my team contacts local emergency services. If the video freezes, call this number and stay on the line." Adapt the wording to your site, but keep the three elements: location, callback, and escalation plan.
The escalation trigger should be defined before the visit, not negotiated during it. If the patient reports chest pain, stroke symptoms, severe shortness of breath, or any symptom your protocol flags as time-critical, the clinician moves to the handoff sequence without waiting for a full assessment. The trigger belongs in the pre-visit plan so the decision is not made under pressure.
Rehearse the opening once per shift if your clinic runs high-risk virtual visits. A script that has been said aloud once is faster and calmer in a real event, and the rehearsal surfaces gaps β a dead phone line, a missing on-site number β while there is still time to fix them. This is a low-cost step with a measurable payoff in handoff speed.
Video Failure and Connectivity Edge Cases: When the Call Drops Mid-Handoff
The most common edge case is a dropped video connection in the middle of a handoff, and the pre-visit preparation should make the recovery automatic. The clinician's fallback is a phone call to the callback number, and the patient's fallback is to call the clinic's published number and stay on the line. Both fallbacks should be stated in the opening sixty seconds.
Audio-only fallback deserves its own plan. If the video platform fails but the phone line works, the clinician can continue the handoff by voice, using the same script and the same trigger criteria. The transfer package should be readable without the video, which means the one-page handoff note has to work as a phone script. Design it that way.
Platform-specific behavior varies, so confirm the disconnect notification in your own platform's documentation rather than assuming. Some platforms alert the clinician when the patient drops; others do not, and the clinician may not notice for several seconds. The named source to check is your vendor's administrator documentation, and the verification path is a test call with a colleague.
A second edge case is a patient who cannot speak or hear well enough for the script. In that situation, the on-site contact becomes the communication channel, and the callback number should be the on-site contact's line rather than the patient's. If no on-site contact exists, the clinician should use the platform's chat function to confirm location in writing before continuing.
Table: Responsibilities Across the Handoff Chain
The handoff chain has four links, and each one owns a specific task. The table below is the division of labor most clinic telehealth protocols use; confirm the boundaries against your own policy.
| Role | Owns before the visit | Owns at the escalation trigger |
|---|---|---|
| Telehealth clinician | Identity and location confirmation, callback and device check, escalation line visibility, transfer package open | Stays with the patient, states the plan aloud, reads the transfer package to local responders |
| On-site clinical contact | Physical presence at the patient's location, direct line confirmed | Receives the handoff, begins local assessment, meets EMS on arrival |
| Site coordinator or scheduler | Contact list accuracy, EMS number verification, platform readiness | Notifies the on-call clinician and the receiving facility |
| Local EMS or receiving facility | Number on file, response window known | Takes over care and transport |
The verdict rule for this table: the clinician never owns the physical response, and the on-site contact never owns the remote assessment. When a role is unfilled β no on-site contact, no confirmed line β the chain defaults to the clinician plus local EMS, and the pre-visit step is to state that fallback explicitly.
The table also exposes a common gap: the site coordinator role is often informal, held by whoever answers the phone. Naming the role and the person, and keeping the contact list current, is the cheapest fix available to most clinics.
Documenting Readiness and Running a Five-Minute Drill
Documentation of pre-visit readiness is a quality measure, not a bureaucratic formality. Record the confirmed location, callback number, second device, on-site contact, and EMS number in the chart before the visit. If an emergency occurs, the note becomes the evidence that the handoff was prepared, and the review can focus on what actually happened rather than reconstructing what was known.
A five-minute drill is the practical way to test the whole chain. Once a month, a clinician and a site coordinator run a simulated handoff: confirm location, read the callback number, call the escalation line, and time how long it takes to reach the on-site contact. The number that comes out of the drill is the number the clinic should plan around, and it will differ from the target in the policy.
Track a small set of metrics. Time from escalation trigger to on-site contact reached, time from trigger to EMS notified, percentage of high-risk virtual visits with all readiness elements documented, and the number of stale contacts found during quarterly verification. These four are enough to spot a degrading chain before a real event exposes it.
Feed the drill results back into the checklist. If the drill shows the escalation line takes ninety seconds to answer, the pre-visit step should include a direct number to the on-site contact as the first call, not the escalation line. The checklist is a living document, and the drill is how it stays accurate.
FAQ
Does the pre-visit checklist apply to every telehealth visit or only high-risk ones?
It applies in proportion to risk. Every visit should have confirmed identity, location, and callback number; the full chain β on-site contact, EMS number, transfer package, escalation line β should be ready before any visit where the intake note flags time-critical symptoms. Clinics that run the full checklist only on high-risk visits report that the partial version becomes routine within a few weeks. Decide the threshold in your policy, not at the clinician's discretion.
What if the patient refuses to share their physical location?
A refusal is itself a clinical finding. The clinician should explain that the location is needed only for emergency response and is protected under the same privacy rules as the rest of the record. If the patient still declines, document the refusal, keep the visit audio-only if your policy allows, and treat the visit as high-risk with the callback number as the only contact path. Your institutional privacy office should have a script for this; confirm it before the situation arises.
Is 911 always the right number to have ready?
No. 911 is correct for the United States, but a patient in the United Kingdom needs 999, and one in the European Union needs 112. A patient in a U.S. territory or on a federal facility may have a different number, and a patient traveling internationally needs the local emergency number for that country. Confirm the number for the patient's actual location, not the clinic's location.
How is a clinic-based telehealth emergency handoff different from a hospital transfer?
A hospital transfer moves the patient between facilities, while a clinic-based telehealth handoff moves responsibility from a remote clinician to a local responder, often without a receiving hospital being named. That means the handoff package must be readable by a paramedic in the field, not just a receiving physician. The transfer-package logic is the same, but the audience is different, and the pre-visit steps should reflect that.
Can a medical assistant run the pre-visit checklist instead of the clinician?
Yes, in many clinics the medical assistant or site coordinator completes the readiness elements and documents them, and the clinician verifies them in the opening sixty seconds. The division works because the clinician owns the clinical judgment and the assistant owns the logistics. The failure mode is a checklist that is completed but not verified β the clinician should always confirm location and callback number personally, even if the fields are already filled.
What should the clinic do when the on-site contact cannot be reached during a drill?
Escalate to the fallback path immediately and document the attempt. The fallback is usually direct contact with local EMS plus the patient's emergency contact, and the drill should time how long the fallback takes. A drill that surfaces an unreachable contact is a successful drill, because it found the problem before a real event did. Update the contact list and re-run the drill within the week.
Does the handoff preparation create extra liability if an emergency happens anyway?
Documented preparation supports the standard of care rather than creating new exposure, because it shows the clinician planned for the emergency and followed the site's protocol. The greater risk is an undocumented, improvised handoff that cannot be reviewed afterward. Your malpractice carrier and your legal counsel can confirm how your jurisdiction treats telehealth documentation; this article cannot give legal advice.
What is the single most important pre-visit step if time is short?
Confirm the physical location and the callback number, in that order. Those two facts determine whether local help can find the patient and whether the clinician can stay in contact when the video fails. Everything else in the checklist is valuable, but those two are the ones that make a handoff possible at all. If only one minute is available, spend it on location and callback.
This article is general educational information about clinic-based telehealth emergency handoff preparation. It is not a diagnosis, treatment plan, legal opinion, or substitute for your institution's emergency protocol, your state licensure rules, or the advice of a qualified local clinician or attorney. Emergency response procedures vary by jurisdiction, facility, and platform, so confirm the specific numbers, roles, and response windows with your own clinical leadership and legal counsel before relying on them. If a patient is in immediate danger or at risk of self-harm, contact local emergency services such as 911 in the United States, 999 in the United Kingdom, or 112 in the European Union right away.