Skip to main content

The IT Manager's Guide to the HIPAA Security Rule in Behavioral Health

Jeremy Bloom, Co-founder · · Updated

The HIPAA Security Rule’s technical safeguards are in 45 CFR 164.312 [1]. A covered entity or business associate implements them in accordance with 45 CFR 164.306 [9]. Required specifications must be implemented [9]. An addressable specification requires the entity to assess whether it is a reasonable and appropriate safeguard in its environment, analyzed with reference to the likely contribution to protecting electronic protected health information [9]. If it is reasonable and appropriate, the entity implements it [9]. If implementing it is not reasonable and appropriate, the entity documents why it would not be reasonable and appropriate to implement that specification and implements an equivalent alternative measure if that alternative is reasonable and appropriate [9]. Addressable does not mean the specification sets a number of minutes or a product to buy. A covered entity or business associate must also review and modify the security measures implemented under that subpart as needed to continue provision of reasonable and appropriate protection of electronic protected health information, and update the documentation of those measures as 45 CFR 164.316(b)(2)(iii) describes [9].

As of September 2026, that is the rule in force. HHS published a proposal to revise the Security Rule on January 6, 2025, at 90 FR 898 [6]. The Federal Register still classifies that document as a proposed rule, and it has no effective date [6].

Access control, encryption, and automatic logoff

The access-control standard requires technical policies and procedures so that only people or software programs that have been granted access rights, as specified in § 164.308(a)(4), can reach electronic information systems that maintain electronic protected health information [1]. Section 164.308(a)(4) requires policies and procedures for authorizing access to electronic protected health information that are consistent with the applicable requirements of the privacy rule [12]. If a health care clearinghouse is part of a larger organization, the clearinghouse must implement policies and procedures that protect its electronic protected health information from unauthorized access by the larger organization [12]. Unique user identification is required: the entity assigns a unique name or number, or both, for identifying and tracking user identity [1]. An emergency access procedure is also required: the entity establishes, and implements as needed, procedures for obtaining necessary electronic protected health information during an emergency [1].

Automatic logoff is addressable. The specification says to implement electronic procedures that terminate an electronic session after a predetermined time of inactivity [1]. The rule does not set that time. A program that chooses a short inactivity limit for a shared workstation is choosing an operational practice. It is not quoting a duration from the regulation.

Encryption and decryption of electronic protected health information, under the access-control standard, is also addressable [1]. Transmission security has an addressable integrity-controls specification: security measures to ensure that electronically transmitted electronic protected health information is not improperly modified without detection until it is disposed of [1]. It also has an addressable encryption specification: a mechanism to encrypt electronic protected health information whenever deemed appropriate [1]. The current text does not make encryption of data at rest a required specification. The integrity standard requires policies and procedures to protect electronic protected health information from improper alteration or destruction [1]. A mechanism to authenticate that information, using electronic mechanisms to corroborate that it has not been altered or destroyed in an unauthorized manner, is addressable [1]. The person or entity authentication standard requires procedures to verify that a person or entity seeking access is the one claimed [1].

The January 2025 proposal would remove the distinction between addressable and required implementation specifications [6]. If adopted, the proposed paragraph would require regulated entities to comply with both the standards and the implementation specifications [6]. The same proposal would add a network segmentation specification at 45 CFR 164.312(a)(2)(vi) that would require a regulated entity to deploy technical controls to segment its relevant electronic information systems in a reasonable and appropriate manner [6]. Under that proposal, a regulated entity with multiple, distinct electronic information systems would have to separate the relevant electronic information systems using reasonable and appropriate technical controls [6]. Neither change is the current rule. 45 CFR 164.312, as published today, does not contain a segmentation requirement [1].

Audit controls and the six-year documentation rule

The audit-controls standard requires hardware, software, or procedural mechanisms that record and examine activity in systems that contain or use electronic protected health information [1]. It does not set a retention period for those logs.

The six-year period is in 45 CFR 164.316(b)(2) [2]. It applies to the documentation the Security Rule requires: the policies and procedures, which may be electronic, and a written record, which may be electronic, of actions, activities, or assessments the rule requires to be documented. The entity keeps that documentation for six years from its creation or from when it was last in effect, whichever is later [2]. It must make that documentation available to the people responsible for implementing the procedures to which the documentation pertains, and it must review the documentation periodically and update it as needed when environmental or operational changes affect the security of the electronic protected health information [2]. Treating audit logs as if they were that documentation adds a retention rule the section does not state.

Breach notification

A breach is an acquisition, access, use, or disclosure of protected health information that the privacy rule does not permit and that compromises the security or privacy of the information [11]. It excludes a good-faith, in-scope, unintentional acquisition, access, or use by a workforce member or a person acting under the authority of the covered entity or business associate, when that acquisition, access, or use is not further used or disclosed impermissibly; an inadvertent disclosure by a person authorized to access the information at a covered entity or business associate to another person authorized to access it at the same covered entity or business associate, or at an organized health care arrangement in which the covered entity participates, when the information received is not further used or disclosed impermissibly; and a disclosure where the covered entity or business associate has a good-faith belief that the unauthorized person to whom the disclosure was made would not reasonably have been able to retain the information [11]. Outside those exclusions, an impermissible acquisition, access, use, or disclosure is presumed to be a breach unless the covered entity or business associate shows a low probability that the information was compromised [11]. That showing is a risk assessment of at least the nature and extent of the information, including the types of identifiers and the likelihood of re-identification; the unauthorized person who used it or received it; whether it was actually acquired or viewed; and the extent to which the risk has been mitigated [11]. Unsecured protected health information is protected health information that has not been made unusable, unreadable, or indecipherable to unauthorized persons by a technology or methodology the Secretary specifies in the guidance issued under section 13402(h)(2) of Public Law 111-5 [11].

After a breach of unsecured protected health information, a covered entity notifies each individual whose unsecured protected health information has been, or is reasonably believed by the covered entity to have been, accessed, acquired, used, or disclosed as a result of the breach [3]. The breach is treated as discovered on the first day the covered entity knew of it, or would have known of it by reasonable diligence. The covered entity is deemed to know of a breach that any person, other than the person who committed it, knows or would have known by exercising reasonable diligence, if that person is a workforce member or an agent of the covered entity. Agency is determined under the federal common law of agency [3]. Except for a law-enforcement delay under § 164.412, the notice goes out without unreasonable delay and no later than 60 calendar days after discovery [3]. That individual deadline applies to the breach. It is not reserved for breaches affecting 500 or more people [3]. To the extent possible, the notice includes a brief description of what happened, including the date of the breach and the date of the discovery of the breach, if known; a description of the types of unsecured protected health information that were involved in the breach; any steps individuals should take to protect themselves from potential harm resulting from the breach; and a brief description of what the covered entity is doing to investigate the breach, to mitigate harm to individuals, and to protect against any further breaches; and how to ask questions or learn additional information, including a toll-free telephone number, an email address, a website, or a postal address [3]. The notice is written in plain language. It is sent by first-class mail to the individual’s last known address, or by electronic mail if the individual has agreed to electronic notice and has not withdrawn that agreement [3]. If the covered entity knows the individual is deceased and has the address of the next of kin or personal representative, it mails the notice to one of them [3]. If the contact information is insufficient or out of date and written notice to the individual cannot be given, the covered entity provides a substitute notice reasonably calculated to reach the individual [3]. That substitute notice is not required when the missing address is for the next of kin or personal representative of a deceased individual [3]. For fewer than 10 individuals, the substitute notice may be an alternative written notice, a telephone call, or another means [3]. For 10 or more individuals, it must be a conspicuous posting for 90 days on the home page of the covered entity’s website, or a conspicuous notice in major print or broadcast media in the geographic areas where the individuals affected by the breach likely reside, and it must include a toll-free telephone number that stays active for at least 90 days so a person can learn whether their information may be included in the breach [3].

Notice to HHS is different. For a breach involving 500 or more individuals, the covered entity notifies the Secretary contemporaneously with the individual notice and in the manner specified on the HHS website, except for a law-enforcement delay under § 164.412 [5]. For a breach involving less than 500 individuals, the covered entity maintains a log or other documentation of those breaches and notifies the Secretary no later than 60 days after the end of the calendar year for breaches discovered during the preceding year, in the manner specified on the HHS website [5].

If a breach involves more than 500 residents of a state or jurisdiction, the covered entity notifies prominent media outlets serving that state or jurisdiction, without unreasonable delay and no later than 60 calendar days after discovery, except for a law-enforcement delay under § 164.412 [4]. That media notice must meet the content requirements for the individual notice [4].

A business associate that discovers a breach of unsecured protected health information must notify the covered entity [10]. Discovery for the business associate is the first day the breach is known to it or, by exercising reasonable diligence, would have been known to it [10]. The business associate is deemed to know of a breach that any person, other than the person who committed it, knows or would have known by exercising reasonable diligence, if that person is an employee, officer, or other agent of the business associate. Agency is determined under the federal common law of agency [10]. Except for a law-enforcement delay under § 164.412, that notice goes out without unreasonable delay and no later than 60 calendar days after discovery [10]. To the extent possible, it identifies each individual whose unsecured protected health information has been, or is reasonably believed by the business associate to have been, accessed, acquired, used, or disclosed during the breach, and it includes any other available information the covered entity must put in the individual notice, at the time of the notice or promptly thereafter as that information becomes available [10].

Part 2 uses the HIPAA breach rule

42 CFR 2.16(b) applies 45 CFR part 160 and subpart D of 45 CFR part 164 to Part 2 programs for breaches of unsecured records, in the same manner those provisions apply to a covered entity for breaches of unsecured protected health information [7]. A Part 2 program, and any other lawful holder of patient identifying information other than family, friends, and other informal caregivers, must have in place formal policies and procedures to reasonably protect against unauthorized uses and disclosures of patient identifying information and to protect against reasonably anticipated threats or hazards to the security of that information. Those policies must address all of the paper and electronic safeguards § 2.16(a) lists [7]. Breach notification for Part 2 records is not a second, separate clock.

A Part 2 program, covered entity, or business associate that receives records under a single consent for all treatment, payment, and health care operations is not required to segregate or segment those records [8]. The Security Rule’s audit-controls standard still requires hardware, software, or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information [1]. The Part 2 rule does not add a requirement that every recorded access prove it followed a consent directive.

Sources

  1. 45 CFR 164.312, Technical safeguards, eCFR, HHS. Accessed September 28, 2026.
  2. 45 CFR 164.316, Policies, procedures, and documentation, eCFR, HHS. Accessed September 28, 2026.
  3. 45 CFR 164.404, Notification to individuals, eCFR, HHS. Accessed September 28, 2026.
  4. 45 CFR 164.406, Notification to the media, eCFR, HHS. Accessed September 28, 2026.
  5. 45 CFR 164.408, Notification to the Secretary, eCFR, HHS. Accessed September 28, 2026.
  6. HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information (90 FR 898), HHS, Federal Register. Accessed September 28, 2026.
  7. 42 CFR 2.16, Security for records and notification of breaches, eCFR, HHS. Accessed September 28, 2026.
  8. 42 CFR 2.12, Applicability, eCFR, HHS. Accessed September 28, 2026.
  9. 45 CFR 164.306, Security standards: General rules, eCFR, HHS. Accessed September 28, 2026.
  10. 45 CFR 164.410, Notification by a business associate, eCFR, HHS. Accessed September 28, 2026.
  11. 45 CFR 164.402, Definitions for breach notification, eCFR, HHS. Accessed September 28, 2026.
  12. 45 CFR 164.308, Administrative safeguards, eCFR, HHS. Accessed September 28, 2026.

How Encore OS approaches HIPAA and 42 CFR Part 2 safeguards, tenant isolation and AI controls is set out on one page.

Security and compliance