S06.380D — Contusion, laceration, and hemorrhage of brainstem without loss of consciousness, subsequent encounter
Is S06.380D billable?
Yes — S06.380D is billable for FY2027. S06.380D is a valid, billable ICD-10-CM code at the highest level of specificity in its branch. S06.380D may be submitted for encounters from October 1, 2026 through September 30, 2027.
S06.380D at a glance
| Code | S06.380D |
|---|---|
| Description | Contusion, laceration, and hemorrhage of brainstem without loss of consciousness, 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 S06.380D?
In S06.380D, the 7th character D means subsequent encounter. The 7th character is required for S06.380D to be a valid, complete code.
Same condition, different episode of care — switch the 7th character:
Which MS-DRGs does S06.380D group to?
S06.380D 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 S06.380D listed in the Alphabetic Index?
The Alphabetic Index lists these routes under S06.38, the nearest indexed parent of S06.380D. Use them to find the family, then select the specific code.
- Contusion › brainstem (skin surface intact)
- Injury › brainstem
- Laceration › brainstem
- Hemorrhage, hemorrhagic › brainstem › traumatic (concealed)
Excludes1 — never code together — inherited from S06
The conditions below can never be reported together with S06.380D on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.
- head injury NOS (S09.90)
Use additional code — inherited from Chapter 19
Report an additional code alongside S06.380D to fully describe the condition. S06.380D is sequenced first.
- code to identify any retained foreign body, if applicable (Z18.-)
Use additional code — inherited from S06
Report an additional code alongside S06.380D to fully describe the condition. S06.380D is sequenced first.
- code, if applicable, to identify mild neurocognitive disorders due to known physiological condition (F06.7-)
Use additional code — inherited from S06.3
Report an additional code alongside S06.380D to fully describe the condition. S06.380D is sequenced first.
- code, if applicable, for traumatic brain compression or herniation (S06.A-)
Excludes2 — not included here — inherited from Chapter 19
The conditions below are not part of S06.380D, but a patient may have both at the same time. When documentation supports it, S06.380D and the excluded code may both be reported.
Excludes2 — not included here — inherited from S00-S09
The conditions below are not part of S06.380D, but a patient may have both at the same time. When documentation supports it, S06.380D and the excluded code may both be reported.
- burns and corrosions (T20-T32)
- effects of foreign body in ear (T16)
- effects of foreign body in larynx (T17.3)
- effects of foreign body in mouth NOS (T18.0)
- effects of foreign body in nose (T17.0-T17.1)
- effects of foreign body in pharynx (T17.2)
- effects of foreign body on external eye (T15.-)
- frostbite (T33-T34)
- insect bite or sting, venomous (T63.4)
Excludes2 — not included here — inherited from S06.3
The conditions below are not part of S06.380D, but a patient may have both at the same time. When documentation supports it, S06.380D and the excluded code may both be reported.
Code also — inherited from S00-S09
Two codes may be needed to describe the condition fully. Whether S06.380D is sequenced first depends on the reason for the encounter.
- for any associated infection
Code also — inherited from S06
Two codes may be needed to describe the condition fully. Whether S06.380D is sequenced first depends on the reason for the encounter.
How long has S06.380D existed?
S06.380D 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.