ICD-10 code S30.9AXS: Superficial flank injury, sequela

Key takeaways

ICD-10 code S30.9AXS reports the sequela of an unspecified superficial injury of the flank.

The flank is the side of the torso between the lower ribs and the top of the hip.

S30.9A and its three 7th character codes are new for FY2026, effective October 1, 2025.

S30.9A on its own is not billable, so every claim needs the 7th character A, D, or S.

Use the S extension only after the original injury has healed and a late effect remains.

ICD-10 code S30.9AXS reports the sequela of an unspecified superficial injury of the flank. It arrived with the FY2026 update on October 1, 2025. Until then, flank injuries disappeared into broader abdominal codes.

Two mistakes drive most denials on this code. Coders copy the old S30.9 descriptor, which still names the abdomen, lower back, pelvis and external genitals. Or they drop the 7th character and submit the non-billable parent. Both are avoidable once you know what the code says now.

ICD-10 code S30.9AXS covers the flank, not the whole abdomen

S30.9AXS is a billable ICD-10-CM diagnosis code. Its full descriptor is unspecified superficial injury of flank, sequela. The code took effect on October 1, 2025 as part of the FY2026 update, and it stays valid through September 30, 2026. You can confirm the current release on the CMS ICD-10 codes page.

The longer descriptor you may remember belongs one level up. Category S30.9 still reads “unspecified superficial injury of abdomen, lower back, pelvis and external genitals”. That phrase describes the whole category. It does not describe this subcode, and reusing it on a claim narrative is how the flank detail gets lost.

The hierarchy explains why the wrong descriptor spreads so easily. Three levels sit above S30.9AXS, and two of them still carry the broad wording. Only the bottom three rows can go on a claim.

S30, S30.9 and S30.9A are structural headers in the Tabular List. None of them can be submitted, and payer edits reject them on sight. The 2026 ICD-10-CM entry flags S30.9A as non-billable for exactly this reason.

Where the flank starts and where it stops

The flank is the side of the torso between the lower ribs and the top of the hip bone. ICD-10-CM calls it the latus region. It wraps from the side of the body around toward the back, sitting lateral to the abdomen and above the iliac crest.

Two boundaries matter on a claim. The flank is not the hip, and the S30 block carries a Type 2 excludes note pointing hip injuries to S70. The flank is also not the abdominal wall, which keeps its own code at S30.92. Get either boundary wrong and the code changes.

“Unspecified” carries a narrow meaning here. It describes a record that confirms a superficial injury but never names the type. FY2026 also gave the flank a full set of typed codes, so check these first:

• S30.13, contusion of flank (latus) region
• S30.81A, abrasion of flank
• S30.82A, blister (nonthermal) of flank
• S30.84A, external constriction of flank
• S30.85A, superficial foreign body of flank
• S30.86A, insect bite (nonvenomous) of flank
• S30.87A, other superficial bite of flank

Each of those takes the same 7th characters, so their sequela forms also end with the S extension. Reach for S30.9A only when none of them is supportable. That is the specificity principle in practice. Code to the highest detail the record supports, and no higher.

The 7th character is what makes S30.9AXS billable

S30.9A becomes billable only once a 7th character names the encounter type. Three options exist, and each one has to be supported by what the note says. The AAPC Codify entry lists all three.

The X in the 6th position is a placeholder, not a typo. S30.9A has no 6th character subdivision, so the X holds the slot and keeps the 7th character in position seven. Write S30.9AS instead and the string is invalid, which means an instant rejection.

Three extensions cover this code, and other Chapter 19 families run longer. Fracture codes add characters for healing status, which is how S92.209K reports a nonunion. A superficial injury never needs that much detail.

Sequela or subsequent encounter? Healing decides

Choose S when the original wound has healed and a new problem remains because of it. Choose D when the wound itself is still the thing you are treating. That single question settles most of these claims. Mixing the two up is the fastest route to an audit flag.

Use S30.9AXS (sequela) when:

• The original flank injury has fully healed.
• The patient presents with a late effect of it, such as scar tissue, chronic pain, or a functional limitation.
• The note links that current problem to the earlier injury.
• The late effect, not the original wound, is the reason for today’s visit.

Use S30.9AXD (subsequent encounter) when:

• The flank injury is still healing.
• The patient is back for wound care, dressing changes, or routine monitoring.
• Active treatment has finished but recovery is ongoing.

Here is how that looks in a chart. A cyclist catches their right flank on a fence in March, and the note records a superficial injury without naming the type. The wound is dressed and healed by April.

In August they return with a tight, painful scar over the same area. So April’s visits were D, and August is S.

One more sequencing rule catches people out. Sequence the residual condition first, then let S30.9AXS explain where it came from. So the scar or the chronic pain leads on the claim. That order holds right across the injury chapter, from S60.219S to S56.599S.

Your note has to show the injury already healed

A sequela claim lives or dies on the causal link in the clinical note. Payers want to see that today’s problem came from a specific earlier injury. Run through these five elements before the claim goes out.

• Body region. The note names the flank. “Trunk” or “side” is too vague, and “abdomen” sends the coder to a different subcode.
• Injury type. The note confirms a superficial injury and does not name a type. If it says abrasion or contusion, use the typed code instead.
• Encounter type. The note states that the original injury has healed and that the visit concerns its late effect.
• Causal link. Something like “scar pain over the right flank following the superficial injury sustained on March 4” does the job.
• Date of the original injury. Not strictly required, but it strengthens the link and cuts your audit risk.

Two sections of the FY2026 ICD-10-CM Official Guidelines govern this. Section I.B.10 sets the general sequela rules, including sequencing. Section I.C.19.a explains how the 7th characters work across Chapter 19 injury codes.

Most of this is easier to capture at the visit than to reconstruct at billing. Practices using structured digital intake forms can prompt for the injury date and cause up front, which is the detail sequela claims usually lack.

Five mistakes that get S30.9AXS denied

Because the code is less than a year old, the errors cluster in predictable places. Here are the five worth checking on every claim.

1. Submitting S30.9A on its own. The parent is a header code. Without a 7th character it never reaches adjudication.
2. Dropping the X placeholder. S30.9AS is not a code. The X has to sit in the 6th position.
3. Reusing the old descriptor. If the note describes the abdominal wall or the lower back, the code is S30.92 or S30.91, not S30.9A.
4. Choosing S while the wound heals. Routine follow-up on an open or healing flank injury is D.
5. Leading with the injury code. Sequence the residual condition first, and let S30.9AXS support it.

A sixth trap is quieter. Payer edits and internal code lists were built before FY2026, so some still do not recognize the flank codes. If a clean claim comes back rejected as invalid, check the payer’s code set date before you rework the note.

S30.9AXS is too new to have an ICD-9 crosswalk

There is no General Equivalence Mapping for this code, and there never will be. CMS published its final set of GEMs for FY2018 and stopped maintaining them after that. S30.9AXS did not exist until October 1, 2025, so it was never in scope for the mappings.

That matters if your team still runs legacy crosswalk lookups. A tool that returns an ICD-9 equivalent for S30.9AXS is guessing. For pre-October 2015 records, unspecified trunk injuries sat under ICD-9 code 959.19, but that is a rough concept match rather than an official mapping.

Date of service governs everything here. Encounters on or after October 1, 2025 can use S30.9AXS. Anything earlier has to use the code set in force at the time, and the flank codes were not part of it. You can check any code’s history in the CDC ICD-10-CM web tool.

How Pabau keeps flank injury coding tied to the note

Most denials on codes like this one start with a fragmented record. The original injury sits in one visit note and the follow-up sits in another. Months later, someone builds the sequela claim from memory.

Pabau keeps that history in a single patient file, so the injury date and the causal link survive the wait. Pabau Scribe, our AI scribe, drafts the treatment note during the consultation itself. Healing status gets written down while it is fresh.

Medical records management keeps every note, form, and photo on the same record. The claims workflow then submits from that record rather than a separate billing silo.

For a physical therapy practice or a sports medicine team seeing injury sequelae every week, that saves hours of chart archaeology.

Keep injury history and coding in one record

Pabau links every treatment note, intake form, and claim to the same patient record. The causal link behind a sequela code stays where you can find it.

Book a demo

Conclusion

The safest habit with S30.9AXS is to read the code fresh rather than from memory. It means the flank, it means an injury that has already healed, and it means a late effect that brought the patient back. Anything else belongs in a different subcode.

One more thing is worth remembering. A new code takes a while to settle in, so payer edits lag, cheat sheets go stale, and old descriptors keep circulating. Checking the descriptor against the current Tabular List costs a minute and saves a rework cycle.

If your team is rebuilding sequela claims from scattered notes, the fix is upstream of the coder. Book a demo to see how Pabau keeps injury history, documentation, and claims in one place.

Continue your research

Coding another sequela this week? S59.199S runs the same 7th character decision through a physeal fracture of the upper radius.

Not sure the injury has finished healing? S53.442D shows how the subsequent encounter extension works on an elbow sprain still under review.

Handling laceration sequelae as well? S56.529S applies the same sequencing rules to an extensor muscle laceration at the forearm.

Losing claims to thin documentation? Going paperless while staying HIPAA compliant explains how structured digital notes hold up when an injury claim is reviewed.

Need the records rules behind a claim? HIPAA compliance checklist for primary care walks through the documentation behind HIPAA-covered claim submission.

Frequently asked questions