How to Bill S5170 for Home-Delivered Meals

S5170 is a HCPCS Level II code. In the CMS HCPCS file its long descriptor reads: home delivered meals, including preparation; per meal. Two words in that sentence shape every claim you will send. Including preparation means the code covers the meal as it arrives, not a separate cooking charge. Per meal means the unit is one meal, not one day and not one delivery.

S5170 is an S code. CMS describes S codes as used primarily by private insurers, and also by Medicaid programs, and not payable by Medicare. In the HCPCS file the code carries coverage code I, not payable by Medicare. In practice, the payers who pay S5170 are state Medicaid programs and the managed care plans that run their home and community based services.

Medicaid pays for home-delivered meals mostly through waivers that keep people at home instead of in a nursing facility. In its technical guide for 1915(c) home and community based services waivers, CMS explains that a waiver may not pay for room and board, where board means three meals a day or any other full nutritional regimen, but it may cover meals on wheels or similar services that bring one meal each day to a participant living in their own home.

Each state then writes its own definition: who qualifies, how many meals a person may receive, what each meal must contain. Many states deliver the benefit through managed care, so the plan that authorizes the meals, the plan that pays the claim and the rules on the claim all belong to the member's plan, not to the state directly.

• The authorization comes from the member's plan, with a number of meals and a start and end date.
• The claim goes to that same plan, under its payer ID, usually through a clearinghouse.
• The plan's provider manual decides details the HCPCS descriptor leaves open, such as modifiers and how to date a multi-day delivery.

Because S5170 is billed per meal, the units on a claim line are meals. The CMS claim form instructions say to enter the number of days or units for each line, and to enter 1 when only one service was performed. A client who received two meals on Tuesday is two units of S5170 for Tuesday.

The third row is where meal programs lose the most time. Weekly or twice-weekly drops are common, and plans do not all read them the same way. Some expect a single line on the delivery date; others expect one line per day the meals cover. The HCPCS descriptor does not settle it, so the plan's billing manual or provider services team has to.

Meal claims are professional claims: the CMS-1500 form on paper, the EDI 837P electronically. CMS states that the 837 professional is the standard for sending these claims electronically, and the fields map one to one.

These instructions come from the Medicare claims processing manual, and Medicaid plans use the same form, but each plan can add its own requirements. The authorization number is the field most often rejected: a typo, an expired authorization or a number from the wrong plan all send the claim back before it is paid.

In Florida, home-delivered meals are a service of the Statewide Medicaid Managed Care long-term care program. The coverage policy incorporated by rule 59G-4.192 defines them as nutritionally sound meals delivered to an enrollee's home when the enrollee has difficulty shopping for or preparing food without assistance.

• Each meal must provide at least 33 1/3 percent of the current Dietary Reference Intake.
• Meals must also follow the current Dietary Guidelines for Americans.
• The policy's procedure code table lists S5170, home delivered meals, with no modifier.
• The policy itself sets no limit on meals per day: the enrollee's plan authorizes the number.

Because the program runs through managed care plans, a Florida meal provider bills each plan separately, under that plan's payer ID, with that plan's authorization number. The Florida guide to long-term care billing goes further into the program itself.

1. Billing meals that were planned rather than delivered: a missed stop or a hospital stay still shows up on a weekly batch built from the schedule.
2. Reading a weekly authorization as daily, or the reverse.
3. Billing past the authorization's end date while the renewal is still on its way.
4. Billing the same day twice after rerunning a batch for a period that was already sent.
5. Sending the claim to the wrong plan after a member changed plans in the middle of the month.

None of these is caught by the HCPCS code itself. They are caught by comparing three things before the claim leaves: what the plan authorized, what was actually delivered, and what has already been billed.

Zeumatic was built first for meal programs. Each client carries their plan, their authorization and the meals each delivery brings; AI reads the authorization PDF so the office checks a filled form instead of typing one. Routes are planned and optimized in Spoke, and the days Spoke confirms as delivered come back to Zeumatic.

Claims are built per served day under S5170, with the meals as units, sent to each plan through Availity, and the database refuses to bill the same day twice for the same client. Paused clients are not billed, and the daily checks list who cannot be billed before the batch leaves.