how-to
How to Protect Your Practice From Telehealth Breach Liability
Last Updated: November 7, 2026
Quick Summary
Telehealth breach liability arises when protected health information is accessed or exposed through a visit, record or message, and the practice cannot show it took reasonable safeguards. HIPAA applies to telehealth the same way it applies to in-person care, so a written policy, vendor agreements and documented training are central to reducing that exposure.
- HIPAA Privacy and Security Rules apply to telehealth services the same as in-person care.
- Obtain a business associate agreement from every telehealth vendor that handles patient data.
- Keep a dated written telehealth security policy that names owners and approved platforms.
- Document staff training with dates, attendees and topics, and refresh it after changes.
- Preserve platform logs and records immediately when a suspected breach occurs.
Table of Contents
- Why Telehealth Breaches Create Liability for Your Practice
- Common Telehealth HIPAA Violations and How They Happen
- Can a Telehealth Provider Be Liable for a Vendor's Security Breach?
- Writing a Telehealth Security Policy That Holds Up
- Responding to a Telehealth Data Breach Step by Step
- Liability Exposure Under Texas Law and Federal Rules
- Scheduling Your Telehealth Compliance Review With Brewster Law Firm
- Frequently Asked Questions
Telehealth has made patient care easier to reach, but it has also widened the surface area for data breaches, and every telehealth breach liability question starts there. When a video visit, patient record or prescription message is exposed, the practice that ran the platform can face real legal exposure. Brewster Law Firm, PLLC helps healthcare practices understand where that liability starts and how to reduce it before something goes wrong.
Why Telehealth Breaches Create Liability for Your Practice
A telehealth breach is more than a technology problem. It is a legal event that triggers obligations under federal privacy rules and state law.
The HIPAA Privacy and Security Rules apply to telehealth services the same way they apply to in-person care.
Telehealth breach liability tends to grow when a practice cannot show it took reasonable steps to protect data.
- Regulators look at whether you documented your safeguards.
- Patients look at whether you warned them and acted quickly.
- Insurers look at whether you followed your own written policies.
Common Telehealth HIPAA Violations and How They Happen
Most telehealth violations are not dramatic. They come from everyday shortcuts that add up over time.
Frequent problems include:
- Using a consumer video app that does not sign a business associate agreement (BAA)
- Recording visits to a personal device without a documented policy
- Leaving a shared login active on a clinic computer
Each of these is preventable. Many practices discover them only after an audit or a complaint.
Can a Telehealth Provider Be Liable for a Vendor's Security Breach?
Yes, in many cases a practice can remain responsible even when the breach happens at a vendor. To reduce that exposure, review guidance on selecting secure telehealth vendors before signing any agreement.
Whether a practice is liable depends on the facts, including what due diligence it performed and what its contracts required. State law may also impose duties beyond HIPAA.
Writing a Telehealth Security Policy That Holds Up
A written policy is one of the first things regulators and attorneys ask to see. For a Texas-specific starting point, see the Texas telehealth cybersecurity policy guide. It shows that your practice planned for risk instead of reacting to it. For a small practice, the goal is not a hundred-page manual, it is a short, dated document that names owners, describes the workflow, and can be produced on request.
A strong policy usually covers:
- Who may access telehealth systems, and how that access is granted and removed
- Which platforms are approved, and who must sign a business associate agreement
- How sessions are protected, including encryption and private locations
Role-Based Responsibilities
Broad recommendations become actionable only when they are assigned. The table below translates common telehealth safeguards into responsibilities for a small practice. Adapt the roles to your staffing.
| Role | Before the visit | During the visit | After the visit |
|---|---|---|---|
| Front-desk staff | Confirm patient identity and contact details; send the approved visit link; verify the patient is in a private location | Confirm the patient can see and hear the clinician; note any connection problems | Confirm the visit ended; route follow-up messages through approved channels |
| Clinician | Use the approved platform and a private room; confirm no one else is listening or recording | Verify the patient's identity; pause if an uninvited participant appears | Document the visit; report any suspected incident to the Privacy Officer |
| Practice manager | Maintain the approved-platform list and vendor agreements; confirm training records are current | Serve as the escalation point for connection or privacy problems | Log incidents; schedule the next policy review |
| IT support | Confirm multi-factor authentication and access controls are enabled; check device encryption | Monitor for outages or unusual account activity | Preserve logs; disable accounts for departing staff |
Sample Policy Language for a Small Practice
Adapt the wording below to your practice. Have counsel review it before adoption.
"All telehealth visits will be conducted only on [approved platform name], which has signed a business associate agreement with [Practice Name]. Each staff member will use a unique login and multi-factor authentication. Clinicians will conduct visits only from a private room where conversations cannot be overheard. Any suspected security incident must be reported to the Privacy Officer within 24 hours."
Add the following fields so the policy is usable rather than decorative:
- Policy owner: [name and title]
- Approved by: [name and title]
- Effective date: [date]
Training and Documentation
Training is where many small practices fall short, not because they skip it but because they cannot show it happened. Keep a simple training log with the date, the topic, the names of attendees, and a short description of the content. Refresh training when a new platform is adopted, when a staff member joins, and after any incident. A one-page acknowledgment signed by each staff member is usually enough to demonstrate awareness.
Ongoing Review and Measurable Indicators
A policy that is never reviewed becomes a liability of its own. Set a review cadence, annually at minimum, and sooner when a platform changes, a vendor agreement is renewed, or an incident occurs.
Watch out: practices often adopt a policy and then never update the approved-platform list, so staff keep using a tool the policy no longer covers.
Keep a dated record of who approved the policy and when it was last reviewed.
Responding to a Telehealth Data Breach Step by Step
When a breach is suspected, speed and documentation matter most. For the legal steps to take immediately after a breach, see legal steps after a telehealth breach. A telehealth incident is rarely a single event, it usually involves a platform, a device, a user account, and a patient record at the same time. For the specific rules that govern breach notifications in Texas, see Texas breach notification rules.

- Contain the incident. Disable the compromised account, revoke active sessions, and, if a device is involved, disconnect it from the network without wiping it. If the issue is a platform misconfiguration (for example, a waiting room that let an uninvited participant join), ask the vendor to lock the session and preserve logs. The practice manager or IT support usually owns this step.
- Preserve evidence. Keep platform audit logs, chat transcripts, screenshots, emails, and phone records. Do not delete anything, including the original notification that triggered the review. Export logs before a vendor's retention window closes, many platforms keep session logs for a limited period, so capture them early.
- Assess the scope. Identify what data was involved (demographics, clinical notes, prescriptions, images, recordings), which patients are affected, and whether the data was actually accessed or only exposed. The Privacy Officer and a clinician lead usually work together here so the clinical and legal pictures match.
- Notify required parties. HIPAA sets notification requirements for patients, HHS, and, in some cases, the media. Confirm current timing requirements at the official HHS source. Confirm the timing and content of notices with counsel before sending. Keep copies of every notice and the date it went out.
- Document everything. Record each decision, who made it, and the reason. A contemporaneous timeline is often the single most useful document if a regulator or insurer later asks what happened.
- Review and improve. Update your policy, training, and vendor oversight based on what you learned, and set a date to confirm the fixes were made.
Telehealth-Specific Incident Scenarios
A generic breach checklist does not cover the situations that actually come up in virtual care. The table below maps common telehealth incidents to the first actions and the records to keep.
| Scenario | First actions | Records to preserve |
|---|---|---|
| Compromised clinician account | Disable the account, revoke sessions, check for forwarded messages or new rules, reset credentials with multi-factor authentication | Login history, mailbox rules, any messages sent from the account |
| Exposed visit recording | Remove the recording from shared storage, identify who had access, confirm whether it was viewed or downloaded | Storage access logs, sharing settings, device used to record |
| Uninvited participant in a visit | End the session, notify the clinician and patient, review waiting-room and link settings | Platform participant log, meeting link distribution record |
| Platform outage during care | Switch to the documented downtime procedure, document the interruption, reschedule or complete by phone if appropriate | Outage notice from vendor, clinical note describing the interruption |
| Lost or stolen device used for telehealth | Remote-wipe if configured, change passwords, assess what was stored locally | Device inventory record, remote-wipe confirmation, list of accessed records |
Downtime and Continuity Procedures
A breach response and a downtime plan are related but not identical.
Watch out: staff often improvise a consumer video app or personal email during an outage, which can turn a temporary disruption into a reportable breach.
What to Hand to Counsel
When you call counsel, bring a short packet: the incident timeline, the affected platform and vendor contract, the business associate agreement, the list of affected patients, copies of any notices sent, and the current policy sections that apply. This shortens the review and helps counsel advise on notification timing and content. Acting quickly often helps determine whether a breach becomes a manageable event or a costly enforcement matter.
Liability Exposure Under Texas Law and Federal Rules
Healthcare practices face both federal and state obligations. HIPAA sets the baseline, but state statutes and medical practice rules can add requirements for breach notice, record retention and professional conduct.
Because the rules interact, a practice should not rely on a single checklist. Official state medical board and attorney general guidance may be available for review, and a licensed attorney can map those duties to your specific operations.
Scheduling Your Telehealth Compliance Review With Brewster Law Firm
Protecting your practice from breach liability is easier when the review happens before an incident. Brewster Law Firm, PLLC works with healthcare providers to assess telehealth risks, review vendor contracts and build written policies that fit real clinic workflows.
Ready to see where your practice stands? book a consultation with Brewster Law Firm, PLLC to review your telehealth safeguards before a breach forces the issue.
Frequently Asked Questions
Can a healthcare provider be liable for a telehealth data breach?
Yes. Under HIPAA, a covered entity remains responsible for protecting electronic protected health information even when it uses a third-party video platform or cloud vendor. The Office for Civil Rights can investigate and penalize a practice whose safeguards were inadequate, regardless of whether the failure began with a vendor. Liability can also arise under state privacy laws and negligence theories. A written risk analysis, a signed business associate agreement with each vendor, and documented staff training are the core steps that reduce exposure. Providers should review their obligations with counsel before an incident occurs.
What are common HIPAA violations in telehealth?
Frequent telehealth HIPAA violations include using a consumer video app that does not offer a business associate agreement, failing to encrypt data in transit, allowing unauthorized people to overhear or view sessions in an unprivate location, sharing login credentials among staff, and keeping recordings or chat logs without a retention policy. Many violations stem from missing documentation rather than a single technical failure. Conducting a risk analysis that covers every platform, device, and location used for virtual visits helps identify these gaps before a regulator does.
What should a telehealth security policy include?
A practical telehealth security policy should define approved platforms, user authentication requirements such as unique user IDs and multi-factor authentication, encryption standards, rules for private locations and screen privacy, device security including automatic logoff, recording and data retention practices, vendor management steps, and training schedules. It should also assign responsibilities by role, so the front desk, clinicians, and IT contact know what they must do. The policy should be reviewed at least annually and whenever a new platform or service is adopted.
What should a healthcare provider do after a telehealth breach?
Act quickly: contain the incident, preserve logs and evidence, and identify which patients and data were affected. Assess whether the event is a reportable breach under HIPAA, which requires notice to affected individuals without unreasonable delay, with notice to HHS and, for larger breaches, the media. Confirm current timing and content requirements at the official HHS source and review applicable state breach notification requirements with counsel. Document every step taken. Contacting legal counsel early helps preserve privilege and ensures notices are accurate.