S31.616D — Laceration without foreign body of abdominal wall, right flank with penetration into peritoneal cavity, subsequent encounter
Is S31.616D billable?
Yes — S31.616D is billable for FY2027. S31.616D is a valid, billable ICD-10-CM code at the highest level of specificity in its branch. S31.616D may be submitted for encounters from October 1, 2026 through September 30, 2027.
S31.616D at a glance
| Code | S31.616D |
|---|---|
| Description | Laceration without foreign body of abdominal wall, right flank with penetration into peritoneal cavity, subsequent encounter |
| Billable | Yes |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
| 7th character "D" | subsequent encounter |
What does the 7th character "D" mean in S31.616D?
In S31.616D, the 7th character D means subsequent encounter. The 7th character is required for S31.616D to be a valid, complete code.
Same condition, different episode of care — switch the 7th character:
Which MS-DRGs does S31.616D group to?
S31.616D sits in MDC 23 and helps define the logic of 2 MS-DRGs (version 44, FY2027). Which one a stay actually groups to also depends on procedures and secondary diagnoses.
- 949Aftercare with CC/MCCmedical
- 950Aftercare without CC/MCCmedical
How is S31.616D listed in the Alphabetic Index?
The Alphabetic Index lists these routes under S31.616, the nearest indexed parent of S31.616D. Use them to find the family, then select the specific code.
- Laceration › flank › right › with › penetration into peritoneal cavity
Excludes1 — never code together — inherited from S31
The conditions below can never be reported together with S31.616D on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.
Use additional code — inherited from Chapter 19
Report an additional code alongside S31.616D to fully describe the condition. S31.616D 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 S31.616D, but a patient may have both at the same time. When documentation supports it, S31.616D and the excluded code may both be reported.
Excludes2 — not included here — inherited from S30-S39
The conditions below are not part of S31.616D, but a patient may have both at the same time. When documentation supports it, S31.616D and the excluded code may both be reported.
Excludes2 — not included here — inherited from S31
The conditions below are not part of S31.616D, but a patient may have both at the same time. When documentation supports it, S31.616D and the excluded code may both be reported.
Code also — inherited from S31
Two codes may be needed to describe the condition fully. Whether S31.616D is sequenced first depends on the reason for the encounter.
How long has S31.616D existed?
S31.616D first appears in FY2026.
Derived from the official order files for FY2016–FY2026. FY2017 and FY2020 publish no order file, so those years are not covered.