Part 2 minor-application disclosure to parent

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

Current rule checkpoint

Live 42 CFR 2.14(b)(2) says that when state law requires parental consent to treatment, the fact that a minor applied for SUD treatment may be communicated to a parent, guardian, or other state-authorized person only with the minor's written Part 2 consent or when the program director makes the rational-choice determination under paragraph (c). Current section 2.31 governs the written-consent route. The HHS fact sheet gives February 16, 2026 as the amended framework's compliance date.

The communication has two possible gates

Current 42 CFR 2.14 identifies the minor's written consent and the program-director determination under paragraph (c). Record which gate applies, legal source, decision-maker, facts, recipient authority, information, purpose, time, and response.

Routine family notification needs review

Intake calls, portal invites, appointment reminders, voicemail, mail, transportation, insurance, emergency contacts, referral follow-up, and missed-visit outreach can reveal the application. Configure every channel around the verified authority and minor's preferences.

Keep the disclosure tightly scoped

A permissible statement about application supplies no general access to diagnosis, assessment, treatment, notes, schedule, location, peers, communications, payment, or future care. Select only information supported by the specific gate.

Recognize application disclosures in ordinary workflows

An application can be exposed by a returned intake call, calendar invitation, voicemail, text reminder, portal enrollment, location name, transportation request, referral update, benefits inquiry, authorization, mailed packet, missed-visit outreach, or staff transfer. Inventory sender, recipient, content, metadata, channel, timing, and automation for each contact.

Configure a safe contact plan before outreach. Verify phone, email, mail, portal, proxy, preferred language, and whether a message can identify the SUD program or service. A parent who must consent to treatment does not automatically receive unrestricted notice through any channel.

Choose and document the correct gate

For written consent, verify the minor's identity, voluntary decision, recipient, information, purpose, expiration, revocation, signature, and date under section 2.31. Limit contact to that scope and recheck consent before transmission.

The alternative route is narrow. The program director must determine both that the applicant lacks capacity because of extreme youth or a mental or physical condition to make a rational disclosure choice and that a substantial threat to life or physical well-being may be reduced by communicating relevant facts. Administrative convenience, missed appointments, nonpayment, or a general belief that parental involvement helps does not substitute for those findings.

Protect the response after contact

Authenticate the authorized adult and check custody, abuse, neglect, endangerment, or conflict concerns before disclosure. Share only the application fact and other information supported by the selected gate. Give staff a script for questions that exceed scope and a rapid safety escalation route.

Log authority, recipient, content, purpose, channel, time, responder, delivery, and follow-up. If an automated notice revealed the application without authority, stop further messages, preserve evidence, assess the event with privacy and security, correct the workflow, and test the repair.

Maintain a contact matrix for each application

Record which people and channels are approved, restricted, unknown, or unsafe for intake calls, appointment details, transportation, payment, emergency outreach, and general messages. Include safe wording, voicemail permission, sender name, language, accessibility needs, time windows, and an escalation owner. Do not place sensitive explanations in a broadly visible banner or notification.

Reconfirm the matrix after a consent, custody, address, phone, portal, risk, or treatment-status change. Test reminder and missed-visit systems with the approved settings before relying on them.

The minor can ask whether a parent will be told about the application, what legal route supports that contact, which facts will be shared, how messages will identify the sender, whether a safer channel is available, and who can correct a mistaken notification. Staff should answer before activating routine outreach.

Example

Ten proposed notifications are assessed. Seven have the correct gate, adult authority, purpose, scoped content, channel, and disclosure log; three follow an automatic parent-contact workflow. Readiness is 7 of 10 notifications.

Application-disclosure checklist

• inventory every call, message, portal, payer, mail, transport, and referral route;
• confirm state treatment law and the adult's authority and restrictions;
• select minor written consent or document both paragraph (c) findings;
• disclose only information supported by that gate through a safe channel;
• log delivery, follow-up, and any request that exceeds scope; and
• contain, assess, correct, and retest unauthorized automated contact.

The fact of application is protected. A treatment-consent role, family relationship, emergency-contact label, or payment role alone does not answer whether that fact may be disclosed.