Part 2 counseling-notes program-defense exception

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

The patient-brought proceeding is the first gate

42 CFR 2.31 states this limited exception. Verify the parties, claims, forum, procedural posture, program identity, responsive issues, notes category, legal hold, and exact defense purpose before any use or disclosure.

Preserve the complaint, petition, demand, docket, or other authoritative source showing who brought the matter and what is alleged. Confirm that the patient initiated the action or proceeding against the program and that the proposed notes use is for the program's defense. A family dispute, employee claim, payer matter, collection action, licensing inquiry, or program-initiated claim does not fit merely because the patient is mentioned.

Track amendments, counterclaims, consolidation, settlement, appeal, and dismissal. A matter can change after intake, so the exception should never become an enduring “legal access” label.

Defense need controls the record set

Counsel and the Part 2 privacy owner should identify the smallest relevant set and who needs it. Restrict access to the matter team, use protected channels, challenge overbroad demands where appropriate, and preserve court-specific sealing or protective measures.

Classify the records before review. Confirm which documents are SUD counseling notes, who originated them, which portions relate to the patient's allegation, and whether other Part 2 records or unrelated people appear. Build a candidate set, exclusion log, final approved set, and disclosure or use record.

Limit recipients to counsel, experts, court personnel, or other actors whose role and need are approved for the defense. Use matter-specific workspaces, least-privilege access, download controls, secure transfer, expiration, and closure. A broad legal drive or email group can expose notes beyond the defense team.

Separate defense preparation from disclosure

Internal review of notes, sharing with outside counsel, expert use, discovery production, filing, hearing exhibit, and testimony are different events. Record the authority, scope, recipient, protective conditions, and decision for each. A legal hold preserves information; it does not authorize anyone to use or disclose it.

Consider redaction, sealing, protective orders, in-camera review, privilege, state law, and court procedures through counsel. Never alter the underlying record to create a cleaner exhibit. Preserve the original, derivative work, and filed version distinctly.

Other Part 2 process may still matter

A subpoena, discovery request, complaint, or opposing counsel's demand does not explain every required step. Analyze court-order provisions, confidential communications, state privilege, licensing duties, and the forum's procedures. Track the authority used for each action.

Counsel should review whether a separate Part 2 court order, notice, opportunity to be heard, or other condition applies. Treat testimony, declarations, summaries, screenshots, and oral confirmation as possible disclosures of note content. Keep proceeding consent and counseling-notes consent analyses separate from this narrow exception.

Close or change access promptly

Reassess when the patient withdraws the matter, parties settle, claims narrow, counsel changes, an expert finishes, or the case closes. Remove access, recover permitted copies, follow retention and hold instructions, and preserve the audit trail. If notes were used for an unsupported purpose, contain access and route privacy, security, legal, clinical, and patient communication decisions.

Example with legal matters

Eight matters mention counseling notes. Five are proceedings brought by the patient with a documented defense need; three are unrelated employment or collection disputes. Exception fit is 5 of 8 matters.

The program opens restricted defense workspaces for the five qualifying matters and keeps only counsel-approved notes. It denies the other three requests, preserves their intake records, and identifies another lawful records process where appropriate. The legal team reviews existing folder permissions for similar overbroad labels.

Program-defense checklist

• Verify that the patient brought the action or proceeding against the program.
• Link each proposed note to a specific defense issue.
• Classify counseling notes and exclude unrelated records and people.
• Approve each internal use, counsel share, production, filing, and testimony event.
• Keep legal holds separate from use or disclosure authority.
• Remove access when claims, roles, or matter status change.
• Investigate unsupported access and related legal-workspace rules.

Owner controls

The 2024 final rule supplies current context. Use matter intake, party verification, counsel approval, relevance review, legal holds, restricted workspaces, disclosure logs, and closure controls.

Monitor matters, party status, notes reviewed, recipients, productions, testimony, access duration, holds, and incidents. Audit from each notes event back to a patient-brought matter and documented defense need, then from active legal workspaces into current least-privilege evidence. Retest after counsel, platform, policy, or proceeding changes.