If the Video Connection Fails: A Contrast Supervision Downtime Plan

Why Downtime Planning Is a Compliance Issue, Not Just an IT Issue

CMS permanently allows the "immediate availability" requirement of direct supervision to be met virtually, effective January 1, 2026, but only through real-time audio and video. Audio-only communication doesn't meet the standard. (Background: CMS Makes Virtual Direct Supervision Permanent Effective January 1, 2026.)

That has a direct operational consequence: when the video link is down, your site may not be meeting the direct supervision requirement for new contrast administrations. A phone call keeps communication going, and it's valuable for clinical support, but it isn't a substitute for compliant virtual supervision.

A downtime plan protects three things at once:

• Patients, by making sure no one receives contrast without appropriate supervision and anyone already receiving care stays safe.

• Compliance and billing, by keeping supervision requirements met and documented.

• Operations, by restoring coverage quickly so a brief outage doesn't turn into a day of canceled studies.

First Principle: Patient Safety Always Comes Before the Connection

Before the step-by-step plan, one rule should sit at the top of every downtime policy:

A lost video connection never delays care for a patient who is having a reaction. Onsite staff treat per your contrast reaction protocol and activate your emergency response (code team or EMS) exactly as they would for any other emergency. Restoring the connection runs in parallel and never comes first.

That's why ACR guidance puts so much weight on trained onsite personnel who can recognize and begin managing contrast reactions. The remote physician directs and supports. Your onsite team has to be able to act on its own if communication fails.

Know Your Scenario: Where Was the Patient When the Video Dropped?

The right response depends on timing. Build your plan around four scenarios:

Your written policy, developed with your medical director, should spell out exactly what staff do in each scenario, especially Scenario B, where site protocols may differ.

The 6-Step Contrast Supervision Downtime Framework

Step 1: Pause Safely

The first minute sets the tone. The goal is to stop new risk from entering the situation while protecting anyone already in your care.

Checklist:

• [ ] Stop any contrast administration that hasn't yet begun.

• [ ] Assess patients who have received contrast and are still in the observation window.

• [ ] Tell the patient in plain, calm language what's happening ("We're reconnecting with our physician. You're being monitored and are safe.").

• [ ] Alert the charge technologist or lead, who owns the downtime response from here.

• [ ] Note the time the connection was lost. Everything that follows is measured from this moment.

Who does what: the technologist stays with the patient, and the lead technologist takes over restoration and communication. Separating those two roles keeps patient care from competing with troubleshooting.

Step 2: Restore Communication

Most outages are short and local. A tiered restoration sequence gets you back quickly without guesswork.

Tier 1: Fast fixes (first 1–2 minutes)

• Reconnect or rejoin the session.

• Check the local network: Wi-Fi signal, wired connection, and whether other devices are online.

• Restart the application, then the device if needed.

Tier 2: Backup path (next few minutes)

• Switch to a backup device (a second tablet, workstation, or cart kept charged and logged in).

• Switch to a backup network, such as a cellular hotspot or alternate connection, if your IT policy allows.

• Call the supervision provider's support line to confirm whether the issue is on your side or theirs.

Tier 3: Clinical contact by phone (in parallel)

• Reach the supervising physician by phone for clinical guidance on any patient already under care.

• Remember that phone contact supports patient care but doesn't restore compliant virtual supervision for new contrast administrations.

Preparation that makes this work: keep backup devices charged and tested, post support numbers at each scanner, and document which network paths are approved. The most common cause of a "vendor outage" is a site-side network problem, so knowing your own infrastructure pays off.

Step 3: Escalate Coverage

If connection can't be restored quickly, move from troubleshooting to escalation. Your policy should define a time threshold that triggers escalation automatically, so no one has to make that call under pressure.

Escalation paths:

• Backup supervising physician: your provider connects a different physician through a working channel or device.

• Onsite physician: if a qualified physician is physically present or nearby, they can provide in-person direct supervision.

• Provider incident response: for a platform-wide outage, the provider should notify affected sites, give an estimated resolution time, and put its own continuity plan into action.

Decision point: continue, delay, or reschedule. If coverage can't be restored within your defined window, the lead and medical director (or designee) decide:

• Delay contrast studies until supervision is restored

• Convert to non-contrast imaging when clinically appropriate and ordered

• Reschedule affected patients, with clear communication to them and to referring providers

Having these options pre-approved keeps a technical problem from turning into a clinical judgment call on the fly.

Step 4: Resume With Verification

Resume contrast administration only when compliant supervision is confirmed:

• [ ] Real-time audio and video are working.

• [ ] The supervising physician confirms they're available and ready.

• [ ] Patients who waited are reassessed (IV site, status, any changes).

• [ ] The time supervision was restored is recorded.

• [ ] The schedule is re-sequenced, with emergent and time-sensitive studies first.

Step 5: Document the Disruption

If it isn't documented, it's hard to show it was handled correctly. Every downtime event should produce a short, consistent record.

Downtime event record (template):

Example entries are illustrative.

Also document in the patient record any delay, conversion to non-contrast imaging, or cancellation that affects a specific patient, following your usual clinical documentation standards.

Share it with your provider. Ask your supervision provider to log the event on its side too and to include outages in its regular performance reporting. Downtime should appear in the same reports as response-time metrics.

Step 6: Test the Plan Before You Need It

A downtime plan that's never been practiced is a document, not a capability. Build testing into your routine:

Daily

• Confirm the primary and backup devices are charged, updated, and able to connect.

Monthly

• Run a 5-minute tabletop drill: the lead reads a scenario (A, B, C, or D) and the team talks through each step.

• Test the backup network path.

Quarterly

• Run a live simulation during a low-volume window: disconnect the primary device and time how long it takes to restore compliant supervision on the backup path.

• Combine it with a contrast reaction drill, so staff practice treating a simulated reaction while communication is lost.

Annually (and after any real event)

• Review the policy with your medical director, IT, and supervision provider.

• Update contact lists, escalation thresholds, and device inventory.

• Retrain new staff and refresh everyone else.

Track drill results the same way you track real events: time to restore, what worked, what didn't, and what changed as a result.

The One-Page Downtime Quick-Reference Card

Post this at every contrast-capable scanner:

VIDEO CONNECTION LOST: CONTRAST SUPERVISION DOWNTIME

1. PATIENT FIRST. Reaction in progress? Treat per protocol and activate emergency response NOW.
2. PAUSE. Do not start any new contrast injection. Note the time.
3. ALERT the lead technologist: ______________
4. RESTORE: Rejoin → check network → restart → backup device → backup network
5. CALL provider support: ______________ | Supervising physician line: ______________
6. ESCALATE if not restored in ___ minutes: backup physician / onsite physician / delay or reschedule per policy
7. RESUME only when audio + video are confirmed and the physician is ready.
8. DOCUMENT the downtime event record before end of shift.

What to Ask Your Supervision Provider About Downtime

Your plan is only as strong as your provider's side of it. Before signing, or at your next review, ask:

• What's your platform uptime commitment, and how is it measured?

• How and how quickly do you notify sites of an outage on your end?

• What backup communication paths do you support?

• How fast can you connect a backup physician when the primary can't be reached?

• Do you schedule maintenance outside our scanning hours, with advance notice?

• Will you help us design and run downtime drills?

• Do you report outages and root causes in your regular performance reporting?

For the full evaluation checklist, see The Contrast Coverage SLA: Questions Every Imaging Center Should Ask.

Frequently Asked Questions

Can we continue contrast studies by phone if the video connection fails?

CMS's permanent virtual direct supervision policy requires real-time audio and video. Audio-only doesn't meet the standard. Phone contact is valuable for clinical support of patients already under care, but new contrast administrations should wait until compliant supervision is restored, either through video or an onsite physician.

What should staff do if a patient is having a reaction when the video drops?

Treat right away according to your contrast reaction protocol and activate your emergency response. Restoring communication happens in parallel and should never delay care.

How long should we wait before escalating?

Set a specific threshold in your policy, together with your medical director and supervision provider, so escalation happens automatically instead of by judgment in the moment. Many sites set a short window for troubleshooting before moving to a backup physician or rescheduling.

What's the most common cause of a virtual supervision outage?

Many disruptions come from site-side issues like Wi-Fi drops, device problems, or network configuration rather than the provider's platform. Backup devices and backup network paths resolve most of them quickly.

How often should we test our downtime plan?

Check devices daily, run short tabletop drills monthly, run a live simulation quarterly, and do a full policy review every year and after any real event.

What documentation should we keep for a downtime event?

Record when the connection was lost and restored, which patients were affected and how, the restoration and escalation steps taken, any clinical events, the root cause, and corrective actions. Document patient-specific delays or changes in the patient record.

Sources:

• CMS CY 2026 Physician Fee Schedule Final Rule fact sheet

• Reed Smith: CMS Makes Permanent Virtual Direct Supervision for Diagnostic Tests

• ACR: Statement on Supervision of Contrast Material Administration

• Tether Supervision Blog: CMS Makes Virtual Direct Supervision Permanent