A residential program faxes an intake packet to a referral source. One digit in the fax number is wrong. The packet, with a diagnosis, a substance use history and an insurance ID, lands at a dental office across town. The intake coordinator notices the next morning, calls the dental office, gets a verbal promise that the pages were shredded, and moves on. Nothing gets written down. Fourteen months later a surveyor or an OCR investigator asks to see the breach log, and the program has nothing to show for an incident that its own staff remember clearly.
That is the most common way behavioral health operators fail the HIPAA Breach Notification Rule: not by hiding a ransomware attack, but by treating everyday misdirected disclosures as non-events. This is operational guidance, not legal advice; confirm specifics against the primary sources linked below and with counsel.
The Three Clocks in Plain Terms
The HIPAA breach notification clocks for a behavioral health program: when unsecured protected health information is breached, the covered entity must notify each affected individual without unreasonable delay and no later than 60 calendar days after the breach is discovered. If the breach affects 500 or more individuals, HHS must also be notified within that same 60-day window, and if more than 500 residents of a single state or jurisdiction are affected, prominent media outlets serving that area must be notified as well. Breaches affecting fewer than 500 individuals may be logged and reported to HHS in one batch no later than 60 days after the end of the calendar year in which they were discovered.
Those timeframes are set out in the rule itself and summarized in the HHS Office for Civil Rights breach notification guidance. Two details trip programs up. First, 60 days is an outer limit, not a target; OCR expects notice without unreasonable delay, and sitting on a finished investigation until day 59 is itself a problem. Second, the clock starts at discovery, which the rule treats as the first day the breach is known, or by exercising reasonable diligence would have been known, to any workforce member other than the person who committed it. In the fax example, the clock started the morning the intake coordinator noticed, not the day the compliance officer heard about it.
Why the Small-Breach Log Is Where Programs Get Caught
Large breaches get attention within hours. The under-500 incidents do not, and in behavioral health they are constant. When we review compliance files, the pattern we see most often is a breach log that is empty, or nearly empty, for a full calendar year at a program that sends hundreds of faxes, emails and portal messages every week. An empty log at that volume does not read as excellent privacy practice. It reads as a reporting culture that does not exist.
The reasons are predictable:
- Misdirected fax and email: staff fix the immediate problem and never route it to the privacy officer, so no risk assessment is ever performed.
- Wrong-client documents: a discharge summary or a lab result goes into the wrong client’s portal or mailing, and the front desk treats it as a clerical error rather than a disclosure.
- Payer and referral mix-ups: records sent to the wrong managed care plan or the wrong referring provider are assumed to be “safe” because the recipient is also a covered entity.
- Personal devices and texting: clinicians text client details from personal phones that are later lost, sold or shared, and nobody asks whether the data was encrypted.
Each of those can be a reportable breach. Each can also turn out not to be one. The rule does not let staff decide that informally. It requires a documented assessment.
The Four-Factor Risk Assessment
Under the rule, an impermissible use or disclosure of protected health information is presumed to be a breach unless the covered entity demonstrates a low probability that the information has been compromised. That demonstration rests on a risk assessment covering at least four factors, described in the HHS guidance:
- The nature and extent of the information involved, including the types of identifiers and the likelihood of re-identification. A behavioral health diagnosis or substance use history weighs heavily here.
- The unauthorized person who used the information or to whom the disclosure was made. Another HIPAA-covered provider with its own confidentiality obligations is a different risk from an unknown member of the public.
- Whether the information was actually acquired or viewed. An unopened envelope returned by the post office is not the same as a fax that was read and filed.
- The extent to which the risk has been mitigated, such as a written attestation from the recipient that the information was destroyed and not further used or disclosed.
The burden of proof sits with the program. If the assessment is not written down, there is no demonstration, and the presumption of breach stands. That is the inconvenient operational truth behind the fax example: the dental office probably did shred the packet, but a verbal promise on a phone call is not mitigation the program can prove.
What Changes When the Records Are Part 2 Records
Substance use disorder programs covered by 42 CFR Part 2 used to treat breach notification as a HIPAA-only issue. That changed with the 2024 Part 2 final rule, which extended HIPAA-style breach notification requirements to Part 2 records, with compliance required by February 16, 2026. For a program that holds Part 2 records, a misdirected SUD record now runs through the same clocks and the same risk assessment described above. If separate Part 2 and HIPAA incident procedures still exist, check that they produce the same answer for the same incident.
The Notification Letter and the HHS Submission
When an incident is a breach, the individual notice has required content. In general terms it must describe what happened and when, the types of information involved, the steps individuals should take to protect themselves, what the program is doing to investigate, mitigate and prevent recurrence, and contact procedures that include a toll-free number, email address, website or postal address. It goes by first-class mail to the last known address, or by email if the individual has agreed to electronic notice.
The HHS submission is made through the OCR breach portal. The HHS breach reporting instructions describe the difference between reporting a large breach contemporaneously and submitting the year’s smaller breaches after the calendar year ends. Each small breach is submitted as its own entry, so a program with a dozen logged incidents is filling out a dozen reports, not one.
If the incident involved a vendor, the business associate has its own obligation to notify the covered entity without unreasonable delay and no later than 60 days after discovery. Check whether your business associate agreements require faster notice than that; a short contractual window keeps a vendor’s delay from consuming your own clock.
What to Do Before the End of the Year
Breaches affecting fewer than 500 individuals that were discovered during calendar year 2026 must be submitted to HHS no later than 60 days after December 31, 2026, which puts the deadline at March 1, 2027. Put that date in the compliance calendar today, with an internal target in early February. Then work through this list:
- Pull the 2026 breach log and count the entries. If the count is zero or close to it, interview the intake, front desk and medical records leads about misdirected faxes, emails and mailings this year, and assess anything they recall.
- Open the risk assessment for every log entry and confirm it addresses all four factors in writing, with a named reviewer and a date. A one-line “low risk” note is not an assessment.
- Check discovery dates against notice dates for every incident that was determined to be a breach. Any gap over 60 days needs an explanation in the file.
- Confirm retention. HIPAA documentation, including breach assessments and notices, must be kept for six years. Make sure your retention schedule says so and that old incident files have not been purged.
- Read your incident reporting policy and confirm it tells staff to report misdirected disclosures to the privacy officer the same day, with an example of a wrong-number fax. Staff report what the policy shows them.
If you want a second set of eyes on the log before the March deadline, our compliance services team reviews breach files, risk assessments and incident policies for behavioral health operators. You can also start with our HIPAA compliance checklist, or, if your program does not have a dedicated privacy lead, look at a fractional compliance officer to own the log year-round. Call us at (888) 458-6619 to talk through your 2026 incidents.
The Bottom Line
An empty breach log at a busy program is a finding waiting to happen; a log of documented, assessed wrong-number faxes is evidence of a working compliance program. Questions about a specific incident? Reach our compliance team at (888) 458-6619.