Start hereDecide which programs and records Part 2 covers
~80 days leftOpen step
Guide library
Regulation North America

42 CFR Part 2 SUD patient-record confidentiality

42 CFR Part 2 compliance: scope, consent, disclosure and breach response

A working guide for treatment programs, health plans, vendors and other record holders that need to protect substance use disorder records and still support care.

Issuing authority
U.S. Department of Health and Human Services, Office for Civil Rights (OCR)
Timing
The 2024 Part 2 Final Rule compliance date was February 16, 2026, so programs should now close any gaps rather than plan a future transition. For breaches of unsecured Part 2 records, notify affected people without unreasonable delay and no later than 60 calendar days after discovery. Report to HHS OCR by 60 days for breaches affecting 500 or more people; for smaller breaches, report by 60 days after the end of the calendar year. As of November 18, 2026, HHS has also announced HIPAA Privacy Rule changes scheduled for Federal Register publication on November 19. That separate rule sets its effective date 60 days after publication and compliance 240 days after publication. Confirm the published dates before setting the HIPAA work plan.
Reviewed
Inside this guide
5 steps · 5 templates

Who it applies to

Part 2 protects records identifying people who receive substance use disorder diagnosis, treatment or referral from a federally assisted Part 2 program. Confirm the program test and the way the record was created or received. Some rules also follow records to qualified service organizations, HIPAA entities, lawful holders and other recipients. A health service is not automatically a Part 2 program just because it treats substance use disorder.

What you’ll produce

An approved applicability decision, record-flow map, consent and legal-request controls, patient notices, vendor terms, breach workflow and a retained evidence file that staff can use during a complaint or OCR review.

A patient may give one consent for future treatment, payment and health care operations disclosures. This is not permission for use against the patient in a legal proceeding, and SUD counseling notes require their own specific consent. Recipients that are not HIPAA entities do not automatically get HIPAA redisclosure rights. HHS also issued narrow September 2026 guidance on when state Medicaid agencies may use SUD records to verify certain exclusions. Check that specific purpose and authority; it is not a general permission to reuse treatment records. The 2026 HIPAA Privacy Rule update is a fresh moving part for organizations that are also HIPAA covered entities; do not treat it as a new Part 2 implementation deadline. In LA Alliance for Human Rights v. County of Los Angeles, a November 2025 federal court order addressing a monitor’s data request included Part 2 records and required findings about need and patient harm, limits on who could receive data, and protections such as sealing. It is a case example, not a reusable permission slip.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

42 CFR Part 2 SUD patient-record confidentiality kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Decide which programs and records Part 2 covers · Privacy officer + Clinical leadership + Compliance + counsel [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Which clinic, service or organizational unit actually meets the Part 2 program test, and what evidence supports that conclusion?
  • Can a staff member tell the difference between a valid TPO consent, a court order for a narrow purpose, a subpoena without the required order, and a request that must be declined?

Worked scenario

Fictional Harbor Ridge Recovery Network is a federally assisted outpatient treatment program. It sends an eligible record to a health plan under a patient’s single TPO consent, but its records team receives a subpoena seeking the same patient file. Privacy pauses the legal-request workflow, routes the document to counsel and checks whether the distinct Part 2 court-order requirements are met before anything is disclosed. Months later, a vendor reports an exposed export involving 512 patients. The team opens the 60-day individual and HHS reporting clocks, checks whether more than 500 are from one state for media notice, and assigns separate senders for the notices.

What to read next

  • HIPAA

    Use the HIPAA guide to map the separate covered-entity, business-associate and security obligations.

DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • February 16, 2026

    Updated Part 2 Final Rule compliance date

    This date has passed. Validate that patient notices, consent workflows, breach response and training meet the current requirements.

    Official reference (opens in a new tab)
  • Without unreasonable delay; no later than 60 calendar days

    Notify affected patients after a breach of unsecured Part 2 records

    Document discovery, unsecured status, population estimate, notice owner and every applicable state or sector clock.

    Official reference (opens in a new tab)
  • At 500 affected people

    Report the breach to HHS within the 60-day limit

    For fewer than 500 people, report no later than 60 days after the end of the calendar year in which the breach was discovered. Report earlier if ready.

    Official reference (opens in a new tab)
  • More than 500 residents of one state or jurisdiction

    Assess the HIPAA media-notice requirement

    Route the geographic count and media decision to Privacy counsel. Keep the separate HHS and patient notice decisions.

    Official reference (opens in a new tab)
  • Within 180 days after learning of the alleged violation

    OCR complaint filing period

    OCR may extend for good cause. Keep a dated complaint intake and legal hold process.

    Official reference (opens in a new tab)
  • As scheduled for November 19, 2026 publication

    Track the separate HIPAA Privacy Rule final dates

    The prepublication HHS filing says effective 60 days after publication and compliance 240 days after publication. Confirm the final publication date and text before setting project deadlines.

    Official reference (opens in a new tab)
The whole journeyabout 80 days across 5 steps
  1. 01Decide which programs and records Part 2 covers, Privacy officer + Clinical leadership + Compliance + counsel, about 10 days
  2. 02Build a consent and disclosure decision path, Privacy operations + Health information management + Legal, about 14 days
  3. 03Update patient notices, forms and frontline instructions, Privacy + Patient experience + Communications + Training, about 21 days
  4. 04Secure vendors, connected systems and breach response, Security + Procurement + Privacy + vendor owner, about 21 days
  5. 05Prepare for complaints, legal requests and OCR review, Compliance + Legal + Privacy officer + executive owner, about 14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 5 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Decide which programs and records Part 2 coversPrivacy officer + Clinical leadership + Compliance + counselStart now; repeat before a new service, merger or data exchangeSet a start datePart 2 applicability and role mapOpen
Build a consent and disclosure decision pathPrivacy operations + Health information management + LegalBefore a data exchange or legal-request responseSet a start dateConsent and disclosure path matrixOpen
Update patient notices, forms and frontline instructionsPrivacy + Patient experience + Communications + TrainingPart 2 notice requirements have applied since February 16, 2026; correct gaps nowSet a start datePatient notice and frontline control rollout packOpen
Secure vendors, connected systems and breach responseSecurity + Procurement + Privacy + vendor ownerBefore granting access; rehearse at least annually and after material changesSet a start datePart 2 recipient, security and breach registerOpen
Prepare for complaints, legal requests and OCR reviewCompliance + Legal + Privacy officer + executive ownerKeep evidence current; act immediately on a complaint, subpoena or breachSet a start dateOCR readiness and court-order review fileOpen
0 of 5 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Decide which programs and records Part 2 covers

    Who Privacy officer + Clinical leadership + Compliance + counsel When Start now; repeat before a new service, merger or data exchange

    For each service line, record who provides SUD diagnosis, treatment or referral, the federal-assistance facts, the record systems and the applicable Part 2 program analysis. Map who creates, maintains, receives and can access identifiable records. Separate Part 2 status from HIPAA covered-entity and business-associate status. Mark uncertain cases for counsel rather than applying the label to an entire hospital or vendor by assumption.

    What to produce

    Part 2 applicability and role mapScope decision memo and data-flow register

    Gather first

    • Service-line inventory
    • Federal assistance facts
    • Program activities
    • Record systems
    • Recipient and vendor list
    • Current 42 CFR §§2.11–2.12

    How to prepare it

    1. Create a row for each program or business unit. Describe whether it provides SUD diagnosis, treatment or referral, who operates it, where the work occurs and what federal assistance may apply. Link evidence such as grant terms, Medicare or Medicaid participation, federal registration or a government contract.
    2. Map how an identifiable SUD record is created, maintained, disclosed, received and retained. Identify record systems, paper files, portals, backups, HIE connections, health plans, QSOs and other downstream holders. Record the business owner and technical custodian for each system.
    3. Assess Part 2 status separately from HIPAA covered-entity or business-associate status. Explain which organization is a Part 2 program and why, which systems contain its records, and which rules apply to recipients. Send uncertain scope questions to counsel with supporting facts instead of assuming every SUD service is covered.
    4. Approve the scope, set an annual review date and reopen the analysis after a federal-assistance change, acquisition, new service, new record flow or change in the way care is delivered.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional program
    Harbor Ridge Recovery Network, fictional outpatient program. Compliance records that it receives federal assistance and provides SUD treatment and referral. The legal owner attaches the current evidence and signs the applicability decision.
    Fictional system
    HBR-Clinical stores treatment notes and referral status. HBR-Billing sends a limited claims file to a health plan. The data-flow diagram lists user roles and the vendor that hosts each system.
    Separate HIPAA analysis
    The clinical entity is also a HIPAA covered provider. The billing vendor is a business associate for the HIPAA work it performs. Compliance records this separately from the Part 2 program and QSO analyses.
    Open question
    An affiliated peer-support service makes referrals but uses a separate entity, funding and record system. Counsel reviews those facts before the organization applies Part 2 controls to it.

    Check before handing it over

    A new manager can identify which service and systems are in scope, why the decision was made, who owns the records and which assumptions need counsel’s review.

    Give the approved scope map to HIM, Security, Procurement and the privacy notice owner. Update it before any new disclosure integration goes live.

  2. 02

    Build a consent and disclosure decision path

    Who Privacy operations + Health information management + Legal When Before a data exchange or legal-request response

    For each use, identify the actor, recipient, purpose, record type and legal authority. Use the current consent elements for the intended disclosure. Distinguish a single TPO consent from consent for a civil, criminal, administrative or legislative proceeding. Identify SUD counseling notes separately because a broad TPO consent does not authorize their disclosure. For court orders, subpoenas, medical emergencies, audits and evaluation, route to the applicable Part 2 provision and preserve the required findings and limits. Do not rely on a subpoena alone where Part 2 requires a qualifying order and process.

    What to produce

    Consent and disclosure path matrixDecision matrix and consent evidence index

    Gather first

    • Part 2 program and record map
    • Current patient consent
    • Recipient role
    • Requested purpose
    • 42 CFR §§2.31–2.33 and applicable exception or court-order section

    How to prepare it

    1. Use one row for each disclosure route. Capture who is disclosing, who will receive the record, the specific purpose, record type, authority, date, expiration or revocation handling and required accompanying statement.
    2. Check consent elements against the current regulation. Distinguish single consent for treatment, payment and health care operations from a consent for use or disclosure in a civil, criminal, administrative or legislative proceeding. Record SUD counseling notes separately and require their specific consent where applicable.
    3. For each recipient, record whether the recipient is subject to HIPAA, is a qualified service organization, is a lawful holder or has another Part 2 role. State what redisclosure is allowed and what warning must accompany the disclosure. Do not automatically give a non-HIPAA recipient the HIPAA recipient’s redisclosure permissions.
    4. Send subpoenas, warrants, court orders, audits, emergencies and law-enforcement requests to the correct legal review path. Record which exact section is being considered, the findings or safeguards required, and who approved disclosure or refusal.
    5. Test consent entry, identity matching, revocation and downstream release in a non-production environment. Keep the request, consent version, reviewer and audit event linked without placing actual patient records in this workbook.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional TPO path
    Harbor Ridge patient HBR-P-042 signs the approved single TPO consent for future disclosures to the named health plan. The reviewer records the form version, scope and date, then confirms the receiving HIPAA entity and its access role.
    Fictional subpoena
    A records desk receives a subpoena seeking HBR-P-042’s SUD treatment notes. Staff do not send or confirm a patient relationship. They preserve the request, open case LEG-026 and route it to counsel for the applicable Part 2 order and process review.
    Fictional counseling note
    An SUD clinician separately maintains session-analysis notes. The disclosure checker flags that ordinary TPO consent is not the required authority for these notes.
    Fictional recipient warning
    For a permitted release, HIM records the required Part 2 notice accompanying the disclosure and the released page range. The recipient receives only the approved records and scope.

    Check before handing it over

    A reviewer can follow each disclosure from purpose to authority, consent, recipient permissions and audit trail, and can see which requests must stop for counsel.

    Give HIM the signed decision path and test cases. Give counsel the queue of requests waiting for a legal determination.

  3. 03

    Update patient notices, forms and frontline instructions

    Who Privacy + Patient experience + Communications + Training When Part 2 notice requirements have applied since February 16, 2026; correct gaps now

    Compare the program’s notice with the HHS Part 2 Patient Notice model. If the program is also a HIPAA covered entity, compare the combined notice with the current HIPAA NPP model. Fill in the organization’s actual uses, contacts, rights and complaint route. Give the notice to patients and make it available as required. Train intake, HIM, billing, clinicians and call-center staff on identity, consents, redisclosure statements, revocations and escalation. Separately schedule the HIPAA-only changes in HHS’s 2026 final rule using the actual Federal Register publication and compliance dates.

    What to produce

    Patient notice and frontline control rollout packNotice crosswalk, approved draft and training checklist

    Gather first

    • Current Part 2 Patient Notice
    • HIPAA NPP if applicable
    • HHS model notices
    • Service contacts and complaint route
    • Intake, HIM and support workflows

    How to prepare it

    1. Select the HHS model that fits the organization. Determine whether the Part 2 program also needs a HIPAA NPP or can issue a combined notice. Record the legal entities and service lines covered by each notice.
    2. Complete a requirement crosswalk for Part 2 confidentiality, permitted uses and disclosures, patients’ rights and how to raise a concern. Replace every generic model placeholder with a real contact, office, process and delivery channel.
    3. Have Privacy compare each statement with the current data flows and consent forms. Have Legal check exceptions and rights language. Ask a patient-experience reviewer to test whether a person can find the privacy contact and understand how their records may be shared.
    4. Publish and distribute the approved notice in the ways required. Record version, approval, publication location, distribution date, languages and how the program will provide it to someone who asks.
    5. Train intake, clinical staff, HIM, billing, support and vendors with role-specific scenarios. Test requests, consent questions, legal demands, revocation, complaint intake and escalation. Keep attendance and the version of materials taught.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional notice contact
    Harbor Ridge replaces the model contact with Privacy Office, 555-0108, [email protected] and the patient portal help path. These fictional details must be replaced before use.
    Crosswalk question
    Does the notice say the same thing as the actual health-plan data flow? Privacy checks the consent, recipient and disclosure statement before approval.
    Fictional frontline test
    A caller asks whether a family member attended treatment. Reception does not confirm or deny participation, explains the privacy contact route and records the escalation without entering diagnosis details in an open CRM.
    Change control
    Version P2-NPP-04 approved by Legal and Privacy on the fictional date 3 June 2026. The prior copy remains in the version history; the website owner records the new public URL and screenshot.

    Check before handing it over

    Patients can find a current notice and a working contact route; staff can apply the same approved message without confirming treatment participation to an unauthorized caller.

    Give the notice to the website owner, intake lead and all covered program managers. Schedule a review after a service or legal change.

  4. 04

    Secure vendors, connected systems and breach response

    Who Security + Procurement + Privacy + vendor owner When Before granting access; rehearse at least annually and after material changes

    Inventory qualified service organizations and other recipients, the records each can reach, locations, subcontractors and onward disclosures. Check written agreements, access approvals, staff training, audit trails, incident escalation and return or destruction at exit. The 2024 rule does not require organizations to segregate every Part 2 record, but teams still need controls that can identify records, consent status and redisclosure restrictions where staff need them. Rehearse discovery time, unsecured-record assessment, patient notice, HHS reporting, media thresholds, supplemental reports and evidence preservation.

    What to produce

    Part 2 recipient, security and breach registerRestricted third-party, access and incident register

    Gather first

    • Record-flow map
    • QSO and other contracts
    • Access-control export
    • Security incidents
    • 42 CFR §2.16
    • HHS breach reporting workflow

    How to prepare it

    1. List each vendor or recipient, what records it can access, its purpose, user population, hosting location, subcontractors, agreement, incident contact and end-of-service return or destruction process.
    2. Record who approved each account and role, the evidence used, the date granted, last review, revocation date and relevant audit-log location. Keep a separate privileged record for actual patient data and do not paste names, records or diagnosis into this tracker.
    3. For an incident, log discovery time, affected systems, whether records are unsecured, estimated people and states, containment, investigation owner and the next review time. Keep unknowns open and use estimates when a timely HHS submission is required.
    4. At 500 or more affected individuals, assign the HHS OCR report and the 60-calendar-day outside date. Below 500, assign the report due within 60 days after the end of the calendar year of discovery. Track individual notice without unreasonable delay and no later than 60 days; check the more-than-500-per-state media trigger and stricter state or contract duties.
    5. Retain each submitted notice, portal transaction number, affected population calculation, addendum, individual notice version, media decision, vendor handoff and corrective action. Close only after counts and delivery evidence reconcile.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional incident
    Training only. A vendor alert on 7 September 2026 reports a public export containing 512 fictional patient records. The incident lead preserves the vendor notice and starts parallel individual, OCR, state and media threshold checks.
    Threshold calculation
    Fictional count: 512 people overall, 508 from State A and 4 from State B. OCR’s 500-person reporting threshold is reached. The State A count also prompts a separate media-notice review under the applicable HIPAA standard.
    OCR transaction
    Leave blank until an actual report. The workflow stores the portal transaction number and authorized filer in the restricted incident record, then links later addenda to the original transaction.
    Vendor action
    Owner: Privacy vendor manager. Evidence: signed QSO terms, current access list, incident statement, preservation request and a dated confirmation that the public export was removed.

    Check before handing it over

    The incident commander can see the correct thresholds and owners without handling patient-level data in the tracker, and a reviewer can reproduce the notice decisions.

    Assign the report and notice owners at incident opening. Reconcile vendor facts against the program’s own affected-population query.

  5. 05

    Prepare for complaints, legal requests and OCR review

    Who Compliance + Legal + Privacy officer + executive owner When Keep evidence current; act immediately on a complaint, subpoena or breach

    Maintain versioned policies, training evidence, consent forms, request decisions, access logs, vendor terms, notice versions, breach reports and corrective actions. Route court orders to counsel before disclosure and limit any permitted release to the authorized material and recipients. Anyone can file a Part 2 complaint with OCR within 180 days after learning of the alleged act or omission; OCR may extend that period for good cause. Since February 16, 2026 OCR may conduct compliance reviews and investigate complaints, and civil penalties are available under the HIPAA Enforcement Rule framework. Assign an evidence owner and a response lead before an OCR inquiry arrives.

    What to produce

    OCR readiness and court-order review fileEvidence index and legal request review memo

    Gather first

    • Approved policies
    • Training evidence
    • Consent and disclosure samples
    • Access audit trails
    • Incident notices
    • Court request
    • Current Part 2 and OCR instructions

    How to prepare it

    1. Build a dated index of policies, notice versions, training, contracts, consent controls, access reviews, complaint handling and incidents. For each item, name a custodian, source system, date range, approval and retention location.
    2. On a complaint or OCR request, preserve relevant evidence. Log the request, assigned response lead, legal hold, due date, data minimization review, response owner and approvals. Do not send patient records through ordinary email or an unapproved shared folder.
    3. For any subpoena or court order, record the issuing tribunal, requesting party, proceeding, patient notice and opportunity-to-be-heard status where required, the exact Part 2 provision counsel is applying, and whether another route could obtain the information. Pause disclosure until the authorized reviewer approves the exact scope.
    4. If a court order permits use or disclosure, map the exact records and persons to the order, enforce purpose limits, preserve required protections and confirm the receiving party understands handling restrictions. Capture the return, destruction or sealing step where directed.
    5. Use actual court examples to train reviewers, not as substitutes for a current order. In LA Alliance for Human Rights v. County of Los Angeles, the November 10, 2025 order discussed Part 2 findings and restricted use to essential records and persons whose need supported the order. Record this only as an example of case-specific safeguards.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional OCR request
    Case OCR-2026-014. Response lead: Privacy officer. Counsel verifies authority and due date. HIM preserves the consent version and disclosure audit, Security preserves the access log, and the response index uses coded evidence references.
    Fictional subpoena hold
    Request LEG-026 seeks an entire record. Status: no disclosure. Counsel is checking the exact order and Part 2 route. HIM keeps the requested record on a narrow hold and does not confirm whether the named person is a patient.
    Court-order scope check
    Order reference: fictional CO-2026-004. Only specified dates and record fields may be used by the named monitor for the stated case purpose. Legal confirms permitted recipients, sealing and onward-use limits before release.
    Corrective action
    Finding: one intake employee used an old consent version. Owner: HIM director. Fix: disable retired form and add a quarterly form-version test. Evidence: updated form library, completed test and training record.

    Check before handing it over

    A response team can show who had the record, why a disclosure was allowed, what a court order actually covered and which changes were made after a finding.

    Counsel approves any legal response. The privacy officer maintains the evidence index and tracks every corrective action to retest.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes