ICD code T63.442D – Bee venom toxicity, intentional self-harm

Key takeaways

T63.442D codes the toxic effect of bee venom from intentional self-harm at a subsequent encounter, after active treatment is complete.

The seventh character D separates routine follow-up care from T63.442A (initial encounter) and T63.442S (sequela). A wrong seventh character is a common denial trigger.

Self-harm intent needs provider attestation in the record, and many payers also expect a supporting psychiatric diagnosis code.

Practice management software like Pabau submits claims electronically, checks eligibility in real time, and tracks each claim through to the remittance.

ICD-10 Code T63.442D: definition and code details at a glance

ICD-10 Code T63.442D is a valid, billable ICD-10-CM code for FY2026, confirmed in the CDC/NCHS official ICD-10-CM web tool. Its full official descriptor is Toxic effect of venom of bees, intentional self-harm, subsequent encounter. Read it as three stacked qualifiers. They are the toxic agent (bee venom), the intent (intentional self-harm), and the encounter type (subsequent).

The CMS ICD-10 coding page publishes the annual update files confirming each code’s active status. Check that file for the date of service before you submit a claim.

Breaking down the T63.442D code structure

Each character segment of T63.442D carries a distinct meaning. Reading the code left to right reveals the complete clinical picture a coder must confirm before assignment.

T63.44 covers bees only, inside the T63.4 group for venom of other arthropods. Wasp stings, ant stings, and scorpion envenomation each have their own codes, so none of them belongs under T63.44. The AAPC ICD-10-CM lookup tool displays the full subcategory tree for verification.

Understanding the seventh character D: subsequent encounter

The seventh character D means the patient is receiving routine care while the toxic effect is healing or recovering, distinct from the initial acute encounter. The ICD-10-CM Official Guidelines, Section I.C.19, apply “subsequent encounter” once active treatment of the injury is complete. From then on, the patient is receiving follow-up care such as wound checks, medication adjustments, or monitoring of residual effects.

Coders sometimes assign T63.442A across several visits because the patient is still symptomatic. Symptoms alone do not make an encounter “initial.” Once active treatment is complete, each later visit for routine care takes the seventh character D, even if symptoms persist.

Coding the intentional self-harm component

The intent digit 2 in T63.442D classifies the exposure as intentional self-harm. The patient deliberately exposed themselves to bee venom with the intent to cause harm. That separates it from accidental envenomation (T63.441D) and from exposure with undetermined intent. The classification carries legal, psychiatric, and reporting implications, so the documentation has to be unambiguous.

The self-harm code captures the toxic mechanism, but it rarely stands alone on the claim. When a psychiatric condition drives the self-harm behavior and the provider documents it, that condition gets its own code as well.

Additional codes commonly needed alongside T63.442D

• Mental health diagnosis codes (such as F32.x depressive or F43.2x adjustment disorders): many payers expect a psychiatric diagnosis code alongside a self-harm code. That is a payer convention, not an ICD-10-CM mandate, so check the payer’s LCD or coverage policy first.
• Personal history Z-codes: Z91.5 is a non-billable category, so pick a billable code by intent. Use Z91.51 for a personal history of suicidal behavior, or Z91.52 for a personal history of nonsuicidal self-harm.
• Mandatory reporting obligations: state laws on self-harm reporting vary widely. Confirm the applicable state statute with your compliance team before coding, rather than assuming an obligation.

Clinically related codes and how to choose between them

The T63.44 subcategory holds parallel codes built from intent and encounter type. Two questions, answered in order from the provider’s note, lead to the right one.

On anaphylaxis: anaphylactic shock is coded separately, typically as T78.2xxA (or the appropriate seventh-character variant). Anaphylaxis is not subsumed under T63.442D. Per standard ICD-10-CM coding conventions, if the record documents anaphylactic shock in addition to bee venom toxicity, assign both codes. Verify the current Excludes1 and Excludes2 notes in the FY2026 Tabular List, as these notes govern whether codes may be assigned together. The WHO ICD-10 browser provides the international classification context for cross-reference.

Documentation requirements for T63.442D

For T63.442D, the clinical record has to support all three qualifier layers at once. Coders can only assign what the provider has documented, so the elements below belong in the note before the claim is built.

Required documentation elements

• Confirmation of bee venom as the toxic agent: the provider note should specifically identify bees (not wasps, hornets, or unspecified insects). “Bee sting” or “bee envenomation” in the provider’s own words is sufficient; a lab-confirmed apitoxin result is not required.
• Provider attestation of intentional self-harm intent: the record must document that the exposure was intentional and self-directed. A physician or advanced practice provider (APP) query response confirming intent is acceptable if the presenting note is ambiguous. Coders may not infer intent from circumstantial documentation alone.
• Encounter type support for subsequent care: documentation should clearly indicate the patient is presenting for follow-up, monitoring, or aftercare rather than emergency or acute intervention. Phrases like “follow-up for bee envenomation” or “monitoring for residual symptoms after bee venom exposure” support the seventh-character D assignment.
• Psychiatric or behavioral health co-documentation: where a mental health diagnosis is clinically present and documented, capture it with an appropriate code. Its presence strengthens the record’s coherence for payer review, even in jurisdictions where it is not mandated.

Payer requirements and prior authorization for T63.442D

Claims carrying intentional self-harm injury codes tend to attract heightened payer scrutiny. The patterns below reflect common payer conventions; specific requirements vary by plan, and coders should verify against each payer’s current LCD, NCD, or coverage policy.

• Psychiatric evaluation documentation: many commercial payers expect a behavioral health evaluation to accompany or follow a self-harm admission. Without it on file, post-payment audits frequently flag the claim. Submit it proactively when available, even if not explicitly required by the payer portal at submission time.
• Inpatient vs. outpatient submission rules: for inpatient claims, the principal diagnosis sequencing rules under the Uniform Hospital Discharge Data Set (UHDDS) apply. T63.442D may be the principal diagnosis or a secondary code, depending on what was chiefly responsible for admission. For outpatient claims, code the reason for that day’s visit first. On a psychiatric follow-up where the bee envenomation is only background, the psychiatric code may sequence first.
• Mental health and medical claim coordination: one episode can produce a medical claim for the toxic effect and a behavioral health claim for the evaluation. Confirm whether the payer adjudicates both the same way, or whether a separate behavioral health carve-out applies.

Checking eligibility before a T63.442D claim goes out confirms the patient’s active coverage. It also shows whether a behavioral health carve-out applies with that payer. When a claim is not paid as expected, the electronic remittance advice carries CARC denial reason codes that tell coders exactly what to fix.

Common claim denial reasons for T63.442D

T63.442D denials cluster around five patterns, and each one is preventable at the coding or documentation stage. Once a denial lands, the denial codes in medical billing reference decodes the payer’s reason. Our denial management in healthcare guide covers the appeal workflow.

A clean claim catches these errors before transmission. Add a check to your pre-submission review: does every self-harm code have a supporting psychiatric code where the payer expects one? That one question takes care of the third trigger.

How claims management software keeps T63.442D claims moving

Self-harm follow-up claims often pass through several hands. Eligibility is checked by phone, claims are keyed into a payer portal, and remittances are matched against a spreadsheet. A denied T63.442D claim can sit unnoticed for weeks.

Practice management software like Pabau brings that work into the patient record. Its claims management software runs on the Claim.MD clearinghouse, with real-time eligibility checks across 400+ payers. Claims go out electronically, their status is tracked in one place, and electronic remittances come back against the right visit.

The result is a shorter loop. A denial on a follow-up visit shows up with its reason code the day it arrives. Your coder can then query the provider and resubmit while the encounter is still fresh.

Get T63.442D claims paid on the first pass

Pabau’s claims management software checks eligibility in real time, submits claims electronically, and tracks each one to the remittance. Your team sees a denial the day it lands and fixes it while the chart is fresh.

Book a demo

Conclusion

Assign T63.442D only after the note confirms three points: bee venom as the agent, attested self-harm intent, and a visit that follows completed active treatment. If any one is missing, query the provider before the claim goes out.

The trade-off is a slower first pass for a faster payment. A query today costs minutes, while a denied self-harm claim can take weeks to appeal. Book a demo to see how Pabau tracks every T63.442D claim from eligibility check to remittance.

Continue your research

Need a framework for working denials after submission? Denial management in healthcare covers the appeal and resubmission workflow for complex diagnosis code denials.

Want to understand clearinghouse submission for ICD-10 claims? Medical claims clearinghouse explains how electronic claims move from practice management system to payer adjudication.

Want fewer claims coming back for rework? Clean claims in medical billing sets out the checks a claim should pass before it leaves the practice.

Reading CARC codes on a remittance? Electronic remittance advice shows how to read an ERA and act on its denial reason codes.

Frequently asked questions