HIPAA Requirements for Substance Abuse Treatment Centers: What You Need to Know (Including 42 CFR Part 2)

Product Pricing Demo Video Free HIPAA Training
LATEST
video thumbnail
Admin Dashboard Walkthrough Jake guides you step-by-step through the process of achieving HIPAA compliance
Ready to get started? Book a demo with our team
Talk to an expert

HIPAA Requirements for Substance Abuse Treatment Centers: What You Need to Know (Including 42 CFR Part 2)

Kevin Henry

HIPAA

February 08, 2026

7 minutes read
Share this article
HIPAA Requirements for Substance Abuse Treatment Centers: What You Need to Know (Including 42 CFR Part 2)

42 CFR Part 2 Applicability

Substance abuse treatment centers operate under both HIPAA and 42 CFR Part 2. Part 2 protects the confidentiality of records that identify someone as having or having had a substance use disorder or receiving related services. If your organization creates, receives, or maintains these records, you must treat them as “Part 2 records.”

Part 2 generally applies to “programs” that provide substance use disorder diagnosis, treatment, or referral for treatment and are federally assisted. Federally assisted programs include organizations that receive federal funding, participate in Medicare or Medicaid, are tax‑exempt, hold a DEA registration, or are operated by state or local government units. Many hospitals, clinics, and behavioral health providers therefore fall within Part 2’s scope.

In integrated delivery systems, you should assume mixed records. Segment Part 2 information from other protected health information and control access based on role. Data segmentation in EHR systems helps prevent unauthorized viewing and supports compliance with re-disclosure restrictions downstream.

Unlike HIPAA—where many uses for treatment, payment, and health care operations do not require consent—42 CFR Part 2 generally requires prior written patient consent before disclosure. Your patient consent documentation must be specific, understandable, and revocable.

  • Patient’s name and, if desired, other identifiers to ensure accuracy.
  • What information may be disclosed (a specific, limited description).
  • Who may disclose and to whom (a named person, organization, or a clearly described class of recipients).
  • Purpose of the disclosure (for example, treatment coordination, payment, or another stated purpose).
  • Expiration date or event that ends the consent’s validity.
  • Patient’s signature and date (electronic signatures are acceptable when legally valid).
  • Statement of the right to revoke consent in writing and how to do so.
  • Notice that re-disclosure is prohibited unless expressly permitted by law.

Maintain consent logs with versions, revocations, and disclosures made in reliance on each consent. Train staff to verify the scope and expiration of consents before releasing information, and configure EHR prompts to catch mismatches.

Disclosure Exceptions

Part 2 includes limited situations when you can disclose without patient consent. Apply the minimum necessary concept operationally, disclose only what is allowed, and document your decision‑making.

Common exceptions

  • Medical emergency disclosures: Permitted when there is a bona fide medical emergency posing an immediate threat to health or safety and the patient’s consent cannot be obtained in time. Document the emergency, what was disclosed, to whom, and when.
  • Research: Allowed under strict conditions, typically when a HIPAA- or Common Rule–compliant authorization or waiver is in place and researchers agree to Part 2 protections.
  • Audit and evaluation: Disclosures to government agencies, payors, or qualified persons for audit or evaluation of the program are permitted, with safeguards against re-disclosure.
  • Court order: A special Part 2 court order—distinct from a routine subpoena—can authorize disclosure. It requires specific findings and limits on what can be released.
  • Crimes on program premises or against personnel: Limited information may be shared with law enforcement about the incident, the suspect, and the circumstances.
  • Child abuse or neglect reporting: Initial reports to appropriate authorities are allowed; further sharing requires consent or a court order.
  • Qualified Service Organization Agreement (QSOA): You may disclose to a contractor that provides services like data processing, billing, or lab work under a QSOA that binds the contractor to Part 2 confidentiality.
  • Internal communications: Sharing within a program or among entities with direct administrative control is allowed for care and operations, subject to need-to-know limits.

Re-disclosure Prohibitions

Re-disclosure restrictions are a hallmark of Part 2. Any recipient of Part 2 records—whether a provider, payor, researcher, or contractor—is prohibited from re-disclosing those records unless the patient’s consent expressly permits it or another Part 2 exception applies.

Every disclosure should carry the required prohibition-on-re-disclosure notice so downstream recipients understand that the information is specially protected. Use data segmentation in EHR systems and tagging in document management to prevent accidental forwarding, printing, or bulk exports that would violate these restrictions.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

HIPAA and 42 CFR Part 2 Compliance

HIPAA and Part 2 share a privacy mission but differ in approach. HIPAA allows many routine uses and disclosures for treatment, payment, and health care operations without consent. Part 2 is stricter and generally requires consent, backed by re-disclosure prohibitions.

Build a unified compliance program that maps both regimes. Where HIPAA permits but Part 2 restricts, default to Part 2’s stricter standard. Use Business Associate Agreements for HIPAA functions and a Qualified Service Organization Agreement when a vendor touches Part 2 records; some vendors may need both, depending on their role.

Technology and workflow alignment

  • Implement data segmentation in EHR systems (for example, DS4P tagging, role‑based access, and “break‑glass” controls) so only authorized staff can view or share Part 2 data.
  • Adopt standardized patient consent documentation templates and electronic consent capture with audit trails.
  • Configure e-prescribing, HIE, and referral interfaces to filter or mask Part 2 elements unless a valid consent or exception applies.
  • Embed alerts that surface re-disclosure restrictions before users export, print, or transmit records.

Breach Reporting and Penalties

If Part 2 or HIPAA-protected information is impermissibly used or disclosed, activate your incident response plan. Conduct a risk assessment, mitigate harm, and provide breach notifications as required by HIPAA’s Breach Notification Rule and applicable state laws. Keep detailed logs for medical emergency disclosures and any incidents to demonstrate due diligence.

Enforcement can include civil and criminal enforcement. Violations may lead to civil monetary penalties, corrective action plans, reporting obligations, and—in egregious or intentional cases—criminal liability. Regulators and, in some cases, state attorneys general can take action, and contractual breaches with payors or vendors can trigger additional consequences.

Training and Compliance

Make privacy practical through routine training. Teach staff how 42 CFR Part 2 differs from HIPAA, how to recognize Part 2 records, and how to process medical emergency disclosures. Use real scenarios—care coordination, billing edits, external referrals—to reinforce correct choices.

  • Policies and procedures: Write clear, role‑based steps for obtaining, verifying, and documenting consent; responding to subpoenas; and handling emergencies.
  • Access controls and audits: Enforce role‑based permissions, monitor access to Part 2 data, and investigate anomalies promptly.
  • Vendor governance: Execute and maintain each Qualified Service Organization Agreement and any required Business Associate Agreements. Validate vendors’ technical safeguards and training.
  • Ongoing verification: Run periodic privacy walk‑throughs, mock requests, and EHR configuration reviews to ensure re-disclosure restrictions work as intended.

Conclusion

To meet HIPAA requirements for substance abuse treatment centers and honor 42 CFR Part 2, pair precise patient consent documentation with rigorous access controls, data segmentation, and disciplined workflows. When in doubt, follow the stricter rule, document your rationale, and keep your team and vendors aligned through training and oversight.

FAQs.

You need a written, revocable consent that specifies the patient, what information may be disclosed, the purpose, who may disclose and to whom, the expiration date or event, and the patient’s signature and date. Include the required prohibition-on-re-disclosure notice and keep thorough patient consent documentation, including any revocations.

Common exceptions include bona fide medical emergency disclosures, qualified audit and evaluation activities, approved research, child abuse or neglect reports, limited disclosures about crimes on program premises or against staff, internal communications, and disclosures under a valid Part 2 court order. Disclosures to certain vendors are allowed under a Qualified Service Organization Agreement.

How do HIPAA and 42 CFR Part 2 compliance requirements differ?

HIPAA allows many routine uses for treatment, payment, and operations without consent, while Part 2 generally requires patient consent and imposes strict re-disclosure restrictions. Effective compliance blends both frameworks using QSOAs and BAAs, strong role‑based access, and data segmentation in EHR systems.

What are the penalties for breaching 42 CFR Part 2 confidentiality rules?

Consequences can include civil and criminal enforcement, such as monetary penalties, corrective action plans, and, for willful or improper disclosures, potential criminal liability. You may also face contractual consequences, regulatory oversight, and reputational harm, along with HIPAA breach notification duties where applicable.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Related Articles