ICD-10 code S22.022G: T2 burst fracture, delayed healing

Key takeaways

S22.022G codes an unstable burst fracture of the second thoracic vertebra at a follow-up visit where healing is delayed.

The code is billable and specific, and it stays valid for FY2026 claims from October 1, 2025.

The 7th character G is what separates delayed healing from routine follow-up care (D) and from nonunion (K).

Thoracic vertebra fractures in the S22 family use only six 7th characters: A, B, D, G, K and S.

Your claim holds up only if the note states the fracture type, the T2 level, the encounter type and the healing status.

S22.022G is the ICD-10-CM code for an unstable burst fracture of the second thoracic vertebra, T2. You use it at a follow-up visit, when the fracture is healing slower than expected. It is billable and specific, so it can stand on its own on a claim.

One letter carries all of that weight. Swap G for D and you have told the payer the fracture is healing normally. Swap it for K and you have said the bone stopped healing altogether. Both are easy slips on a busy follow-up day.

And the letter is only as good as the note behind it. Payers want the healing status written down at that visit, not carried forward from the last one.

Here is the reference data for the code, all in one place.

What S22.022G covers and when it’s billable

What an unstable T2 burst fracture looks like in the chart

An unstable burst fracture happens when compression shatters the vertebral body and drives fragments outward. Posterior element involvement is what makes it unstable. At T2 that matters, because fragments can travel toward the spinal canal.

The tabular list gives S22.022G one inclusion term. It reads: Burst fracture NOS of second thoracic vertebra, subsequent encounter for fracture with delayed healing. NOS means the record does not have to classify the burst any further. It still has to confirm the level and the instability.

• Vertebral level: T2, the second thoracic vertebra. T1 and T3 have codes of their own.
• Fracture type: unstable burst, where fragments may reach the spinal canal.
• Encounter type: subsequent. The patient is in ongoing care, not at the first treatment visit.
• Healing status: delayed, as judged and recorded by the treating clinician.

Rehab teams often see these patients long after the surgeon does. So those four elements have to survive into physical therapy notes as well, or the follow-up claims start to wobble.

Picking the right 7th character: G, D, K, or S

The 7th character reports where the fracture is in its healing, at this visit. Guidance from CMS ties the character to what the clinician documented that day, not to the code on the last claim.

There is a quick way to keep the middle three straight. G means the fracture is still knitting, only slowly. K means it has stopped and will not join without help.

S sits at the other end. It applies once healing has finished and you are treating what the fracture left behind, such as chronic pain or deformity. S56.125S shows the same character at work on a hand injury. Only one of these can be true at a single encounter.

Coders arriving from limb fractures often go looking for P, the malunion character. The S22 codes do not offer it. Thoracic vertebra fractures run on A, B, D, G, K and S, and nothing else.

Long bone codes go further. S52.692R comes from a family with separate characters for open fracture types. If a note says malunion at T2, query the clinician rather than forcing a character the record cannot support.

Coding rules that decide whether the claim holds up

Three rules do most of the work here. The ICD-10-CM Official Guidelines, published by CMS and NCHS, set them out for the S22 chapter.

• Reassess the 7th character every visit. It reports today’s healing status, not the status you coded last time.
• Code neurological injury separately. S22.022G says nothing about cord or nerve damage, so those injuries need codes of their own.
• Use the most specific code the record supports. HIPAA has required ICD-10-CM on covered claims since October 1, 2015.

Those records carry obligations of their own. HIPAA compliance rules govern how the notes behind an S22 claim are stored and who is allowed to open them.

What the note must say before you bill G

Four things have to appear in the chart. Miss one and the claim is exposed on review.

• Unstable burst confirmed. A CT or MRI report showing posterior element involvement or canal compromise. “Stable compression fracture” will not support this code.
• Level documented as T2. Imaging or the clinical note names the second thoracic vertebra. “Mid-thoracic” is not enough.
• Delayed healing stated. The treating clinician writes that healing is delayed or slower than expected. “Incomplete consolidation on follow-up imaging” works as supporting language.
• Encounter confirmed as subsequent. The note shows this is not initial treatment. Emergency and initial surgical visits take A or B.

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

Before you submit: A five-point check

Run this list before the claim goes out the door.

• The imaging report names T2 and describes an unstable burst pattern.
• The visit note is dated and marked as follow-up care, not initial treatment.
• The clinician’s own words describe healing as delayed or incomplete.
• Any cord or nerve injury carries a separate code on the claim.
• The 7th character on the claim matches the 7th character the note supports.

How the claim moves from visit to payment

Here is the path a typical S22.022G claim takes.

1. The patient returns twelve weeks after a T2 burst fracture, and imaging shows partial consolidation.
2. The clinician records slow healing and extends bracing for another six weeks.
3. The coder reads that note, confirms the level and the pattern, then assigns S22.022G.
4. Billing pairs the diagnosis with the visit’s procedure codes and submits the claim.
5. The payer checks that the diagnosis supports the service that was billed.

Two things 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 everyone assumed the imaging said it.

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

Surgery is reported with procedure codes, not diagnosis codes. Spine cases often carry codes such as 20937 on the operative claim. S22.022G stays on the follow-up visits that come after.

Neighboring S22 codes that coders mix up

Three mistakes come up again and again. Coders pick the wrong level, the wrong morphology, or a 7th character borrowed from the last encounter. The S22 block covers thoracic vertebra fractures and sits inside S20-S29, injuries to the thorax.

The same choices repeat at every thoracic level. S22.049K shows what the nonunion character looks like a few levels down the spine.

Mapping S22.022G back to ICD-9 for old audits

Legacy billing systems and pre-2015 audits still need the ICD-9-CM equivalent. Crosswalk data from CMS code lists maps S22.022G to 805.2.

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 fracture pattern, or the encounter type. Treat it as a direction rather than a match.

How practice management software keeps S22 follow-ups clean

Most of the risk here is admin, not clinical judgment. 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 follow-up appointments live on the same patient file, so the coder reads the same note the clinician wrote.

Pabau’s claims management tools then check that the required fields on a claim are complete before it can be sent. Once it is out, a status view shows where each submission sits, 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.

Keep follow-up records and claims in one place

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

Book a demo

Conclusion

S22.022G is a narrow code, and narrow codes live or die on documentation. Get one line about healing status into every follow-up note and most of the denial risk goes away.

The trade-off worth remembering is speed against accuracy. Reaching for D because the visit felt routine saves a few seconds and costs a rework cycle later. Reading the note costs less than reworking the claim.

If your S22 follow-ups are spread 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

Coding a thoracic fracture that stopped healing? S22.049K covers the nonunion 7th character and the documentation payers expect behind it.

Billing the surgical side of a spine case? 20937 walks through autograft reporting for spine surgery, including what belongs on the operative claim.

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

Coding soft tissue work on the back or flank? 21936 covers radical resection reporting and the documentation that supports it.

Seeing a Medicare patient outside the program? Medicare private contract template sets out what the agreement must include and how to file it.

Frequently asked questions