HCPCS code L1610: Knee orthosis billing, modifiers, and Medicare coverage

Key Takeaways

HCPCS code L1610 describes a prefabricated knee orthosis (KO), elastic with joints, intended for knee stability and support.

L1610 is a DMEPOS item billed to DME MACs under Medicare Part B; a detailed written order and medical necessity documentation are required before supply.

The KX modifier signals medical necessity documentation is on file; misapplying KX, GA, or GZ is the most common reason L1610 claims are denied.

Pabau’s claims management software helps orthopedic and DME practices attach correct HCPCS codes, link supporting ICD-10 diagnoses, and reduce L1610 claim denials.

The official descriptor reads: Knee orthosis, elastic with joints, prefabricated item that has been trimmed, bent, molded, assembled, or otherwise customized to fit a specific patient by an individual with expertise, off-the-shelf. Understanding this distinction between prefabricated, prefabricated-with-customization, and custom-fabricated is critical: L1610 is not custom-made. Different L-codes apply when a device is fabricated from scratch for the patient.

Per the CMS HCPCS overview, HCPCS Level II codes are maintained by the CMS HCPCS Workgroup and updated annually. L1610 sits within the L1600-L1830 subrange covering knee orthoses specifically.

L1610 code description and device specifications

The L1610 knee orthosis is a prefabricated device that must have elastic construction and must incorporate joints. These joints provide a degree of controlled motion, distinguishing L1610 from simpler wrap-style knee braces coded elsewhere.

Products eligible for L1610 must pass PDAC (Pricing, Data Analysis and Coding) contractor verification before Medicare reimbursement is possible. The PDAC confirms that a specific commercial product meets the descriptor requirements. Suppliers should verify each product’s PDAC status before billing, as using L1610 for a non-verified product is a claim liability. The CGS Medicare coding verification guidance outlines this process for DME MACs in their jurisdictions.

Medicare coverage and reimbursement for HCPCS code L1610

Medicare Part B covers HCPCS code L1610 when medical necessity is established and documentation requirements are met. Coverage is governed by applicable Local Coverage Determinations (LCDs), primarily LCD L33686 (Lower Limb Orthoses), issued by the DME MACs. The four DME MAC jurisdictions are administered by CGS Administrators, Noridian Healthcare Solutions, National Government Services, and Palmetto GBA.

Reimbursement rates come from the annual CMS DMEPOS fee schedule. Rates change each calendar year and vary by geographic locality. Always verify the current allowed amount via the CMS Physician Fee Schedule lookup for the applicable year before quoting patients or calculating expected reimbursement. Do not rely on published figures from prior years.

Medical necessity documentation requirements

A detailed written order (DWO) from the treating physician or qualified non-physician practitioner must be on file before the device is supplied. The order must include the patient’s diagnosis, the specific item ordered, the treating practitioner’s signature and date, and a description of the medical necessity. Proper medical forms at your healthcare practice support clean documentation workflows for these requirements.

• Diagnosis supporting the need for a knee orthosis (must align with covered ICD-10 codes in the applicable LCD)
• Clinical findings documenting functional limitation or instability of the knee
• The treating practitioner’s assessment that the device is medically necessary
• Confirmation that the device meets the L1610 descriptor (prefabricated, elastic, with joints)
• Patient’s height and weight if sizing is clinically relevant

Ensuring HIPAA compliance for medical offices when storing and transmitting these records is equally important, particularly when sharing documentation between referring physicians and DME suppliers.

ICD-10 diagnosis codes commonly paired with L1610

The ICD-10-CM diagnosis code on the claim must support the medical necessity for the knee orthosis. The LCD identifies covered and non-covered diagnoses. Common codes paired with HCPCS Code L1610 include the following, though this list is not exhaustive and payer-specific LCD restrictions apply.

Always verify covered diagnoses against the current LCD in your DME MAC jurisdiction. Diagnosis codes that fall outside the covered list require an Advance Beneficiary Notice (ABN) if the item is still being supplied, and the GZ modifier should not be used if an ABN was obtained. Reviewing compliance requirements for physiotherapy clinics can help practices handling musculoskeletal DME coding stay current with documentation standards.

Modifiers used with HCPCS code L1610

Modifier selection is where most L1610 claims go wrong. Each modifier carries a specific meaning under Medicare DMEPOS billing rules, and applying the wrong one can result in automatic denial or, worse, a false claims liability.

A claim submitted with KX but without the required documentation on file is considered a false claim. Practices should use digital intake forms to capture and store DWO and clinical criteria documentation at the point of care, reducing the risk of a KX modifier error at billing time.

Prior authorization requirements for L1610

Medicare’s Prior Authorization program for DMEPOS covers certain items designated as frequently subject to unnecessary utilization. The program list changes periodically. As of 2026, suppliers must verify whether HCPCS Code L1610 is included in the current prior authorization requirement list for their DME MAC jurisdiction before supplying the device.

Check the CMS prior authorization for DMEPOS page directly for the current list. If L1610 is included in your jurisdiction, the process requires:

1. Obtain the detailed written order from the treating physician before supply
2. Compile supporting clinical documentation meeting LCD criteria
3. Submit the prior authorization request to the DME MAC with the DWO and clinical notes attached
4. Await a provisional affirmation or non-affirmation before delivering the device
5. Include the prior authorization number on the submitted claim

Supplying a device before receiving prior authorization (when required) does not automatically result in denial if documentation is sufficient, but it significantly increases audit risk. Maintaining HIPAA-compliant clinic software ensures that documentation attached to prior auth requests meets security and access standards during DME MAC review.

Reduce L1610 claim denials with smarter billing workflows

Pabau helps DME suppliers and orthopedic practices manage HCPCS coding, attach supporting documentation, and track claim status from one place. See how it works.

Book a demo

How to bill L1610: step-by-step claim submission

Getting the claim right the first time depends on a structured workflow. Each step below maps to a potential denial point if skipped or completed incorrectly.

1. Confirm device eligibility: Verify the specific product is on the PDAC-verified list for L1610 before ordering inventory or supplying the patient.
2. Obtain the detailed written order: The DWO must be signed by the treating physician or qualified NPP before supply. It must name L1610 or describe the device clearly enough to map to it.
3. Document clinical criteria: Record the diagnosis, functional limitation, and clinical justification in the patient file. These must match an LCD-covered ICD-10 code.
4. Apply correct modifiers: Attach NU (purchase) and KX (medical necessity on file) for standard covered claims. Add RT or LT for laterality. Use GA only if an ABN is signed.
5. Link the ICD-10 diagnosis code: Ensure the claim’s diagnosis code is a covered diagnosis under the applicable LCD. Uncovered diagnoses without an ABN result in full denial.
6. Submit to the correct DME MAC: Bill to the DME MAC jurisdiction covering the patient’s Medicare enrollment address, not the supplier’s address. Misrouted claims are rejected, not denied, but still delay payment.
7. Retain documentation for seven years: CMS DMEPOS audit requirements extend to seven years. The DWO, clinical notes, delivery confirmation, and ABN (if applicable) must all be retained.

Using automated billing workflows reduces manual errors at steps 3 through 5, where coding and modifier mismatches most commonly occur. Practices that handle volume DME billing benefit most from workflow automation that flags missing modifiers or unsupported diagnosis codes before claim submission.

Common billing errors and how to avoid them

Three errors account for the majority of L1610 denials:

• KX modifier without supporting documentation: The DWO or clinical notes are absent or incomplete. Fix: use a documentation checklist before submitting any KX-appended claim.
• Non-covered ICD-10 diagnosis without ABN: The diagnosis code is outside the LCD’s covered list and no waiver was obtained. Fix: verify diagnosis coverage in the LCD before supply and obtain an ABN proactively when coverage is uncertain.
• Wrong code for device type: A custom-fabricated or non-jointed brace was billed as L1610. Fix: confirm that the specific product is prefabricated, elastic, and jointed, and appears on the PDAC list for L1610 specifically.

Related HCPCS L-codes for knee orthoses

Choosing the correct knee orthosis L-code depends on the device’s construction method and feature set. The table below contrasts L1610 with adjacent codes to help coders select accurately. Misclassifying a custom device as prefabricated (or vice versa) is an audit trigger. The AAPC HCPCS code lookup and PGM Billing HCPCS lookup tool both provide quick code-to-descriptor verification.

The distinction between L1600 and L1610 is subtle but significant: L1600 is off-the-shelf with stays; L1610 has joints and has been individually fitted by a qualified provider. Billing L1600 when a jointed device was customized leaves reimbursement on the table. Billing L1610 when a simpler device was supplied invites recoupment.

How practice management software supports L1610 billing

Most L1610 denials trace back to process gaps, not coding knowledge. The DWO exists but was not scanned into the patient file. The diagnosis code was entered correctly but the laterality modifier was dropped. The ABN was signed but misfiled. These are workflow failures, and claims management software addresses them by building documentation requirements into the ordering and billing workflow.

Pabau’s platform supports DME and orthopedic practices through structured intake, coding, and claim tracking. Practice management software features that matter most for HCPCS billing include: mandatory documentation fields tied to DME orders, modifier-rule validation before claim submission, and diagnosis-code linkage that flags unsupported pairings before they reach the payer. Practices managing volume DMEPOS claims can also use medical practice management software to automate the DWO tracking and re-authorization workflow across multiple patients simultaneously.

For practices that also handle practice management workflows across multiple service lines, having L1610 coding rules embedded in the system means billers do not need to remember modifier rules from memory. The system surfaces them at the claim creation stage. See how Pabau handles this by reviewing practice management software capabilities for DME and orthopedic workflows.

Conclusion

HCPCS Code L1610 is narrow in scope but dense in billing requirements. The prefabricated/jointed construction requirement, PDAC product verification, KX modifier discipline, and LCD-matched diagnosis code linkage each represent a distinct failure point. Missing any one of them delays or denies payment.

Practices billing L1610 at volume need a system that enforces documentation checklists, validates modifiers, and routes claims to the correct DME MAC automatically. Review how Pabau’s practice management features support HCPCS billing accuracy, or book a demo to see the claims workflow in action.

Continue your research

Need a structured claims billing checklist? Claims management software provides a step-by-step framework for submitting DMEPOS and HCPCS claims with correct modifiers and diagnosis linkage.

Handling compliance across your orthopedic or DME practice? Compliance management software helps practices maintain audit-ready documentation for Medicare DME billing requirements.

Want to reduce manual data entry at intake? Digital forms capture DWO details, diagnosis information, and patient consent in structured fields that feed directly into the billing workflow.

Frequently Asked Questions