L8511 — Insert for indwelling tracheoesophageal prosthesis, with or without valve, replacement only, each
L8511 is a HCPCS Level II code for insert for indwelling tracheoesophageal prosthesis, with or without valve, replacement only, each. It belongs to the Orthotic and Prosthetic Procedures and Devices section. Whether Medicare pays it depends on the coverage rule below.
Medicare coverage: Carrier judgment
Coverage is decided by your Medicare contractor, not by national policy. Whether this is paid depends on the LCD for your jurisdiction and on what the documentation supports.
From the coverage field of the CMS Alpha-Numeric HCPCS File, release 2026Q3-Jul. This states Medicare’s position on the code, not on your particular claim.
Medically Unlikely Edits — units per day
The most units of L8511 Medicare will pay on one date of service. Bill more on a single line and it is denied. The limit is not the same in every setting, so the row that matters is the one matching the claim you are building.
- practitioner
- 1 unit MAI 3 — Date of Service Edit: Clinical · Nature of Equipment
- outpatient
- 1 unit MAI 3 — Date of Service Edit: Clinical · Nature of Equipment
- DME supplier
- 1 unit MAI 3 — Date of Service Edit: Clinical · Clinical: Data
The adjudication indicator decides whether exceeding the limit is worth appealing at all: MAI 1 is a line edit you can support with documentation, MAI 3 is a date-of-service edit that is also appealable, and MAI 2 is absolute — no documentation overrides it. CMS MUE 2026Q3.
The CMS record for L8511
- Long descriptor
- Insert for indwelling tracheoesophageal prosthesis, with or without valve, replacement only, each
- Short descriptor
- Indwelling trach insert
- Added
- January 1, 2004
- BETOS
- D1F
- Pricing indicator
- 38 — DMEPOS
The official wording. This is what the code means.
CMS's 28-character form, which is what shows up on a remittance advice.
When CMS introduced the code.
Berenson-Eggers Type of Service — CMS's own analytic grouping.
Orthotics, prosthetics, prosthetic devices and vision services. Price subject to floors and ceilings.
Codes adjacent to L8511
HCPCS has no hierarchy — related items simply sit next to each other in the numbering. If L8511 is not quite right, the correct code is very often within a few positions of it.
- L8485Prosthetic sock, single ply, fitting, upper limb, each
- L8499Unlisted procedure for miscellaneous prosthetic services
- L8500Artificial larynx, any type
- L8501Tracheostomy speaking valve
- L8505Artificial larynx replacement battery / accessory, any type
- L8507Tracheo-esophageal voice prosthesis, patient inserted, any type, each
- L8509Tracheo-esophageal voice prosthesis, inserted by a licensed health care provider, any type
- L8510Voice amplifier
- L8512Gelatin capsules or equivalent, for use with tracheoesophageal voice prosthesis, replacement only, per 10
- L8513Cleaning device used with tracheoesophageal voice prosthesis, pipet, brush, or equal, replacement only, each
- L8514Tracheoesophageal puncture dilator, replacement only, each
- L8515Gelatin capsule, application device for use with tracheoesophageal voice prosthesis, each
- L8600Implantable breast prosthesis, silicone or equal
- L8603Injectable bulking agent, collagen implant, urinary tract, 2.5 ml syringe, includes shipping and necessary supplies
- L8604Injectable bulking agent, dextranomer/hyaluronic acid copolymer implant, urinary tract, 1 ml, includes shipping and necessary supplies
- L8605Injectable bulking agent, dextranomer/hyaluronic acid copolymer implant, anal canal, 1 ml, includes shipping and necessary supplies
Questions about L8511
What is HCPCS code L8511?
L8511 is a HCPCS Level II code for insert for indwelling tracheoesophageal prosthesis, with or without valve, replacement only, each. It sits in the Orthotic and Prosthetic Procedures and Devices section.
Does Medicare cover L8511?
The CMS HCPCS file marks L8511 as "Carrier judgment". Coverage is decided by your Medicare contractor, not by national policy. Whether this is paid depends on the LCD for your jurisdiction and on what the documentation supports.