Part 2 substance-use-disorder definition

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.11 defines substance use disorder as a cluster of cognitive, behavioral, and physiological symptoms indicating continued use despite significant substance-related problems such as impaired control, social impairment, risky use, and pharmacological tolerance and withdrawal. For Part 2, tobacco and caffeine use are expressly excluded. The definition supports regulatory scope; it is not a substitute for individual clinical diagnosis.

Use the definition for regulatory classification

Current 42 CFR 2.11 supplies the symptom-cluster language and exclusions. Record the source information, purpose, program, clinical authorship, substance, treatment or referral connection, patient-identifying content, date, and privacy classification. Avoid diagnosing from an administrative flag.

Respect the explicit exclusions

For this Part 2 term, tobacco and caffeine use fall outside the definition. That exclusion does not erase other health-record, professional, payer, public-health, state, consent, or confidentiality duties that may apply to related information.

Separate scope from clinical judgment

The HHS Part 2 fact sheet explains the current federal privacy framework. A privacy team may classify records and systems; only an appropriately qualified clinician acting within scope diagnoses, recommends care, and interprets symptoms for the person.

Use the term for regulatory classification

Identify the substance-related information, source, author, patient, program, purpose, service, date, and downstream use. Determine whether the record refers to the defined symptom cluster or a condition linked to it and whether it was created in a Part 2-relevant context. Preserve the reasoning and reviewer.

An administrative SUD flag, claim code, screening result, medication, self-report, or single symptom does not by itself establish an individual diagnosis or every Part 2 condition.

Respect the stated scope and exclusions

Document the substance involved and keep tobacco and caffeine information outside this particular Part 2 definition. Do not assume those records are unprotected: HIPAA, state confidentiality, public-health, professional, payer, consumer, and other rules may still apply. Analyze polysubstance records carefully when excluded and included substances appear together.

Avoid deleting or hiding clinically relevant tobacco or caffeine information merely because the Part 2 term excludes it.

Separate clinical judgment from privacy scope

Appropriately qualified clinicians evaluate symptoms, duration, severity, differential diagnosis, remission, withdrawal, treatment, and safety within professional standards. Privacy and compliance teams classify programs, records, uses, and disclosures under applicable law. Software may organize evidence but should not infer a diagnosis from isolated data.

Route uncertain clinical meaning and coding corrections to the appropriate clinician, then update affected data and privacy workflows without erasing history.

Trace the record footprint

Map diagnosis and screening fields, referrals, problem lists, medications, notes, claims, alerts, summaries, counseling content, exports, analytics, and derived models. Record lineage, patient-identifying context, access, recipients, retention, and transformation. A category can reveal SUD meaning without using the term itself.

Keep Part 2 program, patient, diagnosis, treatment, referral, and record coverage analyses distinct. One definition does not answer them all.

Apply and audit controls

Once the classification is supported, identify consent or other disclosure authority, recipient, purpose, minimum information, notice, proceedings restriction, security, and state law. The HHS fact sheet supplies broader context, not individual diagnosis guidance.

Audit structured and free-text records, mixed-substance data, exclusions, clinical corrections, model flags, releases, and overrides. Review both overclassification and missed SUD references.

When communicating the classification to staff or patients, use language that distinguishes a regulatory data-scope decision from a clinical statement about the person. Limit access to the underlying clinical evidence and avoid surfacing stigmatizing labels in general administrative views. Preserve who made each clinical and privacy decision, their source, and effective date. If a code or model changes, sample prior and new records for drift instead of assuming the new mapping improves accuracy across every substance and service.

Example

Seventeen data elements tagged 'SUD' are reviewed. Fourteen preserve substance, source, purpose, program, clinical author, patient-identifying content, Part 2 decision, and reviewer; three are tobacco screening fields. Classification accuracy is 14 of 17 elements.

SUD-definition checklist

• identify the substance, symptom-cluster information, source, purpose, and program context;
• apply the tobacco and caffeine exclusions without discarding other protections;
• keep regulatory scope separate from qualified individual clinical diagnosis;
• trace fields, notes, claims, medications, referrals, exports, and derived signals;
• analyze program, patient, record, treatment, and disclosure questions separately; and
• audit mixed records, corrections, overrides, false positives, and missed references.

The Part 2 term is a precise regulatory definition. It should guide scope without turning an administrative classification into a clinical conclusion.