Methodology

Every fact on this site — a Medicare fee, a coverage yes/no, a recall count, a product pick — traces to a named primary source below, not to memory or a guess. This page explains exactly how, how often each source gets rechecked, and the honesty rules you'll see applied on the pages themselves.

The fact

Every one of the 68 HCPCS codes on this site's Medicare coverage checks against CMS's own July 2026 fee schedule (DME26-C) and DY2024 national utilization data — not a summary or a third party's interpretation of either.

Recall status for the same equipment checks against 191 CPSC and FDA records pulled directly from those agencies' own public APIs.

Source: data/coverage_status.json + data/recalls.json (see Sources below for every underlying dataset)

How we verify Medicare coverage facts

Whether Medicare pays for an item — and how much — comes from four government sources, checked together rather than any one in isolation:

How we verify recall history

Recall and safety-enforcement records come from the two federal agencies that actually run consumer and device recalls — queried directly, not aggregated through a third-party recall tracker:

Together those searches currently cover 191 deduplicated records. A record that matches more than one search term (a rollator recall matching both "walker" and "rollator," for instance) is only counted once.

How we verify product picks

Every "verified pick" on a gear page is fetched live against the Amazon Creators API on the date shown next to its price — not pulled from a stock catalog or a manufacturer's marketing page. The ASIN, price, product photo, and fitment specs (weight capacity, handle height, folded width, and similar) all come straight from that listing's own data, stamped with the date it was checked (price_date). Where a listing doesn't publish a spec we need, the page says so directly rather than filling in a typical number.

The honesty rules you'll see in action

These aren't abstractions — they show up as specific sentences on specific pages, because a fact that isn't disclosed this way is a fact an answer engine can misquote.

Absence is not the same as "not covered because it's bad"

When a code shows zero Medicare claims and no fee-schedule entry, we say exactly why, when we know it. The nine bath-safety codes (E0240–E0248 — shower chairs, tub rails, transfer benches) show zero national claims not because CMS overlooked them, but because bath-safety equipment is excluded from the DME benefit category by statute (Social Security Act §1861(s)(6): not "primarily medical in nature"). That's a categorical exclusion, disclosed as one — not silently treated the same as a code CMS simply hasn't gotten around to covering.

"Never searched" is not the same as "searched and clean"

Our recall searches run against a fixed list of product terms. When a product category — cold-therapy machines are the current example — isn't one of those terms, a page says so plainly: the absence of a recall in our data is disclosed as an out-of-scope zero, not a verified-clean record, and readers are told to check CPSC/FDA directly for their specific brand and model before buying secondhand.

Unsourced facts get omitted, not estimated

If a number can't be traced to one of the data files below or a fresh primary-source fetch, it doesn't appear on the page — it's cut, not filled in with a plausible-sounding guess. Earlier drafts of some pages used placeholder price estimates before live product data existed; once real Amazon listings were fetched, those placeholders were replaced and the pages note the correction rather than quietly overwriting it.

The recovery-forum corpus is disclosed as hip-skewed, not knee-verified

Several pages quote recovery-forum posts for color — how people describe using a wedge pillow, whether a reacher actually gets used, whether an ice machine felt necessary. That corpus was built from general lower-extremity joint-replacement threads (BoneSmart, AgingCare), and turned out to be predominantly hip-replacement (THR) content: only 1 of 31 posts actually mentions a knee. Every page that quotes it says so — "predominantly hip/THR-skewed" — rather than presenting hip-replacement commentary as knee-specific consensus. (A planned knee-specific scrape of BoneSmart's TKR forum wasn't run: bonesmart.org/robots.txt explicitly disallows this site's crawler by name, and spoofing past a rule that names it specifically would defeat the point of checking robots.txt at all.)

What this site does not do

VerifiedCareData verifies equipment, cost, and coverage facts. It does not, and will not:

Where a page touches anything close to these lines, it says outright to check with your surgeon, PT, or supplier instead of guessing — see the medical-disclaimer box on the affected pages.

Refresh cadence

DataHow often we recheckWhy
DMEPOS fee schedule + HCPCS codesQuarterlyCMS releases new fee-schedule and HCPCS files every January, April, July, and October. The current pull is the July 2026 release (DME26-C); the next is due October 2026.
DMECS product classificationsQuarterlyTracks the same HCPCS/PCL update cycle as the fee schedule.
MCD DME MAC policy articlesRechecked quarterly, alongside the fee scheduleArticle revisions are rare and irregular, but we check for an updated revision date every quarter rather than assuming a citation is still current indefinitely.
CPSC + openFDA recall dataWeekly-capableBoth agencies' APIs are free, unauthenticated, and low-volume enough to query far more often than we need to — we can turn the crank as often as the data actually changes.
CMS DMEPOS utilization (claims)Annual, live-fetched (not cached)CMS publishes one calendar year of national claims data per year, with roughly an 18-month lag before the newest year is available. Live-fetching (instead of caching a snapshot) means a recheck always pulls whatever year is currently published.
Amazon product picksPer page, stamped with a price_datePrices and availability shift; every pick shows the exact date it was last checked rather than an unstamped "current price."

Affiliate disclosure

We earn a commission if you buy through the Amazon links on our gear pages (Amazon Associates, tag verifiedcare-20), routed through /go/ redirects on this site. It doesn't change the price you pay, and it doesn't change which products we pick or what we say about them — picks are chosen before any affiliate link is attached, based on live fitment specs and verified pricing, not commission rate.

Two places on this site are deliberately kept free of affiliate links, by design, not oversight:

About the byline

Erin Rose is a healthcare price-transparency analyst who also works on CareCost, a separate healthcare-cost-estimation project. She reviews and is credited on every page of this site. No clinical credentials are claimed anywhere on this site, because none apply here — the expertise behind this site is in reading and reconciling government pricing, coverage, and safety data, not in medicine.

Found something wrong? Every fact here is meant to be checkable against the source it cites — if one doesn't hold up, tell us and we'll fix it.

Sources

  1. CMS HCPCS Level II quarterly file (updates and code lists) — July 2026 release used for current code descriptions
  2. CMS DMEPOS Fee Schedule — July 2026 release, DME26-C — purchase and rental fee ranges
  3. CMS DMEPOS utilization by Geography and Service (data.cms.gov) — live API; current published year is DY2024, an ~18-month lag as of this check
  4. CMS Medicare Coverage Database (MCD) — DME MAC Policy Articles — coverage rules, cited by article ID, e.g. Walkers A52503, Canes and Crutches A52459, Commodes A52461, Hospital Beds A52508, Seat Lift Mechanisms A52518, Patient Lifts A52516, Manual Wheelchair Bases A52497
  5. openFDA Device Recall database — phrase-quoted product_description search
  6. openFDA Device Enforcement database — phrase-quoted product_description search
  7. CPSC SaferProducts.gov Recall API — ProductName search, no API key required
  8. Amazon Creators API — live product search/detail lookup for every verified pick — ASIN, price, image, and spec bullets, each stamped with its own price_date
  9. data/DATA-README.md (this site's repository) — full schema, refresh scripts, and known gotchas for every dataset above