By Sagar Shankaran, Founder of CallSphere
Substance-use treatment programs have a tighter privacy regime than the rest of behavioral health. The 2024 final rule aligned Part 2 with HIPAA — and February 16, 2026 was the hard compliance date.
Key takeaways
If your AI agent answers calls for a methadone clinic, an MAT prescriber, or any SAMHSA-funded SUD program, HIPAA is the floor, not the ceiling. 42 CFR Part 2 is the ceiling, and it just got rebuilt.
flowchart LR
Voice[Voice call] --> Redact[PII / PHI redaction]
Redact --> LLM[LLM with BAA]
LLM --> Resp[Response]
Resp --> Sanitize[Remove non-needed PHI]
Sanitize --> Caller[Caller]
Resp --> AuditDB[(Audit DB)]42 CFR Part 2 governs the confidentiality of substance use disorder (SUD) patient records held by federally assisted programs. SAMHSA published a final rule on February 16, 2024 (89 Federal Register 12472) that aligns Part 2 with HIPAA in five major dimensions. The rule went into effect April 16, 2024 with a two-year compliance window — enforcement of the updated provisions began February 16, 2026.
The five alignment changes most relevant to AI voice agents are: (1) a single patient consent now covers all future uses and disclosures for treatment, payment, and health care operations under 42 CFR 2.31; (2) HIPAA covered entities and business associates that receive Part 2 records under that consent may redisclose under HIPAA rules at 42 CFR 2.33; (3) the HIPAA Breach Notification Rule (45 CFR Subpart D) now applies to Part 2 breaches; (4) Part 2 penalties shift from criminal-only to the civil and criminal HIPAA enforcement structure; and (5) patients gain HIPAA-style rights to an accounting of disclosures and to request restrictions.
Critically, even after alignment, Part 2 still prohibits use of Part 2 records in legal proceedings against the patient without specific written consent or a court order — a protection that exceeds HIPAA.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent for behavioral health in your browser — 60 seconds, no signup.
An AI voice agent at a Part 2 program collects, by definition, Part 2 records the moment a caller says "I'm calling about my methadone dose" or "I have an appointment for my buprenorphine refill." That utterance, the call recording, the transcript, the AI summary, and the post-call analytics are all Part 2 records.
The single-consent simplification helps — once a patient signs the new omnibus consent, downstream HIPAA business associates (the EHR, the claims clearinghouse, the AI vendor) can move records under HIPAA rules. But the agent still needs to: (a) recognize Part 2 status at intake; (b) capture and version the consent; (c) tag every record produced by the call as a Part 2 record so segmentation rules can fire; (d) prevent the records from being used in legal proceedings without explicit additional authorization; and (e) honor the new accounting-of-disclosures right under 42 CFR 2.25.
CallSphere ships a behavioral-health workflow at /lp/behavioral-health that turns Part 2 mode on by default for SUD-coded clinics. The intake flow captures the omnibus consent at the first call, records the consent version, and tags every record produced thereafter with a Part 2 flag in the healthcare_voice PostgreSQL database. Tagged records are excluded from non-Part-2 reporting paths automatically. Sentiment, lead score, and AI summary still run, but the segregated tag flows through every downstream view. Accounting of disclosures is generated on demand. Breach notifications use the HIPAA timeline (60 days, business associate to covered entity). Practices treating opioid use disorder, alcohol use disorder, or running residential SUD programs should explore /industries/behavioral-health and /lp/behavioral-health, and start with a 7-day free pilot.
Did 42 CFR Part 2 go away? No. It was aligned with HIPAA on the consent, breach, and penalty mechanics. The core protection — heightened confidentiality of SUD records — remains, especially around legal proceedings.
Still reading? Stop comparing — try CallSphere live.
See the behavioral health AI agent handle a real call — complete, industry-specific, and live in your browser. No signup.
When does the new rule have to be in place? April 16, 2024 effective date, with a two-year compliance window. Enforcement of the new provisions began February 16, 2026.
Can a single consent cover treatment, payment, and operations? Yes, under 42 CFR 2.31 as amended. That is the headline simplification of the 2024 rule.
Does the AI agent need its own Part 2 designation? No. It operates as a HIPAA business associate. But records originating from a Part 2 program retain their Part 2 status when the agent processes them.
Are mental-health-only practices covered by Part 2? No. Part 2 covers SUD records held by federally assisted SUD programs. A general therapy practice that does not meet the 42 CFR 2.11 program definition is HIPAA-only.

Written by
Sagar Shankaran· Founder, CallSphere
LinkedInSagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
HIPAA-aware AI customer support uses privacy-conscious design, minimal data handling, and human routing for clinical cases. A 2026 guide for providers.
How clinics in Escazú, San José, and Liberia can capture US and Canadian medical-tourism inquiries around the clock with CallSphere's HIPAA-capable AI voice and chat agents — across time zones and languages.
American medical clinics miss a huge share of inbound calls at the front desk. See how CallSphere HIPAA-capable AI voice and chat agents book patients 24/7 without adding staff.
Using GPT-Realtime-2 for healthcare voice agents. BAA scope, PHI handling, retention, logging, and why a managed platform usually wins this build.
AWS HealthScribe became the open scribe layer EHR vendors built on top of in 2026. Here's the API surface, the per-encounter pricing, the BAA terms.
Why Claude salon AI is reshaping voice and chat automation, with concrete patterns for appointment AI in production deployments. A field-tested view from production teams shippi...
© 2026 CallSphere Inc. All rights reserved.
Made within San Francisco