S92.101P — Unspecified fracture of right talus, subsequent encounter for fracture with malunion
Is S92.101P billable?
Yes, but S92.101P is an unspecified code. S92.101P is a valid, billable ICD-10-CM code for encounters from October 1, 2026 through September 30, 2027. However, S92.101P is an unspecified or catch-all code. Payers apply additional scrutiny to unspecified codes and many deny them when the medical record supports a more specific option, so check the documentation before selecting S92.101P — the more specific alternatives are listed below.
More specific alternatives
- S92.111PDisplaced fracture of neck of right talus, subsequent encounter for fracture with malunion
- S92.121PDisplaced fracture of body of right talus, subsequent encounter for fracture with malunion
- S92.131PDisplaced fracture of posterior process of right talus, subsequent encounter for fracture with malunion
- S92.141PDisplaced dome fracture of right talus, subsequent encounter for fracture with malunion
- S92.151PDisplaced avulsion fracture (chip fracture) of right talus, subsequent encounter for fracture with malunion
- S92.191POther fracture of right talus, subsequent encounter for fracture with malunion
S92.101P at a glance
| Code | S92.101P |
|---|---|
| Description | Unspecified fracture of right talus, subsequent encounter for fracture with malunion |
| Billable | Yes |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
| 7th character "P" | subsequent encounter for fracture with malunion |
What does the 7th character "P" mean in S92.101P?
In S92.101P, the 7th character P means subsequent encounter for fracture with malunion. The 7th character is required for S92.101P to be a valid, complete code.
Same condition, different episode of care — switch the 7th character:
- Ainitial encounter for closed fractureS92.101A
- Binitial encounter for open fractureS92.101B
- Dsubsequent encounter for fracture with routine healingS92.101D
- Gsubsequent encounter for fracture with delayed healingS92.101G
- Ksubsequent encounter for fracture with nonunionS92.101K
- Psubsequent encounter for fracture with malunionS92.101P
- SsequelaS92.101S
Which MS-DRGs does S92.101P group to?
S92.101P sits in MDC 08 and helps define the logic of 3 MS-DRGs (version 44, FY2027). Which one a stay actually groups to also depends on procedures and secondary diagnoses.
- 564Other Musculoskeletal System and Connective Tissue Diagnoses with MCCmedical
- 565Other Musculoskeletal System and Connective Tissue Diagnoses with CCmedical
- 566Other Musculoskeletal System and Connective Tissue Diagnoses without CC/MCCmedical
As a secondary diagnosis, S92.101P is a complication or comorbidity (CC), which can move a stay into a higher-paying DRG.
How is S92.101P listed in the Alphabetic Index?
The Alphabetic Index lists these routes under S92.10, the nearest indexed parent of S92.101P. Use them to find the family, then select the specific code.
- Fracture, traumatic › tarsal bone › talus (abduction) (adduction) (separation)
Use additional code — inherited from Chapter 19
Report an additional code alongside S92.101P to fully describe the condition. S92.101P 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 S92.101P, but a patient may have both at the same time. When documentation supports it, S92.101P and the excluded code may both be reported.
Excludes2 — not included here — inherited from S90-S99
The conditions below are not part of S92.101P, but a patient may have both at the same time. When documentation supports it, S92.101P and the excluded code may both be reported.
Excludes2 — not included here — inherited from S92
The conditions below are not part of S92.101P, but a patient may have both at the same time. When documentation supports it, S92.101P and the excluded code may both be reported.
How long has S92.101P existed?
S92.101P 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.