Skip to main content

S55.211D vs S55.212D

S55.211D (Laceration of vein at forearm level, right arm, subsequent encounter) compared with S55.212D (Laceration of vein at forearm level, left arm, subsequent encounter), from the official CMS tabular data. S55.211D and S55.212D code the same condition on opposite sides.

Relationship

Review

Laterality relationship

S55.211D
Right
Laceration of vein at forearm level, right arm, subsequent encounter
S55.212D
Left
Laceration of vein at forearm level, left arm, subsequent encounter

Same condition; these differ only in which side is documented.

These codes share a category and title and differ only in the side affected. The documentation decides which applies, and a bilateral code is reported only where the code set provides one.

Source: ICD-10-CM tabular list (laterality variant derived from the code title)

Can these codes be reported together?

Same condition, opposite side. S55.211D and S55.212D name the same condition on opposite sides of the body.

Same category and title, differing only in which side is affected — the documentation decides which one applies, and a bilateral code is reported only where the code set provides one.

Side by side

S55.211DLaceration of vein at forearm level, right arm, subsequent encounterS55.212DLaceration of vein at forearm level, left arm, subsequent encounter
Billing statusBillableBillable
ClassificationS00-T88 — Injury, Poisoning and Certain Other Consequences of External Causes (S00-T88)S00-T88 — Injury, Poisoning and Certain Other Consequences of External Causes (S00-T88)
DefinitionLaceration of vein at forearm level, right arm, subsequent encounter is a billable ICD-10-CM diagnosis code (S55.211D).Laceration of vein at forearm level, left arm, subsequent encounter is a billable ICD-10-CM diagnosis code (S55.212D).
7th characterThe appropriate 7th character is to be added to each code from category S55The appropriate 7th character is to be added to each code from category S55

Derived from the official CMS ICD-10-CM tabular data (FY2026). Not billing advice; verify sequencing rules for the encounter. All data sources