Part 2 overdose-without-SUD diagnosis exception

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Current rule checkpoint

The live exception in 42 CFR 2.12(e)(4)(ii) excludes a diagnosis of drug overdose or alcohol intoxication from the diagnosis-coverage explanation when it clearly shows that the person does not have an SUD. The rule gives involuntary ingestion and reaction to a prescribed dosage as examples. eCFR displays the section as current through August 20, 2026 and last amended August 13, 2026. The HHS fact sheet confirms the February 16, 2026 compliance date for the 2024 amendments.

The record must clearly show the conclusion

Current 42 CFR 2.12 describes a diagnosis of overdose or alcohol intoxication that clearly shows the person does not have an SUD. Preserve the clinician, evaluation, clinical facts, conclusion, date, purpose, program status, source, and record.

Examples do not create a broad category

Involuntary ingestion and prescribed-dose reaction illustrate the rule. Accidental overdose, adverse medication event, poisoning, intoxication, withdrawal, screening result, provisional diagnosis, and later SUD diagnosis can involve different facts and clinical judgments.

Qualified clinicians decide the diagnosis

Administrative staff and software may surface missing fields or conflicts. They should not infer that a person lacks an SUD, change the clinical record, or release information solely from a code. Route clinical meaning and privacy classification to qualified roles.

Require a clear clinical conclusion

Identify the qualified clinician, encounter, evaluation, history, examination, toxicology or other evidence, diagnosis, no-SUD conclusion, rationale, purpose, date, program status, record, and later findings. An overdose code, intoxication label, naloxone use, toxicology result, emergency transport, or accidental-event field does not itself state that the person has no SUD.

Use the clinician's actual conclusion. Administrative staff, billing rules, and automated classifiers may surface missing or conflicting documentation, but they should not infer absence of an SUD or alter the record.

Treat the examples as examples

Involuntary ingestion and reaction to a prescribed dosage illustrate the rule. Accidental overdose, dosing error, poisoning, adverse event, intoxication, withdrawal, misuse, provisional diagnosis, and later SUD diagnosis require their own clinical facts. Do not extend the exception by keyword.

When evidence is incomplete or conflicting, mark the privacy classification unresolved and use a protective interim workflow. Ask the clinician to clarify through the ordinary correction or amendment process without scripting a desired legal conclusion.

Preserve change over time

Keep the original clinical record, authorship, data, source, date, classification, later assessment, correction, and downstream notifications. A later SUD diagnosis does not automatically rewrite what the earlier overdose diagnosis clearly showed, and the earlier conclusion does not settle later records.

Test emergency, inpatient, outpatient, payer, legal, patient-access, research, analytics, exchange, and migration workflows. Prevent one encounter-level result from becoming an unsupported patient-wide flag.

Example

Ten overdose records are reviewed. Seven contain a qualified clinical conclusion, supporting facts, purpose, program status, and record provenance; three contain only an encounter code. Classification completeness is 7 of 10 records.

Record a limited, encounter-specific outcome

Classify the diagnosis as clearly showing no SUD under the exception, not meeting the exception, or unresolved. State the clinician, evidence, conclusion, patient, encounter, purpose, program, date, reviewer, and affected record. Keep the outcome limited to the supported encounter and information.

For unresolved records, prevent an automated release or patient-wide flag while qualified clinicians clarify the documentation. Preserve the original entry and do not prompt for a predetermined conclusion. If a later assessment differs, record both time-specific results and their sources.

Test the outcome in treatment, payer, patient-access, legal, research, analytics, and exchange workflows. Confirm that billing or diagnosis codes do not override the narrative conclusion and that unrelated SUD records remain separately classified.

When a classification error affected a prior disclosure or decision, preserve evidence, notify privacy and clinical owners, correct downstream systems and recipients as appropriate, and document follow-up.

Overdose-without-SUD checklist

• retain the clinician, evaluation, evidence, diagnosis, conclusion, purpose, and date;
• require the record to clearly show that the person does not have an SUD;
• avoid inference from codes, toxicology, naloxone, labels, or automation alone;
• treat involuntary ingestion and prescribed-dose reaction as examples, not a full list;
• preserve later findings and corrections without overwriting historical evidence; and
• keep the classification limited to the supported encounter and record.

This exception does not determine diagnosis, treatment, safety response, coding, or future SUD status. Qualified clinicians decide clinical meaning; privacy and legal owners apply current Part 2, state law, record facts, and the proposed use.