Part 2 diagnosis 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 diagnosis as any reference to an individual's substance use disorder, or to a condition identified as caused by that disorder, when the reference is made for treatment or referral for treatment. Both the content and the purpose matter. The definition is broader than a formal diagnostic code and narrower than every mention of substance use.

Apply both parts of the definition

Current 42 CFR 2.11 links the reference to SUD content and a treatment or referral purpose. Record who created it, what it says, why it was created, source program, date, audience, system, and relationship to treatment. Avoid deciding from a field label alone.

Classify derived and copied information

Trace problem lists, claims, orders, intake answers, referrals, summaries, alerts, exports, copied notes, and analytics fields back to their source and purpose. A later transformation can preserve identifying SUD meaning even when the original wording disappears.

Keep clinical and privacy decisions separate

The HHS Part 2 fact sheet explains the current privacy framework. A privacy classification does not diagnose a patient or authorize treatment. Qualified clinicians decide diagnosis within scope; privacy owners decide how the resulting record is handled.

Identify the reference

Inventory structured diagnoses, problem lists, symptoms, conditions attributed to SUD, referral text, assessments, orders, medication indications, claims, alerts, summaries, conversations, and derived flags. Record the exact content, author or source, patient, date, system, audience, and whether the reference identifies the person directly or through context.

Do not classify solely from an ICD code, field name, note type, medication, or vendor label. Read the substance and surrounding facts.

Establish the treatment or referral purpose

Document why the reference was created and used. Determine whether it supports treatment or referral for treatment, who intended that purpose, and how the record entered the program. Distinguish clinical and referral purposes from unrelated public health, research, employment, law-enforcement, educational, or administrative contexts, while analyzing other Part 2 definitions and rules separately.

Purpose can change across copies and workflows. Preserve the original context and evaluate the later use rather than assuming the first label controls forever.

Trace derived and transformed data

Map source fields through coding, billing, interfaces, summaries, dashboards, risk models, alerts, exports, de-identification, and vendor systems. A derived category can still reference SUD or an SUD-caused condition even when the original words disappear. Conversely, a broad administrative flag may lack enough content and purpose evidence for the diagnosis definition.

Keep lineage, transformation logic, data owners, access, recipients, and retention with the classification. Review model outputs and free text for indirect references.

Separate privacy from clinical diagnosis

This regulatory classification does not decide whether the patient clinically meets diagnostic criteria, what severity or remission status applies, or which treatment is appropriate. Qualified clinicians make those decisions within professional scope and document corrections. Privacy and compliance roles determine how records and disclosures are governed.

When clinical content is disputed or corrected, preserve versions and update downstream privacy classifications and recipients as appropriate without rewriting history.

Apply the result operationally

Link the diagnosis classification to Part 2 program and patient status, consent or disclosure pathway, access, notices, recipient, purpose, security, and audit evidence. Avoid making the definition itself a disclosure permission. The HHS fact sheet supplies broader rule context but does not replace case-specific analysis.

Audit structured and unstructured records, copied data, derived fields, corrections, exports, and classification overrides. Review false positives and false negatives because both can harm privacy, care, and data integrity.

Example

Sixteen data fields are reviewed. Thirteen have documented content, purpose, source, Part 2 status, downstream uses, and owner; three rely only on an ICD label. Classification evidence is complete for 13 of 16 fields.

Diagnosis-definition checklist

• identify the exact SUD or SUD-caused-condition reference and its patient context;
• document the treatment or referral-for-treatment purpose;
• trace copied, coded, derived, summarized, and model-generated information;
• keep privacy classification separate from an individual clinical diagnosis;
• connect the result to the applicable Part 2 controls and disclosure route; and
• audit free text, fields, corrections, overrides, false positives, and missed references.

The definition turns on what the reference conveys and why it was made. Neither a code nor a clinical-sounding label answers both questions alone.