ICDcodes.org
FY2027

T67.01XDHeatstroke and sunstroke, subsequent encounter

Billable

Is T67.01XD billable?

Yes — T67.01XD is billable for FY2027. T67.01XD is a valid, billable ICD-10-CM code at the highest level of specificity in its branch. T67.01XD may be submitted for encounters from October 1, 2026 through September 30, 2027.

T67.01XD at a glance

CodeT67.01XD
DescriptionHeatstroke and sunstroke, subsequent encounter
BillableYes
Code setICD-10-CM FY2027
Valid for encountersOctober 1, 2026 – September 30, 2027
7th character "D"subsequent encounter

What does the 7th character "D" mean in T67.01XD?

In T67.01XD, the 7th character D means subsequent encounter. The 7th character is required for T67.01XD to be a valid, complete code.

Same condition, different episode of care — switch the 7th character:

Which MS-DRGs does T67.01XD group to?

T67.01XD 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 T67.01XD listed in the Alphabetic Index?

The Alphabetic Index lists these routes under T67.01, the nearest indexed parent of T67.01XD. Use them to find the family, then select the specific code.

  • Ictus solaris, solis
  • Insolation (sunstroke)
  • Siriasis
  • Sunstroke
  • Thermoplegia
  • Apoplexia, apoplexy, apoplecticheat
  • Feverheat (inanition) (of unknown origin) (persistent) (with chills) (with rigor)
  • Feverthermic (inanition) (of unknown origin) (persistent) (with chills) (with rigor)

Inclusion terms

Alternative wording in documentation that is classified to T67.01XD.

  • Heat apoplexy
  • Heat pyrexia
  • Siriasis
  • Thermoplegia

Excludes1 — never code together — inherited from T67

The conditions below can never be reported together with T67.01XD on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.

  • erythema [dermatitis] ab igne (L59.0)
  • malignant hyperpyrexia due to anesthesia (T88.3)
  • radiation-related disorders of the skin and subcutaneous tissue (L55-L59)

Use additional code — inherited from Chapter 19

Report an additional code alongside T67.01XD to fully describe the condition. T67.01XD is sequenced first.

  • code to identify any retained foreign body, if applicable (Z18.-)

Use additional code — inherited from T67.0

Report an additional code alongside T67.01XD to fully describe the condition. T67.01XD is sequenced first.

  • code(s) to identify any associated complications of heatstroke, such as:
  • coma and stupor (R40.-)
  • rhabdomyolysis (M62.82)
  • systemic inflammatory response syndrome (R65.1-)

Excludes2 — not included here — inherited from Chapter 19

The conditions below are not part of T67.01XD, but a patient may have both at the same time. When documentation supports it, T67.01XD and the excluded code may both be reported.

  • birth trauma (P10-P15)
  • obstetric trauma (O70-O71)

Excludes2 — not included here — inherited from T67

The conditions below are not part of T67.01XD, but a patient may have both at the same time. When documentation supports it, T67.01XD and the excluded code may both be reported.

  • burns (T20-T31)
  • sunburn (L55.-)
  • sweat disorder due to heat (L74-L75)

Code also — inherited from T66-T78

Two codes may be needed to describe the condition fully. Whether T67.01XD is sequenced first depends on the reason for the encounter.

  • , if applicable, place of occurrence, such as:
  • highway rest stop (Y92.523)
  • school (private) (public) (state) as the place of occurrence of the external cause (Y92.21-)
  • service areas as the place of occurrence of the external cause (Y92.52-)
  • single-family non-institutional (private) house as the place of occurrence of the external cause (Y92.01-)
  • transport vehicle as the place of occurrence of the external cause (Y92.81-)

How long has T67.01XD existed?

T67.01XD first appears in FY2021 (FY2020 is not available, so it may have appeared then).

Derived from the official order files for FY2016–FY2026. FY2017 and FY2020 publish no order file, so those years are not covered.