ICD-10 code S90.579A: Other superficial bite of unspecified ankle

Key takeaways

S90.579A is a billable ICD-10-CM code for other superficial bite of unspecified ankle, initial encounter, valid for FY2026 (effective October 1, 2025).

The 7th character A designates an initial encounter, meaning active treatment. Use D for subsequent encounters and S for sequelae.

Never use S90.579A for open bites of the ankle. Those code to S91.05- under ICD-10-CM Excludes1 rules.

Practice management software like Pabau embeds ICD-10-CM codes directly into clinical notes and insurance claims, which cuts transcription errors at the point of care.

ICD-10 code S90.579A is the billable ICD-10-CM diagnosis code for other superficial bite of unspecified ankle, initial encounter. It applies when a bite breaks only the skin at the ankle and the chart names no side.

The code took effect on October 1, 2025 and is valid for claims in fiscal year 2026. It comes from the 2026 edition of ICD-10-CM. That edition is published by the Centers for Medicare and Medicaid Services (CMS) and the CDC’s National Center for Health Statistics (NCHS).

Wound depth is what separates this code from its closest neighbor. Superficial bites stay in S90, and a bite that reaches deeper tissue moves to S91.

What does S90.579A mean? Code description and clinical definition

The full clinical description of ICD-10 code S90.579A is “Other superficial bite of unspecified ankle, initial encounter.” Each word in that description carries a specific coding meaning that determines when the code applies and when it does not.

• Other superficial bite: A wound that breaks only the skin surface without penetrating deeper anatomical layers. “Other” distinguishes non-insect bites from insect bites, which carry separate codes in the ICD-10-CM index.
• Unspecified ankle: The documentation does not specify whether the injury is to the right or left ankle. If laterality is documented, use S90.571A (right) or S90.572A (left) instead.
• Initial encounter: The patient is receiving active treatment for the injury. This is the first time the provider is managing this specific condition, not follow-up care.

Clinical scenarios that support S90.579A include:

• Dog or cat bites to the ankle where the skin is broken but tendons and deep tissue stay intact
• Human bites with skin-only involvement
• Rodent bites that do not reach below the skin surface

Insect bites fall under separate tabular entries. The CDC/NCHS ICD-10-CM coding tool also lists approximate synonyms accepted in documentation. They include “bite of ankle,” “superficial bite of ankle,” and “wound of ankle due to bite.”

7th character extensions: A, D, and S explained

S90.579 requires a 7th character to be complete and billable. Without it, the code is a header-level category, not a valid claim submission code. The 7th character identifies the type of encounter, which affects reimbursement logic and medical necessity documentation.

The ICD-10-CM Official Guidelines for Coding and Reporting (Section II) define “initial encounter” as any encounter during active treatment. The calendar order of the visit does not decide it. A patient seen for debridement on visit three is still an “A” encounter if active treatment continues. Switching to “D” is appropriate once the provider’s role shifts to monitoring routine recovery.

S90.579A code hierarchy and parent codes

Understanding the full code hierarchy helps coders confirm they are working in the right section of the tabular list and quickly find related laterality-specific codes.

Related codes and sibling codes in the S90 category

S90.579A has two direct laterality siblings and several closely related codes within the S90 category. When documentation specifies the affected ankle, use a laterality-specific code rather than the unspecified variant.

The AAPC ICD-10-CM code reference restates the tabular list’s guidance on specificity. Coders select the highest degree of specificity the documentation supports. Unspecified codes like S90.579A are valid when the provider genuinely does not document laterality. They should not stand in for a laterality-specific code that the chart supports.

Excludes notes: When not to use S90.579A

The S90 category carries Excludes1 and Excludes2 notes that define the boundaries of this code. Misapplying S90.579A when an exclusion applies is one of the most common reasons ankle-bite claims return with an edit.

Excludes1: Codes that can never be used with S90.579A

An Excludes1 note means the excluded condition is mutually exclusive. You cannot code both S90.579A and an Excludes1 code for the same encounter, because the two conditions are contradictory by definition.

• Open bite of ankle (S91.05-): A bite that penetrates below the skin into subcutaneous tissue, muscle, or deeper structures codes to S91.05-, not S90.579A. The distinction is clinical. Superficial bites are skin-only wounds, while open bites reach deeper tissue or need surgical exploration.
• Insect bite (S90.56-): Insect bites at the ankle carry their own code set. S90.579A is for non-insect bites such as animal and human bites. If the clinical note specifies “insect bite,” use S90.56- instead.

Excludes2: Codes that may be reported together

Excludes2 notes indicate that the excluded condition is not part of S90.579A but may co-exist. Both codes can appear on the same claim when clinically appropriate.

• Superficial foreign body of ankle: A splinter or other foreign material left by the bite gets its own code alongside S90.579A.
• Secondary infection: Cellulitis codes such as L03.11- may be reported with S90.579A when the infection is a documented complication of the bite.

Documentation requirements and coding tips for S90.579A

Accurate documentation is what keeps S90.579A claims out of the denial queue. Providers need to record specific details, and coders need to verify those details map to the code before submission.

What the provider must document

• Bite type: Whether the bite is from an animal, human, or other source. Insect bites go to S90.56-, not S90.579A.
• Wound depth: Superficial (skin only) versus open (deeper tissue). This determines whether S90 or S91 applies.
• Anatomical site: Ankle, not the foot or toes. If documentation says “foot,” look at S90.87- for superficial bites of the foot.
• Laterality: Right, left, or unspecified ankle. “Unspecified” is only appropriate when the provider truly does not document which side.
• Encounter type context: Enough clinical context to confirm active treatment (7th character A) versus routine follow-up (7th character D).

Those details resolve in a fixed order. The chart below runs the decision from bite type down to encounter phase, and shows where S90.579A is the answer.

Laterality decision: When to use “unspecified”

A persistent misconception is that “unspecified” codes are acceptable whenever a provider does not explicitly write “right” or “left.” The standard under ICD-10-CM guidelines is narrower. Use the unspecified code only when the information is genuinely unavailable.

If the provider documented a physical exam of one ankle, the laterality is inferable and should be queried. Submitting S90.579A when the chart supports S90.571A or S90.572A is undercoding, which carries its own compliance risk.

The fix is to query the provider at the point of documentation, before the claim drops, rather than defaulting to “unspecified” as a shortcut. A query takes minutes. A corrected claim costs a whole resubmission cycle.

Common coding errors with S90.579A

• Using S90.579A for insect bites when S90.56- is the correct category
• Using S90.579A when wound depth documentation supports S91.05- (open bite)
• Defaulting to “unspecified” laterality without querying the provider when the chart holds the answer
• Continuing to submit S90.579A after active treatment ends, when S90.579D is the appropriate subsequent-encounter code

Excludes1 violations and an incorrect 7th character are the two errors that show up most on ankle-injury claims. Both surface later as denial codes worth preventing, so a documentation review before submission is cheaper than an appeal.

Submitting a clean claim means confirming the Excludes rules and the encounter type first. Both checks take seconds once the note is in front of you.

How Pabau supports accurate ICD-10 coding

ICD-10 lookup usually happens somewhere other than where the note and the claim live. A coder confirms the code on an external site, then retypes it into the EHR or the billing system. That retyping step is where transcription errors enter.

Practice management software like Pabau removes the retyping step. Pabau builds ICD-10-CM code selection into the clinical note and the billing screen, which is what makes claims management without re-entry possible. Providers document the encounter, pick the diagnosis code in the same place, and that code flows into the outbound claim.

For US practices, Pabau’s Claim.MD clearinghouse integration handles electronic claim submission across thousands of US payers. It also covers real-time eligibility checks and ERA (electronic remittance advice) processing.

A code like S90.579A can move from the clinical note to a submitted 837P claim with built-in ICD-10 and CPT validation. That validation catches a code-level problem before the claim reaches the payer. Injury documentation sits in the patient record alongside the billing record, so the audit trail stays in one place.

Connect your ICD-10 codes to your claims workflow

Pabau links diagnosis codes like S90.579A directly to clinical notes, invoices, and insurance claims in one platform. Less manual transfer means fewer transcription errors and faster reimbursement.

Book a demo

Conclusion

S90.579A is a straightforward billable code when the documentation supports it. Two decision points drive most of the errors. Wound depth separates S90 from S91, and laterality separates the unspecified code from the specific ones.

Get both right before submission and the claim clears without an edit. Get either wrong and the correction costs more than the query would have.

Pabau’s coding and claims workflow removes the retyping step that creates most of those errors. Book a demo to see how an injury code moves from the clinical note into a submitted claim.

Continue your research

Need to understand how clearinghouse submissions work for injury codes? How the Claim.MD clearinghouse processes claims walks through EDI submission, 835 remittances, and denial handling for US payers.

Want to reduce coding-related claim denials across your practice? Electronic remittance advice (ERA) explained covers how 835 files help you identify and correct systematic code errors before they become write-offs.

Need documentation standards that hold up in an audit? Medical billing compliance covers the documentation and query practices that keep coded claims defensible.

Frequently asked questions