ICD code S98.919S – Complete traumatic amputation of unspecified foot

Found our content helpful?

Key takeaways

S98.919S is a valid, billable ICD-10-CM code for complete traumatic amputation of unspecified foot, level unspecified, sequela, effective FY2026 (Oct 2025 to Sep 2026).

The seventh character S designates sequela. The visit addresses a late effect or complication of a prior traumatic amputation, not the acute injury itself.

Use S98.919S only when documentation does not specify left or right foot. The laterality-specific codes S98.911S (right) and S98.912S (left) take priority when the record is clear.

Practice management software like Pabau connects ICD-10 code selection to claim submission, which cuts the manual re-entry errors that sink sequela claims.

• Complete: the whole foot was severed, not part of it.
• Traumatic: an injury caused it, not a surgical procedure.
• Unspecified foot: the record names neither the right nor the left side.
• Level unspecified: the record does not say where the foot was severed.
• Sequela: the visit treats a late effect, not the acute injury.

Understanding the seventh character: A, D, and S in ICD-10 Code S98.919S

The seventh character is the most consequential element of this code. It reports which phase of care the visit belongs to, so the wrong character misrepresents the encounter as well as inviting a denial.

For S98.919 (complete traumatic amputation of unspecified foot, level unspecified), three seventh characters apply:

What does “sequela” mean in ICD-10-CM coding?

Sequela is the ICD-10-CM term for a late effect. It is a condition that exists as a direct consequence of a prior injury, after healing has concluded. Per CDC/NCHS ICD-10-CM coding guidelines Section I.C.19, reporting a sequela usually takes two codes.

One names the sequela itself, such as phantom limb pain. The other is the injury code with seventh character S, S98.919S, which identifies the cause.

The documentation test is short. Is the current condition a direct result of a prior traumatic amputation, presenting after normal healing? If yes, S is correct.

If the patient is still healing from the original injury, D applies, and A applies at the first treatment contact. Coding D where S belongs is one of the more common denial management triggers on amputation claims.

S98.919S in the ICD-10-CM code hierarchy

Knowing where S98.919S sits in the classification tree helps you find parent codes, sibling codes, and the reporting context. The WHO ICD-10 browser shows how Chapter 19 cascades from broad blocks down to individual codes.

• Chapter 19: S00-T88 – Injury, poisoning and certain other consequences of external causes
• Block: S90-S99 – Injuries to the ankle and foot
• Category: S98 – Traumatic amputation of ankle and foot
• Subcategory: S98.9 – Traumatic amputation of foot, level unspecified
• Code: S98.91 – Complete traumatic amputation of foot, level unspecified
• Code: S98.919 – Complete traumatic amputation of unspecified foot, level unspecified
• Full code: S98.919S – Complete traumatic amputation of unspecified foot, level unspecified, sequela

Each level adds specificity. S98 is the reporting category for every traumatic amputation of the ankle and foot. S98.91 narrows it to complete rather than partial amputations. S98.919 marks both the side and the level as undocumented. The seventh character S closes the loop by naming the encounter type as sequela.

Related codes in the S98 category

The S98 category covers traumatic amputations of the ankle and foot across several anatomical sites and amputation types. The AAPC ICD-10-CM code lookup and our own ICD-10-CM code index both let you check a neighboring code before the claim goes out. The table below lists the key S98 codes with the sequela seventh character.

Complete vs partial amputation: coding differences

Documentation has to distinguish complete from partial traumatic amputations. The S98.91x codes apply when the entire foot is detached, and the S98.92x codes apply when part of the foot remains attached.

Do not select on clinical inference: the operative or emergency report must state the amputation type. Where the wording is ambiguous, query the treating provider before coding.

Coding guidelines for unspecified laterality

S98.919S reports an unspecified foot, meaning neither right nor left appears in the clinical record. That leaves coders a practical decision. When is the unspecified code acceptable, and when should the record go back to the provider for more detail?

ICD-10-CM official guidelines instruct coders to assign the most specific code the documentation supports. For traumatic amputation, laterality matters clinically and for payment. The guidance below covers the three scenarios where each code applies:

Laterality and encounter type are the only two facts that separate the nine codes in the S98.91x family. Read them together and the code selects itself, as the matrix below shows.

Payers increasingly flag unspecified laterality codes for medical necessity review. Reaching for S98.919S when the record clearly supports S98.911S or S98.912S is a documentation error, and it delays reimbursement. Query the provider before claim submission whenever the timeline allows it.

Category-level coding notes that apply to S98.919S

Category S98 carries a single instructional note in the FY2026 tabular list, and it settles the question coders ask most often about vague operative wording. Category-level notes apply to every code in the family, S98.919S included.

• Applicable to: An amputation not identified as partial or complete should be coded to complete. Silent documentation therefore lands on S98.91x, not S98.92x.
• Ankle-level amputations stay in S98: subcategory S98.0 covers complete or partial traumatic amputation of the foot at ankle level. Those cases do not move to another category.
• The Excludes1 note sits on S88, not S98: Traumatic amputation of the lower leg (S88) excludes traumatic amputation of the ankle and foot (S98.-). Read in that direction, the note tells you when to leave S88 for S98.
• No Excludes2 note applies at the S98.919S code level in the FY2026 tabular list.

Nothing at S98 instructs you to add a second code, so treat any use-additional-code habit here with suspicion. Where a sequela visit also documents infection at the residual limb, code that infection from its own chapter. Sequence the two by the reason the patient came in.

Clinical context: Traumatic foot amputation coding

Traumatic foot amputations arise from high-energy mechanisms: industrial accidents, motor vehicle collisions, agricultural equipment injuries, and crush injuries. The sequela encounter arrives well after the acute phase. It is typically the visit where the patient presents for a complication that traces directly back to the original injury.

Common sequela presentations in follow-up settings include:

• Phantom limb pain (report the pain code first, followed by S98.919S as the causative injury code)
• Chronic stump wound complications, including residual limb ulceration or poor healing
• Prosthetic fitting adjustments or complications from the prosthetic device
• Neuroma formation at the amputation site
• Psychological sequela, including adjustment disorder related to limb loss

In each of these scenarios the sequela condition is the principal diagnosis, and S98.919S follows as the late-effect injury that identifies causation. ICD-10-CM official guidelines Section I.C.19 requires that sequencing for injury codes carrying seventh character S.

How to use S98.919S in medical billing workflows

Claim accuracy on amputation sequela codes rests on three things: sequencing, documentation that matches the code, and payer coverage checks before submission. The checklist below covers what a clean S98.919S claim carries.

• Principal diagnosis: The sequela condition, such as phantom limb pain or a stump ulcer, is listed first.
• Secondary code: S98.919S is reported as the causative injury code, never as the principal diagnosis.
• Supporting documentation: The record must link the current condition to the prior traumatic amputation. A note reading “phantom pain from prior right foot amputation” supports a sequela code. It also names a side, so query the provider and move to S98.911S.
• Associated conditions: Report a documented residual limb infection with its own code, sequenced by the reason for the encounter.
• FY2026 validity: S98.919S is valid for claims with service dates from October 1, 2025 through September 30, 2026.

Clearinghouses apply code edit checks that flag a sequela code submitted without a condition code in the first position. Catching that at the point of code entry, rather than after a rejection report comes back, is what keeps these claims moving.

How Pabau keeps sequela claims accurate before submission

In most practices the code is chosen twice. A clinician documents the sequela visit in the record, then someone re-enters the diagnosis into a billing screen or a payer portal. Every re-entry is a chance for S98.919S to arrive alone, without the condition code that has to precede it.

Pabau is practice management software that holds the clinical note, the invoice, and the claim in one record. Our connected claims management software carries the codes you selected in the note straight through to submission, so laterality and sequencing survive the trip. Coders review the claim in the same place the documentation lives.

The result is fewer sequela claims returned for a missing principal diagnosis, and a shorter list of denials to work each month.

Reduce claim errors on ICD-10 sequela codes

Pabau’s end-to-end billing workflow supports ICD-10 code selection, claim sequencing, and clearinghouse submission in one place. See how practices use Pabau to cut manual re-entry and claim denials.

Book a demo

Conclusion

S98.919S is the right code far less often than it gets used. Two of the three facts it reports are absences: no side, no level. So before you submit it, treat it as a prompt to read the operative note once more rather than as a finished answer.

Where the record names a side, S98.911S or S98.912S will hold up under review and S98.919S will not. Where the record genuinely says nothing, S98.919S is defensible, and the query you sent is worth keeping on file.

Fixing the sequencing at the point of code entry is cheaper than working the denial. Book a demo to see how Pabau moves a coded sequela visit through to a submitted claim.

Continue your research

Need to understand how claim submissions are processed? Claim.MD clearinghouse overview explains how electronic claims are validated and routed to payers.

Working on revenue cycle efficiency across your practice? What is revenue cycle management covers the end-to-end billing process from coding through payment posting.

Looking to reduce claim rejections before submission? Clean claim requirements outlines the data elements payers require for first-pass acceptance.

Frequently asked questions