Healthcare business law · Updated
HIPAA for telehealth: what a telehealth practice must have in place
HIPAA applies to a telehealth provider that is a covered entity, meaning one that transmits health information electronically in a standard transaction such as a claim or an eligibility check, and to every vendor that handles its patients' information as a business associate. The COVID-19 flexibility that let providers use consumer video apps without HIPAA penalties expired at 11:59 p.m. on May 11, 2023, and its transition period ended at 11:59 p.m. on August 9, 2023. A covered telehealth practice now needs a written business associate agreement with each video, records, messaging and hosting vendor, a documented Security Rule risk analysis and safeguards, and a breach plan that meets the 60-day notice deadline. HHS published a final rule changing the Privacy Rule on November 19, 2026, with compliance due by July 19, 2027, but the stricter Security Rule it proposed in January 2025 had been neither finalized nor withdrawn as of November 21, 2026.
| Question | The rule | Source |
|---|---|---|
| Is the practice covered? | Yes if it is a health care provider that "transmits any health information in electronic form in connection with a transaction" covered by the HIPAA rules, such as a claim, an eligibility check or a referral authorization | 45 CFR 160.103 |
| Which vendors are business associates? | Any person that creates, receives, maintains or transmits protected health information for the practice, and their subcontractors that do the same | 45 CFR 160.103; 164.504(e) |
| Can it use any video app? | No. The COVID-19 enforcement discretion expired May 11, 2023; its transition period ended August 9, 2023 | 88 FR 22380 |
| Risk analysis | Required: an accurate and thorough assessment of the risks to its electronic health information, then security measures to reduce them | 45 CFR 164.308(a)(1) |
| Encryption | "Addressable" today: assess it, then implement it, or document why not and adopt an equivalent alternative if reasonable and appropriate | 45 CFR 164.312(a)(2)(iv), (e)(2)(ii); 164.306(d) |
| Breach notice to patients | Without unreasonable delay and no later than 60 calendar days after discovery | 45 CFR 164.404 |
| Breach notice to HHS | 500 or more people: at the same time as patient notice; fewer than 500: within 60 days after the end of the calendar year | 45 CFR 164.408 |
| Breach notice to the media | More than 500 residents of one state: prominent media outlets serving that state, within 60 days | 45 CFR 164.406 |
| Vendor's notice to the practice | Without unreasonable delay and no later than 60 calendar days after the vendor discovers the breach | 45 CFR 164.410 |
| Keeping the paperwork | Security policies and records kept 6 years from creation or last effective date, whichever is later | 45 CFR 164.316(b)(2) |
| North Carolina breach law | Notice to affected people without unreasonable delay and a report to the Attorney General's Consumer Protection Division, when the breach involves personal information as the state defines it | NC DOJ |
| Culpability | Minimum per violation | Maximum per violation | Calendar-year cap in the regulation |
|---|---|---|---|
| Did not know, and with reasonable diligence would not have known | $145 | $73,011 | $2,190,294 |
| Reasonable cause, not willful neglect | $1,461 | $73,011 | $2,190,294 |
| Willful neglect, corrected within 30 days | $14,602 | $73,011 | $2,190,294 |
| Willful neglect, not corrected within 30 days | $73,011 | $2,190,294 | $2,190,294 |
| Proposal | Proposed section |
|---|---|
| "Encrypt all electronic protected health information at rest and in transit", with listed exceptions | 164.312(b) |
| "Deploy multi-factor authentication to all technology assets", with listed exceptions | 164.312(f) |
| A written technology asset inventory and network map, updated at least every 12 months | 164.308(a)(1) |
| Restore critical systems and data "within 72 hours of the loss" | 164.308(a)(13) |
| Written verification from each business associate of its safeguards at least once every 12 months | 164.308(b)(2) |
| A documented compliance audit at least once every 12 months | 164.308(a)(14) |
| Vulnerability scans at least every six months and penetration testing at least every 12 months | 164.312(h) |
When a telehealth business is covered by HIPAA
HIPAA does not apply to telehealth as such. It applies to covered entities and their business associates. A health care provider is a covered entity if it "transmits any health information in electronic form in connection with a transaction covered by this subchapter", and the covered transactions include health care claims, eligibility checks, claim status and referral authorizations (45 CFR 160.103). In our reading, a telehealth practice that bills any health plan electronically, or uses a billing company that does, is a covered entity, and its duties then extend to the records of all of its patients, cash-pay patients included.
A practice that takes only cash and never conducts one of those transactions electronically may fall outside that definition. That does not leave it free of privacy law. The FTC's Health Breach Notification Rule can reach personal health record vendors and health apps that HIPAA does not cover; the FTC's guidance says "You're not a vendor of personal health records if you're covered by HIPAA" (FTC). State breach laws still apply, and the North Carolina Medical Board's telemedicine statement says "HIPAA and related privacy and security documents should be present and signed where appropriate" (NCMB). Our view: a telehealth company that may ever bill insurance should build to HIPAA from the start, because rewriting vendor contracts later is slower than signing the right ones now.
The COVID-19 telehealth flexibility is over
In a notification published in April 2020, HHS's Office for Civil Rights said it would not impose HIPAA penalties on providers using a "non-public facing remote communication technology" for good-faith telehealth, for any reason, whether or not the visit related to COVID-19. That notification expired with the public health emergency at 11:59 p.m. on May 11, 2023. OCR then gave covered providers a 90-calendar-day transition period, which "will expire at 11:59 p.m. on August 9, 2023", and suggested using it for steps such as "choosing a telehealth technology vendor that will enter into a business associate agreement" (88 FR 22380).
Every telehealth visit since then is judged under the ordinary HIPAA Rules. A consumer video or messaging app whose vendor will not sign a business associate agreement is not a compliant way for a covered practice to see patients.
Business associate agreements: which telehealth vendors need one
A business associate is a person that "creates, receives, maintains, or transmits protected health information" for a covered entity's regulated function, and the definition expressly includes e-prescribing gateways and other data transmission services that need routine access to the information (45 CFR 160.103). In our reading, for a telehealth practice that usually means the video platform, the electronic health record, e-prescribing, patient messaging and texting tools, cloud hosting, the answering service, the billing company and any outside IT support with access to records. A practice may let a vendor handle electronic health information "only if the covered entity obtains satisfactory assurances", given in a business associate contract (45 CFR 164.308(b)(1)). Disclosures to another provider for a patient's treatment do not make that provider a business associate.
The contract's required terms are set by 45 CFR 164.504(e). A business associate agreement that is missing any of them is not compliant, whatever the vendor's marketing says. It must:
- set out the permitted and required uses and disclosures of the information, and bar any others;
- require appropriate safeguards and compliance with the Security Rule for electronic information;
- require the vendor to report any use or disclosure the contract does not allow, "including breaches of unsecured protected health information";
- require each subcontractor that handles the information to agree to the same restrictions;
- support patients' rights of access, amendment and an accounting of disclosures;
- make the vendor's books and records available to HHS;
- require the return or destruction of the information when the contract ends, where feasible; and
- let the practice terminate the contract if the vendor violates a material term.
Phone calls, audio-only visits and recordings
The regulation's definition of electronic media says that certain transmissions "of voice, via telephone, are not considered to be transmissions via electronic media if the information being exchanged did not exist in electronic form immediately before the transmission" (45 CFR 160.103). In our reading, a call over a traditional phone line, of information that did not exist in electronic form just before the call, is outside the Security Rule, although the Privacy Rule still governs what is said and to whom. In the same reading, a call through an internet-based or app-based service, and any electronic recording, transcript or note of it, is electronic health information the Security Rule covers, and a vendor that stores it is a business associate.
Whether an audio-only visit is paid is a separate question. For Medicare, CMS says beneficiaries "may continue to receive audio-only telehealth services in their homes through December 31, 2027" (CMS Telehealth FAQ, updated October 2026).
The Security Rule: what a telehealth practice must have in place
The Security Rule is scaled to the business: a practice weighs its size and capabilities, its technical infrastructure, "the costs of security measures" and the probability and criticality of the risks (45 CFR 164.306(b)). "Addressable" does not mean optional. For an addressable item such as encryption, the practice must assess whether it is reasonable and appropriate, implement it if so, and if not, document why and adopt an equivalent alternative where reasonable (164.306(d)(3)). The core items for a telehealth practice are:
- a written risk analysis, "an accurate and thorough assessment of the potential risks and vulnerabilities", and a risk management plan (164.308(a)(1));
- a named security official (164.308(a)(2));
- security training for the whole workforce, "including management" (164.308(a)(5));
- incident response procedures and a contingency plan with data backup and disaster recovery (164.308(a)(6), (7));
- a unique log-in for every user, audit controls that record activity, and procedures to verify who is accessing records (164.312(a), (b), (d));
- an encryption decision for stored data and for data in transit, documented either way (164.312(a)(2)(iv), (e)(2)(ii)); and
- written policies, kept for 6 years and reviewed "periodically" (164.316).
Breach notice: the federal deadlines and North Carolina's law
An impermissible use or disclosure of protected health information is presumed to be a breach unless the practice shows, through a risk assessment of at least four factors, "a low probability that the protected health information has been compromised" (45 CFR 164.402). Information that has been rendered "unusable, unreadable, or indecipherable to unauthorized persons" through a technology or method HHS specifies in guidance is not "unsecured", and the notice rules apply only to unsecured information. The clocks run from discovery, which is the first day the breach is known or would have been known with reasonable diligence: notice to each patient without unreasonable delay and "in no case later than 60 calendar days after discovery of a breach" (164.404), notice to HHS and, for more than 500 residents of a state, to the media (164.406, 164.408). A vendor has the same 60-day outer limit to tell the practice (164.410), so the business associate agreement should set a much shorter one.
North Carolina's Identity Theft Protection Act is a separate duty. The NC Department of Justice says a business that owns or licenses personal information and suffers a security breach must notify the people affected, the notice "must be clear and conspicuous and given without unreasonable delay", it "can only be delayed at the request of law enforcement", and the business must also report the breach to the Attorney General's Consumer Protection Division (NC DOJ). The Department's list of personal information covers identifiers such as Social Security, driver's license, passport and financial account numbers and some log-in credentials; health information is not on it. A telehealth breach that exposes payment cards or Social Security numbers along with records can trigger both laws.
Penalties
HHS's civil money penalties run by culpability tier, from $145 per violation where the practice did not know and could not reasonably have known, up to $2,190,294 for willful neglect not corrected within 30 days (45 CFR 102.3). Those are the 2025 amounts; HHS announced on October 21, 2026 that it "will continue to use the 2025 civil monetary penalty levels because there will be no cost-of-living adjustment for 2026" (91 FR 66566). Since 2019 HHS has also applied lower annual limits per tier as a matter of enforcement discretion: $25,000, $100,000, $250,000 and $1.5 million before inflation adjustment, and it said that approach is "effective indefinitely" (84 FR 18151).
Rule changes: the Privacy Rule final rule and the proposed Security Rule
The Privacy Rule is changing. HHS published a final rule, "HIPAA Privacy Rule: Changes To Support Coordinated Care and Individual Engagement and Reduce Regulatory Burdens", in the Federal Register on November 19, 2026 (91 FR 74848, FR Doc. 2026-23429). In its own words, "The final rule is effective on January 19, 2027," and regulated persons "must comply with the applicable requirements of this final rule by July 19, 2027." In our reading, the change a telehealth practice will feel first is the deadline for patients' requests for their records: today it must act "no later than 30 days after receipt of the request", with one extension of up to 30 days (45 CFR 164.524(b)(2)); the final rule cuts the first period to "no later than 15 calendar days", keeping one extension of up to 30 calendar days. It does not change the Security Rule. What it changes in vendor contracts is in Business associate agreements.
On January 6, 2025 HHS proposed a rewrite of the Security Rule, "HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information" (90 FR 898, RIN 0945-AA22). By "expressly requiring regulated entities to encrypt ePHI, with limited exceptions", it would end the case-by-case decision on encryption; it would also require multi-factor authentication and add the inventories, testing and vendor verification in the table above, with compliance proposed for "180 days after the effective date of a final rule". Comments closed March 7, 2025. As of November 21, 2026 the Federal Register shows no final rule, withdrawal or other document under that RIN. Until a final rule is published, the current rule governs. In our view, a telehealth company choosing vendors now should still ask for encryption at rest and in transit and multi-factor log-in, since an honest risk analysis under the current rule will usually point there anyway.
HIPAA is one item on a longer list. For the rest, from ownership to licenses, prescribing, payers and clinician contracts, see Starting a telehealth company: the legal checklist, and for licensing across state lines see Telehealth across state lines.
Common questions
Does HIPAA apply to telehealth?
Yes, for a telehealth provider that is a covered entity, meaning one that sends health information electronically in a standard transaction such as a claim or an eligibility check, and for its vendors as business associates (45 CFR 160.103). The same rules apply to a video visit as to an office visit.
Is the COVID-19 HIPAA telehealth waiver still in effect?
No. HHS's telehealth enforcement discretion expired at 11:59 p.m. on May 11, 2023, and the 90-day transition period ended at 11:59 p.m. on August 9, 2023 (88 FR 22380).
Does a cash-only telehealth practice have to follow HIPAA?
Possibly not, if it never conducts a covered transaction electronically, directly or through a billing company. It still has state breach-notice duties, the Medical Board's expectations on privacy, and possibly the FTC's Health Breach Notification Rule, and it becomes a covered entity once it conducts a covered transaction electronically.
Do I need a business associate agreement with my telehealth video platform?
Yes, if the platform creates, receives, maintains or transmits patient information for your practice. The agreement must contain the terms in 45 CFR 164.504(e), including breach reporting and flow-down to subcontractors.
Is encryption required for telehealth under HIPAA?
Today it is an addressable specification: the practice must implement it or document why it is not reasonable and appropriate and adopt an equivalent alternative if reasonable and appropriate (45 CFR 164.306(d), 164.312). The January 2025 proposal would make it mandatory, with exceptions, but it has not been finalized.
How fast must a telehealth practice report a breach?
Patients must be told without unreasonable delay and no later than 60 calendar days after discovery (45 CFR 164.404). HHS is told at the same time if 500 or more people are affected, otherwise within 60 days after the end of the year. North Carolina adds a report to the Attorney General when the breach involves personal information as the state defines it.
Was the 2025 HIPAA Security Rule update finalized?
Not as of November 21, 2026. The Federal Register shows only the January 6, 2025 proposed rule (90 FR 898) under RIN 0945-AA22, with no final rule or withdrawal.
Update log
- November 21, 2026. Added the HIPAA Privacy Rule final rule published November 19, 2026 (91 FR 74848): effective January 19, 2027, compliance by July 19, 2027, and the shorter 15-day deadline for patients' record requests. Rechecked the January 2025 Security Rule proposal: still no final rule or withdrawal as of November 21, 2026.
- November 16, 2026. Published. 45 CFR parts 160, 164 and 102.3 (eCFR, up to date as of November 12, 2026), OCR's April 2023 expiration notice, the January 2025 proposed Security Rule and a Federal Register check of its status, HHS's 2019 and October 2026 penalty notices, the CMS Telehealth FAQ, the NC Department of Justice breach page, the FTC's Health Breach Notification Rule guidance and the Medical Board's telemedicine statement, all read at the source November 16, 2026.
Sources
- 45 CFR 160.103, definitions: business associate, covered entity, electronic media, transaction (eCFR, up to date as of November 12, 2026)
- 45 CFR 164.306, Security standards: general rules
- 45 CFR 164.308, Administrative safeguards
- 45 CFR 164.312, Technical safeguards
- 45 CFR 164.316, Policies, procedures and documentation
- 45 CFR 164.402, Breach definitions
- 45 CFR 164.404, Notification to individuals
- 45 CFR 164.406, Notification to the media
- 45 CFR 164.408, Notification to the Secretary
- 45 CFR 164.410, Notification by a business associate
- 45 CFR 164.504(e), Business associate contracts
- 45 CFR 164.524, Access of individuals to protected health information
- 45 CFR 102.3, Inflation-adjusted civil money penalty amounts
- HHS OCR, Notice of Expiration of Certain Notifications of Enforcement Discretion, 88 FR 22380 (April 13, 2023)
- HHS, HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, proposed rule, 90 FR 898 (January 6, 2025)
- HHS OCR, HIPAA Privacy Rule: Changes To Support Coordinated Care and Individual Engagement and Reduce Regulatory Burdens, final rule, 91 FR 74848, FR Doc. 2026-23429 (November 19, 2026)
- HHS, No Adjustment to HHS Civil Monetary Penalty Amounts for 2026, 91 FR 66566 (October 21, 2026)
- HHS, Notification of Enforcement Discretion Regarding HIPAA Civil Money Penalties, 84 FR 18151 (April 30, 2019)
- CMS, Telehealth FAQ (updated October 2026)
- North Carolina Department of Justice, Security Breach Information
- FTC, Complying with FTC's Health Breach Notification Rule
- North Carolina Medical Board, Position Statement 5.1.4: Telemedicine (amended March 2024)
Related
Launching a telehealth practice, or checking the one you run?
DPS Law drafts and reviews business associate agreements, telehealth vendor contracts and the practice and management structure behind a telehealth business, under HIPAA and North Carolina law. Our attorney is licensed in North Carolina only; for a practice in another state, talk to a lawyer licensed there.