42 CFR Part 2 protects the confidentiality of substance use disorder (SUD) treatment records, and since 16 February 2026 its rewritten rules are enforced by the HHS Office for Civil Rights with the same civil and criminal penalty framework that applies to HIPAA. The 2024 final rule, required by section 3221 of the CARES Act, pulled Part 2 much closer to HIPAA: a single consent can now cover treatment, payment and health care operations, the HIPAA Breach Notification Rule applies to Part 2 records, and patients can complain directly to HHS. Some protections remain stricter than HIPAA, above all the ban on using records against a patient in legal proceedings without consent or a court order.
This guide explains what changed, who is covered, what the obligations mean in practice and what security and identity teams should do now that the compliance date has passed. It is written for practitioners who run the systems, integrations, service accounts and AI tools that touch SUD records. For the wider HIPAA framework, read our HIPAA Privacy Rule Guide; this page does not repeat it.
This page is general information, not legal advice. Status as of 17 Nov 2026. Confirm obligations against the current regulation text and with qualified counsel.
Key takeaways
- The final rule Confidentiality of Substance Use Disorder (SUD) Patient Records was published at 89 FR 12472 on 16 February 2024, took effect on 16 April 2024 and required compliance by 16 February 2026.
- One patient consent can now cover all future uses and disclosures for treatment, payment and health care operations (TPO). HIPAA covered entities and business associates that receive records under that consent may redisclose them as HIPAA allows.
- Part 2's old criminal only penalty regime has been replaced with the HIPAA civil and criminal enforcement authorities in sections 1176 and 1177 of the Social Security Act, including the HITECH culpability tiers.
- The HIPAA Breach Notification Rule now applies to breaches of Part 2 records, and Part 2 programs and lawful holders must keep formal policies and procedures to secure records (section 2.16).
- HHS delegated Part 2 administration and enforcement to the OCR Director on 25 August 2025, and from 16 February 2026 anyone can file a Part 2 complaint with OCR.
- Records still cannot be used to investigate or prosecute a patient without written consent or a court order. Consent for legal proceedings cannot be combined with any other consent.
- A new category of SUD counseling notes needs its own specific consent, similar to HIPAA psychotherapy notes.
- Segregating or segmenting Part 2 records is not required, but you still need to know where they are and who and what can read them.
42 CFR Part 2 at a glance
| Item | Position as of 17 Nov 2026 |
|---|---|
| Instrument | 42 CFR Part 2, as amended by the final rule at 89 FR 12472 (RIN 0945-AA16) |
| Legal basis | 42 U.S.C. 290dd-2, as amended by section 3221 of the CARES Act (enacted 27 March 2020) |
| Published | 16 February 2024 (announced 8 February 2024 by HHS, SAMHSA and OCR) |
| Effective | 16 April 2024 |
| Compliance date | 16 February 2026 |
| Enforcer | HHS Office for Civil Rights, under authority delegated on 25 August 2025 |
| Penalties | HIPAA civil money penalty tiers and criminal penalties (Social Security Act sections 1176 and 1177) |
| Breach notification | HIPAA Breach Notification Rule applies to Part 2 records (section 2.16) |
| Open item | Compliance date for the accounting of disclosures right will be set when the HIPAA Privacy Rule version of that right is revised |
Scope: who and what is covered
Part 2 applies to federally assisted programs that hold themselves out as providing SUD diagnosis, treatment or referral for treatment. The rule calls these Part 2 programs. Federal assistance is broad: Medicare or Medicaid participation, federal licensing or registration (for example DEA registration to dispense controlled substances for SUD treatment), tax exempt status and federal grants can all bring a provider into scope. Whether a particular unit, clinic or clinician is a Part 2 program is a legal question, and the answer drives everything else, so get it documented.
The rule also reaches organisations that receive Part 2 records:
- Lawful holders. The final rule adds a definition for any person who receives records under a consent or another permitted route and is therefore bound by Part 2. Family, friends and other informal caregivers who are lawful holders are exempt from the section 2.16 security policy requirement.
- Qualified service organizations (QSOs). The definition now expressly includes business associates that meet the HIPAA business associate definition for a covered entity that is also a Part 2 program. Cloud hosts, EHR vendors, billing services, analytics firms and AI service providers often sit here.
- Intermediaries. The definition was revised to exclude Part 2 programs, covered entities and business associates, so it now targets organisations such as some health information exchanges and research networks that pass records on.
- HIPAA covered entities and business associates that receive Part 2 records under a TPO consent. They may use and redisclose those records under HIPAA rules, but the legal proceedings restriction still follows the records.
The protected information is any record that would identify a patient as having or having had an SUD, created or received by a Part 2 program in connection with diagnosis, treatment or referral. The protection follows the data, so a copy in a data warehouse, a log file, an analytics extract or an AI prompt history is still a Part 2 record if it identifies the patient that way.
Key obligations
Consent for treatment, payment and health care operations
The headline change is that a single consent can cover all future TPO uses and disclosures. Recipients that are HIPAA covered entities or business associates can then redisclose under HIPAA. Each disclosure made with patient consent must include a copy of the consent or a clear explanation of its scope, so systems that push records to another organisation need a way to attach that information to the transfer. Patients can still revoke consent, and your workflows need to respect revocation from the point it is received.
SUD counseling notes
The rule defines SUD counseling notes as notes by an SUD clinician that analyse the contents of a counseling conversation and are kept separately from the rest of the treatment and medical record. They need specific patient consent and cannot be disclosed under a broad TPO consent. HHS describes this as analogous to HIPAA's protection for psychotherapy notes. In practice that means a separate storage location or record type, with access rules that a general clinical or billing role cannot satisfy.
Legal proceedings
Records and testimony relaying their content cannot be used or disclosed in civil, criminal, administrative or legislative proceedings against the patient without the patient's specific written consent or a court order that meets Part 2's requirements. HHS notes this is stricter than the HIPAA standard. A consent for use in legal proceedings cannot be combined with consent for any other use or disclosure. Records obtained in a Part 2 program audit or evaluation carry the same restriction.
De-identification and public health
Programs may disclose records to public health authorities without consent if the records are de-identified to the HIPAA Privacy Rule standard at 45 CFR 164.514. The de-identification standard in Part 2 is aligned to that HIPAA provision.
Security of records and breach notification (section 2.16)
Part 2 programs and lawful holders (other than informal caregivers) must have formal policies and procedures to protect records against unauthorised uses and disclosures. Section 2.16 also applies the HITECH breach notification provisions, as carried in the HIPAA Breach Notification Rule, to breaches of Part 2 records. HHS states that programs must notify affected individuals, the Secretary and in some cases the media. Our HIPAA Breach Notification Rule Guide covers the risk assessment, timing and content rules you will now apply to SUD records too.
Patient rights and notice
- A right to an accounting of disclosures. The compliance date for this right will be set when the HIPAA Privacy Rule's version of the right is revised, so it is not yet operative.
- A right to request restrictions on certain disclosures.
- A right to opt out of fundraising communications.
- Part 2 patient notice requirements now align with the HIPAA Notice of Privacy Practices. HHS publishes a model Part 2 patient notice and an updated model HIPAA notice.
Complaints and non-retaliation (section 2.4)
Part 2 programs must set up a process to receive complaints. Patients may file complaints with the Secretary under 45 CFR 160.306, and may file with the program at the same time. Programs may not take adverse action against a complainant and may not require patients to waive the right to complain as a condition of treatment, enrolment, payment or eligibility.
Safe harbor for investigative agencies
Section 2.3(b) protects investigative agencies from liability if they act with reasonable diligence before demanding records. The diligence steps include checking SAMHSA's online treatment facility locator, a similar state database where one exists, the provider's website or premises and its patient notice or HIPAA notice, within 60 days before the request. An agency that receives Part 2 records without the required court order must take specified steps to secure them.
What did not change
Segregation or segmentation of Part 2 records is not required. The core protection also remains: SUD treatment records cannot be used to investigate or prosecute the patient without written consent or a court order.
Timeline and current status
| Date | Event |
|---|---|
| 27 March 2020 | CARES Act enacted, section 3221 requires Part 2 alignment with HIPAA |
| 2 December 2022 | Notice of proposed rulemaking published, with a 60 day comment period |
| 8 February 2024 | Final rule announced by HHS, SAMHSA and OCR |
| 16 February 2024 | Final rule published at 89 FR 12472 |
| 16 April 2024 | Final rule effective |
| 25 August 2025 | Secretary delegates Part 2 administration and enforcement to the OCR Director |
| 16 February 2026 | Compliance required; public complaint process opens |
| September 2026 | OCR guidance on state Medicaid agencies using SUD records to verify exclusions from the Medicaid community engagement requirement |
Status as of 17 Nov 2026: the rule is fully in force and OCR is accepting complaints. The accounting of disclosures right still awaits a separate compliance date.
Enforcement and penalties
OCR enforces Part 2 using the HIPAA Enforcement Rule at 45 CFR Part 160, subparts C, D and E. HHS says OCR generally seeks voluntary compliance but can run compliance reviews, investigate complaints and impose financial penalties where it finds a violation. Section 2.3 now points to section 1176 of the Social Security Act (civil money penalties, with the HITECH tiers based on culpability) and section 1177 (criminal penalties for knowingly obtaining or disclosing protected information). That is a material change: HHS describes the old Part 2 criminal penalties as replaced by these HIPAA civil and criminal authorities. Programs now face the same investigation, resolution agreement and corrective action plan model that HIPAA covered entities know well.
Breach exposure also changes. A ransomware event, an exposed storage bucket or a compromised integration account that reaches Part 2 records now triggers HIPAA style breach notification, including a report to the Secretary. Expect OCR to look at whether your section 2.16 policies existed and were followed.
What it means for security and identity teams
Part 2 is often treated as a privacy office topic, but most of the operational risk sits in systems and identities. SUD records move through EHR interfaces, claims clearinghouses, health information exchanges, data platforms and increasingly AI tools. Each of those flows runs on non-human identities: interface engine accounts, API clients, OAuth applications, ETL service principals and agent credentials.
Know where Part 2 data lives
Because segmentation is not mandatory, many organisations hold Part 2 records alongside general clinical data. That is lawful, but it means you need data classification that tags SUD records and counseling notes, so access policies and breach assessments can find them. Start with the systems of the Part 2 program itself, then trace every outbound feed.
Treat machine access as disclosure
A service account that can read SUD records is, in effect, a path for disclosure. Inventory every non-human identity with read access, assign an owner, record the business purpose and the consent basis that permits the flow, and remove standing access that has no current purpose. Counseling notes deserve their own access tier that no shared integration account can reach.
Carry consent with the data
Each consented disclosure must include a copy of the consent or a clear explanation of its scope. That is easier if consent status is stored as data your integrations can read and attach, rather than a scanned form. It also lets you stop flows quickly after revocation and evidence what was sent under which consent.
Watch AI and analytics use
Copying Part 2 records into a model prompt, a retrieval index or a vendor analytics tool is a use or disclosure. Confirm the vendor's role (QSO or business associate), check that the use fits the consent, and prefer HIPAA standard de-identification for anything that does not need identity. Log what AI agents retrieve so you can answer an accounting or a breach question later. Our HIPAA Business Associate Agreements Guide covers the contract terms to look for.
Plan for legal process requests
Subpoenas and law enforcement requests for SUD records need a court order that meets Part 2, or the patient's separate consent. Make sure records custodians, e-discovery tools and anyone who can export data know that a HIPAA compliant subpoena response is not enough for Part 2 records.
Compliance steps
- Confirm Part 2 status. Document which entities, units and clinicians are Part 2 programs, and which of your organisations are lawful holders, QSOs, intermediaries or HIPAA recipients.
- Map records and flows. Locate SUD records and counseling notes, every system that stores copies and every integration or identity that reads them.
- Update consent forms and workflows. Adopt the single TPO consent where it fits, separate legal proceedings consent and counseling notes consent, and build revocation handling.
- Update the patient notice. Align with the HIPAA Notice of Privacy Practices, using the HHS model notices as a starting point.
- Write section 2.16 security policies. Cover access control, logging, encryption, retention and disposal, and tie them to your HIPAA Security Rule programme.
- Extend breach response. Add Part 2 records to incident triage and to your HIPAA breach risk assessment and notification runbooks.
- Stand up the complaints process. Give patients a clear route, train staff on non-retaliation and remove any waiver language from intake forms.
- Review vendor contracts. Update QSO agreements and business associate agreements to reflect the new rules and breach duties.
- Train legal and records teams on the court order and consent requirements for legal proceedings, and on the investigative agency safe harbor.
Common failure patterns
- Treating Part 2 as fully merged into HIPAA and releasing SUD records in response to an ordinary subpoena.
- Relying on a broad TPO consent to release SUD counseling notes.
- Integration accounts with read access to the whole clinical database, including counseling notes, and no named owner.
- Disclosures sent without a copy or explanation of the consent attached.
- Breach runbooks that list PHI and payment data but not SUD records, so the Part 2 angle is missed in the first 60 days.
- Analytics or AI pilots that copy identifiable SUD data into vendor tools with no QSO or business associate agreement.
- Intake forms that still ask patients to waive complaint rights or that do not explain the new complaint route.
Practitioner checklist
- Part 2 program status documented for every relevant entity and unit.
- Data inventory tags SUD records and counseling notes in every system that holds them.
- Every human and non-human identity with access to Part 2 records has an owner, a purpose and a consent basis.
- Counseling notes sit in a separate access tier with specific consent checks.
- Consent status is machine readable, attached to disclosures and enforced on revocation.
- Section 2.16 security policies approved, published and mapped to HIPAA Security Rule controls.
- Incident response and breach notification runbooks cover Part 2 records.
- Patient notice updated and complaint process live, with non-retaliation training.
- QSO and business associate agreements reviewed for every vendor and AI service that touches SUD data.
- Legal and records staff trained on court orders, legal proceedings consent and the investigative agency safe harbor.
Standards and references
- Federal Register: Confidentiality of Substance Use Disorder (SUD) Patient Records, final rule, 89 FR 12472
- HHS: Fact Sheet, 42 CFR Part 2 Final Rule
- HHS OCR: HIPAA and Part 2
- NIST: SP 800-53 Rev. 5
- NIST: SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management
- ISO: ISO/IEC 27701:2025 Privacy information management systems
Related NHI Mgmt Group resources: HIPAA Privacy Rule Guide · HIPAA Breach Notification Rule Guide · HIPAA Business Associate Agreements Guide · Health Data Privacy Beyond HIPAA Guide (My Health My Data)