ICD code W61.42XA – Struck by turkey

Key takeaways

W61.42XA codes being struck by a turkey at the visit where active treatment is given. It names the cause of the injury, so it never stands as the first-listed diagnosis.

The turkey subcategory sorts by mechanism: W61.42 for a strike, W61.43 for a peck and W61.49 for any other contact. There is no “bitten by turkey” code.

The 7th character A marks active treatment. Switch to D for routine care while the injury heals, and to S for late effects.

Most denials trace back to sequencing or specificity: W61.42XA listed first, no injury code on the claim, or a peck documented but a strike coded.

In Pabau, the practice software we build, the injury code, W61.42XA and the companion Y-codes sit on one claim. The full code set reaches the payer at once.

ICD-10 code W61.42XA: Definition and quick-reference data

W61.42XA is a valid, billable ICD-10-CM code for being struck by a turkey, initial encounter. It reports how an injury happened, so it travels with a separate code for the injury itself. It sits in Chapter 20 of ICD-10-CM, External causes of morbidity (V00 to Y99).

Under the CMS ICD-10-CM coding guidelines, an external cause code is never the principal or first-listed diagnosis. There is no national mandate to report these codes. They are required where a state reporting rule or a payer policy asks for them, and many practices report them anyway for complete injury data.

Code breakdown: Anatomy of W61.42XA

Each character of W61.42XA carries a specific meaning. Reading the code this way helps coders land on the right sibling when the bird or the mechanism changes.

W61.42 has only five characters, so the placeholder X is needed before the 7th character. Without it, the code is invalid for submission. Coders who transcribe from a superbill or a manual lookup often drop it.

W61.42XA in the W61 code hierarchy

Category W61 covers contact with birds, both domestic and wild, and splits into subcategories by species. W61.4 is the turkey subcategory, and its codes are sorted by mechanism. Knowing the layout stops coders from settling on the residual code when the note already names the mechanism.

The turkey subcategory has no “bitten” code, and there is no W61.41. The parrot and macaw subcategories do have one (W61.01 and W61.11), which is why coders sometimes expect it here. A turkey injury from the beak is coded as a peck, W61.43XA.

Encounter qualifiers: Initial, subsequent, and sequela for W61.42XA

The 7th character tells the payer which stage of care the visit belongs to. A wrong qualifier is one of the most frequent reasons external cause codes are rejected. The CDC/NCHS ICD-10-CM browser tool lists three valid 7th characters for W61.42: A, D and S.

A common error is keeping W61.42XA on follow-up visits where no new active treatment occurs. Once care moves to monitoring, a wound check or a dressing change, switch to W61.42XD.

What W61.42XA covers and what it excludes

The turkey codes cover a narrower set of events than many coders assume. Knowing the boundaries prevents two errors. One is under-coding with W61.49XA when a strike is documented. The other is using W61.42XA for a peck that belongs under W61.43XA.

What W61.42XA includes

• Being struck by a domestic or wild turkey, such as a blow from its wing or body, at any body site
• The initial encounter with active treatment only (for routine follow-up care, use W61.42XD)
• Farmed, backyard and wild turkeys alike, because the code does not separate settings

What W61.42XA excludes

• A peck from a turkey’s beak — use W61.43XA
• Any other contact with a turkey that is neither a strike nor a peck — use W61.49XA
• Strikes by other birds, such as a chicken (W61.32XA), a parrot (W61.02XA) or a macaw (W61.12XA)
• The injury itself, because W61.42XA never replaces the injury code (for example, a contusion or open wound code by body site)

If the note does not say how the turkey caused the injury, query the provider before you fall back on W61.49XA. W61.42XA never appears as the first-listed diagnosis on any claim.

Codes commonly confused with W61.42XA

The W61 category holds closely related codes that differ by bird and by mechanism. Picking the wrong sibling is a common specificity error. The table below covers the codes most often mistaken for W61.42XA.

The strike versus peck split matters for the claim and for the chart. A strike is a blow from the bird’s wing or body and tends to leave a bruise, an abrasion or, less often, a fracture. A peck is beak contact and tends to leave a puncture or small laceration. The injury code and the W61.4- code should tell the same story, because an auditor reads both. The diagram below maps each mechanism to its code and 7th character.

How to use W61.42XA correctly: Coding guidelines

Section I.C.20 of the ICD-10-CM Official Guidelines for Coding and Reporting governs external cause codes. The steps below apply it to a turkey-strike visit. The AAPC ICD-10-CM code reference is a useful cross-check before submission.

1. Code the injury first. Choose the injury code for the body site and type of injury. Examples are S60.- for a superficial injury or contusion of the wrist, hand or fingers, or S61.- if the skin is broken. This is the first-listed diagnosis.
2. Add W61.42XA as the external cause. List it after the injury code in a secondary diagnosis field. It records how the injury happened.
3. Add an activity code if it applies. Y93.K9 (Other activity involving animal care) fits a patient who was feeding, herding or handling the bird. Y93 codes describe what the patient was doing, not where.
4. Add a place of occurrence code. Place comes from category Y92, such as Y92.7- when the injury happened on a farm. Report place, activity and status codes once, at the initial encounter.
5. Add an external cause status code. Y99.0 (Civilian activity done for income or pay) fits a farm worker injured on the job. Y99.8 (Other external cause status) covers leisure activities, such as a hobby flock.
6. Confirm the encounter qualifier. Use A while the patient receives active treatment. Switch to D for routine follow-up visits.

Secondary codes to report alongside W61.42XA

A complete code set for a turkey-strike visit starts with the injury code and W61.42XA. Activity, place and status codes follow where a payer or state rule asks for them. An infection or other complication needs its own code as well.

A zoonotic infection needs its own code only when the provider confirms it and documents it. General concern about animal contact does not support an A28.- code. For electronic submission, Pabau’s Claim.MD clearinghouse integration sends complete ICD-10-CM code sets to thousands of US payers.

Documentation requirements for W61.42XA

The clinical note must give the coder enough to select W61.42XA and to defend it in a payer audit. A vague note pushes the coder toward W61.49XA (other contact with turkey), which is less specific and invites a query.

• Species: name the bird as a turkey, not “poultry” or “bird”
• Mechanism: state that the patient was “struck,” and say by what part of the bird if known (wing or body)
• Body site: give the anatomical location, such as the left forearm, to support the injury code
• Encounter type: confirm whether the visit involves active treatment or routine follow-up care
• Treatment rendered: record the exam, imaging, wound care or prescriptions given
• Setting and activity: note whether the patient was working on a farm or tending a hobby flock, which supports the Y-codes

Practices that use a structured template for animal-contact injuries capture all six elements every time. An animal injury intake form records the species, mechanism and body site before the coder opens the record. That removes the provider query that can hold a claim for days. The clean claim guide covers what payers expect across ICD-10-CM encounters.

Common W61.42XA claim denial reasons

Denials on W61.42XA claims usually trace back to one of six errors, and each one can be caught before submission. The denial management guide covers CARC reason codes and how to appeal efficiently.

• W61.42XA listed as the primary diagnosis. External cause codes are never first-listed. Resolution: reorder the claim so the injury code comes first.
• Wrong encounter qualifier. W61.42XA is billed on a follow-up visit after active treatment has ended. Resolution: switch to W61.42XD for routine follow-up visits.
• Missing injury code. W61.42XA is submitted without an injury code. Resolution: confirm the claim carries an S-code before submission.
• Missing Y-codes where they are required. Some payers and state reporting rules expect place, activity or status codes with the external cause. Resolution: check the payer’s policy and add Y92, Y93 or Y99 codes as needed.
• Mechanism mismatch. The note says “pecked” but W61.42XA was coded, or the note says “struck” but W61.49XA was used. Resolution: code from the note, using W61.43XA for a peck and W61.42XA for a strike.
• Code not valid for the date of service. The code is billed for a date before it took effect. Resolution: check the CMS ICD-10-CM annual release for that date.

How Pabau keeps turkey-strike claims clean

Without a system check, a coder learns about a missing injury code or a wrong 7th character only when the denial arrives. The claim then needs a correction, a resubmission and another wait for payment.

Pabau holds the injury code, W61.42XA and the companion Y-codes on one claim. Its claims management software lets your team review the full code set while the encounter is still open. Coders can fix sequencing before the claim leaves the practice.

Intake forms and claims sit in the same record, so the mechanism the provider documents is the one the coder sees. That keeps strike and peck codes from getting crossed.

Reduce coding errors before they reach the payer

Pabau keeps ICD-10-CM external cause codes next to the injury code in the patient record. Every claim leaves with the complete code set payers expect.

Book a demo

Conclusion

W61.42XA is precise, but only when the chart backs it up. The code turns on two facts, the bird and the mechanism. A note that says “struck by a turkey” supports it, while one that says “pecked” belongs under W61.43XA.

Sequencing is the other half. The injury code goes first, W61.42XA follows, and the 7th character moves from A to D once active treatment ends.

Practices that capture species and mechanism at intake avoid the six denial triggers above. The medical billing guide shows where coding fits in the revenue cycle. To see how Pabau handles external cause coding from intake to submission, book a demo.

Continue your research

Need to understand how denial codes work after a W61.42XA rejection? Denial codes in medical billing explains CARC and RARC reason codes and the steps to resolve them.

Want a clearer picture of the claim submission process end to end? Medical claims clearinghouse guide covers how claims move from the practice to the payer and where errors are caught.

Looking for guidance on ICD-10-CM documentation best practices? Medical billing compliance outlines the documentation standards payers audit against.

Frequently asked questions