HCPCS code L2116 – Ankle foot orthosis for tibial fracture

Found our content helpful?

Key takeaways

HCPCS Code L2116 covers a rigid, prefabricated tibial fracture orthosis, and its descriptor includes the fitting and adjustment done at delivery.

Medicare covers L2116 under the DME benefit when a compliant physician order, a fracture diagnosis, and proof of delivery are on file before submission.

L2116 is prefabricated, yet Medicare still classifies it as custom fitted rather than off-the-shelf, so PDAC verification and modifier accuracy both apply.

Practice management software like Pabau helps DME suppliers and orthotists track documentation checklists and submit clean claims across payers.

HCPCS Code L2116: Official descriptor and code details

HCPCS Code L2116 describes a rigid, prefabricated ankle foot orthosis dispensed as a fracture orthosis for tibial fractures. The code pays for the device together with the fitting and adjustment the supplier performs at delivery. The table below captures the classification details billers and orthotists need before submitting a claim.

The word custom carries two meanings on this code, and confusing them is a common source of denials. The official descriptor calls L2116 prefabricated, so the device is manufactured in advance rather than built for one patient.

Medicare Policy Article A52457 still classifies L2112, L2114, and L2116 as custom fitted rather than off-the-shelf. Fitting them takes more than minimal self-adjustment by the patient. Confirm your device model against PDAC coding verification guidance before you bill. Coding a device at the wrong fabrication level is one of the most audited errors in orthotic billing.

Clinical indications: When is L2116 used?

L2116 applies when a patient presents with a tibial fracture that needs rigid lower-leg immobilization from an ankle foot orthosis. This is a fracture-specific code, and a general AFO dispensed for another condition belongs elsewhere in the L-code series.

The device covered by L2116 differs from a standard walking boot (CAM boot), and the difference changes the code. Walking boots have their own HCPCS codes, such as L4360, L4361, L4386, and L4387. Those codes split on whether the boot is pneumatic and how much fitting it needs.

L2116 describes a rigid tibial fracture orthosis that the supplier fits and adjusts for the patient. Billing a walking boot under L2116 is a miscoding error that drives denials.

Clinical scenarios that support L2116 billing include:

• Tibial shaft fracture requiring post-reduction immobilization
• Distal tibial fracture stabilization where a rigid AFO is prescribed instead of a cast
• Fracture management in patients who cannot tolerate casting (e.g., skin integrity concerns)
• Transition from cast to a fitted fracture orthosis during the healing phase

The prescribing physician’s order must explicitly name the fracture diagnosis and the device type. A generic order for “an AFO” will not satisfy Medicare documentation requirements for L2116. Practices involved in fracture rehabilitation should raise this with the referring provider at the point of referral.

What L2116 covers and what it does not

Medicare covers L2116 under the DME benefit when the device is a rigid, prefabricated fracture AFO used for tibial fracture management. The documentation must also be complete. CMS Policy Article A52457 governs coverage of ankle-foot and knee-ankle-foot orthoses broadly. The device must be reasonable and necessary for the patient’s condition.

Included in the L2116 code:

• The rigid, prefabricated ankle foot orthosis itself, dispensed for a tibial fracture
• Fitting and adjustment at delivery, including measuring and shaping the device to the patient
• Patient instruction on wearing, removing, and checking the orthosis

Not included or separately coded:

• Knee involvement: if the orthosis extends above the knee, a knee-ankle-foot orthosis (KAFO) code applies instead
• Replacement straps, pads, or components: billed under separate HCPCS codes
• Non-fracture AFOs: a standard AFO for foot drop or spasticity is not L2116
• Walking boots: a boot the patient can apply with little or no adjustment is coded in the L4360-L4387 family, not under L2116

Commercial payers may follow Medicare rules or apply their own coverage criteria, so verify with the specific payer before dispensing. Using claims management software that surfaces payer rules at claim creation stops a technically clean claim from going out against the wrong policy.

L2116 vs related AFO codes: Choosing the right code

The L2106-L2116 range covers tibial fracture orthoses only. The fabrication method and the rigidity of the finished device separate the codes inside it. Selecting the wrong one is the most common coding error for tibial fracture orthotics, so the table below sets the official descriptors side by side.

L2106 and L2108 are the custom-fabricated codes, built for one patient from a cast or a model of the limb. L2112, L2114, and L2116 are prefabricated devices, separated only by rigidity. Soft is L2112, semi-rigid is L2114, and rigid is L2116.

No code in this family turns on whether the orthosis carries an ankle or subtalar joint, so never choose between them on that basis. Check the full descriptor text at the AAPC HCPCS code lookup before you select one. The chart below runs the same two questions in the order a coder asks them.

Medicare and payer coverage rules for HCPCS Code L2116

Medicare covers HCPCS Code L2116 under the Part B DME benefit. The claim is submitted by the orthotist or DME supplier, not the physician. Coverage requires that the device is medically necessary, documented by a compliant written order, and delivered to the patient before the claim date.

Key Medicare coverage requirements:

• Physician order: must be written before the device is dispensed, must specify the fracture diagnosis, and must be signed by the treating physician
• Medical necessity: the patient’s condition must support the need for a rigid fracture AFO rather than a less intensive device
• PDAC verification: where the device model is subject to PDAC coding verification, the code billed must match the verified code on the PDAC product list
• Prior authorization: requirements vary by Medicare Administrative Contractor (MAC) jurisdiction; check your MAC’s local coverage determination (LCD) for ankle-foot orthoses
• ABN requirements: where Medicare is likely to deny the item, an Advance Beneficiary Notice must be obtained from the patient before dispensing. Denial is likely when the device does not meet coverage criteria

Noridian Medicare (DME MAC Jurisdiction D) has historically published specific policy on walking boots and AFOs. The Noridian article referenced in some online resources is marked retired, so always retrieve the current LCD from your MAC’s website.

Commercial payers follow their own coverage policies, which may diverge from Medicare. Verify payer-specific rules before each claim rather than once a year.

L2116 fee schedule: Medicare payment rates

Medicare reimbursement for L2116 is set through the DMEPOS fee schedule, updated annually by CMS. Allowed amounts vary by geographic payment locality and are adjusted each January.

Because rates change each calendar year and vary by locality, this article does not publish specific dollar figures. A reimbursement amount that has since been updated creates compliance risk for anyone relying on the figure.

Verify the current allowed amount through the CMS DMEPOS fee schedule lookup tool. It searches by HCPCS code, year, and geographic locality.

Points to verify on the fee schedule lookup:

• Purchase vs. rental: L2116 is generally billed as a purchase, not a monthly rental; confirm this for your MAC
• Locality: national fee schedules show national rates, and your allowed amount depends on your service location
• Modifier impact: the KX modifier attests that the coverage criteria in the LCD are met. A claim that requires KX and omits it is denied, not paid at a reduced rate

Documentation requirements for L2116 claims

Incomplete documentation is the top driver of L2116 denials. Every item below must be in the patient file before the claim is submitted, not gathered after a denial.

1. Physician order/prescription: written before dispensing, it identifies the patient and gives the fracture diagnosis as an ICD-10 code or clinical description. It must also name the device type (rigid fracture AFO) and carry the treating physician’s signature
2. Letter of medical necessity (LMN): documents why the patient requires this specific device; must reference the fracture diagnosis and clinical rationale
3. ICD-10 diagnosis code: a tibial fracture code from the S82 family must appear on both the order and the claim. An unrelated or non-fracture diagnosis code triggers automatic denial
4. PDAC verification documentation: if the device requires PDAC coding verification, retain the verification confirmation on file
5. Proof of delivery (POD): signed and dated delivery receipt showing the patient received the device; must include the HCPCS code and the patient’s signature
6. KX modifier documentation: retain records confirming that all LCD coverage criteria are met before appending modifier KX

A pre-billing checklist keeps any claim from leaving the practice before every document is confirmed. A missing POD alone will cause Medicare to recover payment on audit, even if the device was legitimately prescribed and delivered. Treat each item as a gate the claim has to pass, rather than paperwork to assemble after the fact.

ICD-10 diagnosis codes commonly paired with L2116

L2116 requires a tibial fracture diagnosis code to establish medical necessity. The correct ICD-10-CM code comes from the S82 category, fracture of lower leg including ankle. It must carry the correct laterality and the correct 7th character.

Always use the most specific code the documentation supports. Submitting an unspecified code when the chart documents laterality and fracture location is an overcoding risk. The 7th character for initial encounter (A) is appropriate when the orthosis is dispensed during active fracture treatment; subsequent encounter (D) applies for follow-up visits. Verify the correct S82 subcategory against official ICD-10-CM coding guidelines for the S82 category.

Common claim denial reasons for L2116 and how to avoid them

Denials on L2116 follow a short list of patterns, and pre-submission checks prevent most of them.

The most frequent denial reasons are:

• Missing or incomplete physician order: the order must precede dispensing, include the fracture diagnosis, and bear the physician’s signature. An order written after delivery is not compliant.
• Non-fracture ICD-10 code: a diagnosis code that does not document a tibial fracture fails medical necessity. A sprain or a chronic foot drop will not support L2116.
• PDAC verification absent: billing a device that does not appear on the PDAC-verified list for L2116 is a compliance violation and triggers recovery on audit.
• Missing proof of delivery: the signed POD must be on file before submitting. A claim paid without a POD is vulnerable to post-payment audit recovery.
• Modifier KX omitted: Medicare requires modifier KX to confirm that documentation on file meets LCD criteria. Without it, the claim is denied.
• Wrong code for device type: billing a walking boot under L2116, which describes a rigid prefabricated fracture orthosis, is miscoding. The device dispensed must match the code billed.
• Modifier LT/RT missing: laterality modifiers are required on orthotic claims. An AFO must be identified as left (LT) or right (RT) on the claim line.

A pre-billing checklist catches these errors before submission. Two of them, a missing POD and the wrong modifier, are the cheapest to prevent and the most common to appeal. The medical billing denial codes on your remittance advice show which of the seven above your practice keeps hitting.

Modifiers used with L2116

Correct modifier assignment is not optional on HCPCS orthotic claims. Medicare uses modifiers to verify that the claim meets coverage requirements and that the device was delivered to the correct side. The table below covers the modifiers most commonly applied to L2116.

RT and LT are required on every orthotic claim line. KX is required when documentation supports coverage; if you are not confident the documentation is complete, do not append KX. Appending KX without adequate documentation constitutes a false attestation.

Billing tips for orthotists and DME suppliers

These practical steps reduce L2116 denial rates for practices that dispense fracture orthotics regularly:

• Verify PDAC status before you bill: check the PDAC product classification list at the time of claim submission, not when you order the device. PDAC classifications can change.
• Match the ICD-10 to the fracture: review the physician’s order and confirm the diagnosis code documents a tibial fracture before the claim leaves your practice. A sprain or post-fracture follow-up coded incorrectly will not support L2116 medical necessity.
• Obtain the written order before dispensing: this is not a documentation formality. A device dispensed before a written order exists is not reimbursable under Medicare, regardless of how clear the clinical need is.
• Audit your LT/RT modifier application: pull a monthly sample of L2116 claims. Confirm every one carries the laterality modifier that matches the delivery record.
• Check your MAC’s LCD: local coverage determinations for ankle-foot orthoses vary by jurisdiction. Noridian, CGS, Palmetto, and other MACs may have different prior authorization thresholds.
• Document the fitting date and POD separately: the fitting date and the delivery date may differ. Both must be documented. The claim date of service should match the delivery date, not the fitting date.

Practices with a strong clean-claim rate on DME codes treat each L2116 claim as a documentation audit rather than a billing task. Applying the same standard across the whole team is what reduces recovery risk on post-payment audits.

How Pabau keeps L2116 documentation and claims together

An L2116 claim is usually assembled from four places. The written order sits in the chart and the fitting note sits with the orthotist. The signed delivery receipt sits in a folder, and the PDAC confirmation sits in somebody’s inbox.

Pulling that trail together after a denial takes far longer than capturing it at delivery. Practice management software like Pabau keeps the order, the fitting note, the signed proof of delivery, and the claim on one patient record.

Staff work from a checklist while the patient is still in front of them, rather than from a reminder that arrives with the remittance advice.

Claims then leave the practice with the documentation already confirmed and the modifiers checked against the device that was dispensed. When a denial does arrive, the record that caused it is easy to trace, so the appeal starts from evidence instead of a search.

Manage orthotic and DME claims without the documentation chaos

Pabau’s claims management tools help orthotists and DME suppliers build pre-billing checklists, track proof of delivery, and submit clean claims across Medicare and commercial payers.

Book a demo

Conclusion

HCPCS Code L2116 covers one device in one situation, a rigid, prefabricated tibial fracture orthosis that the supplier fits and adjusts at delivery. The coding logic is narrow, and the documentation is where most claims fail.

A compliant written order, the correct tibial fracture ICD-10 code, and a signed proof of delivery resolve most denial patterns before they happen. Verified modifier selection handles the rest.

Pabau helps DME suppliers and orthotists track documentation completeness against payer requirements and submit clean claims the first time. To see how Pabau handles orthotic and DME billing workflows, book a demo with the team.

Continue your research

Need to understand denial recovery for DME claims? Denial management in healthcare covers systematic workflows for appealing and preventing claim rejections across payer types.

Looking to strengthen your overall billing compliance posture? Medical billing compliance outlines the documentation and audit practices that protect DME practices during post-payment reviews.

Want to understand how revenue cycle management applies to orthotic billing? Revenue cycle management explains how claim submission, payment posting, and denial resolution connect across the full billing lifecycle.

Frequently asked questions