A discharge coordinator at a Sacramento intensive outpatient program faxes a "treatment summary" to a client's primary care physician. Helpful, routine, done a hundred times. Except this program is a federally assisted substance use disorder program, the summary names the client's opioid use disorder and buprenorphine dose, the consent on file expired two months ago, and the receiving clinic scans the fax straight into a general medical record where it is later re-released to a disability insurer. That single fax is a chain of 42 CFR Part 2 violations, and under the 2024 final rule, Part 2 violations now carry HIPAA-style civil and criminal enforcement instead of the old, rarely used penalty scheme. This lesson runs an entire SUD episode of care end to end, intake, weekly individual sessions, group, urinalysis, MAT coordination with the PCP, release of information, discharge, and teaches you the segmentation pattern: which records can travel on a single consent, which need redisclosure prohibition language stapled to them, and which never leave the Part 2 chart at all. It also asks the AI question almost nobody asks their scribe vendor: does your BAA actually cover Part 2? By the end you will build a Part 2 Segmentation Map with redisclosure consent language you can put in front of your compliance officer.

What Part 2 Protects, and Why It Is Stricter Than HIPAA

42 CFR Part 2 is the federal confidentiality regulation for substance use disorder treatment records held by federally assisted SUD programs. It predates HIPAA, and it exists for one blunt reason: people do not seek addiction treatment if the record can follow them into a courtroom, an employer's file, or a custody battle. SUD treatment history is uniquely weaponizable. A depression diagnosis rarely shows up in a prosecution; an opioid use disorder record shows up in dependency court, criminal court, divorce proceedings, and professional licensing actions constantly. So Congress built a fence taller than HIPAA's: where HIPAA permits broad disclosure for treatment, payment, and operations without patient authorization, Part 2 historically required specific written patient consent for nearly every disclosure, even to another treating provider.

The 2024 final rule, the most significant revision in the regulation's history, moved Part 2 closer to HIPAA without merging them. The headline changes a working clinician needs: a patient may now give a single consent covering all future uses and disclosures for treatment, payment, and health care operations (TPO), rather than signing a new consent for every disclosure; once records are disclosed under that TPO consent to a HIPAA covered entity, they may be redisclosed per HIPAA rules; enforcement now runs through HIPAA-style civil and criminal penalties; patients gained breach-notification rights; and the rule aligned Part 2 patient rights and complaint mechanisms with HIPAA's. What did not change matters just as much: the prohibition on using Part 2 records against the patient in legal proceedings without a specific court order remains, the redisclosure notice requirement remains for records leaving the Part 2 fence outside the TPO pathway, and the consent itself still has required elements that a generic HIPAA authorization does not satisfy.

Carry one analogy through this lesson: a Part 2 program is a country with strict export controls, and every record is cargo. Some cargo ships freely once the customs paperwork (the TPO consent) is on file. Some cargo ships only with an export label permanently affixed, the redisclosure prohibition notice, that binds whoever receives it. And some cargo is on the no-export list entirely: it does not leave the country no matter what paperwork anyone waves. Your job, as the clinician inside the fence, is customs officer for your own chart. AI can print manifests, fill in label templates, and flag suspicious shipments. AI never stamps the export approval. The disclosure decision is the clinician's, every single time.

The Episode of Care: Where Part 2 Touches Every Document

Walk the episode the way the chart experiences it. Intake: a 90791 diagnostic evaluation establishing an F11.20 opioid use disorder diagnosis, the ASAM level-of-care determination, and the consent packet, which in a Part 2 program now includes the Part 2 notice and the TPO consent decision the patient makes with full explanation. Weekly individual therapy: 90834 or 90837 sessions whose notes name cravings, use episodes, triggers, and relapse events. Group: 90853 sessions, where the documentation problem doubles because the note must capture this client's participation without capturing other group members' identities, the same one-client-one-chart discipline the group-therapy lesson taught, now with Part 2 consequences if it fails. Urinalysis: collection dates, results, and the clinical response, some of the most weaponizable data in the entire record, because a single dirty screen reads like a verdict to a family-court judge. MAT coordination: the buprenorphine or methadone prescriber, often a PCP outside the Part 2 program, needs doses, last-use data, and contraindications. Discharge: a summary that will be requested by future providers, payers, and sometimes courts for years.

Every one of those documents is Part 2 cargo, because every one of them comes from a Part 2 program and identifies the patient as having or having had a substance use disorder. This is the point clinicians coming from general mental health miss: Part 2 does not protect a category of sentence; it protects the records of the program. A scheduling note that says nothing clinical still reveals that the person is a patient of an SUD program, and that fact alone is protected. Inside the fence, there is no such thing as a harmless document.

Now layer AI onto the episode. An ambient scribe drafting the 90834 note is processing Part 2 data. A prompt that summarizes the chart for a discharge summary is processing Part 2 data. A billing tool generating the claim is transmitting Part 2 data to a payer, which the TPO consent can authorize. Every vendor in that chain is, in Part 2 vocabulary, handling protected records, and the contracts have to say so explicitly. We come back to the vendor problem below, because it is where most practices are silently exposed today.

The Segmentation Pattern: Three Tiers of Cargo

The practical skill of this lesson is segmentation: sorting the episode's documents into the three export tiers before anyone asks for anything, so disclosure decisions are made calmly at intake and review, not frantically when a fax request lands. Tier one is TPO-consented cargo: with a valid single consent for treatment, payment, and operations under the 2024 final rule, the records reasonably necessary for those purposes can flow to HIPAA covered entities, the claim to the payer, the care-coordination summary to the PCP managing the MAT prescription, the utilization-review packet. Once received by a covered entity under the TPO consent, HIPAA's rules govern redisclosure downstream. This tier is where the 2024 rule actually reduced friction, and it is the tier your MAT coordination lives in, provided the consent on file is the new-style TPO consent with the required elements and the patient understood what they signed.

Tier two is labeled cargo: disclosures outside the TPO pathway, to an employer-mandated treatment verification, to a family member, to a non-covered entity, or under a consent narrower than TPO. These travel only with specific written consent naming the recipient and purpose, and they carry the redisclosure prohibition notice, the export label, affixed to the document itself. The notice tells the recipient that the record is protected by 42 CFR Part 2 and that further disclosure is prohibited without the patient's express written consent or as otherwise permitted by the regulation, and that the record cannot be used to investigate or prosecute the patient absent a specific court order. The label is not decoration. It is what binds the recipient, and a disclosure that should have carried it and did not is itself a violation.

Tier three is the no-export list: content that does not leave the Part 2 chart regardless of paperwork. The clinician's psychotherapy notes, if kept as the separate HIPAA psychotherapy-notes carve-out under 45 CFR 164.501 and 164.508(a)(2), stay out of every release by default. Raw urinalysis result histories beyond what a specific authorized purpose requires stay home; the PCP managing buprenorphine may need to know about a relapse relevant to dosing, but a disability insurer's blanket request gets the minimum necessary, never the lab trail. Other group members' identities never leave under any consent, because no patient can consent away another patient's protection. And nothing, from any tier, goes into a legal proceeding against the patient without the specific court order Part 2 still requires; a subpoena alone does not open the fence. When in doubt, a document defaults upward to a more restrictive tier until the clinician decides otherwise.

Inside a Part 2 program there is no harmless document: every record, down to the appointment reminder, reveals that the person sought addiction treatment, and that fact is exactly what the regulation was built to protect.

The Consent Architecture Under the 2024 Final Rule

The TPO consent is the load-bearing document of the modern Part 2 episode, so treat it with intake-level seriousness. It must be informed: the patient needs to understand that one signature now permits ongoing disclosures for treatment, payment, and operations, that records reaching HIPAA covered entities under it can then move under HIPAA's rules, and that the patient retains the right to revoke. Document the conversation, not just the signature. A consent the patient did not understand is a consent a plaintiff's attorney will unwind, and the population signing these forms is frequently in withdrawal, in crisis, or under legal pressure on day one. Some programs reasonably re-confirm the consent once stabilization is achieved; that re-confirmation note is cheap insurance.

Revocation is the consent architecture's stress test. When the patient revokes the TPO consent, the export approvals stop prospectively: no new disclosures under it, while disclosures already lawfully made are not retroactively unlawful. Your workflow needs a revocation procedure with the same urgency as a high-risk flag: who gets notified, which standing data feeds stop, and how the billing pipeline handles claims that can no longer carry Part 2 data to the payer. A practice that cannot operationally stop the flow within a day of revocation has a paper right and a real violation.

Where does AI sit in the consent architecture? Exactly where it sits in every consent workflow in this program: drafting and tracking, never deciding. AI usefully drafts the plain-language explanation of the TPO consent at an accessible reading level, generates the redisclosure prohibition notice block for tier-two documents, maintains the consent-expiration and revocation tracker, and pre-fills the consent log fields (date, scope, recipient classes, revocation status). AI never makes the Part 2 disclosure decision. Whether this record goes to this recipient under this consent is a judgment about regulation, clinical risk, and the patient's situation, and it belongs to the clinician who signs the disclosure log. The customs officer stamps; the printer prints.

The Vendor Problem: Your Scribe's BAA Probably Does Not Say Part 2

Here is the exposure most SUD programs are carrying right now without knowing it. A standard behavioral health AI scribe arrives with a HIPAA business associate agreement. HIPAA BAAs obligate the vendor to safeguard PHI and report breaches. They do not, by default, bind the vendor to Part 2's rules: the redisclosure restrictions, the prohibition on use in proceedings against the patient, the consent-scope limits. Under Part 2, entities receiving records for the program's purposes need contractual obligations that mirror the regulation, and the 2024 final rule's alignment with HIPAA did not erase that requirement; it sharpened the enforcement behind it. A scribe vendor whose model subprocessors receive your session audio under a generic BAA, with no Part 2 language, is a gap in your fence that you, not the vendor, will answer for, because the program is the regulated party.

So the diligence script for any AI tool touching a Part 2 chart has four questions, asked in writing. One: does your BAA or a Part 2 addendum explicitly acknowledge that the data you receive includes 42 CFR Part 2 records and bind you and all subprocessors to Part 2's redisclosure restrictions? Most generic BH BAAs do not; get the addendum or do not deploy. Two: can your system segment Part 2 clients, so that Part 2 records are excluded from any vendor-side analytics, model improvement, or data-sharing features that a general consent might otherwise permit? Three: what happens to Part 2 data on revocation or program termination, with what deletion attestation? Four: will you commit in writing that our data is never used in any proceeding, disclosure, or product feature that could surface a patient's SUD treatment status? A vendor that hedges on question one has answered all four.

Inside the program, the configuration discipline mirrors the contract. Part 2 clients get flagged in the EHR and in the scribe tool so templates attach the right consent logic; group-session capture follows the one-client rule with other members' identities never entering a draft; and discharge-summary prompts pull only from the sections the destination tier permits. The most dangerous AI behavior in a Part 2 workflow is helpfulness: a summarization model asked for a "complete clinical picture" will cheerfully sweep urinalysis trails, group attendance, and psychotherapy-note content into one tidy document that no single consent on file authorizes. The prompt has to carry the tier, and the clinician has to check the cargo against the manifest before anything ships.

Worked Example: The MAT Coordination Letter to the PCP

Make the abstraction concrete. Your client, eight weeks into the IOP, has a PCP managing buprenorphine-naloxone. The PCP's office requests "records to support medication management." TPO consent is on file, valid, unrevoked; the PCP is a HIPAA covered entity; care coordination is squarely treatment. This is tier-one cargo, but tier one still has a size limit: what is reasonably necessary for the purpose, not the whole chart. The letter the PCP needs contains the diagnosis (F11.20), current level of care and attendance pattern, medication-relevant clinical status (recent use or abstinence as it bears on dosing, withdrawal symptoms, sedation concerns), any contraindication observations, and your care-coordination contact. It does not need the group-session narratives, the trauma-history detail from week three, or the full urinalysis ledger.

The AI workflow: the clinician decides the disclosure is authorized and decides the scope, then prompts: "Draft a care-coordination letter from an SUD treatment program to the prescribing PCP. Include only: diagnosis as stated, level of care and attendance as stated, the medication-relevant clinical observations I provide below, and program contact information. Do not include group content, psychotherapy-note material, urinalysis history beyond what I state, or any content I have not supplied. Append the 42 CFR Part 2 redisclosure prohibition notice block." Note the last line: even on a tier-one TPO disclosure, many programs affix the notice as standard practice, and on any non-TPO disclosure it is mandatory. The verification pass reads the draft against the tier: every sentence either traces to clinician-supplied content within scope or comes out. Then the clinician signs the letter and logs the disclosure: date, recipient, purpose, consent relied upon, contents in summary. That log is what stands between you and an enforcement letter three years from now, because under the 2024 rule the question will not be "did you mean well" but "show me the consent and the manifest."

Discharge, Courts, and the Long Tail of the Record

Discharge is where segmentation pays or fails. The discharge summary is the document most requested for years after the episode: by future providers, by payers, sometimes by attorneys. Write it, from day one of drafting, as a tier-conscious document: a core clinical summary suitable for TPO-pathway continuity of care, with the no-export content, psychotherapy notes, raw urinalysis trails, any group-member-adjacent content, never embedded in it. A discharge summary that braids tier-three content into its narrative cannot be cleanly disclosed at any tier, and the practical result is either over-disclosure or a useless redaction lattice. AI can structure the summary from clinician-selected content, and AI can run the pre-release audit, "flag any sentence referencing urinalysis results, other patients, or psychotherapy-note content", but the inclusion decisions are the clinician's, made against the map.

The court boundary deserves its own paragraph because it is the one place where even valid consent is not the whole story. Part 2 prohibits using protected records to investigate or prosecute the patient absent a specific court order meeting the regulation's criteria; a subpoena, even a stern one on letterhead, does not by itself authorize release. The 2024 final rule kept this protection. Your standing operating procedure: any legal demand touching a Part 2 chart goes to counsel before any document moves, the requester is informed that the records are protected by 42 CFR Part 2 and require a compliant court order, and nothing ships in the meantime. The next two lessons in this chapter, on forensic write-ups and the subpoenaed therapist, build on exactly this reflex. And the AI rule holds at the courthouse door more firmly than anywhere: AI never makes the Part 2 disclosure decision, never weighs whether an order is compliant, and never drafts a response that concedes records exist beyond what counsel approves. The clinician decides, documents, and signs; counsel guards the gate; the model prints the paperwork it is told to print.

The Applied Problem: The Part 2 Segmentation Map with Redisclosure Consent Language

Your artifact is a two-part document. Part one is the Segmentation Map: a single-page table covering the full episode of care, with one row per record type, intake evaluation, TPO consent and notice, individual session notes, group notes, urinalysis orders and results, MAT coordination letters, claims and billing records, treatment plan reviews, discharge summary, psychotherapy notes, and three columns: tier (TPO-consented, labeled-consent, no-export), permitted destinations with the consent each requires, and the AI tasks permitted for that record type. Part two is the Redisclosure Consent Language block: the notice paragraph your program affixes to every tier-two document and, by policy, to tier-one disclosures as well.

Build it in three passes. First pass, sort: take the episode walkthrough from this lesson and assign every record type a tier yourself, on paper, with one sentence of reasoning per row; defaulting upward when uncertain is the correct instinct. Second pass, draft with AI: "Format the following clinician-completed segmentation decisions into a one-page Part 2 Segmentation Map table with columns for record type, tier, permitted destinations and required consent, and permitted AI tasks. Then draft a redisclosure prohibition notice block stating that the accompanying record is protected by 42 CFR Part 2, that further disclosure is prohibited without the patient's express written consent except as the regulation permits, and that the record may not be used to investigate or prosecute the patient absent a specific court order. Plain language, suitable for affixing to outgoing documents. Do not alter any tier assignment I have made." Third pass, verify like a customs officer: confirm no record type drifted tiers in formatting, confirm the notice block contains the three load-bearing elements (Part 2 protection, redisclosure prohibition, court-order requirement), and confirm the AI-tasks column never includes a disclosure decision, only drafting, tracking, formatting, and auditing.

Done looks like this: a map your compliance officer can laminate, a notice block your front office can affix without asking you each time, and a standing answer to the question every fax request raises. Bring the map to your next vendor renewal conversation and ask the four diligence questions from this lesson with the map on the table. If the vendor cannot place their product on your map, the product does not belong inside your fence.

Key Takeaways

• 42 CFR Part 2 protects the records of federally assisted SUD programs because addiction treatment history is uniquely weaponizable in courts, custody disputes, and employment. Inside the fence there is no harmless document; even a scheduling note reveals protected treatment status.
• The 2024 final rule allows a single TPO consent for treatment, payment, and operations, permits HIPAA-rule redisclosure once records reach covered entities under it, and backs Part 2 with HIPAA-style civil and criminal enforcement plus breach-notification rights. The court-order requirement for use against the patient survived intact.
• Segment the episode into three tiers before anyone asks: TPO-consented cargo (claims, MAT coordination), labeled cargo requiring specific consent plus the redisclosure prohibition notice, and no-export content (psychotherapy notes, raw urinalysis trails beyond purpose, other group members' identities). Uncertain documents default upward.
• The TPO consent is informed or it is nothing: document the explanation, build a same-day revocation procedure that actually stops the data flows, and consider re-confirming consent after stabilization for clients who signed in crisis.
• Most generic behavioral health BAAs do not cover Part 2. Demand a written Part 2 addendum binding the vendor and all subprocessors to redisclosure restrictions, Part 2 client segmentation, deletion attestations, and a no-proceedings commitment before any AI tool touches the chart.
• AI drafts notices, formats letters, tracks consents and expirations, and audits outgoing documents for tier violations. AI never makes the Part 2 disclosure decision, never judges whether a court order is compliant, and never assembles a "complete clinical picture" that no consent on file authorizes. The clinician decides, documents, and signs.
• A subpoena is not a court order under Part 2. Any legal demand goes to counsel before anything moves, and the disclosure log, date, recipient, purpose, consent relied upon, contents, is the artifact that answers an enforcement inquiry years later.