# Checklist: record security, breach notification and the patient notice under the 2024 Part 2 rule

Twelve steps for Part 2 programs and other lawful holders of substance use disorder records: written security policies for paper and electronic records, HIPAA-style breach notification, the new patient notice, and what to do when a program closes.

Checklist · Healthcare · Security & Resilience. Published November 14, 2026. Last reviewed November 14, 2026.

## The security side of the 2024 rule

HHS’s final rule on the Confidentiality of Substance Use Disorder (SUD) Patient Records, published at 89 FR 12472 on February 16, 2024, took effect on April 16, 2024 [2]. This checklist covers the other half: section 2.16 now requires formal policies and procedures for paper and electronic records and applies the HIPAA breach notification rules to Part 2 programs, section 2.22 replaces the old patient notice with a full notice of privacy practices, and section 2.19 sets how a closing program disposes of records [1]. Enforcement now runs through the HIPAA enforcement rules in 45 CFR part 160, subparts C, D and E, under section 2.3(c) [1].

The rule’s DATES section says persons subject to it must comply with its applicable requirements by February 16, 2026 [4], the compliance date that section 2.22(c)(1)(i) refers to [1]. Consent and redisclosure have their own [Part 2 consent checklist](https://insights.moraph.com/checklist-42-cfr-part-2-consent-and-redisclosure-2024-rule).

## Using the steps

The first four steps cover security policies, the next three breach notification, the next three the patient notice, and the last two closing programs and requests for records. Each step cites the section of 42 CFR part 2 as current on eCFR to November 12, 2026 [1], or the HIPAA breach notification sections it points to [3]. Where a step is our suggestion, it says so. The owner under each step is a typical role, not one the rule names, unless the step says the rule names it. This page explains the rule; it is not legal advice, and state law may add its own duties.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## The checklist

1. **Confirm whether the organization is a Part 2 program or another lawful holder, since both must keep formal security policies.** (Privacy officer) Section 2.16(a) applies to the Part 2 program or other lawful holder of patient identifying information, and section 2.16(a)(2) exempts only family, friends and other informal caregivers who are lawful holders [1].
2. **Write policies for paper records that cover transfer and removal, destruction with sanitizing of hard copy media, locked storage when not in use, access to workstations and storage areas, and de-identification.** (Privacy officer, with facilities) Section 2.16(a)(1)(i) lists these five topics for paper records and requires destruction that renders patient identifying information non-retrievable, and de-identification to the standard in 45 CFR 164.514(b) [1].
3. **Write policies for electronic records that cover creating, receiving, maintaining and transmitting them, destroying them with media sanitization, access and use, and de-identification.** (CISO) Section 2.16(a)(1)(ii) lists these four topics for electronic records [1]. Mapping each topic to existing HIPAA Security Rule policies, where the organization has them, is our suggestion.
4. **Check that the policies protect against unauthorized uses and disclosures and against reasonably anticipated threats or hazards, and record when they were last reviewed.** (CISO) Section 2.16(a) sets these two aims for the policies and procedures [1]. The rule does not set a review cycle; recording one is our suggestion.
5. **Extend the breach response plan to Part 2 records, so a breach of unsecured records is handled under the HIPAA breach notification rules.** (Incident response lead, with the privacy officer) Section 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 as they apply to covered entities for unsecured protected health information [1]. Under section 164.402, an impermissible use or disclosure is presumed to be a breach unless a low probability of compromise is shown [3].
6. **Put the HIPAA timelines in the plan: notice to each affected patient without unreasonable delay and no later than 60 calendar days after discovery, media notice for a breach involving more than 500 residents of a state or jurisdiction, and notice to the Secretary.** (Privacy officer) Sections 164.404(b) and 164.406(b) set the 60-calendar-day limit; section 164.404(a)(2) treats a breach as discovered on the first day it is known or by reasonable diligence would have been known. Section 164.408 requires notice to the Secretary at the same time as individual notice for 500 or more individuals, and for fewer than 500 a log and notice not later than 60 days after the end of each calendar year [3]. The [HIPAA breach notification checklist](https://insights.moraph.com/checklist-hipaa-breach-notification) covers the content of each notice.
7. **Keep the documentation that shows each notification was made or that an incident was not a breach.** (Privacy officer) Section 164.414(b) puts the burden of demonstrating that all notifications were made, or that the use or disclosure was not a breach, on the covered entity or business associate [3], and section 2.16(b) applies that subpart to Part 2 programs [1].
8. **Replace the old patient notice with the new notice of privacy practices, with the required header and every element section 2.22(b) lists.** (Privacy officer, with legal) Section 2.22(b)(1) requires the header, a description of uses and disclosures without consent, at least one example of disclosures that need consent, statements on single consent for treatment, payment and health care operations, revocation and limits on use in proceedings against the patient, patient rights, the program’s duties including notifying affected patients after a breach of unsecured records, how to complain without retaliation, a contact with telephone and email, and an effective date [1].
9. **Give the notice by the first service delivery, post it where patients can read it without being identified as receiving SUD services, keep copies on hand, and post it prominently on the program’s website.** (Patient access manager, with the web team) Section 2.22(a) requires telling the patient at admission that federal law protects SUD records. Section 2.22(c) requires providing the notice no later than the first service delivery after the compliance date, or as soon as reasonably practicable after emergency treatment, posting it at physical sites in a way that does not identify the patient, posting it on a website that describes services or benefits, and sending electronic notice automatically when the first service is delivered electronically [1].
10. **Set a trigger to revise and redistribute the notice whenever a material change is made to uses or disclosures, patient rights, legal duties or privacy practices.** (Privacy officer) Section 2.22(b)(3) requires prompt revision and distribution after a material change and bars putting a material change into effect before the effective date of the notice that reflects it, except when required by law [1].
11. **Keep a closure procedure: if the program closes or is acquired, remove or destroy patient identifying information unless the patient consents to transfer, a law requires retention, or the program is transferred, retroceded or reassumed under the Indian Self-Determination and Education Assistance Act, and follow the sealing, encryption and labeling steps where records must be kept.** (Records manager, with the CISO) Section 2.19(a) sets the general rule and its exceptions. Section 2.19(b) requires sealed and labeled containers for paper records, encrypted transfer with access controls for electronic records, sanitizing the original electronic media within one year of the discontinuation or acquisition, and a responsible person who keeps decryption tools separate from the data [1].
12. **Answer requests for records that the rule does not permit without confirming that any identified person is or was a patient, and do not require patients to carry anything identifying them off the premises.** (Health information management) Section 2.13(c)(2) requires answers to impermissible requests to be made in a way that does not affirmatively reveal that an identified individual has been or is being diagnosed or treated for a substance use disorder. Section 2.18 bars requiring patients to carry an identifying card or object away from program premises [1].

## Sources

1. Electronic Code of Federal Regulations. 42 CFR part 2, Confidentiality of Substance Use Disorder Patient Records (eCFR current to November 12, 2026; checked November 14, 2026). <https://www.ecfr.gov/current/title-42/chapter-I/subchapter-A/part-2> Checked November 14, 2026.
2. Department of Health and Human Services, Federal Register. Confidentiality of Substance Use Disorder (SUD) Patient Records (final rule, 89 FR 12472, February 16, 2024; API record checked November 14, 2026). <https://www.federalregister.gov/api/v1/documents/2024-02544.json> Checked November 14, 2026.
3. Electronic Code of Federal Regulations. 45 CFR part 164, subpart D, Notification in the Case of Breach of Unsecured Protected Health Information (eCFR current to November 12, 2026; checked November 14, 2026). <https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-D> Checked November 14, 2026.
4. Department of Health and Human Services, Federal Register. Confidentiality of Substance Use Disorder (SUD) Patient Records, final rule, 89 FR 12472 (GovInfo PDF, Internet Archive copy captured October 3, 2026; checked November 14, 2026). <https://web.archive.org/web/20261003082353/https://www.govinfo.gov/content/pkg/FR-2024-02-16/pdf/2024-02544.pdf> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-42-cfr-part-2-record-security-breach-and-patient-notice>
Publisher: Moraph Insights
