ICD code W55.39XA – Other contact with other hoof stock

Key takeaways

W55.39XA covers contact with other hoof stock, such as goats and sheep, that was neither a bite nor a strike, at the initial encounter.

Bites by other hoof stock go to W55.31XA, and kicks, butts or other strikes go to W55.32XA.

W55.39XA is an external cause code, so it always follows an injury code and is never the principal diagnosis.

Never swap it for W55.59XA, which means other contact with raccoon, not hoof stock.

ICD-10 Code W55.39XA: Quick reference

ICD-10 Code W55.39XA is the billable ICD-10-CM code for other contact with other hoof stock, such as goats and sheep, at the initial encounter. It has been valid for encounters on or after October 1, 2015. The table below captures the fields a coder checks first.

What W55.39XA means: Code descriptor and clinical definition

W55.39XA records contact with other hoof stock that was neither a bite (W55.31XA) nor a strike (W55.32XA). Think of a sheep pinning a handler against a gate, or a goat trampling a farm worker’s foot.

The ICD-10-CM tabular list names two animals under subcategory W55.3: goats and sheep. Horses sit in W55.1, cattle in W55.2 and pigs in W55.4, so those species never land here. For any other hoofed species, check the Alphabetic Index before you assign the code.

Category W55 also includes contact with the saliva, feces or urine of a mammal. A handler exposed to goat or sheep waste, with no bite or strike, can therefore fall under W55.39XA.

As an external cause code, W55.39XA explains how an injury happened rather than what the injury is. The injury code comes first, and W55.39XA follows to tell the payer what caused it.

Where W55.39XA sits in the ICD-10-CM hierarchy

The code’s parent structure decides which animal and contact type it can describe. The full path from chapter to the W55.39XA code is shown below.

Two sibling codes share subcategory W55.3 with W55.39XA. W55.31XA covers being bitten by other hoof stock, and W55.32XA covers being struck by it. W55.39XA takes the remaining contact types, such as pressure, crushing, entrapment or trampling. The decision path below shows how the species, the contact and the encounter settle the code.

Watch the neighboring subcategory W55.5, which covers raccoons. W55.59XA reads almost the same as W55.39XA but means other contact with raccoon, so one wrong digit changes the animal on the claim.

The 7th character extension: XA, XD, and XS explained

W55.39XA follows the standard 7th character convention for injury and external cause codes. The X is a placeholder that fills the empty sixth position, and the final letter records the encounter type.

The A extension applies to every visit where the patient receives active treatment, including visits after the first. A patient who saw another provider first still takes A at your practice while active treatment continues.

What W55.39XA covers and what it excludes

The descriptor is narrow, so most routing errors come from the species or the contact type. The table below contrasts covered scenarios with the correct code for excluded ones.

Category W55 also carries four Excludes1 notes. An animal being ridden is coded as a transport accident (V80), and a bite or strike by a dog goes to W54. Rodents go to W53, and marine mammals go to W56.

How to code W55.39XA correctly: Step-by-step

Correct sequencing is the most reliable way to avoid a rejection on the first submission. Follow these four steps in order for every encounter involving this code.

1. Assign the injury code first. Identify the injury, such as a contusion, laceration or fracture, and list it first. Per the CMS ICD-10-CM guidelines, an external cause code is never the principal or first-listed diagnosis.
2. Add W55.39XA after the injury code. Confirm the notes describe contact other than a bite or a strike. A bite routes to W55.31XA, and a kick or butt routes to W55.32XA.
3. Add place, activity and status codes where the payer wants them. Common choices are Y92.71 (barn), Y93.K9 (other activity involving animal care) and Y99.0 (civilian activity done for income or pay). Report each one only at the initial encounter.
4. Match the 7th character to the encounter type. Use A while active treatment continues, D for routine follow-up during healing and S for a late effect.

S20.211A (contusion of right front wall of thorax, initial encounter) is a typical injury code after a sheep pins a handler. S30.11XA (contusion of abdominal wall, initial encounter) fits a crush against a pen rail. Document the body region and side so the most specific injury code is supported.

Neighboring codes most often confused with W55.39XA

Subcategory W55.3 holds three codes that coders often interchange, and two nearby subcategories add more risk. The clinical notes must document the animal and the nature of the contact to support the code.

“Patient injured by goat on farm” is not enough documentation. The chart must describe how contact occurred, which body part was affected and the species involved, per the CDC/NCHS ICD-10-CM coding guidelines.

Documentation requirements to support W55.39XA

Payers review external cause codes when the record does not clearly support them. For W55.39XA, the chart should contain the following elements to hold up in a retrospective review.

• Species identification: Name the animal, such as a goat or a sheep. Vague wording such as “a farm animal” can prompt a coder query before any W55 code is assigned.
• Nature of contact: State that the contact was not a bite and not a kick. Phrases like “crushed by,” “trapped between” or “trampled by” support W55.39XA.
• Circumstances of encounter: Note the setting, such as a barn, a farm field or a petting zoo, because place-of-occurrence coding depends on it.
• Body region affected: Record the region and side to support the most specific injury code as principal diagnosis.
• Encounter type: Confirm whether this is an active-treatment visit (A), a routine follow-up (D) or a sequela visit (S).
• Work-related details: If the injury happened at work, document employment status, the task under way and the date the employer was told.

Strong documentation also supports medical billing compliance when a payer audits an injury claim.

Payer requirements and prior authorization considerations

Medicare, Medicaid and commercial payers accept W55.39XA as a secondary code. The rules for reporting external cause codes still vary by payer type.

Medicare and Medicaid

The ICD-10-CM guidelines set no national requirement to report external cause codes. Reporting becomes mandatory where a state mandate or a payer policy requires it. Check each plan’s policy before you treat the code as optional.

Workers’ compensation

Workers’ compensation carriers use external cause codes to establish how and where an occupational injury happened. W55.39XA appears most often in farm injury claims involving sheep and goats. Place and activity code requirements vary by state and by carrier.

Pabau, the practice management platform we build, connects to the Claim.MD clearinghouse for electronic claim submission. Clearinghouse rejections then show up before a claim reaches the payer’s adjudication stage, as our Claim.MD clearinghouse guide explains.

Commercial payers

Most commercial insurers accept W55.39XA as a secondary code without prior authorization. The injury it accompanies may still need authorization, such as a fracture that requires surgical repair. Confirm insurance eligibility verification and authorization based on the principal diagnosis code, not the external cause code.

Common claim denial reasons for ICD-10 Code W55.39XA

Denials on W55.39XA claims follow predictable patterns. The table below maps each one to a likely CARC (Claim Adjustment Reason Code) to support your denial management workflow.

Review denial codes against your ERA data after each remittance cycle. It is the fastest way to spot repeat W55.39XA errors before they spread across claims.

W55.39XA in ICD-11: What to know

ICD-11, published by the World Health Organization, restructures external cause coding compared with ICD-10-CM. CMS has not announced a US transition date to ICD-11, and ICD-10-CM updates continue each October.

No action is needed for current billing. Keep using ICD-10 Code W55.39XA for all US claims until CMS issues transition requirements.

How claims management software supports W55.39XA claims

Coding W55.39XA correctly depends on what the clinician wrote: the species, the contact type and the encounter. When notes sit in one system and claims in another, those details get retyped or lost.

In Pabau, the patient record, the treatment note and the invoice live in the same place. Your coder builds the claim in Pabau’s claims software for practices, starting from the note the clinician signed.

The bite, strike or other-contact wording stays next to the code that depends on it. Fewer claims go out with a sibling code the notes don’t support.

Keep injury claims tied to the clinical note

Pabau keeps the treatment note, the diagnosis codes and the claim in one patient record, so coders work from what the clinician wrote. See how claims management fits your injury and occupational health workflow.

Book a demo

Conclusion

W55.39XA does one narrow job: it records non-bite, non-strike contact with goats, sheep and other hoof stock. It always sits after the injury it explains.

Make the subcategory digit your first check on every livestock claim, because W55.59XA describes a raccoon. Then confirm the contact type and the 7th character against the note before the claim goes out.

If your team bills farm or occupational injuries, book a demo to see how Pabau keeps the note and the claim together.

Continue your research

Need to understand how clearinghouse claim validation works? Claim.MD clearinghouse overview explains how electronic claim validation catches sequencing errors before payer submission.

Want a walkthrough of clean claim requirements? Submitting a clean claim covers the field-by-field requirements that keep external cause code claims out of the denial queue.

Looking to understand the full medical billing process? Medical billing fundamentals gives context on how external cause codes fit into the end-to-end revenue cycle workflow.

Frequently asked questions