HCPCS code L0462 – TLSO Triplanar 3-Shell Orthosis

Key takeaways

HCPCS Code L0462 covers a prefabricated TLSO only. Custom-fabricated TLSOs use different codes in the L0450-L0492 range.

Billing requires both a Certificate of Medical Necessity (CMN) and a Detailed Written Order (DWO) before the device is dispensed.

Shell count separates the neighboring codes. Two rigid shells bill as L0458 or L0460, three as L0462, and four as L0464.

Medicare Part B covers L0462 as durable medical equipment under CMS Policy Article A52500. Medical necessity must be documented for a covered diagnosis, such as a spinal fracture.

Pabau’s claims management software supports DME billing workflows, documentation storage, and claim submission in a single platform.

What HCPCS Code L0462 covers

HCPCS Code L0462 is the Medicare billing code for a prefabricated TLSO with triplanar control. The device is a modular segmented spinal system built from three rigid plastic shells and a soft liner. Fitting and adjustment are bundled into the code, so neither is billed separately.

The code sits in the L0450 to L0492 TLSO range maintained by CMS as part of the HCPCS Level II code set. It falls under the wider Orthotic Procedures and Devices section, which covers spinal orthoses for the thoracic, lumbar, and sacral regions.

Each element of the descriptor carries billing weight. “Triplanar control” means the orthosis restricts motion in the sagittal, coronal, and transverse planes. “Modular segmented” means the shell system is assembled from separate components rather than formed as one piece. Shell count is the element reviewers check first, because three rigid shells are what hold a device on L0462. Getting any descriptor element wrong in the order or the medical record is enough to trigger a code mismatch denial.

2026 Medicare fee schedule and reimbursement rates for L0462

Medicare Part B reimburses L0462 under the DMEPOS fee schedule, which CMS updates on a published cycle. Reimbursement varies by locality and by provider participation status. The figures below reflect 2026 national benchmarks. Always confirm current amounts in the CMS DMEPOS fee schedule for the Medicare Administrative Contractor (MAC) jurisdiction you bill.

The national limiting charge is a ceiling rather than a required price. Non-participating providers cannot bill a patient above it, and they are not obliged to charge up to it. Participating DMEPOS suppliers accept assignment and bill Medicare directly, so the patient pays only the coinsurance and deductible portion. Check the current DMEPOS fee schedule file before you submit, because CMS revises the amounts between updates.

Medicare coverage and medical necessity criteria

Medicare Part B covers L0462 as durable medical equipment under CMS Policy Article A52500, which governs spinal orthoses in the TLSO and LSO categories. Coverage requires documented medical necessity, and a prescription on its own does not establish it. Confirm both Part B enrollment and the DME benefit before the device is dispensed.

Conditions CMS recognizes as supporting medical necessity for a rigid TLSO include:

• Spinal fracture (vertebral compression fracture, acute traumatic fracture)
• Post-surgical stabilization following spinal fusion or laminectomy
• Spinal stenosis with documented functional limitation
• Scoliosis or kyphosis requiring external support
• Spinal instability due to tumor, infection, or degenerative disease

Coverage is not automatic even for a covered diagnosis. The clinical record must show that conservative measures were tried or are contraindicated, and that the device is expected to improve the patient’s condition. It must also show that the device meets the L0462 descriptor rather than a less restrictive code. Non-covered situations include routine low back pain without structural pathology, and preventive use with no documented spinal instability.

ICD-10 diagnosis codes that support medical necessity for L0462

The ICD-10-CM codes below are commonly accepted by Medicare and most commercial payers as supporting medical necessity for a rigid TLSO. Coverage varies by MAC and by the applicable Local Coverage Determination (LCD). Verify the covered diagnosis list against your MAC’s LCD for spinal orthoses before you submit.

Always pair the primary spinal diagnosis with any relevant aftercare or encounter-type code. A claim carrying only a symptom code does not meet medical necessity for a rigid TLSO and will be denied. M54.5 is the classic example, and it was deleted from ICD-10-CM effective FY2022. The clinical documentation has to show the structural pathology that justifies L0462, not only the claim form.

Documentation requirements before you bill

Inadequate documentation is the primary reason L0462 claims fail on post-payment audit rather than on initial submission. CMS Policy Article A52500 requires all of the following before a compliant claim goes out.

Certificate of Medical Necessity (CMN)

A CMN is required for L0462 and must be completed by the treating physician rather than the supplier. The CMN documents the diagnosis, the length of need, and the clinical justification. It must be signed and dated before the device is dispensed. A CMN backdated after dispensing is grounds for denial and a possible fraud referral. The supplier retains the CMN and does not submit it with the claim, but must produce it on request.

Detailed Written Order (DWO)

A DWO must reach the supplier before billing. It carries the patient’s name and date of birth, the prescribing physician’s name and NPI, and the physician’s handwritten or electronic signature. It must also name the item ordered in enough detail to determine the HCPCS code, plus the quantity. A verbal order becomes a DWO only once the supplier receives the written document. Digital intake forms in practice management software like Pabau capture those fields at the point of order, which shortens the wait for a signed DWO.

Supporting clinical documentation

The medical record must independently support the diagnosis and the medical necessity. Progress notes, imaging reports (X-ray, MRI, CT), and operative reports for post-surgical cases should all be on file. The record must show that the treating physician evaluated the patient, identified the structural pathology, and judged a rigid TLSO to be medically necessary. Supplier notes recording the fitting and adjustment belong in the dispensing record too.

How L0462 differs from the other TLSO codes

Choosing the wrong code inside the TLSO range is a frequent billing error. Among the prefabricated triplanar codes, the number of rigid plastic shells does most of the work, and the anterior extent separates L0458 from L0460. Flexible TLSOs with no rigid shells sit elsewhere in the range, under codes such as L0450. The AAPC HCPCS code range lookup carries the full descriptors for the whole range.

The decision between L0462 and its neighbors comes down to how many rigid plastic shells the device has. Two shells bill as L0458 or L0460, three as L0462, and four as L0464. Between L0458 and L0460, the anterior extent is what differs. All four codes include a soft liner, so the liner never decides which code applies.

The medical record and the supplier’s dispensing notes must describe the device components that justify whichever code is billed. Counting the shells at the fitting and writing that number down is what makes the claim defensible on audit.

How to bill L0462 for Medicare Part B, step by step

Billing L0462 correctly means completing several pre-claim steps in the right sequence. Skipping one, or taking them out of order, causes most preventable denials.

1. Verify Medicare Part B eligibility and the DME benefit. Confirm the patient is enrolled in Part B and that the DME benefit is active. Check for secondary insurance that may affect cost-sharing. Do this before the device is ordered or dispensed.
2. Obtain the Detailed Written Order from the treating physician. The DWO must specify the patient, the provider, and the device in enough detail to determine the HCPCS code. Receive and retain the signed DWO before billing.
3. Confirm the device matches the L0462 descriptor. Check that it is prefabricated, triplanar, and built as a modular segmented system with three rigid plastic shells and a soft liner. Confirm that fitting and adjustment are included. If any element differs, identify the correct adjacent code before you proceed.
4. Complete the Certificate of Medical Necessity. Have the treating physician complete and sign the CMN, documenting the diagnosis, the length of need, and the clinical rationale. Retain it on file, because it is produced on audit rather than submitted with the claim.
5. Dispense the device and document the fitting. Record the fitting and adjustment in the supplier notes. That is what evidences the service bundled into L0462.
6. Submit the claim with the correct diagnosis code. Use a covered ICD-10-CM diagnosis that supports medical necessity under A52500. Submit on the CMS-1500 form with the appropriate place of service and the supplier NPI.
7. Monitor the remittance and respond to any denial. Review the CARC code, check the documentation file, and appeal with the supporting clinical records. Grouping denials by cause shortens the time between a denial and a corrected resubmission.

Common billing errors and denial reasons for L0462

Most L0462 denials fall into five categories, and each one is preventable with the right pre-claim workflow.

A denial codes reference helps a team decode the CARC and RARC values on a remittance. CO-4 means the procedure code is inconsistent with the modifier used, or that a required modifier is missing. CO-50 means the payer does not accept the service as medically necessary, and it is the code billers see most often on TLSO claims. A clean claim checklist written for L0462 is among the highest-value process improvements a DMEPOS billing team can make.

How Pabau keeps L0462 documentation audit-ready

Most DMEPOS suppliers keep the CMN in one place, the DWO in another, and the dispensing notes in a third. When a post-payment audit asks for the file, someone rebuilds it out of email and scans, and the claim ages while they look.

Pabau, practice management software for healthcare practices, keeps the order, the signed forms, the clinical notes, and the claim on one patient record. Its claims management software submits and tracks the claim from that record. The documents supporting L0462 stay with the claim instead of sitting in a separate folder.

The payoff is a faster audit response and fewer denials traced to a missing document. A biller can see which L0462 claims still lack a signed CMN before the device leaves the building. The fitting note lands on the same record the moment the supplier writes it.

Manage DME billing documentation in one place

Pabau brings together documentation workflows, claims management, and patient records so your team spends less time chasing paperwork and more time on care. See how it works for DME-billing practices.

Book a demo

Conclusion

Three rigid plastic shells and a soft liner are what L0462 describes. A device with a fourth shell belongs on L0464, and a two-shell device belongs on L0458 or L0460. Counting the shells at the fitting takes a minute, while correcting the claim afterwards takes an appeal.

The denials that follow L0462 are rarely clinical. They come from a signed document that arrived late, a diagnosis code the MAC does not cover, or a shell count nobody wrote down. Fix that sequence once and the same claim stops coming back.

Book a demo to see how Pabau keeps CMN, DWO, and claim records together for DMEPOS billing.

Continue your research

Need a framework for handling denied DME claims? Denial management in healthcare walks through a structured appeals process and root-cause analysis for DMEPOS denials.

Want to understand the broader billing compliance picture? Revenue cycle management covers the end-to-end process from eligibility verification through payment posting.

Looking for a reference on the clearinghouse side of claim submission? Medical claims clearinghouses explains how electronic claims reach payers and where L0462 claims can be validated before submission.

Frequently asked questions