S35.321 — Laceration of splenic vein
Is S35.321 billable?
No — S35.321 is a non-billable header code. S35.321 groups more specific codes and cannot be submitted on a claim. A valid ICD-10-CM code must be reported at the highest level of specificity available in its branch. Select one of the 3 billable codes beneath S35.321.
S35.321 at a glance
| Code | S35.321 |
|---|---|
| Description | Laceration of splenic vein |
| Billable | No — header code |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
How is S35.321 listed in the Alphabetic Index?
These are the routes through the Alphabetic Index that lead to S35.321. They show the wording a clinician may have documented, which often differs from the Tabular description.
- Injury › blood vessel NEC › splenic › vein › laceration
Use additional code — inherited from Chapter 19
Report an additional code alongside S35.321 to fully describe the condition. S35.321 is sequenced first.
- code to identify any retained foreign body, if applicable (Z18.-)
Excludes2 — not included here — inherited from Chapter 19
The conditions below are not part of S35.321, but a patient may have both at the same time. When documentation supports it, S35.321 and the excluded code may both be reported.
Excludes2 — not included here — inherited from S30-S39
The conditions below are not part of S35.321, but a patient may have both at the same time. When documentation supports it, S35.321 and the excluded code may both be reported.
Code also — inherited from S35
Two codes may be needed to describe the condition fully. Whether S35.321 is sequenced first depends on the reason for the encounter.
- any associated open wound (S31.-)
What codes fall under S35.321? (3)
How long has S35.321 existed?
S35.321 has been in ICD-10-CM since at least FY2016, the earliest fiscal year on record here.
Derived from the official order files for FY2016–FY2026. FY2017 and FY2020 publish no order file, so those years are not covered.