Skip to main content

W44.H9XA vs Y09

W44.H9XA (Other sharp object entering into or through a natural orifice, initial encounter) compared with Y09 (Assault by unspecified means), from the official CMS tabular data.

Summary

These codes should not be reported together because W44.H9XA’s tabular entry lists Y09 under Excludes1.

Official rule
What is different?

The conditions named.W44.H9XA is “Other sharp object entering into or through a natural orifice, initial encounter”; Y09 is “Assault by unspecified means”.

Registry fact

Can these codes be reported together?

No.W44.H9XA’s entry carries an Excludes1 note covering Y09: “assault (X92-Y09)”. Both may be reported only when the documentation shows the two conditions are unrelated to each other (ICD-10-CM Official Guidelines, Section I.A.12.a).

Official ruleGuide: Excludes1 vs Excludes2

Is there an Excludes1 relationship?

Yes.W44.H9XA’s tabular entry: “assault (X92-Y09)”. The note covers Y09.

Official ruleGuide: Excludes1 vs Excludes2

Is there an Excludes2 relationship?

None.Neither entry carries an Excludes2 note that names the other code. W44.H9XA carries 3 Excludes2 notes covering other codes; the side-by-side table quotes them.

Official rule

Is one more specific?

Not comparable.The codes sit in different categories; specificity is only comparable within one category.

Is one a parent or header code?

No.Both are billable codes, and neither contains the other.

Registry fact

Are there sequencing instructions?

None.Neither entry carries a Code First or Use Additional Code note that names the other.

Official rule

Are there other coding relationships?

None found.No laterality, encounter-phase, Table of Neoplasms, Table of Drugs and Chemicals, or history-versus-active-disease relationship links these codes.

MedCoder-derived

Official rule: a tabular instructional note or a section of the ICD-10-CM Official Guidelines, quoted as published. Registry fact: the codes’ own published attributes (titles, billable status, position in the hierarchy, code set). MedCoder-derived: a reading MedCoder computes from those facts; it is not itself a rule. How to read the labels

Can these codes be reported together?

Conflict

Excludes1 conflict

W44.H9XA
Other sharp object entering into or through a natural orifice, initial encounter
↔
Y09
Assault by unspecified means

What we found

No — do not report together.W44.H9XA carries an Excludes1 note covering Y09: “assault (X92-Y09)”

Sole exception: when the two conditions are documented as unrelated to each other (ICD-10-CM Official Guidelines, Section I.A.12.a).

What to review

Report one of the two. Both may be reported only when the documentation shows the two conditions are unrelated to each other.

Guide: Excludes1 vs Excludes2Check these on a claim

Why it matters

An Excludes1 note means the two conditions cannot occur together, so the pair should not be reported for the same encounter. The sole exception is when the conditions are documented as unrelated to each other.

Source / rule

CMS ICD-10-CM tabular instructional notes; ICD-10-CM Official Guidelines, Section I.A.12.a

Official guidance behind these answers

  • Section I.A.12.a — Excludes1 · applies to: Excludes1

    A type 1 Excludes note is a pure excludes note. It means “NOT CODED HERE!” An Excludes1 note indicates that the code excluded should never be used at the same time as the code above the Excludes1 note. An Excludes1 is used when two conditions cannot occur together, such as a congenital form versus an acquired form of the same condition. An exception to the Excludes1 definition is the circumstance when the two conditions are unrelated to each other. If it is not clear whether the two conditions involving an Excludes1 note are related or not, query the provider. For example, code F45.8, Other somatoform disorders, has an Excludes1 note for "sleep related teeth grinding (G47.63)," because "teeth grinding" is an inclusion term under F45.8. Only one of these two codes should be assigned for teeth grinding. However psychogenic dysmenorrhea is also an inclusion term under F45.8, and a patient could have both this condition and sleep related teeth grinding. In this case, the two conditions are clearly unrelated to each other, and so it would be appropriate to report F45.8 and G47.63 together.

    ICD-10-CM Official Guidelines FY2026

Quoted from the ICD-10-CM Official Guidelines for Coding and Reporting in effect for the release shown. The tabular notes above are the code-level instruction; these sections are the convention that says how such a note is applied. Source document (CMS PDF) · Release and checksum

Side by side

W44.H9XAOther sharp object entering into or through a natural orifice, initial encounterY09Assault by unspecified means
Billing statusBillableBillable
ClassificationV00-Y99 — External Causes of Morbidity (V00-Y99)V00-Y99 — External Causes of Morbidity (V00-Y99)
DefinitionOther sharp object entering into or through a natural orifice, initial encounter is a billable ICD-10-CM diagnosis code (W44.H9XA).Assault by unspecified means is a billable ICD-10-CM diagnosis code (Y09).
7th characterThe appropriate 7th character is to be added to each code from category W44—
Includes
Shard pottery entering into or through a natural orifice
homicide
injuries inflicted by another person with intent to injure or kill, by any means
Assassination (attempted) NOS
Homicide (attempted) NOS
Excludes1
assault (X92-Y09)
contact or collision with animals or persons (W50-W64)
exposure to inanimate mechanical forces involving military or war operations (Y36.-, Y37.-)
intentional self-harm (X71-X83)
injuries due to legal intervention (Y35.-)
injuries due to operations of war (Y36.-)
injuries due to terrorism (Y38.-)
Excludes2
contact with other sharp objects (W26)
contact with sharp glass (W25)
foreign body or object entering through skin (W45)
—

Notes are the code’s own tabular entry, quoted as published. A note that names the other code is the one the verdict above rests on.

Edit this comparisonCheck a whole claim

Derived from the official CMS ICD-10-CM tabular data (FY2026). A coding-rule comparison, not billing advice: payer-specific edits and medical-necessity policy are outside its scope. All data sources