Pabau GO app

The new Pabau GO is heredownload on the App Store

Download on the App Store
Book a demo Book a demo
Diagnostic Codes

ICD-10 code S22.049K: T4 fracture with nonunion

Key takeaways

Key takeaways

S22.049K codes an unspecified fracture of the fourth thoracic vertebra, T4, at a follow-up visit with nonunion.

The vertebral level is specified in this code, and only the fracture type is left unspecified.

A thoracic fracture with no documented level belongs on the S22.00- codes instead, such as S22.009K.

The digit after S22.0 names the level, while the last digit before the 7th character names the fracture type.

Thoracic vertebra fractures run on six 7th characters, A, B, D, G, K and S, with no malunion option.

The word “unspecified” in S22.049K trips up experienced coders. It sounds like nobody wrote down which vertebra broke. In fact the code names the level exactly, and that level is T4, the fourth thoracic vertebra.

Only the fracture type stays open. The record does not have to say wedge compression or burst. That difference decides the claim, because a thoracic fracture with no documented level belongs on S22.009K instead.

Nonunion adds the third layer. The bone has stopped knitting, and the 7th character K reports that at this visit.

S22.049K in plain terms: A T4 fracture that stopped healing

S22.049K is the ICD-10-CM code for an unspecified fracture of the fourth thoracic vertebra, subsequent encounter for fracture with nonunion. Three facts sit inside it. The level is T4, the fracture type was never classified, and the bone has failed to unite.

The code is billable and specific, so it can stand on its own on a claim. CMS places it in Chapter 19 of ICD-10-CM, inside the S22 block for fractures of the ribs, sternum and thoracic spine.

Nonunion also has a strict clinical meaning here. The fragments never bridged, and imaging shows no progress toward union. Malunion is a different finding, because the bone does heal, only in a poor position.

Here is the reference data in one place.

Field Details
Code S22.049K
Full description Unspecified fracture of fourth thoracic vertebra, subsequent encounter for fracture with nonunion
Short description Unsp fx fourth thor vertebra, subs for fx w nonunion
Code system ICD-10-CM, the US clinical modification
Billable Yes, billable and specific
FY2026 effective date October 1, 2025
Parent code S22.049, unspecified fracture of fourth thoracic vertebra
Vertebral level T4, the fourth thoracic vertebra
Fracture type Not documented, so reported as unspecified
7th characters available A, B, D, G, K, S
ICD-9-CM crosswalk 805.2, approximate

The digit that names the level, and the one that names the fracture

Two digits do two separate jobs in this code. The digit straight after S22.0 sets the vertebral level. The digit before the 7th character sets the fracture type.

  • S covers injuries to a single body region.
  • S22 covers fractures of the ribs, sternum and thoracic spine.
  • S22.0 narrows that to a thoracic vertebra, rather than a rib or the sternum.
  • S22.04 names the level as T4, the fourth thoracic vertebra.
  • S22.049 reports the fracture type as unspecified, because the record never classified it.
  • K is the 7th character for a subsequent encounter with nonunion.

The level digits run in order down the spine, and the upper levels each get their own subcategory. Lower down, the levels are paired.

Subcategory Vertebral level
S22.00 Unspecified thoracic vertebra, the level was not documented
S22.01 T1, first thoracic vertebra
S22.02 T2, second thoracic vertebra
S22.03 T3, third thoracic vertebra
S22.04 T4, fourth thoracic vertebra, the level in this code
S22.05 T5 and T6
S22.06 T7 and T8
S22.07 T9 and T10
S22.08 T11 and T12

The final digit then reports the pattern. Wedge compression is 0, stable burst is 1, unstable burst is 2, another documented pattern is 8, and an unclassified pattern is 9.

So S22.049 is not a code for a vertebra nobody identified. The chart names T4, and only the pattern is missing. You can walk the same hierarchy yourself in the CDC ICD-10-CM browser before you settle on a code.

Choosing the 7th character: A, B, D, G, K or S

Every S22 code needs a 7th character, and S22.049 offers six of them. The character reports where the fracture stands at today’s visit, not what you coded last time.

7th character Full code Meaning When to use it
A S22.049A Initial encounter, closed fracture First active treatment for the T4 fracture
B S22.049B Initial encounter, open fracture First active treatment when the skin is breached
D S22.049D Subsequent encounter, routine healing Follow-up care while the fracture heals on schedule
G S22.049G Subsequent encounter, delayed healing Follow-up care when healing runs behind schedule
K S22.049K Subsequent encounter, nonunion The fracture has failed to unite
S S22.049S Sequela Care for a late effect of the fracture

G and K sit next to each other and get swapped often. G says the fracture is still knitting, only slowly. K says the process has stopped and will not finish without help.

P is absent from that list, and its absence catches people out. Coders arriving from limb fractures expect a malunion character, and the S22 family does not offer one. S62.163P shows what P looks like on a wrist code.

If a T4 note says malunion, query the clinician instead of forcing a character the family cannot support. The ICD-10-CM Official Guidelines tie the choice to that day’s documentation.

When S22.049K fits, and when it does not

Four things have to be true at the same visit. Miss one and a more accurate code exists.

  • The encounter is a follow-up. First active treatment takes A, or B for an open fracture.
  • The chart names T4. If the note only says mid-thoracic, the level is undocumented and S22.009K applies.
  • The pattern is missing from the record. A documented wedge compression at T4 belongs on S22.040K instead.
  • The treating clinician documents nonunion. Imaging on its own does not decide it, and neither does the calendar.

An example makes the fit clearer. A patient returns fourteen weeks after a fall fractured T4. Imaging shows a persistent fracture line with no callus, and the surgeon writes nonunion and orders a bone stimulator trial. Nobody ever classified the pattern, so S22.049K is the code.

Orthopedic and spine practices report this code most often. Rehab teams inherit the same patients months later, so the level and the healing status have to survive into physical therapy notes as well.

Workers’ compensation cases run long, and their rules vary by state. Check the payer’s submission requirements before the first follow-up claim goes out.

How a T4 nonunion claim moves from visit to payment

A typical S22.049K claim moves like this.

  1. The patient returns for a scheduled follow-up, and imaging shows the T4 fracture line unchanged.
  2. The clinician records nonunion and changes the plan, often with bracing, stimulation, or a surgical referral.
  3. The coder reads that note, confirms the level and the encounter type, then assigns S22.049K.
  4. Billing pairs the diagnosis with the procedure codes for the visit and submits the claim.
  5. The payer checks that the diagnosis supports the service billed on that date.

Two habits derail that path. The first is a copy-forward note that still reads “initial encounter” from the emergency visit. The second is a healing status nobody wrote down, because the team assumed the imaging report said it.

Follow-up injury visits stack up fast in sports medicine practices. Copy-forward habits spread quickly once they take hold, so a note template fix usually pays for itself inside a quarter.

S22 codes that get picked by mistake

Three slips cause most of the rework here. Coders pick the wrong level, add a pattern the note never gave, or reuse the last encounter’s 7th character. This table lines up the near neighbors.

Code Description How it relates to S22.049K
S22.04 Fracture of fourth thoracic vertebra Header code for the level, not billable
S22.049 Unspecified fracture of fourth thoracic vertebra Parent code, needs a 7th character to bill
S22.049K Unspecified fracture of T4, subsequent encounter, nonunion This code
S22.040K Wedge compression fracture of T4, nonunion Same level, pattern documented as wedge
S22.041K Stable burst fracture of T4, nonunion Same level, burst with posterior elements intact
S22.042K Unstable burst fracture of T4, nonunion Same level, burst with posterior involvement
S22.048K Other fracture of T4, nonunion Pattern documented, but not wedge or burst
S22.009K Unspecified fracture of unspecified thoracic vertebra, nonunion The level itself was never documented
S22.012K Unstable burst fracture of T1, nonunion Different level, with a documented pattern
S22.020K Wedge compression fracture of T2, nonunion Different level, wedge pattern
S22.022K Unstable burst fracture of T2, nonunion Different level, unstable burst pattern

The same grid repeats at every thoracic level. S22.022G shows the delayed healing character two levels up, on a documented burst fracture.

Three errors that get S22.049K denied

Denials on this code cluster around code selection rather than clinical judgment.

  • Billing K for the first visit. The emergency or first surgical encounter takes S22.049A, or S22.049B when the fracture is open.
  • Leaving the 7th character off. S22.049 on its own is not billable, so the claim rejects on submission.
  • Coding D out of habit. Routine healing and nonunion cannot both be true, and the note decides which one you report.

Practices with heavy fracture caseloads catch these earlier with claims management software that checks required fields before submission. The AAPC entry for S22.049 is a quick second check when a level looks ambiguous.

Codes that travel with S22.049K on the claim

S22.049K describes the fracture and nothing else, so associated injuries need their own codes. The S22 category carries a code also note for injury of an intrathoracic organ, which lives in the S27 category.

Spinal cord or nerve injury also sits outside this code. Report it separately when the record documents it, and sequence the codes by the reason for the encounter.

You report treatment with procedure codes rather than diagnosis codes. Surgical spine cases often carry codes such as 20937 on the operative claim, while S22.049K stays on the follow-up visits.

Two more notes are worth keeping in mind. ICD-10-CM sets no national external cause reporting mandate, although some payers and trauma registries ask for one. The S22 category also instructs you to code a fracture as closed when the record does not say otherwise.

Before you submit: Five things to check

Run this list before the claim leaves your practice.

  1. The imaging report or the visit note names T4 by level.
  2. The visit is dated and marked as follow-up care, not initial treatment.
  3. The clinician’s own words describe nonunion, not just ongoing pain.
  4. Any cord, nerve, or intrathoracic organ injury carries a separate code.
  5. The 7th character on the claim matches the healing status in that day’s note.

Keeping imaging, healing assessments, and encounter type on one clinical record removes most of the searching. It also means the coder and the clinician read the same page.

Comprehensive EMR and patient record management
Pabau, a practice management system, holds imaging notes and every T4 follow-up on one record, so the coder is not chasing three systems.

Pro Tip

Audit your S22 claims once a quarter. Pull every subsequent encounter code, then check that a clinician note documents the healing status behind each one. A K-coded claim sitting behind a note that only says ‘follow-up visit’ is a standing denial risk.

Mapping S22.049K back to ICD-9 for old audits

Legacy systems and pre-2015 audits still ask for the ICD-9-CM equivalent. Crosswalk data in the CMS code lists maps S22.049K to 805.2.

ICD-10-CM code ICD-9-CM code ICD-9 description Mapping type
S22.049K 805.2 Fracture of thoracic vertebra, closed, without spinal cord injury Approximate, from the GEMs file

One caveat. ICD-9-CM 805.2 covered every closed thoracic vertebra fracture without spinal cord injury. It had no way to record the level, the pattern, or the encounter type. Treat it as a direction of travel rather than a match.

How practice management software keeps T4 follow-ups clean

Most of the risk on this code is administrative. Imaging sits in one system, the visit note in another, and the claim goes out from a third. Nobody sees the whole encounter in one place.

Practice management software like Pabau keeps the clinical record and the billing side together. Notes, imaging results, and every follow-up appointment live on one patient file, so the coder reads the note the clinician actually wrote.

Pabau’s claims management tools then check that the required fields are complete before a claim is sent. A status view shows where each submission sits afterwards, so an error does not sit unnoticed for a month.

None of that codes the encounter for you. What it removes is the searching, so a thin follow-up note is obvious while you can still do something about it.

Pabau claims management dashboard
Pabau’s claims dashboard shows where each submission sits, so a rejected nonunion claim surfaces in days rather than after a payer letter.

Keep fracture follow-ups and claims in one place

Pabau brings patient records, imaging notes, and billing into one system, and it checks that required claim fields are complete before you submit. See how that fits your fracture follow-up workflow in a live demo.

Pabau claims management dashboard

Conclusion

S22.049K is narrower than it looks. It names T4, it leaves the fracture pattern open, and it reports a fracture that stopped healing. Read those three parts separately and the code stops feeling ambiguous.

The rest is documentation discipline. One line about the level and one about healing status, written at every follow-up, removes most of the denial risk on this family.

If your S22 follow-ups are scattered across imaging, notes, and a separate billing tool, start there. Book a demo to see how Pabau keeps the record and the claim on the same page.

Continue your research

Continue your research

Coding a thoracic fracture that is healing slowly? S22.022G covers the delayed healing character on a documented T2 burst fracture.

Need the malunion character instead? S62.163P shows how P works on a wrist fracture, and what the note has to say.

Working a fracture code with a longer character list? S52.692R breaks down the 7th characters on forearm fracture codes.

Billing the surgical side of a spine case? CPT 20937 walks through autograft reporting and what belongs on the operative claim.

Seeing a Medicare patient outside the program? Medicare private contract template sets out what the agreement must include.

Frequently asked questions

Will a payer deny S22.049K because the fracture type is unspecified?

Rarely. S22.049K is a billable code in its own right, and unspecified reflects what the note documents. A caseload full of unspecified patterns can still invite a documentation review.

The first claim used S22.009K and imaging later named T4. What now?

Code what the record supports at each visit. Once a note names T4, later encounters move to S22.049K. Leave the earlier claim alone unless the payer asks you to correct it.

Does the fracture have to be closed to use S22.049K?

No. Only the initial encounter characters separate open from closed, A and B. Subsequent characters such as K cover both. S22 also tells you to code a fracture as closed when the note does not say.

Can a physical therapist report S22.049K?

Yes, when the therapist’s own note supports it. The 7th character follows the encounter rather than the specialty, so a therapist picking up an existing T4 nonunion still reports a subsequent character.

Is S22.049K enough to justify a bone growth stimulator claim?

Not on its own. The diagnosis supports medical necessity, and the payer’s coverage policy sets the rest, including time since injury and treatment already tried. Read the local coverage determination first.

×