Seven Criteria Stand Between a Speech Device and Payment — and One of Them Disqualifies Your Own SLP (E2500–E2510)

A referral comes in for a patient two years into amyotrophic lateral sclerosis. Speech is down to a handful of intelligible words. The family has already researched devices. The neurologist is supportive, the SLP at the ALS clinic is excellent, and everybody involved wants the same thing.

Eight months later the claim is denied as not reasonable and necessary, the appeal fails, and nobody in the building can explain which of the seven criteria came up short. That is the pattern with SGDs. The clinical case is unusually strong and the paperwork is unusually specific, and the gap between those two facts is where the money goes.

Seven criteria, and only three are about the patient

A speech generating device — E2500, E2502, E2504, E2506, E2508, E2510 or E2511 — is covered when all of the following are met. Not most. All seven.

• 1.Prior to delivery, the beneficiary has had a formal evaluation of cognitive and communication abilities by a speech-language pathologist, in writing, containing seven specific elements.
• 2.The medical condition results in a severe expressive speech impairment.
• 3.The speaking needs cannot be met using natural communication methods.
• 4.Other forms of treatment have been considered and ruled out.
• 5.The speech impairment will benefit from the device ordered — the one ordered, not the category.
• 6.A copy of the SLP's written evaluation and recommendation was forwarded to the treating practitioner prior to ordering the device.
• 7.The SLP performing the evaluation may not be an employee of, or have a financial relationship with, the supplier of the SGD.

Criteria 2 through 5 describe the patient. Criterion 1 describes a document. Criterion 6 describes a sequence of events with a date attached to each end. Criterion 7 describes a business relationship. If one of the seven is not met, the LCD is unambiguous — the device is denied as not reasonable and necessary, and every accessory goes down with it.

The evaluation has seven elements, and reviewers count them

Criterion 1 is not satisfied by a strong clinical narrative. The written evaluation must include, at minimum:

• The current communication impairment — type, severity, language skills, cognitive ability, and the anticipated course of the impairment.
• An assessment of whether daily communication needs could be met using other natural modes of communication.
• The functional communication goals expected to be achieved, and the treatment options.
• Rationale for the specific device and any accessories selected.
• A treatment plan that includes a training schedule for the selected device.
• The cognitive and physical abilities to use that device and those accessories effectively.
• For an upgrade to a previously issued SGD, the functional benefit of the upgrade compared to the original.

"Most SGD evaluations we read are clinically excellent and structurally incomplete. The training schedule is missing, or the accessory rationale is missing, and the denial reads as though the patient did not qualify."

Two of those elements get skipped almost as a rule. The training schedule feels like a formality when the family has already been using a loaner. And the device-and-accessory rationale gets compressed into a product name, because by the time the report is written the trial has happened and the choice feels obvious. It is not obvious to a reviewer holding a page that does not say why this device and not a simpler one.

Criterion 6 is the other quiet one. The evaluation has to reach the treating practitioner beforethe device is ordered. That is a sequence, and sequences leave timestamps. A file where the standard written order is dated the 3rd and the SLP report was faxed to the physician's office on the 11th does not meet criterion 6, no matter how good either document is on its own.

The evaluator you are not allowed to use

Criterion 7 has no exceptions written into it. The SLP who performs the evaluation may not be an employee of the supplier, and may not have a financial relationship with the supplier.

This is a harder rule to live with than it looks on paper. Suppliers who serve this population well tend to build clinical depth in-house, because SGD fittings are complicated and families need somebody who knows the products. Employing an SLP is the natural way to do that. It is also the fastest way to make every evaluation that clinician writes unusable for coverage purposes.

The financial relationship language reaches further than payroll. Contracted arrangements, referral fees, anything that connects the evaluating clinician's compensation to the supplier — a contractor reviewing the file will look at the relationship, not the job title. And unlike the seat elevation policy, which carves out hospital-owned suppliers using that hospital's own clinicians, the SGD policy states criterion 7 flat.

So the operating model has to separate two functions that everyone wants to combine. The independent SLP evaluates and recommends. Your team fits, trains, delivers and supports. When those blur — when your clinician's assessment becomes the evaluation of record because it was thorough and it was there — you have a file that fails on a criterion nobody clinical will ever flag.

What you shipped may not be durable medical equipment at all

Before reasonable-and-necessary is even reached, the item has to land inside the DME benefit category. Policy Article A52469 lists seven requirements for that, and the last two are specific to speech devices: the item must be limited to use by a patient with a severe speech impairment, and it must be primarily used for generating speech.

Which produces the rule that catches suppliers who think in terms of hardware. A device built on tablet, smartphone or computer hardware has to be designed by the manufacturer to function solely as a speech generating device at the time of initial issue. Desktops, laptops, tablets, smartphones and other hand-held computers are not DME. They fail four of the seven benefit-category tests. A general computing device is coded A9270, and A9270 is a statutory non-cover.

If the patient's device is a consumer tablet running communication software, Medicare pays for the software as E2511 and pays nothing for the tablet. That is the entire arrangement. Suppliers who bill the combination as an SGD are not making a coding error at the margins — they are billing a non-covered item.

The PDAC line deserves a second look. For dates of service on or after June 1, 2016, the only products billable as E2510 are those with a written coding verification listed on the Product Classification List in DMECS. If a product needs coding verification and is not on the list for that code, the claim line denies as incorrect coding. No amount of evaluation quality touches that outcome. It is a lookup, and it takes about ninety seconds.

"A file can contain a flawless seven-element evaluation from an independent SLP and still deny, because the item in the box was a general computing device with a speech app on it."

Accessories inherit every problem the base device has

Accessories must meet the same seven coverage criteria as the base SGD. If the beneficiary does not meet criteria 1 through 7, the accessories are denied. If the SGD itself is denied as not reasonable and necessary, every related accessory follows automatically. There is no scenario where the mounting system survives a failed base.

Beyond that, the accessory rules have their own documentation burden:

• The medical necessity of each E2599 accessory has to appear in the SLP's formal evaluation. Not in a supplier note, not in the order. In the evaluation.
• Alternative input devices are covered only when the beneficiary cannot use standard input devices, and the evaluation has to say why standard access will not work. Claims for alternative input on a beneficiary who can use standard input are denied.
• Eye tracking, gaze interaction and electromyographic sensors are covered where there is a demonstrated medical need. E2513 is valid only with E2510.
• Claims for E2511, E2512, E2513 and E2599 must carry a narrative: item description, manufacturer name, product name and number. E2599 also needs the supplier price list amount. A multicomponent mounting system lists every component's manufacturer and product name and number.
• Mounting systems under E2512 bill on a single claim line, one unit of service, however many components they have. Software, interfaces, cables, adapters and switches that let an access device talk to the SGD are already paid for in the access device.
• A4601 covers a lithium ion rechargeable battery used with an SGD or accessory. Batteries, chargers and AC adapters shipped with the base device are included in it, and so is a non-integrated keyboard.

Then the upgrade rule, which surprises people managing progressive-disease patients. Upgrades to the device or the software provided within the five-year reasonable useful lifetimeare denied as statutorily non-covered. Software replacement inside that window is only covered when the patient's condition changed, or the software was lost, stolen or irreparably damaged. For an ALS patient whose access method degrades from touch to switch to eye gaze over eighteen months, "a change in the patient's condition" is the entire argument — and it has to be documented as a change, by the SLP, at the time.

The modifier that rejects the claim before anyone reads it

KX, GA and GZ on codes E2500, E2502, E2504, E2506, E2508, E2510, E2511, E2512, E2513 and E2599 work the way they do across DME, with one consequence worth stating plainly.

KX goes on only when every coverage criterion in the LCD has been met and the evidence is in your files, available on request. If the criteria are not met, GA applies when you hold a properly executed Advance Beneficiary Notice and GZ applies when you do not. And a claim line billed on any of those codes without KX, GA or GZ is rejected as missing information.

Rejected, not denied. There is no appeal on a rejection. The line comes back, somebody has to notice, and the correction competes with everything else in the queue. We see clean, fully documented SGD files sit unpaid for months because a modifier was never appended and nobody was watching the rejection report closely enough to catch it.

KX is also an attestation. Putting it on an E2510 line asserts that an independent SLP performed a seven-element evaluation, that it reached the practitioner before the order, that natural communication methods were assessed and ruled out, and that a training schedule exists. If any of that is thin, KX is the wrong modifier and GA is the honest one.

How the sequence actually has to run

Step 2 is the one that gets done out of order, and out of order is fatal here. The common version is innocent: the physician has already agreed in clinic, the order is generated so the fitting can be scheduled, and the SLP report is routed to the office afterward for the file. Clinically identical. Administratively a failed criterion, with two dates to prove it.

What this asks of one coordinator

Look at what an SGD file actually requires someone to verify. Seven coverage criteria from an LCD. Seven elements inside a document written by a clinician at another organization. A relationship check on that clinician. Two dates compared against each other to prove a sequence. A benefit-category test on the physical hardware. A product lookup in a coding database maintained by a different contractor. Narrative fields on four codes. A price list amount. A modifier decision that is legally an attestation. And a five-year lifetime clock running quietly in the background on a patient whose condition is changing every few months.

That is one referral. The coordinator handling it is also handling twelve others, and the SGD file is the slowest one in the stack because the evaluation has to come from outside the building.

None of these teams are careless. They are running a multi-source compliance review out of a fax queue, on a patient population where the clinical need is so obvious that the paperwork feels like the least important part. The failure arrives months later as a remittance line nobody can trace back to the decision that caused it — by which point the device is in the home, the family is depending on it, and the record can no longer be fixed.

Reading the file against the rule before it goes out is the entire job. That is the part DocuFindr automates.