ICD code T63.591D – Toxic effect of other venomous fish

Key takeaways

T63.591D codes routine healing-phase care for an accidental sting from a venomous fish other than a stingray, such as a stonefish, lionfish or scorpionfish.

The 7th character D marks routine care during healing or recovery. T63.591A covers each encounter for active treatment, and T63.591S covers sequela once late effects remain.

Stingray stings code to T63.51-, and jellyfish, man-o-war and sea anemone stings code to T63.6-, so the species named in the note decides the code.

T63.591D already identifies the agent and intent, so ICD-10-CM has no separate external cause code for the sting itself. Y92 place, Y93 activity and Y99 status codes are reported once, at the initial encounter.

Pabau, the billing and practice platform we build, turns invoices into CMS-1500 claims, submits them through Claim.MD and tracks each one to payment or denial.

ICD-10 Code T63.591D: Quick reference

ICD-10 Code T63.591D reports the toxic effect of an accidental sting from a venomous fish other than a stingray, during routine healing-phase care.

Stonefish, lionfish, scorpionfish and weever fish stings all code here once active treatment has ended. Confirm every field in the table below before the code goes on a claim, because payers validate it against the ICD-10-CM tabular list.

Verify current billability status against the CDC/NCHS ICD-10-CM web tool each fiscal year. The annual October update can retire or modify codes.

What T63.591D means: Breaking down the code structure

T63.591D is an alphanumeric string, and each character carries a specific meaning. Coders who can read each position catch a misassignment before the claim leaves the practice.

• T63: The category for toxic effects of contact with venomous animals and plants. Its subcategories run from T63.0 (snake venom) to T63.9 (unspecified venomous animal).
• .5: The subcategory for venomous fish. It splits into T63.51 for stingrays and T63.59 for every other venomous fish.
• 9: The fifth character, meaning other venomous fish. Any venomous fish that isn’t a stingray codes here.
• 1: The sixth character for accidental (unintentional) intent. Its siblings are .592 (intentional self-harm), .593 (assault) and .594 (undetermined). When the record doesn’t state intent, the T51–T65 notes direct you to code accidental.
• D: The 7th character for a subsequent encounter, meaning routine care during healing or recovery. T63.591 without a 7th character is not a valid billable code.

Which fish fall under “other” in T63.59?

T63.59 covers every venomous fish except the stingray, which has its own subcategory, T63.51. Stings from stonefish, lionfish, scorpionfish and weever fish all code here. The fish’s name in the clinical note is what places the sting in T63.59.

Other marine stings sit elsewhere in T63. Portuguese man-o-war, jellyfish and sea anemone stings code to T63.6-, and venomous marine plants code to T63.7-. Land animals have their own subcategories too.

• T63.0: snake venom
• T63.1: venom of other reptiles
• T63.2: scorpion venom
• T63.3: spider venom
• T63.4: venom of other arthropods
• T63.8: other venomous animals
• T63.9: unspecified venomous animal

T63.011D, the follow-up code for rattlesnake venom, shows how far apart these subcategories sit. Coding a rattlesnake bite to T63.591D reports the wrong animal entirely, so the claim describes a sting the patient never had. A non-fish animal with no named subcategory belongs in T63.89-, never in T63.59-.

What the 7th character D means: Initial, subsequent, and sequela encounters

The 7th character D designates a subsequent encounter. It covers routine care during the healing or recovery phase, after active treatment of the sting has ended. The care delivered at this visit decides the character, so a fourth visit can still be active treatment.

The 7th character follows the type of care. A new clinician who only checks healing still uses D (T63.591D). One who starts or continues active treatment uses A (T63.591A). The decision path below puts the species and the type of care together.

A sting that fails either question needs a different code, so check both before the claim goes out.

Excludes notes and code conflicts for T63.591D

T63.591D inherits instructional notes from subcategory T63.5, category T63 and the T51–T65 block. Ignoring them creates claim edits that payer systems catch quickly.

Excludes1 notes (cannot be coded together)

Category T63 carries no Excludes1 note of its own. The Excludes1 that applies sits at the T51–T65 block level and covers contact with and suspected exposure to toxic substances (Z77.-). Z77.- describes exposure without a toxic effect, so it never sits beside T63.591D for the same exposure.

Excludes2 notes (may be coded together when both conditions are present)

Category T63 carries an Excludes2 note for ingestion of a toxic animal or plant (T61.-, T62.-). Subcategory T63.5 adds its own Excludes2 for poisoning by ingestion of fish (T61.-). Excludes2 means the excluded condition isn’t part of this code, but the patient may have both.

A diver stung by a weever fish who separately develops ciguatera from eating reef fish would carry both a T63.59- code and a T61.- code. The T51–T65 block also tells you to code associated manifestations of the toxic effect separately.

Adverse effect vs toxic effect: A common miscoding error

T63.591D describes a toxic effect, not an adverse effect. Toxic effects arise from exposure to inherently poisonous substances, which here means fish venom. Adverse effects arise from correct administration of a therapeutic substance. Coding a fish sting as an adverse effect reports the wrong mechanism and can trigger a payer edit. Category T63 is the correct home for every venomous sting, however mild the presentation.

External cause codes with T63.591D

T63.591D already identifies the agent and intent, so ICD-10-CM has no separate external cause code for the sting itself. The ICD-10-CM Official Guidelines, Section I.C.20, state that there is no national requirement to report external cause codes. Some payers and state data systems do collect them.

Three supplementary families add context where they’re collected:

• Place of occurrence (Y92 family): Documents where the sting happened, such as a beach, a boat or a home aquarium.
• Activity (Y93 family): Documents what the patient was doing, such as swimming, snorkeling, wading or fishing.
• External cause status (Y99 family): Separates civilian, military and work-related activity. It matters for a commercial fisher’s workers’ compensation claim.

All three are reported once, at the initial encounter for treatment. On a T63.591D follow-up claim they normally don’t repeat. External cause codes are always secondary and are never sequenced as the first-listed diagnosis.

Documentation that supports T63.591D

Coders assign T63.591D from the note alone, so each element below has to be in the record. Use the table as a pre-submission checklist you can share with your clinical team.

Practices using medical billing compliance workflows build these documentation prompts into the clinical note template. That catches missing details before the encounter closes, which costs far less than chasing documentation after a denial. Understanding medical billing fundamentals helps clinicians see why each field matters for claim adjudication.

Payer requirements for T63.591D

Medicare and most commercial payers accept T63.591D as a valid diagnosis code for routine healing-phase visits after a venomous fish sting. Prior authorization is not typically required for routine follow-up wound care. It may apply when the visit involves a specialist consultation, imaging for a retained spine, or a procedure. Payer policies vary, so confirm the plan’s rules first.

Common procedure codes that pair with T63.591D include evaluation and management codes (99211-99215). Wound care visits may add debridement codes (97597, 97598) or 99070 for dressing supplies. Removing a retained spine fragment is active treatment, so that visit takes T63.591A with the matching foreign body removal code.

Top reasons T63.591D claims are denied

Five documentation and coding errors put a T63.591D claim at risk. Each one below comes with the corrective action that prevents it.

• Wrong encounter type (A instead of D): A coder assigns T63.591A to a routine wound check because the clinician is new to the case. A new clinician does not turn healing-phase care into active treatment. Corrective action: Code from the care the note documents. Routine healing-phase care uses D, and active treatment uses A at any visit.
• Wrong subcategory for the species: A stingray wound coded to T63.591D, or a jellyfish sting coded to T63.59-, reports the wrong animal. Corrective action: Match the species to T63.51-, T63.59- or T63.6- before you code.
• Fish not named in the documentation: The provider writes “marine sting” or “puncture wound” without naming the fish. The coder then can’t confirm T63.59 over the stingray or marine animal codes, and the payer may request records. Corrective action: Ask clinicians to name the fish at the point of documentation.
• Adverse effect coding error: The claim uses an adverse effect code from the T36-T50 drug range instead of the T63 toxic effect code. Venom is not a therapeutic substance, so an adverse effect code reports the wrong mechanism. Corrective action: Code every venomous sting to T63.
• Procedure code mismatch: The procedure code billed doesn’t match the care documented. A complex debridement code paired with a brief follow-up exam triggers a mismatch edit. Corrective action: Make sure the visit note supports the complexity of the procedure code selected.

For practices managing a high volume of denials, structured denial management workflows help. Reviewing denial reason codes systematically, rather than claim by claim, surfaces the pattern quickly and helps prioritize corrective action.

Coding best practices for T63.591D: A pre-submission checklist

Walk through this sequence before every T63.591D claim submission. Building it into your billing workflow catches the errors listed above before the claim goes out.

1. Confirm the type of care. Is the patient receiving active treatment for the sting, at any visit? Use T63.591A. Is this routine healing-phase care, such as a wound check? Use T63.591D. Do only late effects remain? Use T63.591S.
2. Verify the fish falls in the “other” group. Stingrays code to T63.51-, and jellyfish, man-o-war and sea anemones code to T63.6-. If either applies, use that code instead of T63.591D.
3. Confirm accidental intent. The record should support an unintentional sting. If it documents self-harm (.592), assault (.593) or undetermined intent (.594), assign that code instead.
4. Check external cause codes. Y92, Y93 and Y99 codes are reported once, at the initial encounter, so they usually don’t repeat on a D claim. Follow payer-specific rules where they differ.
5. Check excludes notes. Confirm no Z77.- exposure code sits on the claim. If fish-ingestion poisoning (T61.-) is also documented, code it as well.
6. Match the procedure code. Verify that the procedure code billed (E&M level, wound care, foreign body removal) matches the care documented in the visit note.
7. Submit through a clearinghouse with pre-submission edits. A clearinghouse checks the claim before it reaches the payer, catching format errors and code mismatches. Practices using Pabau send each clean claim through Claim.MD. A real-time eligibility check (270/271) runs on the patient’s insurance before the claim goes out.

How Pabau helps practices bill T63.591D cleanly

Billing a T63.591D claim means checking the encounter history, the fish named in the note and the payer’s edits, often across several visits. Doing that by hand across payer portals is slow, and a missed A-versus-D error comes back as a denial weeks later.

Pabau turns invoices into CMS-1500 claims and submits them as electronic claims via Claim.MD, our US clearinghouse partner. Claim.MD carries the claim to thousands of US payers, and Pabau shows its status from submission to payment or denial.

Pabau also checks patient eligibility in real time. Claim status updates and electronic remittance advice flow back into Pabau’s denial-tracking claims software, and denied claims are flagged for rework. Your billing team can follow every visit for the same sting from invoice to payment in one dashboard.

Stop letting T63.591D denials slip through

Pabau turns invoices into CMS-1500 claims, checks eligibility in real time, and sends each claim to payers through Claim.MD. See how it works for practices billing toxic effect codes.

Book a demo

Conclusion

T63.591D is narrow by design. It fits only an accidental sting from a venomous fish other than a stingray, during routine healing-phase care. Get the species and the type of care right, and the code rarely causes trouble.

The practical step is to make both facts hard to skip in the clinical note. Prompt for the named fish and for what care each visit delivers, then match the 7th character to it. Reading each electronic remittance advice file closes the loop on every visit you bill.

Book a demo to see how Pabau tracks each T63.591D claim from invoice to payment.

Continue your research

Want to see how a T63 claim travels from Pabau to the payer? Pabau’s Claim.MD clearinghouse guide explains how claim submission and real-time eligibility verification work together.

Managing a volume of toxic effect denials across multiple payers? Revenue cycle management fundamentals covers how to build a systematic denial review process that scales.

Frequently asked questions