A patient walks in with a tick still attached to their scalp, or a red mark on the thigh where one was pulled out that morning. The clinical part is usually quick. The coding part is where things go sideways, because a tick bite is one of the few common encounters that legally cannot be billed with a single code.

Get the sequencing wrong, and the claim either denies outright or pays at the wrong level. Get it right, and it clears the first time. This guide walks through the exact codes, the sequencing rule behind them, every related tick-borne illness code you might need, the CPT side of tick removal, and the documentation habits that keep these claims from bouncing back.

Quick Answer: What Is the ICD-10 Code for a Tick Bite?

There is no single “tick bite code.” A tick bite is coded with two codes together:

1. An injury code from the S00–S99 range that identifies the body site the bite occurred on (this is the first-listed, primary diagnosis)
2. W57.XXXA, the external cause code for “Bitten or stung by nonvenomous insect and other nonvenomous arthropods, initial encounter,” which explains how the injury happened

For example, a tick bite on the left thigh at an initial visit is coded as S70.362A (insect bite, nonvenomous, left thigh, initial encounter) listed first, followed by W57.XXXA. Neither code stands alone. This two-code requirement is the single most common source of tick bite claim errors, and it’s worth understanding why before you look anything up.

Why a Tick Bite Always Needs Two Codes

ICD-10-CM treats a tick bite as an injury, not a diagnosis in isolation. Chapter 19 (Injury, Poisoning, and Certain Other Consequences of External Causes, S00–T88) governs the clinical injury itself, while Chapter 20 (External Causes of Morbidity, V00–Y99) governs how and where the injury happened.

The Official ICD-10-CM Guidelines for Coding and Reporting are explicit that external cause codes are never sequenced first and are never reported as the sole code for an encounter. W57.XXXA describes the mechanism (bitten by a nonvenomous arthropod). It does not tell a payer where on the body the injury is, and payers need that information to process the claim. That’s the job of the S-code.

So the logic runs in one direction every time:

• First-listed code: the S-code describing the injury and its location
• Secondary code: W57.XXXA describing the cause

Submit W57.XXXA by itself, or list it first, and most clearinghouses and payer edits will kick the claim back before a human even looks at it.

The External Cause Code: W57.XXXA and Its Variants

W57 covers bites and stings from nonvenomous insects and other nonvenomous arthropods, which is the category ticks fall under for ICD-10-CM purposes (ticks are technically arachnids, but the classification treats the bite mechanism the same way regardless of exact taxonomy). The code requires a 7th character to identify the encounter type, and the “XXX” placeholders exist purely to hold that 7th character in position:

W57.XXXA is by far the most frequently reported of the three, since most tick bite encounters are a single urgent care or primary care visit.

Injury (S-Code) Selection: Match the Body Site

The S-code is where the real specificity lives, and it’s also where most of the coding errors AAPC and other coding authorities flag actually happen. ICD-10-CM organizes injury codes by body region, and each region has its own block:

Within each block, the specific “insect bite, nonvenomous” code also carries laterality (right, left, or unspecified) and the same 7th character options as the external cause code (A for initial, D for subsequent, S for sequela). A few confirmed, frequently billed examples:

• S00.06XA – Insect bite (nonvenomous) of scalp, initial encounter
• S70.362A – Insect bite (nonvenomous), left thigh, initial encounter
• S60.96XA – Insect bite (nonvenomous) of unspecified upper arm, initial encounter

Only the fully specified code (site, laterality, and 7th character all present) is billable. A truncated version of the same code, missing the laterality digit or the 7th character placeholder, is not a valid code for claim submission and will reject.

Coding tip: searching an EHR’s problem list or an encoder for “tick” alone often returns nothing, because ICD-10-CM’s External Cause Index files tick bites under “Bite, bitten by, insect (nonvenomous),” not under “tick.” If your search comes up empty, that’s the index working as intended, not a missing code. Search “insect bite” instead.

When the Bite Site Isn’t Documented

If the provider’s note doesn’t specify a body site (which happens more often than it should), the coder is stuck with an unspecified-site option, and reimbursement or claim acceptance can suffer for it. This is a documentation gap, not a coding one, and it’s worth flagging back to the clinical team rather than guessing. A quick, standardized documentation habit at the point of care (site, laterality, and whether the tick was still attached, partially removed, or already gone) prevents this from becoming a recurring problem. Building that habit into your intake and charting workflow is really a charge capture issue as much as a coding one, and it’s worth reviewing alongside your practice’s broader charge capture process if unspecified-site claims keep showing up in your denial reports.

Related Codes: Tick-Borne Illness Diagnoses

A tick bite and a tick-borne disease are coded completely differently, and mixing them up is a common audit flag. W57.XXXA and an S-code describe the bite itself. If the patient is being treated for an actual infection transmitted by the tick, rather than the bite wound, the diagnosis code changes entirely and the injury/external-cause pair typically drops off the claim (unless the visit is addressing both the bite and a suspected exposure in the same encounter).

A patient presenting weeks after a bite with a bullseye rash and joint pain is a Lyme disease encounter (A69.2x family), not a W57.XXXA encounter, even though the tick bite is what started it. Document and code the condition the provider is actually treating that day.

CPT Codes for Tick Removal: What’s Actually Billable

This is where a lot of practices lose money they were entitled to, or bill something they shouldn’t. Simple removal of an attached tick with forceps or tweezers, the way it’s done in the overwhelming majority of visits, is generally considered part of the evaluation and management (E/M) service and isn’t separately billable as a procedure.

A separate procedure code only applies when the removal is genuinely more involved, typically because part of the tick (the mouthparts or head) has broken off and remains embedded under the skin, requiring incision to extract it:

• CPT 10120 – Incision and removal of foreign body, subcutaneous tissues; simple
• CPT 10121 – Incision and removal of foreign body, subcutaneous tissues; complicated

If you bill 10120 or 10121 for a routine tweezer removal, expect a denial or, worse, an audit finding down the line. Documentation needs to clearly support that an incision was actually performed, not just that the tick was “removed.” The E/M code for the visit itself is billed based on the complexity of the history, exam, and decision-making involved, same as any other problem-focused visit, and it can be billed alongside 10120/10121 when a true procedure was performed and documentation supports both.

A Complete Coding Example

Putting it together for a typical initial-encounter visit:

Scenario: A patient comes in with an attached tick on the right forearm. The provider removes it intact with forceps, cleans the site, and counsels the patient on Lyme disease warning signs. No incision is performed.

• Diagnosis codes: S50.96XA describes the injury pattern in this region (elbow/forearm block, insect bite, right side, initial encounter, pending confirmation of the exact leaf code in your encoder for the specific site documented), sequenced first, followed by W57.XXXA
• Procedure code: E/M code only, level based on documented complexity. No 10120/10121, since no incision was performed.

Scenario 2: A tick’s mouthparts remain embedded after an attempted at-home removal. The provider performs a simple incision to extract the remaining fragment.

• Diagnosis codes: appropriate S-code for the site, initial encounter, followed by W57.XXXA
• Procedure code: CPT 10120, supported by an operative note describing the incision

Always verify the exact leaf-level S-code against your current encoder or the CMS ICD-10-CM tabular list, since the precise code depends on the documented site and laterality down to the individual digit.

Common Coding and Documentation Errors

• Billing W57.XXXA as the only code, or listing it first. External cause codes are never billed alone and are never first-listed.
• Using a truncated S-code without the 7th character. These are not valid for claim submission.
• Coding a suspected or confirmed Lyme disease case with W57.XXXA instead of A69.2x. These represent different clinical scenarios and payers can flag the mismatch.
• Billing 10120/10121 for a routine forceps removal. This is one of the more common audit triggers in this category, precisely because the difference between “simple removal” and “incision and removal” isn’t always obvious from a quick note.
• Missing laterality or site documentation, which forces the coder into an unspecified code and weakens the claim’s specificity.

Most of these trace back to the same root cause: a workflow that doesn’t prompt the provider to document site, laterality, and removal method at the time of the visit. If tick bite denials (or denials in general) are becoming a pattern rather than a one-off, it’s worth tracing them back through your payment posting data to see which remark codes keep showing up, since that’s usually the fastest way to find where in the workflow the breakdown is actually happening.

FAQs

Is a tick bite always coded with two codes? Yes. An S-code identifying the injury site is listed first, and W57.XXXA (or the appropriate 7th character variant) is listed second to describe the external cause. Neither is billed alone.

What is the ICD-10 code for a tick bite on the leg? It depends on exactly where on the leg and which side. Hip and thigh injuries fall in the S70–S79 range (for example, S70.362A for the left thigh), while knee and lower leg injuries fall in the S80–S89 range. The provider’s documentation of the precise site determines the correct leaf code.

Can I bill for removing a tick? Only if the removal required an incision because part of the tick remained embedded under the skin. Routine forceps or tweezer removal is included in the E/M service and isn’t billed separately with CPT 10120 or 10121.

What ICD-10 code do I use if the patient develops Lyme disease after a tick bite? Once the diagnosis shifts from the bite itself to an actual tick-borne infection, the coding shifts too. Lyme disease is coded from the A69.2 family (A69.20 for unspecified Lyme disease), not with W57.XXXA.

Why can’t I find “tick” when I search the ICD-10-CM index? The External Causes Index files tick bites under “insect (nonvenomous),” not under “tick” as its own entry. Searching “insect bite” or going directly to the W57 category in the tabular list will get you there.

What happens if the body site isn’t documented? The coder has to default to an unspecified-site code, which is valid but less specific, and can affect how cleanly the claim processes with some payers. This is a documentation workflow issue as much as a coding one, and it’s worth building the habit of noting site and laterality into your documentation and coding compliance checks rather than catching it after the fact.

The Bottom Line

A tick bite is a two-code diagnosis every time: the injury site from the S00–S99 range, sequenced first, paired with W57.XXXA (or its D/S variant) to describe the cause. Get the site-specific S-code right, keep W57.XXXA in the second position, only bill 10120/10121 when an actual incision was performed, and switch over to the correct infectious-disease code the moment the visit is about treating Lyme disease or another tick-borne illness rather than the bite itself. Small details, but they’re exactly the kind that separate a claim that pays the first time from one that lands back on your desk three weeks later.

If tick bite claims, or coding-driven denials more broadly, keep showing up in your charge capture and denial reports more than they should, it’s usually a sign of a workflow gap rather than a one-off mistake, and it’s worth having someone look at the pattern across your whole claim volume rather than one chart at a time. Our team at The Billing Advisors reviews exactly this kind of coding and documentation gap for practices every week. Reach out if you’d like a second set of eyes on how your urgent care or primary care visits are coding out.