Pain Point, Solved 4.9 ★★★★★ Google Rating

How Do DME Suppliers Check Same-or-Similar History Before Shipping Supplies?

DME suppliers check same-or-similar history by running the device HCPCS against the beneficiary’s claims record in the MAC portal or IVR before every new setup and before resuming a lapsed supply schedule, because Medicare pays a supply only against a base device already in that patient’s history, and patients switch suppliers or pick up equipment elsewhere without telling anyone. The denial is rarely an ordering mistake; it is that a same-or-similar item was already on file inside its reasonable useful lifetime, and no one looked before the box left the dock. The fix has four moves: run the same-or-similar check against the exact HCPCS before setup, check across all four DME jurisdictions when the patient may have moved, gate the shipping queue so nothing ships without a completed check, and re-verify before restarting any lapsed schedule. We run those moves inside the portals you already use, so the supply you ship is a supply that will actually pay. The table of contents maps the whole method; the moves after it are the detail.

Why a Device Already on File Kills Your Supply Claim

The goal is simple: no product leaves the dock until a same-or-similar check clears, so nothing you ship becomes an unrecoverable loss. Here is what does that, move by move.

1. Run the HCPCS Against the Claims History Before Setup

Before any new setup ships, run the device HCPCS through the MAC portal or IVR against the beneficiary’s claims history. You are looking for the same or a similar item already rented or owned inside its reasonable useful lifetime, which for most equipment runs about five years. If a matching device is on file, the supply you are about to ship will not pay, no matter how clean your order is. Four minutes of checking is the difference between a paid claim and product you cannot get back.

2. Check All Four Jurisdictions When the Patient May Have Moved

A same-or-similar item does not have to be on file in your jurisdiction to deny your claim. If a beneficiary moved, snowbirds between states, or has any history of getting equipment elsewhere, a device on file in another DME MAC jurisdiction will still trigger the denial. When there is any reason to believe the patient obtained a similar item outside your region, check the other jurisdictions too, because the claims system sees all four and your setup queue usually does not.

3. Gate the Shipping Queue on a Completed Check

The denial happens when product ships ahead of the check, so put the check in front of the dock. Nothing leaves until the same-or-similar result is documented in the order, and any hit routes to a person before a box is packed. This is the move that turns a four-minute verification into a hard requirement instead of a step someone skips on a busy intake day. A gated queue means the unrecoverable denial simply stops happening, because the product never leaves without a clear check.

4. Re-Verify Before Restarting a Lapsed Supply Schedule

A patient who paused therapy and came back is not the same as a fresh setup, and treating them like one is where lapsed schedules turn into denials. In the gap, the patient may have gotten a new device elsewhere, or the old base equipment may have aged out of its useful lifetime. Before resuming any lapsed resupply, re-run the same-or-similar and eligibility check as if it were day one, because the claims history that governs your supply may have changed while the schedule was dark.

5. Hand Same-or-Similar Checks to a Dedicated Team

Suppliers that stop eating shipped-product denials do it by handing same-or-similar and eligibility verification to a dedicated team: remote specialists who run every HCPCS against the claims history, check across jurisdictions, and gate the queue, live in 1 to 2 weeks. Your intake staff go back to processing orders, a trained backup covers every gap, and the unrecoverable denial stops being the loss nobody saw coming. Below is what it sounds like when nobody owns this yet, in suppliers’ own words.

Key Pain Points and Discussions by Providers

real reports from practice staff, lightly edited

“We shipped ninety days of sensors to a new patient, and the claim came back same-or-similar. Turned out the receiver was already on file under another supplier with an active rental. The product was at the patient’s house and we ate the whole thing. Nobody here did anything wrong except not see a device we had no way to see.” – billing lead, DME supplier

“The check takes four minutes and the denial is a hundred percent loss, and we still skip it on busy days because there is no gate stopping the shipment. That math is insane when you say it out loud, but when the orders are stacking up, the box goes out before anyone runs the history.” – operations manager, DME supplier

“Half our same-or-similar denials are patients who snowbird. The device is on file in another jurisdiction, our setup queue never sees it, and we find out only when the claim bounces. If we are not checking all four jurisdictions, we are basically guessing on anyone who spends winters out of state.” – intake coordinator, DME supplier

“The lapsed ones get us the most. A patient goes quiet for six months, comes back, and we resume the schedule like nothing changed. But in that gap they got a new device somewhere else, and now our resupply denies. We treat a restart like a refill when it is really a brand-new verification.” – billing lead, DME operation

“We appealed one of these thinking the order justified it, and the answer was basically that medical necessity is not the question. The question is whether a similar item was already in the history, and it was. There is nothing to argue. You either checked before you shipped or you did not.” – revenue cycle lead, DME supplier

Our Answer

Here is what we actually do. A dedicated remote specialist runs the device HCPCS against the beneficiary’s claims history in your MAC portal or IVR before every new setup, and checks across all four DME jurisdictions whenever the patient may have obtained equipment elsewhere. The shipping queue is gated on that result, so nothing leaves the dock until the same-or-similar check is documented and any hit is worked by a person first. Before any lapsed schedule resumes, they re-verify as if it were day one, because a device that aged out or a new item picked up elsewhere changes what your supply can pay against. Our specialists are credentialed professionals, overseas-trained physicians and US-licensed nurses and pharmacists, working inside the portals and order systems you already use, with AI drafting the first pass and a human verifying every check. This is our eligibility and verification support built for DME same-or-similar, in one paragraph.

Why This Keeps Happening

If the order is clean, why does the supply still deny? Because Medicare is not asking whether the patient needs the item; it is asking whether a same or similar device is already sitting in that beneficiary’s claims history within its reasonable useful lifetime, which the DME MACs generally set at about five years for durable equipment. A supply pays only against a covered base device on file, so when a similar item is already there under another supplier, your claim has nothing valid to attach to. It is a history question, not a necessity question, and that is why a documented order does not save it.

The scale of this is the second half of the problem. CMS data has pointed to same-or-similar failures as a leading driver of DME denials, with a large share of denied claims tracing back to a supplier not verifying whether a same or similar item was already on file. These are not edge cases; they are one of the most common ways clean orders turn into unpaid product. Closing that gap before the box ships is exactly what a disciplined insurance eligibility verification workflow is built to do.

And the cost structure is what makes this denial different from most. A denied office visit is revenue you did not collect. A same-or-similar denial on shipped supplies is worse: the product is already at the patient’s home, it is consumable or fitted, and it is not coming back, so you absorb the cost of goods on top of the lost reimbursement. Multiply that across a busy intake queue where the check gets skipped on high-volume days, and the four-minute step you skipped becomes the most expensive shortcut in the operation.

⚠️ The quiet one that hurts most: The quiet one that hurts most: the out-of-jurisdiction device you never thought to check. A patient who winters in another state can have a same or similar item on file in a different DME MAC jurisdiction, invisible to your local setup queue, and your claim denies for equipment you had no reason to know existed. It reads like bad luck, but it is a checkable fact. Unless someone runs the history across all four jurisdictions for any patient who may have moved, the most avoidable denials are the ones hiding one region over from where you looked.

Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:

What you tried What actually happened Who ended up doing the work
Trusted the order and shipped without a check Denied same-or-similar when a device was already on file; product gone, cost of goods eaten Whoever packed the box that day
Checked only the local jurisdiction Missed devices on file in other DME MAC jurisdictions for patients who moved or snowbird The local portal, blind to three regions
Treated a lapsed restart like a routine refill Resupply denied because a new device was picked up elsewhere during the gap The refill queue, on autopilot
Gave same-or-similar checks to a dedicated specialist Every HCPCS run against history, all jurisdictions checked, queue gated before anything ships Someone whose whole job it is

The Solution

So what does “someone whose whole job it is” look like before a box ships? The specialist starts where the intake queue usually cannot: running the device HCPCS against the beneficiary’s claims history in your MAC portal or IVR, looking for a same or similar item already on file inside its useful lifetime. When the patient may have obtained equipment in another region, they check across all four DME jurisdictions, not just yours. Most shipped-product denials are a verification-timing problem, and that is exactly what dedicated eligibility and verification support is built to solve, before the product ever leaves the dock.

Then comes the gate. Nothing ships until the same-or-similar result is documented in the order, and any hit routes to a person who works it before packing begins. If the check surfaces a device already on file, the setup pauses and the situation gets resolved, a rejected order, a coordination-of-benefits path, or a conversation with the patient, instead of a box going out that guarantees a loss. Your intake team feels the change fast: the unrecoverable denial they used to absorb on busy days simply stops arriving, because the busy day no longer skips the check.

Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow pulls the history and flags the same-or-similar hits; a person confirms the read, checks the jurisdictions, and clears the order to ship. Every security control that protects the beneficiary data moving through that verification is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving patient eligibility data through a verification workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team run your same-or-similar checks better than your own intake staff? Because reading claims history and clearing eligibility is their entire day, not the thing they squeeze between packing orders. The people running your checks are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US DME eligibility and same-or-similar workflows. They know how to read a reasonable useful lifetime, when a lapsed schedule needs a full re-verify, and why an out-of-jurisdiction device still denies your claim. That is not a generalist task handed to whoever is free at the dock; it is a specialty.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical supplier is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so a setup never ships unchecked because the one person who handles verification is on vacation.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.

Put the routine and the people together, and a specific list of things simply stops happening.

✓ What stops happening: What stops happening: the ninety-day supply shipped to a patient with a device already on file. The unrecoverable product cost eaten on a busy intake day. The out-of-jurisdiction device nobody thought to check. The lapsed schedule resumed like a routine refill that denies on the first claim. The four-minute check skipped under pressure that turns a clean order into a total loss.
2-Week Free Trial

Ready to Stop Eating Same-or-Similar Denials?

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented verification workflow: which HCPCS to run for which setup, how far back the reasonable useful lifetime reaches for each item, when to check all four jurisdictions, and the exact gate that stops a shipment until the check clears, all written down and worked the same way every time. Before we run a single check for a new supplier, we chart your top same-or-similar denials by product so we can see where shipped product is actually being lost, and we build the workflow against that, not against a generic template.

From there the workflow becomes a living playbook rather than knowledge in one coordinator’s head. It records which items age out at which useful-lifetime marks, how to spot a patient who may have equipment in another jurisdiction, how to handle a same-or-similar hit before setup, and the re-verify path for every lapsed schedule. It is written down, kept current as the DME MACs update guidance, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so a box never ships unchecked because one person is away.

That is the difference between eating this month’s shipped-product denials and fixing the process for good, and it is what a dedicated eligibility verification partner actually buys you. A coordinator leaving used to mean the checks got skipped and the losses started again. Under this model the workflow keeps running, the playbook stays, the backup steps in, and a same-or-similar denial stops being the loss you find out about after the product is already gone.

The Whole Thing in Four Sentences

DME same-or-similar denials keep happening because Medicare pays a supply only against a base device already in the beneficiary’s claims history, and patients switch suppliers or get equipment elsewhere without telling anyone, so a device on file inside its useful lifetime kills your claim no matter how clean the order is. Trusting the order and shipping, checking only your local jurisdiction, or resuming a lapsed schedule like a routine refill all fail the same way. The fix is to run the HCPCS against the claims history before setup, check all four jurisdictions when the patient may have moved, gate the shipping queue on a completed check, and re-verify before restarting any lapsed schedule. A multi-site DME supplier runs exactly this model with us today, names withheld, no patient data shown.

If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.

Ready to stop eating same-or-similar denials? Try us risk free: two weeks, your real setup and resupply queue, dedicated specialists running every check before the box ships, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.

Transparent Weekly Pricing

One Flat Weekly Rate. 45 Hours of Coverage.

No hourly meters, no setup fees, no long-term contracts. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.

Single
$399/ week

One dedicated remote specialist running same-or-similar and eligibility checks before every setup and resupply, single-site DME supplier

Enterprise
$299/ week

10+ remote specialists, multi-state DME network, MSO, or PE-backed platform running same-or-similar checks across many order intake teams

  How Pricing Works

45 hours of coverage for less than others charge for 40.

Standard US full-time year: 40 hrs x 52 weeks = 2,080 hours, the federal basis for computing hourly pay per the U.S. Office of Personnel Management. A Staffingly plan: 45 hrs x 52 weeks = 2,340 hours a year, that is 260 additional hours included in your flat rate. $399/week x 52 = $20,748 a year / 2,340 hours = $8.87 per hour. Typical US market rates for healthcare virtual assistants run $9.50 to $13.00 per hour for 40 hours of coverage.

Trained backup VA Dedicated success manager Monthly training updates HIPAA-certified staff $5M E&O and cyber liability

Clear Every Same-or-Similar Check This Month

You have seen the whole method. The pilot proves it on your own setup and resupply queue, with a tracker your team can watch every day.

Start My 2-Week Free Trial

Request Information

Single specialty or multi-site? One payer or many? Tell us your situation and we will map the right coverage within 24 hours.

Frequently Asked Questions

Because Medicare pays a supply only against a base device already in the beneficiary’s claims history, and it is asking whether a same or similar item is already on file inside its reasonable useful lifetime, not whether the order was justified. If a matching device is already there, often under a different supplier, your claim has nothing valid to attach to. A clean order does not overcome a device that is already on record, which is why the check has to happen before you ship.
The DME MACs generally apply a reasonable useful lifetime of about five years for durable equipment, so a same or similar device can block your claim for years after it was first supplied. The exact window depends on the item, which is why the check runs the specific device HCPCS against the claims history rather than assuming a device from a few years ago has aged out. Reading that useful-lifetime line correctly is part of clearing the setup.
Yes, whenever there is reason to believe the patient may have obtained equipment elsewhere. A same or similar item on file in another DME MAC jurisdiction will still deny your claim even though your local queue cannot see it. Patients who move or spend seasons in another state are the common trap, so any setup where the beneficiary may have crossed regions should be checked across all four jurisdictions, not just your own.
Because a patient who paused therapy and returned may have picked up a new device somewhere else during the gap, or the original base equipment may have aged out of its useful lifetime. Treating a restart like a routine refill skips the verification that a fresh setup would get. The fix is to re-run the same-or-similar and eligibility check before resuming any lapsed schedule, as if it were day one, because the history that governs your supply may have changed.
Staffingly charges a flat weekly rate per dedicated remote specialist, with lower per-person rates for teams of 5 or more and 10 or more. Every plan covers 45 hours of coverage per week with a trained backup included, and there is no percentage of your reimbursement. The pricing section on this page shows how the flat rate compares with typical US market rates for this work.
No. AI drafts the first pass, pulling the claims history and flagging same-or-similar hits, and a credentialed human verifies every check, confirms the jurisdictions, and clears the order to ship. The judgment stays with people. Automation removes the repetitive lookup work so the specialist spends their time on the setups that need a human read, not on retyping the same portal queries.
No. Our specialists work inside the MAC portals, IVR, and order intake systems you already use, so there is no migration and no new platform for your staff to learn. They run the checks where your orders already live and document the result in your workflow, which is why a typical supplier is live in 1 to 2 weeks rather than months.
Usually within the first two weeks. Once every setup and resupply is gated on a completed same-or-similar check and the checks run across jurisdictions, the orders that used to ship blind stop leaving the dock, and the unrecoverable denials that used to arrive after the product was gone start disappearing from the queue.
Your dedicated specialist works a 9-hour day, Monday to Friday, which is 45 hours of coverage each week. The ninth hour is part of the flat weekly rate, not billed as overtime. Over a year that is 2,340 hours of coverage, against the standard US full-time work year of 2,080 hours (40 hours x 52 weeks, the same basis the U.S. Office of Personnel Management uses to compute hourly rates of pay). That is how $399 per week works out to $8.87 per hour.
Dan Nandan, CEO of Staffingly, Inc.

Written By

Dan Nandan
Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From

Sources & References

  • CMS Medicare Claims Processing and DME Coverage Resources. Federal guidance on durable medical equipment billing, reasonable useful lifetime, and same-or-similar coverage rules. cms.gov
  • Noridian DME MAC Same-or-Similar Guidance. Medicare Administrative Contractor guidance on checking beneficiary claims history for same or similar items before supplying DME. noridianmedicare.com
  • CMS DMEPOS Standard Documentation Requirements (Article A55426). Federal documentation requirements for claims submitted to the DME MACs, including verification obligations. cms.gov
  • MGMA Practice Operations and Revenue Cycle Resources. Benchmarks and guidance on eligibility verification and denial prevention for medical suppliers and group practices. mgma.com
  • HFMA Revenue Cycle and Denials Management Resources. Guidance on eligibility-related denials, appeals workflow, and the revenue impact of preventable denials. hfma.org