A clinician at an outpatient SUD program gets a routine records request from a client's primary care physician, signed release attached, and almost faxes the chart the way she would for any therapy client. Then she remembers: this is not a HIPAA question. This is 42 CFR Part 2, the federal confidentiality rule for substance use disorder records, where the wrong fax has historically been a federal violation even with a release that would satisfy HIPAA. The 2024 final rule rewrote major parts of Part 2 to align it with HIPAA, and most clinicians know something changed without knowing what. This lesson walks the 2024 changes slowly: the single-consent option, the new redisclosure rules, what "holds itself out as providing SUD treatment" means for your practice, and what each change implies for an AI scribe transcribing sessions where substance use is the presenting problem. You will finish by drafting a Part 2 Consent Language Block for your own program, including the segmentation pattern for the client who also sees a non-Part 2 PCP.

Why Part 2 Exists: A Stricter Lock on a Specific Room

Hold one controlling analogy: if HIPAA is the legal architecture of the house where client information lives, 42 CFR Part 2 is a vault inside that house, built for one category of records, with its own combination. Congress built the vault in the 1970s on a blunt insight: people will not seek addiction treatment if seeking it can be used against them. An SUD diagnosis is not like a cholesterol panel. It has been grounds for arrest, prosecution, custody loss, job termination, and divorce leverage. So the rule that grew into Part 2 made SUD treatment records from federally assisted programs confidential above ordinary medical privacy: for decades, nearly every disclosure required specific written consent naming the recipient, and the recipient could not redisclose without going back for new consent.

That strictness protected patients and also created clinical harm. A hospitalist treating an overdose could not see the methadone dose. A PCP managing diabetes could not see the naltrexone prescription. Care coordination hit the vault door and stopped. The CARES Act of 2020 ordered HHS to align Part 2 more closely with HIPAA, and the result was the 42 CFR Part 2 final rule published in February 2024, with compliance required by February 2026. If you searched "42 cfr part 2 final rule 2024" and landed in a wall of preamble, here is the plain version: the vault still exists, the combination changed, and the new combination borrows most of its digits from HIPAA while keeping a few that are unmistakably Part 2's own.

Before the changes, one threshold question, because it decides whether any of this applies to you. Part 2 covers records created by a federally assisted "Part 2 program": an individual or entity that holds itself out as providing, and provides, SUD diagnosis, treatment, or referral for treatment, and is federally assisted, a bar most practices clear through Medicare or Medicaid participation, DEA registration to prescribe controlled substances for SUD treatment, federal funding, or tax-exempt status. "Holds itself out" is the phrase that surprises group practices. It is not about your license; it is about your shingle.

"Holds Itself Out": What the Phrase Means for a Group Practice

Picture Jordan's 25-clinician group practice in Sacramento. The website lists "anxiety, depression, trauma, couples, addiction and recovery." Two clinicians run an IOP-style relapse prevention group. Several clinicians market themselves as addiction specialists. Has the practice "held itself out" as providing SUD treatment? Very plausibly yes, and that is the analysis the phrase demands. Holding out includes advertising SUD services, listing them on your website or insurance directories, operating an identifiable SUD program or track, or having staff whose primary function is SUD care. A general therapy practice where substance use sometimes comes up in sessions is generally not a Part 2 program; a practice with an addiction services page and a recovery group very likely is, at least as to the records of that program.

This distinction matters enormously for AI adoption because it determines which records sit in the vault. If part of your practice is a Part 2 program, the SUD records it creates carry Part 2 protection even as the rest of your charts live under ordinary HIPAA. An AI scribe contracted for the whole practice is now touching two legally distinct record classes through one pipeline. The vendor that is merely a HIPAA business associate for your general caseload must also satisfy Part 2 for the SUD program's records: under the 2024 final rule, a vendor processing Part 2 records through a qualified service organization or BAA-style agreement takes on the use and disclosure limits and exposure to the same penalty scheme as the program itself, because the rule swapped Part 2's old criminal-only enforcement for HIPAA's civil and criminal structure, complete with breach notification obligations.

The practical takeaway: before vetting any AI tool, decide whether you are, in whole or part, a Part 2 program. Write the analysis down, one paragraph, with the facts (website language, program structure, federal assistance) and the conclusion. If the answer is yes or probably, every vendor conversation changes: you are no longer asking only "will you sign a BAA," but "do you understand Part 2, will your agreement cover it, and can your system segment these records?"

The 2024 Final Rule: Alignment With HIPAA, in Plain Language

The 2024 final rule's headline is alignment. Enforcement moved from the old criminal-penalty framework to the HIPAA civil and criminal penalty structure, which means OCR's culpability tiers and the breach notification rules from the previous lesson now reach Part 2 records too. Patients gained HIPAA-style rights, including an accounting of disclosures. Programs must apply Patient Notice requirements aligned with the HIPAA Notice of Privacy Practices. And the rule created the change clinicians feel most in daily workflow: the single-consent option.

Under the old regime, consent was transactional: each disclosure to each recipient effectively needed its own paper, and downstream treatment partners needed new consent to pass anything along. Under the 2024 final rule, a patient may sign a single consent authorizing all future uses and disclosures for treatment, payment, and healthcare operations. One signature, given once, opens the vault for the TPO purposes ordinary healthcare runs on, until the patient revokes it. For a busy SUD program, this is the difference between a consent administration job and a workable clinic. But, and this is the part to teach slowly, the single consent is an option the patient grants, not a default the program assumes. No consent, no TPO disclosures; Part 2's baseline remains consent-first, the opposite of HIPAA, where TPO flows without authorization. The vault analogy holds: HIPAA's rooms open for TPO by design; the vault opens only because the patient handed you the combination in writing.

Redisclosure changed in a paired way. Once records are disclosed under that TPO consent to a HIPAA covered entity or business associate, the recipient may redisclose them under HIPAA's rules rather than chasing fresh Part 2 consent each time. That single change finally lets the PCP who lawfully received SUD records share them with the cardiologist under ordinary HIPAA treatment rules. Two guardrails survived with full force, and you should be able to recite both. First, courts: SUD records and testimony about them still may not be used or disclosed against the patient in civil, criminal, administrative, or legislative proceedings absent patient consent or a specific court order meeting Part 2's standards. Second, the redisclosure notice: disclosed records still travel with a written prohibition notice telling recipients the records are protected and may not be used in proceedings against the patient.

HIPAA opens for treatment by default; Part 2 opens only because the patient handed you the combination in writing. Build every AI workflow as if the vault door is closed until the consent says otherwise.

What Stayed Strict: The Lines the 2024 Rule Did Not Move

Alignment is not surrender, and an SUD clinician who treats Part 2 as "basically HIPAA now" will eventually be wrong in a way that matters. The consent-first baseline stayed: no TPO disclosure happens without a signed consent containing Part 2's required elements, including the patient's name, the purpose, what may be disclosed, who may disclose and receive it (the general designation "my treating providers" is permitted), the right to revoke, and an expiration event or date. The protection against use in legal proceedings stayed and is arguably the rule's soul: a prosecutor, a custody attorney, or a licensing board cannot reach into the vault with an ordinary subpoena; they need consent or a Part 2 court order issued under the rule's own heightened standards.

SUD counseling notes received their own psychotherapy-notes-style protection in the 2024 rule: notes a Part 2 clinician keeps separately, analyzing the contents of a counseling session, require their own specific consent and sit outside the single TPO consent, mirroring the HIPAA carve-out at 45 CFR 164.508(a)(2). The same structural lesson applies: the protection depends on separation, and an AI pipeline that merges counseling-note content into the general SUD record collapses it. The revocation right stayed live too: a patient can revoke the TPO consent, after which new disclosures stop, so your systems, including any AI vendor's, must be able to honor a revocation operationally, not just theoretically.

One more line that did not move: Part 2 attaches to the record, not the conversation topic. A client at a non-Part 2 general therapy practice who discusses drinking is protected by HIPAA, state law, and your ethics code, but not by Part 2. A client of a Part 2 program is protected by Part 2 even when the session is about her marriage. Clinicians invert this constantly. The vault protects what the program creates, because the program is what the patient was afraid to walk into.

What This Means for an AI Scribe in an SUD Program

Now run the AI question through the vault. An AI scribe that records, transcribes, and drafts notes for a Part 2 program is receiving Part 2 records at the moment of capture. Three consequences follow. First, the vendor agreement must cover Part 2, not just HIPAA: a qualified service organization or business associate arrangement acknowledging Part 2 obligations, the prohibition on use in proceedings against patients, and the breach duties that now attach. A vendor that has never heard of Part 2 fails this conversation in the first five minutes, which is itself useful screening. Second, your consent architecture must account for the scribe: the cleanest pattern under the 2024 rule is to include AI-assisted documentation within the healthcare operations scope of the single TPO consent and disclose it plainly in your Patient Notice, so the patient who signs knows a documentation service processes session content under the program's agreements. Third, segmentation becomes a system requirement: if your practice is part Part 2 program and part general therapy, the scribe and the EHR must mark, route, and restrict the SUD program's records separately, because the vault's contents cannot mingle into charts that flow under ordinary HIPAA rules.

The hard worked example is the dual-provider client. Your Part 2 program treats Marcus for opioid use disorder; he also sees a PCP at an unaffiliated clinic for hypertension. The PCP's office requests records. Walk it slowly. Has Marcus signed the single TPO consent designating his treating providers? If yes, you may disclose to the PCP for treatment, attaching the redisclosure prohibition notice; the PCP, as a HIPAA covered entity, may then redisclose under HIPAA's rules but inherits the prohibition on use in proceedings against Marcus. If no, the vault stays shut: you go get consent, and "his doctor asked" is not an exception. Now add the AI layer: your scribe's draft of the coordination session is a Part 2 record; when the PCP's own AI scribe later ingests the records you sent, those records are Part 2-protected content inside a non-Part 2 program's vendor pipeline, which is exactly why the redisclosure notice travels with the records and why the 2024 rule's alignment of downstream handling matters in an AI-saturated referral network.

One guardrail belongs in every SUD-and-AI conversation, stated plainly: AI never makes the clinical determinations surrounding these records. It does not score the AUDIT-C or DAST-10, does not assess overdose risk, does not decide level of care, and does not make the mandated-report call when a disclosure implicates child welfare. The clinician determines; AI structures, transcribes, and formats after the determination. In an SUD program, where the records are legally radioactive, letting a tool drift into judgment is a double failure: clinical and regulatory at once.

Anatomy of a Compliant Consent: The Elements, One by One

Because the artifact for this lesson is consent language, take the elements apart before assembling them. A Part 2 consent under the 2024 final rule needs: the patient's name; who may disclose (your program); who may receive, where the rule now permits broad designations like "my treating providers and their business associates" for TPO consents; a description of the information, which may be "all my SUD records" for the TPO consent; the purpose, where "treatment, payment, and healthcare operations" is now a permissible single purpose; the patient's signature and date; a statement of the right to revoke in writing, except to the extent the program has already acted on it; and the expiration: a date, event, or condition, where "until I revoke" framing tied to the TPO relationship is workable under the single-consent structure. Miss an element and the consent fails, and a disclosure on a failed consent is a violation under the newly imported HIPAA penalty scheme.

Two drafting habits separate adequate consents from defensible ones. First, write the AI disclosure into the operations language rather than hiding it: a sentence such as "healthcare operations includes contracted documentation services, including AI-assisted transcription and note drafting, operating under written agreements binding them to these confidentiality rules" tells the patient the truth and ties the vendor to the consent's scope. Second, pair every consent with the redisclosure notice text you will stamp on outgoing records, drafted as a set: the consent opens the vault; the notice rides with whatever leaves it. Programs that draft these separately end up with consents promising protections the cover letters forget to carry.

The Segmentation Pattern: One Practice, Two Record Classes

For the group practice that is partly a Part 2 program, segmentation is the architecture that makes everything above workable. The pattern has four moves. Tag at creation: every record originating in the SUD program is flagged as Part 2 the moment it is created, including AI-drafted notes, transcripts, and retained audio, because a record you cannot identify is a record you cannot protect. Route by tag: the EHR and scribe store Part 2 records in a partition or behind access controls so a general-caseload clinician, biller, or integration does not pull SUD records by default. Gate disclosures by consent status: outgoing flows check for a valid, unrevoked TPO consent before any Part 2 record moves, and attach the redisclosure notice automatically. Audit the boundary: someone reviews, quarterly, what crossed and on what consent, because the accounting-of-disclosures right means a patient can ask, and you must be able to answer.

Test your AI vendor against this pattern explicitly. Can the scribe apply a Part 2 flag per client or per program? Can it exclude Part 2 clients entirely from analytics, model-improvement, or secondary-use processing? Can it delete a specific client's audio and transcripts upon revocation or request? Can it show, in writing, how its subprocessors handle flagged records? A vendor that answers all four crisply has met Part 2 before; a vendor that answers "our platform is fully HIPAA compliant" has just told you it has not, because that answer is responsive to the wrong rule. The vault question is never whether the house has good locks; it is whether the contractor knows the vault is there.

The Applied Problem: Draft Your Part 2 Consent Language Block

Your artifact is the Part 2 Consent Language Block: the core paragraphs of a single TPO consent for your program, plus the matching redisclosure notice, drafted as a set you hand to your attorney or compliance officer for finalization. Open a document with three sections. Section A, the consent core: the designation sentence ("I authorize [Program Name] to disclose all records related to my substance use disorder diagnosis, treatment, and referral for treatment to my treating providers, health plans, and their business associates"), the purpose sentence ("for purposes of treatment, payment, and healthcare operations, which include contracted documentation services such as AI-assisted transcription and note drafting operating under written agreements binding them to these rules"), the revocation sentence ("I may revoke this consent in writing at any time, except to the extent the program has already acted on it"), and the expiration sentence ("this consent remains in effect until I revoke it or until [event]"). Section B, the redisclosure notice: a short block stating the records are protected by 42 CFR Part 2, may not be used or disclosed in any civil, criminal, administrative, or legislative proceeding against the patient absent consent or a qualifying court order, and that the recipient is bound accordingly. Section C, the counseling-notes carve-out: one sentence stating that separately maintained SUD counseling notes are not covered by this consent and require specific separate authorization.

If you draft with AI assistance, keep client data out and use a prompt like: "Draft a 42 CFR Part 2 single consent for treatment, payment, and healthcare operations under the 2024 final rule for an outpatient SUD program. Include: general designation of treating providers and business associates as recipients, an explicit healthcare-operations sentence covering AI-assisted documentation services under written agreements, the written revocation right, an expiration tied to revocation, and a companion redisclosure prohibition notice referencing use in proceedings against the patient. Flag every element a compliance attorney must verify." Then run the verification pass: all required elements present, the redisclosure notice exists as a separate block, the counseling-notes exclusion sentence appears, and nothing implies disclosures can occur before the consent is signed.

"Done" looks like a two-page set: consent core, notice block, carve-out sentence, plus a one-paragraph "holds itself out" analysis of your own practice stapled to the front, dated. You are not done until a colleague can read the front paragraph and know whether your practice is a Part 2 program and why. That front page is the artifact most programs are missing, and it is the first thing a reviewer asks about when an AI tool, a payer audit, or a breach puts your SUD records in question.

Key Takeaways

• 42 CFR Part 2 is a vault inside the HIPAA house: SUD records from federally assisted programs carry protection above ordinary medical privacy because people avoid addiction treatment when seeking it can be used against them. The 2024 final rule changed the combination, not the vault.
• You are a Part 2 program if you hold yourself out as providing SUD diagnosis, treatment, or referral and are federally assisted, a bar most practices clear via Medicare, Medicaid, DEA registration, or tax-exempt status. "Holds itself out" turns on your marketing and program structure, not your license; write the analysis down.
• The 2024 final rule aligned Part 2 with HIPAA: HIPAA's civil and criminal penalty structure and breach notification now apply, patients gained an accounting-of-disclosures right, and a single signed consent can authorize all future TPO uses and disclosures until revoked.
• Part 2 remains consent-first. HIPAA opens for TPO by default; the vault opens only because the patient signed. Records disclosed under a TPO consent to HIPAA entities may be redisclosed under HIPAA rules, but the prohibition on use in proceedings against the patient survives, and the redisclosure notice travels with the records.
• An AI scribe in a Part 2 program receives Part 2 records at capture: the vendor agreement must cover Part 2 explicitly, the single consent's operations language should name AI-assisted documentation, and separately kept SUD counseling notes stay out of the AI pipeline because their protection depends on separation.
• Mixed practices need the four-move segmentation pattern: tag Part 2 records at creation, route by tag, gate disclosures on valid unrevoked consent with the notice attached, and audit the boundary quarterly. "We are HIPAA compliant" answers the wrong rule.
• AI never scores the AUDIT-C or DAST-10, never assesses overdose risk, never decides level of care, and never makes the mandated-report call. The clinician determines; AI structures and formats after the determination. Your artifact, the Part 2 Consent Language Block with redisclosure notice and a written holds-itself-out analysis, comes before any tool touches an SUD session.