ICD code T39.94XD – Poisoning by unspecified nonopioid analgesic, undetermined, subsequent encounter

Key takeaways

T39.94XD reports a poisoning by an unidentified nonopioid analgesic, antipyretic or antirheumatic, with undetermined intent, at a subsequent encounter.

Use undetermined intent only when the record states that intent cannot be determined. Unknown or unstated intent is coded as accidental (T39.91-).

Sequence T39.94XD first, then a code for each documented manifestation. No separate external cause code is needed, because intent is built into the code.

Once the drug or the intent is documented, switch to the specific code, such as T39.1X4D for acetaminophen or T39.92XD for self-harm.

Pabau, our practice management platform, validates claims for missing or invalid details before submission, so errors surface before the payer sees them.

ICD-10 Code T39.94XD: Quick reference

ICD-10 Code T39.94XD is a billable code for the follow-up care of a poisoning by a nonopioid pain reliever that no record identifies.

The intent behind the poisoning is also on record as undetermined. For medical billing teams, each character of the code carries one of those facts.

What T39.94XD covers: An unidentified drug and an unknown intent

T39.94XD sits at the least specific corner of the T39 category on two axes at once. The drug is a nonopioid analgesic, antipyretic or antirheumatic, but the record does not name it. The intent is documented as undetermined. Three questions about the chart, answered in order, show whether a follow-up visit lands there.

That makes it a narrow code. A coder should reach it only after confirming that the chart names neither a specific drug nor a clear intent. Whenever the record names the drug, the ICD-10-CM Table of Drugs and Chemicals routes it to a more specific subcategory.

Check the drug in the Table of Drugs and Chemicals before you settle on T39.9. A toxicology result or a pharmacy record often names the agent after the first visit. When it does, the follow-up encounter takes the specific code, not T39.94XD.

When intent is undetermined, and when it is not

The ICD-10-CM Official Guidelines, Section I.C.19.e, set a default for poisoning codes. If the intent is unknown or unspecified, you code it as accidental. Undetermined intent is only for records where the documentation specifies that intent cannot be determined.

In practice, the difference is one sentence in the chart. “Intent unclear” from a busy emergency note does not support the code on its own. A statement such as “unable to establish whether the ingestion was accidental or intentional” does.

• Silent or unstated intent: Code accidental, T39.91XD.
• Clinician states intent cannot be determined: Code undetermined, T39.94XD.
• Clinician documents a deliberate overdose: Code intentional self-harm, T39.92XD.
• Another person gave the drug to cause harm: Code assault, T39.93XD.

T39.94XD vs the other T39.9 codes

The 5th character of a T39.9 code is the intent axis. Picking the wrong one turns a poisoning into an adverse effect, or the other way round, and payers read the two very differently.

A poisoning involves a wrong substance, a wrong dose, a wrong route or a drug taken by the wrong person. An adverse effect is a reaction to a drug used as prescribed. If the chart describes a correctly taken prescription, T39.95XD applies, and no T39.94- code fits.

What the 7th character D means for T39.94XD

Per the CMS ICD-10-CM Official Guidelines, the 7th character D applies once active treatment has ended. The patient is now receiving routine care during the healing or recovery phase.

The test is the phase of care, not whether symptoms persist. A patient can still feel unwell at a D visit, and a second provider can still be giving active treatment at an A visit. Do not swap in an aftercare Z code either. For injuries and poisonings, the guidelines use the 7th character D in place of aftercare codes.

Sequencing T39.94XD with manifestation codes

For a poisoning, Section I.C.19.e of the guidelines sets the order. The T39.94XD code goes first, followed by a code for each manifestation the provider documents at this visit.

• Poisoning code first: T39.94XD heads the claim when the visit is for follow-up of the poisoning.
• Manifestations next: Add a code for each documented condition still being monitored, such as R74.01 for elevated liver transaminase levels.
• No Chapter 20 code: An external cause code is not needed, because T39.94XD already states the intent.
• Related conditions: If the provider documents drug abuse or dependence, add the matching F code as well.

Code only what this visit addresses. A manifestation that resolved before the follow-up does not belong on the D claim.

Documentation requirements to support T39.94XD

An auditor reviewing T39.94XD looks for evidence behind each of its characters. Medical billing compliance reviews often flag poisoning codes where the chart supports only part of the code.

• Poisoning, not adverse effect: The note describes an overdose, a wrong drug or a drug taken without a prescription, not a reaction to correct use.
• Drug class without a named agent: The record identifies a nonopioid analgesic or antipyretic, and no source names the specific drug.
• Explicit undetermined intent: The provider states that intent cannot be determined, rather than leaving it blank.
• Subsequent encounter status: The chart shows that active treatment took place earlier and has ended.
• Current manifestations: Each condition coded alongside T39.94XD is documented and addressed at this visit.

If any element is missing, query the provider before the claim goes out. Getting the chart right first is what makes a clean claim possible.

Common denial reasons for T39.94XD and how to prevent them

T39.94XD denials and audit findings cluster around five predictable errors. Sound denial management in healthcare starts with catching them before submission.

When a denial arrives, read the denial codes on the remittance. They show whether the payer objected to the code, the documentation or the coverage policy.

Coding T39.94XD in practice: A worked example

A patient was brought to the emergency department after taking an unknown number of tablets from an unlabeled bottle of over-the-counter pain reliever. The toxicology screen did not identify the agent. The emergency physician documented that intent could not be determined. Twelve days later, the patient sees their primary care provider for repeat liver function tests.

1. Confirm poisoning: The patient took an unknown quantity without medical direction, so this is a poisoning rather than an adverse effect.
2. Confirm the drug class: The record identifies a nonopioid pain reliever, but no source names it. Subcategory T39.9 applies.
3. Confirm the intent: The follow-up note restates that intent cannot be determined. The 5th character is 4.
4. Confirm the encounter: Active treatment ended in the emergency department, and this is a recovery follow-up. The code is T39.94XD.
5. Add the manifestation: Transaminases remain mildly elevated and are being monitored. Add R74.01 after T39.94XD.
6. Recheck at each visit: If a later note names acetaminophen, the next visit takes T39.1X4D instead.

Track the claim through your revenue cycle management workflow so any code edit surfaces before the payer processes it.

How Pabau keeps T39.94XD claims clean from chart to payer

An unsupported intent character or a missing manifestation code tends to surface as a denial weeks after the visit. By then the fix means chasing the provider for an addendum, so the chart checks above belong before the claim is built.

Pabau’s claims management software adds a second check at billing. Its claim validation scrubs claims for missing or invalid details before they leave Pabau, so errors surface before submission.

Claims go to US payers through Claim.MD, Pabau’s US clearinghouse partner, as electronic CMS-1500 claims. Electronic remittance advice comes back into Pabau and is matched to the claims it settles.

Catch claim errors before T39.94XD claims go out

Pabau’s claim validation scrubs claims for missing or invalid details before submission. Validated claims then go to US payers through Claim.MD.

Book a demo

Conclusion

T39.94XD holds up on audit only when the chart supports both of its vague characters. The provider has to state that intent cannot be determined, and no record can name the drug. If either one fails, a more specific T39 code is the honest choice.

Recheck both axes at every follow-up, because toxicology results and patient disclosures arrive after the emergency visit. Then list T39.94XD ahead of each documented manifestation, so the claim answers each denial reason in the table above.

Book a demo to see how Pabau’s claim validation catches missing or invalid claim details before they reach the payer.

Continue your research

Coding another poisoning with undetermined intent? ICD-10 code T44.1X4A walks through the documentation an undetermined-intent claim needs.

Need another subsequent-encounter poisoning example? ICD-10 Code T44.902D shows how the D character works on a follow-up poisoning visit.

Want to know how clearinghouse edits catch coding errors? Medical claims clearinghouse guide explains the validation layers between your practice and the payer.

Building a clean-claim checklist for your billing team? Superbill documentation guide covers what every claim needs before submission.

Frequently asked questions