42 CFR Part 2 Substance Use Disorder Records Release
This 42 CFR Part 2 Substance Use Disorder Records Release template captures patient consent, recipient details, record scope, expiration, and redisclosure acknowledgment in one form. Use it to document a compliant, patient-specific authorization before sharing SUD treatment records.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Behavioral Health · Substance Use Treatment · Hospitals And Health Systems · Community Health Clinics
Overview
This template is a patient authorization form for disclosing substance use disorder treatment records under 42 CFR Part 2. It is built around the fields that matter for a valid release: patient identification, the disclosing program, the recipient, the exact records to be shared, the purpose of disclosure, the expiration rule, and the patient’s signature and acknowledgment.
Use it when a program needs written consent before sending SUD records to another provider, a family contact, a legal representative, or another authorized recipient. The structure supports progressive disclosure, so you can keep the release narrow by selecting only the relevant information categories, date range, or specific episode instead of exposing the full chart. That helps reduce unnecessary PII collection and supports the minimum-necessary principle.
Do not use this form as a substitute for a general intake form, a treatment plan, or a broad medical records request. It is not meant for situations where disclosure is already permitted by another rule or where the patient is not authorizing the release. It also should not be used to collect extra data that is not needed for the disclosure decision. The template is most useful when your workflow needs a clear, auditable consent record that staff can review, route, and store with the patient file.
Standards & compliance context
- This template supports 42 CFR Part 2 by documenting patient consent, recipient identity, disclosure scope, and expiration for SUD records.
- The form is structured to support data minimization by collecting only the fields needed to authorize the disclosure.
- Clear field labels, required markers, and date-specific inputs help align the form with WCAG 2.1 AA usability expectations.
- The redisclosure acknowledgment helps ensure the patient is informed that downstream recipients may not be subject to the same confidentiality protections.
- If the form is used in an HR or intake context for accommodations or benefits, keep the language separate from treatment disclosure consent to avoid mixing purposes.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Consent Notice and Submission Terms
This section tells the patient exactly what they are authorizing and sets expectations for how the form will be processed.
- Authorization Notice
- I have read and understand the authorization notice above
- Submission Type
Patient Identification
These fields match the authorization to the correct patient without collecting unnecessary identifiers.
- Patient Full Name
-
Date of Birth
Collect only if needed to accurately identify the patient record.
-
Medical Record Number
Optional identifier if used by your organization to locate the correct record.
- Phone Number
Disclosing Program and Recipient
This section identifies who is releasing the records and who is allowed to receive them, which is essential for a valid disclosure.
- Disclosing Program / Facility Name
- Recipient Type
- Recipient Name
- Recipient Department or Attention To
-
Recipient Contact Information
Include address, fax, secure email, or other contact details used for disclosure.
Records to Be Disclosed
This is where you narrow the scope so the release covers only the information the patient intended to share.
- Information Categories to Disclose
- Describe Other Information
- Records From Date
- Records Through Date
-
Specific Program Episode or Service Period
Use this field if the release should be limited to a specific episode of care.
Purpose and Expiration
These fields define why the disclosure is happening and when the authorization stops being valid.
- Purpose of Disclosure
- Authorization Expires
- Expiration Date
-
Expiration Event
Describe the event that will end this authorization.
- Other Expiration Details
Patient Rights, Signature, and Acknowledgment
This section captures the patient’s consent, any representative authority, and the acknowledgments needed to complete the record.
- I understand I may revoke this authorization in writing except to the extent action has already been taken in reliance on it
- I understand that records protected by 42 CFR Part 2 may not be redisclosed without my consent except as permitted by law
- Patient Signature
- Signature Date
- Representative Name
- Relationship to Patient
- Witness Name
How to use this template
- 1. Enter the consent notice and submission terms so the patient understands what the form authorizes and what happens after submission.
- 2. Fill in the patient identification fields with only the identifiers your workflow needs to match the record, such as name, date of birth, and medical record number.
- 3. Specify the disclosing program and the recipient with enough detail to avoid ambiguity, using conditional logic for recipient type, department, and contact information where applicable.
- 4. Select the records to be disclosed by category, then narrow the release with a date range or specific episode instead of defaulting to the full chart.
- 5. Define the purpose and expiration clearly, choosing a date or event that matches the intended disclosure window and avoids open-ended consent.
- 6. Capture the patient signature, date, and any representative or witness details, then store the signed form in the audit trail before releasing records.
Best practices
- Keep the records-to-be-disclosed section narrow by default and use conditional logic to reveal extra fields only when the patient selects a broader release.
- Mark required versus optional fields clearly so patients do not assume they must provide unnecessary PII.
- Use a date picker for birth date, signature date, and expiration date instead of free text to reduce validation errors.
- State in plain language what happens after submission, including who receives the authorization and how staff will process it.
- Include a redisclosure acknowledgment that explains the recipient may not be bound by the same confidentiality rules after disclosure.
- If a representative signs, require the relationship field so staff can verify authority before releasing records.
- Avoid collecting unrelated identifiers or notes that are not needed to execute the disclosure request.
- Store the completed form with an audit trail so staff can confirm who authorized the release, when it was signed, and what scope was approved.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should I use this 42 CFR Part 2 release form?
Use it any time a program needs patient authorization to disclose substance use disorder treatment records covered by 42 CFR Part 2. It is designed for a specific recipient, a specific purpose, and a defined set of records or date range. If the disclosure is required by law or otherwise permitted without consent, this template may not be the right fit. It is best used before sending records to another provider, family member, attorney, insurer, or other third party.
What makes this different from a general medical records release?
This template is built for SUD records and includes the consent details that matter under Part 2, including the recipient, purpose, expiration, and redisclosure acknowledgment. A general release often does not capture the narrower scope and patient protections needed for Part 2 disclosures. If your workflow handles behavioral health or recovery services, using a Part 2-specific form helps avoid over-disclosure. It also makes the authorization easier to audit later.
Who should complete and sign this form?
The patient should complete and sign it, or a legally authorized representative should sign when permitted. Staff can help explain the fields, but they should not fill in patient intent or choose the disclosure scope without direction. If a representative signs, the form should capture the representative name and relationship. A witness field is included when your workflow requires an extra acknowledgment step.
How often does this form need to be renewed?
It should be renewed whenever the expiration date or expiration event has passed, or when the patient wants to change the recipient or scope. Part 2 authorizations are not meant to be open-ended by default, so the expiration field should be specific and easy to verify. Many programs tie renewal to a treatment episode, a date, or a single disclosure. If the purpose changes, create a new authorization rather than editing the old one.
What records should I include, and what should I avoid?
Include only the categories of information the patient actually wants disclosed, such as treatment summaries, attendance, lab results, or a specific episode of care. Use the date range and specific episode fields to narrow the release further when needed. Avoid collecting or disclosing more than necessary, especially unrelated behavioral health notes or broad chart access. The template supports progressive disclosure so you can keep the release limited and intentional.
Does this template support redisclosure warnings and consent language?
Yes. It includes a redisclosure acknowledgment so the patient is informed that the recipient may not be able to protect the information in the same way once it leaves the program. It also includes a consent notice and submission acknowledgment so the patient understands what they are authorizing and what happens after submission. If your organization uses additional notice language, you can customize the wording without changing the core consent fields. Keep the language clear and readable for accessibility.
Can I customize this for different programs or recipients?
Yes. You can adapt the recipient type, recipient department, and information categories for hospitals, outpatient clinics, recovery programs, case managers, attorneys, or family contacts where allowed. The form is structured so you can add conditional logic for different recipient types without exposing unnecessary fields. Keep required fields limited to what is needed for the disclosure decision. That helps with GDPR-style data minimization and reduces completion errors.
How should this integrate with our EHR or document workflow?
This form works well when the submission creates an audit trail, routes the authorization to records staff, and stores the signed copy in the patient chart. You can map the patient identity, recipient, purpose, and expiration fields into your EHR or document management system. If you use e-signature tools, make sure the signature date and witness fields are preserved in the final record. A clear submission confirmation line helps staff know when the authorization is ready for processing.
What are the most common mistakes when using this form?
The biggest mistakes are making every field required, leaving the expiration vague, and using broad language for the records to be disclosed. Another common issue is failing to name the recipient precisely enough, which makes the authorization hard to execute. Programs also sometimes skip the redisclosure acknowledgment or do not explain what happens after submission. This template is designed to prevent those gaps by separating each consent element into its own field.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
Compare 9 top shift scheduling platforms for 2026—features, pricing, and workforce fit for frontline, retail, healthcare, and enterprise teams.
-
Boost team collaboration with modern tools that improve visibility, accountability, and communication for stronger project outcomes.
-
Discover 4 proven keys to successful project management and team collaboration — from transparent goal-setting to real-time communication and workflow...
-
Compare the best employee apps of 2026—MangoApps, Blink, WorkJam, Flip, and more—to find the right fit for your frontline workforce.
Ready to use this template?
Get started with MangoApps and use 42 CFR Part 2 Substance Use Disorder Records Release with your team — pricing built for small business.
