Inelastic adjustable-strap below-knee gradient compression wrap with mechanical tension-calibration indicators, launched into the Medicare lymphedema compression benefit and coded to A6583
8/9
factors scored
4/4
core factors
7/56
claims verified
0
refuted
How to read a tag. Only
verified counts toward a score — it means a typed connector
resolved this against a primary US federal record.
unconfirmed means the Verifier checked and could not confirm,
which very often means the source could not be queried at all rather than that
the claim is doubtful. refuted means a primary source
contradicts it. unverified means nothing has checked it yet.
claim 1verifiedUS
21 CFR 880.5780 exists and is titled "Medical support stocking"
jurisdiction: US — confidence: verified — source: eCFR versioner title-21, issue 2026-08-19, section=880.5780 (connectors regulation 880.5780 --title 21 --expect "medical support stocking"). Connector detail: section exists and contains "medical support stocking"; heading reads "§ 880.5780 Medical support stocking."…the full check Amendment history ends "[45 FR 69682, Oct. 21, 1980, as amended at ... 90 FR 55987, Dec. 4, 2025]".
claim 2verifiedUS
21 CFR 880.5780(b) covers a medical support stocking "for medical purposes other than the prevention of pooling of blood in the leg", is Class I, and is exempt from the premarket notification procedures in subpart E of part 807
jurisdiction: US — confidence: verified — source: eCFR versioner title-21, issue 2026-08-19, section=880.5780, paragraph (b). Verbatim: "(b) Medical support stocking for general medical purposes —(1) Identification. A medical support stocking for general medical purposes is a device that is constructed of elastic…the full check material and designed to apply controlled pressure to the leg and that is intended for medical purposes other than the prevention of pooling of blood in the leg. (2) Classification. Class I. The device is exempt from the premarket notification procedures in subpart E of part 807 of this chapter, subject to the limitations in § 880.9. The device is also exempt from the current good manufacturing practice requirements of the quality management system regulation in part 820 of this chapter, except for requirements concerning records and complaint files under § 820.35." All three asserted elements — paragraph text, Class I, subpart-E exemption — are confirmed against primary text, and the exemption is broader than claimed (it reaches part 820 as well; see the capital-intensity claim). Two qualifications the Verifier is recording rather than burying, neither of which refutes this claim but both of which bear on whether this device is inside paragraph (b) at all — see the "wrap is not a stocking" claim below: (i) the paragraph (b)(1) identification requires a device "constructed of elastic material", and this candidate's mechanism is explicitly inelastic (short-stretch); (ii) § 880.9 (checked separately, eCFR versioner title-21, issue 2026-08-19, section=880.9) states the exemption "is only to the extent that the device has existing or reasonably foreseeable characteristics of commercially distributed devices within that generic type", and requires a premarket notification anyway where "(a) The device is intended for a use different from the intended use of a legally marketed device in that generic type ... e.g., ... the device is intended for lay use where the former intended use was by health care professionals only" or "(b) The modified device operates using a different fundamental scientific technology than a legally marketed device in that generic type". The candidate's intended_use: is self-application by the patient without a fitter. Whether that is "lay use where the former intended use was by health care professionals only", and whether inelastic short-stretch is a "different fundamental scientific technology" than elastic, are FDA judgments that no connector answers; they are flagged here, not resolved.
claim 3verifiedUS
21 CFR 880.5780(a) covers a medical support stocking intended to prevent the pooling of blood in the legs, is Class II (special controls), and is also exempt from premarket notification
jurisdiction: US — confidence: verified — source: eCFR versioner title-21, issue 2026-08-19, section=880.5780, paragraph (a). Verbatim: "(a) Medical support stocking to prevent the pooling of blood in the legs —(1) Identification. ... intended for use in the prevention of pooling of blood in the leg. (2)…the full check Classification. Class II (special controls). The device is exempt from the premarket notification procedures in subpart E of part 807 of this chapter subject to the limitations in § 880.9." The Generator flagged premarket-exempt Class II as unusual; the primary text confirms it as written. The 880.9 limitation language the Generator did not read is now on record under the claim above and applies identically to paragraph (a). Note that paragraph (a) does not carry the part 820 CGMP exemption that paragraph (b) carries — so the venous/blood-pooling marketing copy the frontmatter warns about would cost the QMS exemption as well as Class I.
claim 4verifiedUS
FDA product code FQL is "Stocking, Medical Support (For General Medical Purposes)" and maps to 21 CFR 880.5780
jurisdiction: US — confidence: verified — source: openFDA device/classification product_code=FQL. Connector detail: "Device class 1: Stocking, Medical Support (For General Medical Purposes) (regulation 880.5780, review panel HO)". Device name, class and regulation number all match the claim exactly; the aggregator…the full check page is now superseded by the primary record. Checked against the intended_use: as written (maintenance-phase gradient compression for clinician-diagnosed lower-extremity lymphedema, no venous/blood-pooling claim) — this mapping is what makes that indication a "general medical purpose" rather than a paragraph (a) purpose. Caveat carried forward: an openFDA classification record carries no exemption field, so it is not evidence of the 510(k) exemption — that comes from the regulation text above, and only if the device is in fact within this generic type.
claim 5verifiedUS
FDA product code DWL is "Stocking, Medical Support (To Prevent Pooling Of Blood In Legs)" and maps to 21 CFR 880.5780
jurisdiction: US — confidence: verified — source: openFDA device/classification product_code=DWL. Connector detail: "Device class 2: Stocking, Medical Support (To Prevent Pooling Of Blood In Legs) (regulation 880.5780, review panel HO)". Device name, Class II and regulation number match the claim exactly. Not live…the full check under the current intended_use:; confirms the frontmatter's two-paragraph regulatory design is real rather than assumed.
claim 6unconfirmedUS
The Generator did NOT establish that FDA reads an adjustable-strap inelastic wrap into 880.5780 at all. The regulation says "stocking"; this product is a strapped wrap, not a knitted tube. No product code has been confirmed for "compression wrap" as a distinct generic type, and the Generator is not naming one
jurisdiction: US — confidence: unconfirmed — note: and the primary text makes this a materially larger risk than the Generator framed it, not a smaller one.** Source and reasoning: (i) classification --device-name "compression wrap" --jurisdiction US → unconfirmed, detail: "No classification record found for…the full check query='device_name:\"compression wrap\"'". This null is worth almost nothing as evidence, and the Verifier is recording why rather than letting it read as reassurance: the identical query form classification --device-name "medical support stocking" --jurisdiction US also returned unconfirmed ("No classification record found"), even though FQL and DWL demonstrably exist and are named "Stocking, Medical Support (...)" in that same database. openFDA stores device names inverted-comma-first, so a natural-language device-name probe misses records that exist. Neither null establishes that no wrap generic type exists. Settling this needs the FDA product-code classification database browsed by regulation number (880.5780) and by panel HO, which no connector in this repo does. (ii) The regulation text now read in full cuts against the wrap reading on its face. Both paragraphs of § 880.5780 identify the device as one "constructed of elastic material and designed to apply controlled pressure to the leg" (eCFR versioner title-21, issue 2026-08-19, section=880.5780). This candidate's mechanism: is expressly inelastic (short-stretch) — that is the product's whole therapeutic premise. A device that is not constructed of elastic material does not obviously satisfy the identification paragraph of either (a) or (b), independent of the "stocking" versus "wrap" form-factor question the Generator raised. (iii) § 880.9 adds two further conditions on any Part 880 exemption (eCFR versioner title-21, issue 2026-08-19, section=880.9): the exemption holds "only to the extent that the device has existing or reasonably foreseeable characteristics of commercially distributed devices within that generic type", and a premarket notification is still required where the device "is intended for a use different from the intended use of a legally marketed device in that generic type ... e.g., ... the device is intended for lay use where the former intended use was by health care professionals only", or where it "operates using a different fundamental scientific technology". This candidate's intended_use: is patient self-application "without a fitter" — squarely the lay-use fact pattern the section names. This is unconfirmed, not refuted: whether FDA reads an inelastic strapped wrap into § 880.5780, and whether § 880.9(a)/(b) fire on this indication, are FDA substantial-equivalence and enforcement judgments. The eCFR connector serves regulation text only — it does not reach FDA guidance, product-code assignment practice, or enforcement policy, so it cannot settle an interpretation question. The text is quoted above so a human can make the call. Per the Scores table's own note, the routes that resolve it are a 513(g) Request for Information to FDA or Tier 3 regulatory-counsel review of the draft labelling — neither is an agent action. (i) classification --device-name "compression wrap" --jurisdiction US → unconfirmed, detail: "No classification record found for query='device_name:\"compression wrap\"'". This null is worth almost nothing as evidence, and the Verifier is recording why rather than letting it read as reassurance: the identical query form classification --device-name "medical support stocking" --jurisdiction US also returned unconfirmed ("No classification record found"), even though FQL and DWL demonstrably exist and are named "Stocking, Medical Support (...)" in that same database. openFDA stores device names inverted-comma-first, so a natural-language device-name probe misses records that exist. Neither null establishes that no wrap generic type exists. Settling this needs the FDA product-code classification database browsed by regulation number (880.5780) and by panel HO, which no connector in this repo does. (ii) The regulation text now read in full cuts against the wrap reading on its face. Both paragraphs of § 880.5780 identify the device as one "constructed of elastic material and designed to apply controlled pressure to the leg" (eCFR versioner title-21, issue 2026-08-19, section=880.5780). This candidate's mechanism: is expressly inelastic (short-stretch) — that is the product's whole therapeutic premise. A device that is not constructed of elastic material does not obviously satisfy the identification paragraph of either (a) or (b), independent of the "stocking" versus "wrap" form-factor question the Generator raised. (iii) § 880.9 adds two further conditions on any Part 880 exemption (eCFR versioner title-21, issue 2026-08-19, section=880.9): the exemption holds "only to the extent that the device has existing or reasonably foreseeable characteristics of commercially distributed devices within that generic type", and a premarket notification is still required where the device "is intended for a use different from the intended use of a legally marketed device in that generic type ... e.g., ... the device is intended for lay use where the former intended use was by health care professionals only", or where it "operates using a different fundamental scientific technology". This candidate's intended_use: is patient self-application "without a fitter" — squarely the lay-use fact pattern the section names. This is unconfirmed, not refuted: whether FDA reads an inelastic strapped wrap into § 880.5780, and whether § 880.9(a)/(b) fire on this indication, are FDA substantial-equivalence and enforcement judgments. The eCFR connector serves regulation text only — it does not reach FDA guidance, product-code assignment practice, or enforcement policy, so it cannot settle an interpretation question. The text is quoted above so a human can make the call. Per the Scores table's own note, the routes that resolve it are a 513(g) Request for Information to FDA or Tier 3 regulatory-counsel review of the draft labelling — neither is an agent action.
claim 7unconfirmedUS
Structural null warning, not a claim about the market: because the launch route is 510(k)-exempt, an openFDA 510k or clearances query for competing compression wraps will return nothing. That silence is a property of the exemption, not evidence that no competitor exists
jurisdiction: US — confidence: unconfirmed — note: the interpretive half is sound and now rests on verified primary text, but the literal prediction is not borne out, and the difference matters. The Verifier ran the queries deliberately so the record shows exactly what each null does and does not establish: - `510k…the full check "juxtafit" --applicant "medi" --jurisdiction US → status **refuted**, source_ref null, detail: "No 510(k) record found for device_name='juxtafit' applicant='medi'". - 510k "FarrowWrap" --jurisdiction US → status unconfirmed, source_ref null, detail: "No 510(k) record found for device_name='FarrowWrap'". - 510k "compression wrap" --jurisdiction US → status **verified**, source_ref openFDA device/510k k_number=K162481, detail: "Cleared 510(k): RF1400 Active Compression Wrap / Recovery Force, LLC decided 2017-02-16". **What these establish: nothing whatsoever about the competitive field, and in particular no whitespace and no moat.** The refuted on the medi/juxtafit query is a database-absence status from the connector and **must not be read as a finding that medi has no such product or does not compete** — medi circaid juxtafit/juxta-lite, Essity/BSN JOBST FarrowWrap, Sigvaris Compreflex and Solaris are named as commercially marketed products in this file's own predicate_or_analog: frontmatter, and a 510(k)-exempt device is *expected* to be absent from the 510(k) database. That absence is now confirmed to be structural rather than assumed: § 880.5780(a) and (b) both state the device "is exempt from the premarket notification procedures in subpart E of part 807" (eCFR versioner title-21, issue 2026-08-19, section=880.5780). **Any reading of these nulls as support for Factor 8 (competitive intensity) or Factor 5 (moat) would be a fabricated finding.** **Where the claim as written overreaches:** the prediction that such a query "will return nothing" is false as stated — K162481 is a real cleared device whose name contains "compression wrap". It is an *active* (powered) compression device under a different generic type, so it is not a counterexample to the exemption logic, but it does show the null is not guaranteed and that a name-match hit can arrive from an unrelated regulation. The Generator/Scorer should restate the claim as the interpretive rule it actually is ("a 510(k) null for an exempt generic type is uninformative about competition"), which is what the verified § 880.5780 text supports. **The database where exempt-route competitors actually appear is FDA Establishment Registration & Device Listing, which no connector in this repo reaches** — that remains a Scout/human retrieval, and until it is done the competitor count is unmeasured rather than zero. - 510k "juxtafit" --applicant "medi" --jurisdiction US → status **refuted**, source_ref null, detail: "No 510(k) record found for device_name='juxtafit' applicant='medi'". - 510k "FarrowWrap" --jurisdiction US → status unconfirmed, source_ref null, detail: "No 510(k) record found for device_name='FarrowWrap'". - 510k "compression wrap" --jurisdiction US → status **verified**, source_ref openFDA device/510k k_number=K162481, detail: "Cleared 510(k): RF1400 Active Compression Wrap / Recovery Force, LLC decided 2017-02-16". **What these establish: nothing whatsoever about the competitive field, and in particular no whitespace and no moat.** The refuted on the medi/juxtafit query is a database-absence status from the connector and **must not be read as a finding that medi has no such product or does not compete** — medi circaid juxtafit/juxta-lite, Essity/BSN JOBST FarrowWrap, Sigvaris Compreflex and Solaris are named as commercially marketed products in this file's own predicate_or_analog:` frontmatter, and a 510(k)-exempt device is expected to be absent from the 510(k) database. That absence is now confirmed to be structural rather than assumed: § 880.5780(a) and (b) both state the device "is exempt from the premarket notification procedures in subpart E of part 807" (eCFR versioner title-21, issue 2026-08-19, section=880.5780). Any reading of these nulls as support for Factor 8 (competitive intensity) or Factor 5 (moat) would be a fabricated finding.Where the claim as written overreaches: the prediction that such a query "will return nothing" is false as stated — K162481 is a real cleared device whose name contains "compression wrap". It is an active (powered) compression device under a different generic type, so it is not a counterexample to the exemption logic, but it does show the null is not guaranteed and that a name-match hit can arrive from an unrelated regulation. The Generator/Scorer should restate the claim as the interpretive rule it actually is ("a 510(k) null for an exempt generic type is uninformative about competition"), which is what the verified § 880.5780 text supports. The database where exempt-route competitors actually appear is FDA Establishment Registration & Device Listing, which no connector in this repo reaches — that remains a Scout/human retrieval, and until it is done the competitor count is unmeasured rather than zero.
claim 8unconfirmedUS
HCPCS A6583 exists and is descriptor-defined as "Gradient compression wrap with adjustable straps, below knee, 30-50 mmHg, each"
jurisdiction: US — confidence: unconfirmed — source: none; nothing was searched.connectors hcpcs A6583 --expect "gradient compression wrap with adjustable straps" --jurisdiction US → status unconfirmed, source_ref null, detail: "No local cache at data/hcpcs_level_ii.csv — HCPCS Level II code A6583 cannot be…the full check checked until it exists. See data/README.md for the exact CMS source and expected columns. Do not substitute a web search for this file." This null is the absence of a file in this deployment, not the absence of a code from the HCPCS Level II code set — it is not evidence either way. The descriptor wording, the 30-50 mmHg range and the below-knee scope that this product was deliberately sized to are all still unread against primary CMS text, which means the single strongest-looking element of the reimbursement story ("the descriptor match is by construction") rests on the same web pages the Generator started with. The Verifier did not re-use those pages and did not substitute a web search. Settles when a human places the CMS HCPCS Level II quarterly file at data/hcpcs_level_ii.csv and this line is re-run.
claim 9unconfirmedUS
Adjacent codes A6552 ("gradient compression stocking, below knee, 30-40 mmHg, each") and A6554 ("below knee, 40 mmHg or greater, each") exist in the same 2024 code set and describe the garment alternative this product competes against
jurisdiction: US — confidence: unconfirmed — source: none; nothing was searched. connectors hcpcs A6552 --jurisdiction US and connectors hcpcs A6554 --jurisdiction US → both status unconfirmed, source_ref null, identical detail: "No local cache at data/hcpcs_level_ii.csv — HCPCS Level II code A65xx cannot be…the full check checked until it exists. See data/README.md for the exact CMS source and expected columns. Do not substitute a web search for this file." Same missing-file cause as the A6583 line above; the comparator half of the reimbursement argument is unread for the same reason, not for a different one.
claim 10unconfirmedUS
Lymphedema compression treatment items became a distinct Medicare Part B benefit category for items furnished on or after 2024-01-01, following the Lymphedema Treatment Act as enacted in the Consolidated Appropriations Act, 2023
jurisdiction: US — confidence: unconfirmed — source: none read. No connector in this repo answers this claim, for a reason worth stating precisely: the benefit category is created by statute (an amendment to the Social Security Act), and connectors regulation serves CFR text only — it reaches neither the…the full check US Code nor CMS transmittals, MLN Matters articles or manual instructions, which is where the effective date is actually published. The Verifier nevertheless probed the implementing-regulation side to see whether CFR text touched it: connectors regulation 410.36 --title 42 --expect "lymphedema compression treatment items" → status unconfirmed, source_ref null, detail: "eCFR returned HTTP 503 for 42 CFR 410.36". That section number was the Verifier's own probe, not a citation this claim makes, and the 503 is an infrastructure failure — it establishes nothing about the section or the claim. The eCFR endpoint was down for the whole of this pass: a control lookup of 21 CFR 880.9 — a section the earlier Regulatory pass verified successfully off the same endpoint — returned HTTP 503 and then four consecutive read timeouts to www.ecfr.gov. So no CFR text of any kind could be read today. This is the timing premise of the whole candidate and it remains entirely on secondary sources; it settles from the CMS transmittal / MLN Matters article implementing the LTA, downloaded into data/ by a human or Scout.
claim 11unconfirmedUS
Medicare payment for these items is 80% of the lesser of the supplier's actual charge or the DMEPOS fee schedule amount, with the Part B deductible and coinsurance applying
jurisdiction: US — confidence: unconfirmed — note: two independent checks, both blocked, neither of them evidence of absence: (i) connectors payment A6583 --jurisdiction US → status unconfirmed, source_ref null, detail: "No local cache at data/hcpcs_payment_rates.csv — payment rate for A6583 cannot be checked…the full check until it exists. See data/README.md for the exact CMS source and expected columns. Do not substitute a web search for this file." So there is still no dollar figure for A6583 anywhere in this file, correctly — and the 80%-of-lesser rule is a formula whose operand is unknown. A payment rule verified without a fee schedule amount would tell a reader nothing about whether this product is economic at DMEPOS margins. (ii) The rule itself lives in CFR text, so the Verifier probed connectors regulation 414.210 --title 42 --expect "80 percent of the lesser of the actual charge" → status unconfirmed, source_ref null, detail: "eCFR returned HTTP 503 for 42 CFR 414.210". Section number again the Verifier's probe rather than the claim's citation, and again an infrastructure failure rather than a finding — see the control-lookup note on the benefit-category line above. Re-run both when eCFR is reachable and data/hcpcs_payment_rates.csv is present; confirm the schedule field reads DMEPOS, since a PFS or OPPS row for a supply code would be the wrong number. (i) connectors payment A6583 --jurisdiction US → status unconfirmed, source_ref null, detail: "No local cache at data/hcpcs_payment_rates.csv — payment rate for A6583 cannot be checked until it exists. See data/README.md for the exact CMS source and expected columns. Do not substitute a web search for this file." So there is still no dollar figure for A6583 anywhere in this file, correctly — and the 80%-of-lesser rule is a formula whose operand is unknown. A payment rule verified without a fee schedule amount would tell a reader nothing about whether this product is economic at DMEPOS margins. (ii) The rule itself lives in CFR text, so the Verifier probed connectors regulation 414.210 --title 42 --expect "80 percent of the lesser of the actual charge" → status unconfirmed, source_ref null, detail: "eCFR returned HTTP 503 for 42 CFR 414.210". Section number again the Verifier's probe rather than the claim's citation, and again an infrastructure failure rather than a finding — see the control-lookup note on the benefit-category line above. Re-run both when eCFR is reachable and data/hcpcs_payment_rates.csv is present; confirm the schedule field reads DMEPOS, since a PFS or OPPS row for a supply code would be the wrong number.
claim 12unconfirmedUS
Coverage is available for beneficiaries with any diagnosis of lymphedema, rather than being restricted to a subtype
jurisdiction: US — confidence: unconfirmed — source: none; nothing was searched. connectors coverage A6583 --expect-stance covered --jurisdiction US → status unconfirmed, source_ref null, detail: "No local cache at data/medicare_coverage_policies.csv — Medicare coverage policy for A6583 cannot be checked until it…the full check exists. See data/README.md for the exact CMS source and expected columns. Do not substitute a web search for this file." Two things to keep straight when this is re-run. First, the missing file means no policy was looked for, so nothing here bears on whether an NCD or LCD exists. Second, even with the cache present the coverage connector verifies the existence of a policy, not a positive coverage stance — many LCDs are non-coverage or impose diagnosis and quantity/frequency limits, and "any diagnosis of lymphedema" is exactly the kind of breadth an LCD narrows. Since the breadth is what the claim asserts, resolving it needs the DME MAC Local Coverage Determination and its Policy Article read directly (L-number pulled from the CMS Medicare Coverage Database, not guessed), which is a human/Scout retrieval and no connector call.
claim 13unconfirmedUS
RT and LT laterality modifiers are required when billing gradient compression garments and related supplies
jurisdiction: US — confidence: unconfirmed — note: no connector in this repo reaches this source and none was substituted. Modifier requirements are published in DME MAC Policy Articles and CMS claims-processing manual instructions; hcpcs returns a code descriptor, coverage returns policy existence, and…the full check neither carries billing-modifier rules, so there was no typed call to make. The original source remains a contractor web page read via search, which is secondary. Low commercial stakes on its own, but it belongs with the PDAC/supplier-enrolment mechanics below as part of the billing-readiness work that has to be done by a human before first revenue.
claim 14unconfirmedUS
The Generator believes a PDAC coding-verification review may be required before a specific manufacturer's product may be billed under A6583, and that quantity/replacement limits per limb per benefit period exist
jurisdiction: US — confidence: unconfirmed — note: no connector reaches the PDAC (DME MAC pricing contractor) coding-verification process or its published product list, and none was substituted; the claim still rests on article titles surfaced by web search. Nothing in this pass established either the requirement…the full check or any quantity allowance, and consistent with the claim as written no number is asserted here. The related coverage A6583 call that would have surfaced quantity/replacement limits from an LCD returned unconfirmed for the missing-cache reason recorded above, so that route is also unread. Flagging the asymmetry deliberately: this is the item most likely to gate first revenue for a device whose FDA route is exempt, and it is the item with the least primary evidence behind it in the entire file — PDAC verification plus DMEPOS supplier enrolment (CMS-855S), not FDA, is where the calendar risk sits.
claim 15unconfirmedUS
TAM component 1 — annual Medicare claim volume for A6583
jurisdiction: US — confidence: unconfirmed — source: none; nothing was searched, and the Generator still states no number. connectors procedures A6583 --jurisdiction US → status unconfirmed, source_ref null, detail: "No local cache at data/medicare_procedure_volumes.csv — procedure volume for A6583 cannot be…the full check checked until it exists. See data/README.md for the exact CMS source and expected columns. Do not substitute a web search for this file." This is the one genuinely checkable component of the three and it stayed unchecked for a missing-file reason, so the decomposition is still the right shape but has zero of three components resolved. When the cache lands, carry two caveats into the line: a Medicare FFS count is a floor on US volume and never a market size (it excludes Medicare Advantage, commercial, Medicaid, VA and cash-pay), and for a code first payable 2024-01-01 the published utilisation year may not exist yet or may catch only a partial, still-climbing uptake curve — a low number here would be a young-code artefact, not a small market.
claim 16unconfirmedUS
TAM component 2 — net selling price per below-knee wrap, which is bounded above by the DMEPOS fee schedule allowable for A6583 and below by a fitter-channel margin
jurisdiction: US — confidence: unconfirmed — note: permanently so absent a human-attached licensed source. connectors market "net selling price per below-knee gradient compression wrap bounded by the DMEPOS fee schedule allowable for A6583" → status unverifiable, source_ref null, detail: "Market-size claim ... has…the full check no free, authoritative, machine-queryable source. Stays unconfirmed permanently unless a human attaches a licensed report and edits the claim by hand." The upper bound is separately unread: payment A6583 returned unconfirmed (no data/hcpcs_payment_rates.csv, recorded above), so the ceiling that would discipline this estimate does not exist in this deployment either. Correctly, no price is asserted.
claim 17unconfirmedUS
TAM component 3 — addressable share assumption: the obtainable segment is below-knee lymphedema wrap volume dispensed through DMEPOS suppliers and certified fitters, assumed by the Generator at 10-20% within five years against four named incumbents
jurisdiction: US — confidence: unconfirmed — note: permanently so. connectors market "obtainable share of below-knee lymphedema wrap volume through DMEPOS suppliers and certified fitters, 10-20% within five years against four incumbents" → status unverifiable, source_ref null, same detail as component 2. Worth…the full check naming what this component actually is: it embeds a switching assumption about who chooses the product, which is an adoption claim in market-share clothing, and the adoption route is unverifiable by design too (see the fitter/supplier assumption below). So this component is unconfirmable by two independent paths, and the Verifier produced no estimate of its own to fill the gap.
claim 18unconfirmedUS
Denominator context, explicitly aggregator-grade — US adult lymphedema prevalence is commonly cited in the 3-5 million range
jurisdiction: US — confidence: unconfirmed — note: connectors market "US adult lymphedema prevalence commonly cited at 3-5 million" → status unverifiable, source_ref null, detail: "Market-size claim ... has no free, authoritative, machine-queryable source." Strictly, this is an epidemiology claim and no…the full check connector in this repo answers one at all: literature is a Stage 0 scan that returns a ScanResult carrying no confidence tag and cannot verify a claim (see connectors/result.py), so even a clean PubMed sweep could not move this line. The file's own instruction stands and the Verifier is restating it: this is not a TAM input and must not be multiplied by anything. It records what the Generator did and did not find, nothing more.
claim 19unconfirmedUS
FTO — no patent search was performed and no patent number is named. The likely estates sit with medi GmbH (circaid adjustable-strap wraps), Essity/BSN (FarrowWrap), Sigvaris (Compreflex) and Solaris
jurisdiction: US — confidence: unconfirmed — note: , and specifically unconfirmed as an unexamined field, not as a clear one — this pass did not change that in either direction. Two independent blocks, both recorded so neither can later read as an all-clear: (i) There is no number to look up. `connectors…the full check patent takes a patent_id; the claim names none, and the Verifier did not invent one. No connector in this repo performs patent *discovery* — assignee or CPC-class sweeps are a human/Scout retrieval (USPTO Patents Public Search, Espacenet), not an agent action. (ii) **The lookup path is unavailable anyway.** A probe call to establish connector state returned status unconfirmed, source_ref null, detail: "PATENTSVIEW_API_KEY not set — request one at https://patentsview.org/apis/keyrequest before running Stage 3 IP checks". The probe number was arbitrary and is deliberately not recorded as a claim referent. **The correct reading of both results is "no search was performed" — an absence of found patents is not freedom to operate**, and the Verifier did not fall back to a patent search engine to route around the missing key. The concentration risk the file already names is unchanged: the product's only differentiator, a printed strap elongation window calibrated to a target tension, sits in exactly the narrow art four long-established incumbents would occupy. A definitive answer is a Tier 3 legal FTO opinion; nothing an agent produces is one. (i) **There is no number to look up.** connectors patent takes a patent_id; the claim names none, and the Verifier did not invent one. No connector in this repo performs patent *discovery* — assignee or CPC-class sweeps are a human/Scout retrieval (USPTO Patents Public Search, Espacenet), not an agent action. (ii) **The lookup path is unavailable anyway.** A probe call to establish connector state returned status unconfirmed`, source_ref null, detail: "PATENTSVIEW_API_KEY not set — request one at https://patentsview.org/apis/keyrequest before running Stage 3 IP checks". The probe number was arbitrary and is deliberately not recorded as a claim referent. The correct reading of both results is "no search was performed" — an absence of found patents is not freedom to operate, and the Verifier did not fall back to a patent search engine to route around the missing key. The concentration risk the file already names is unchanged: the product's only differentiator, a printed strap elongation window calibrated to a target tension, sits in exactly the narrow art four long-established incumbents would occupy. A definitive answer is a Tier 3 legal FTO opinion; nothing an agent produces is one.
claim 20unconfirmedUS
Moat lever — the defensible asset is the mechanical tension-calibration indicator (strap elongation window and its calibration to a target sub-bandage pressure profile) plus the certified-fitter and DMEPOS-supplier channel
jurisdiction: US — confidence: unconfirmed — note: checked as two halves, both unresolved, and the claim's own candid framing ("this is a weak moat") is not contradicted by anything found: (i) IP half — inherits the block above verbatim: no number named, PATENTSVIEW_API_KEY not set, no discovery connector. Until…the full check an FTO/IP search exists, the indicator is an asserted differentiator rather than a demonstrated asset, and this half cannot resolve ahead of the FTO line. (ii) Channel half — connectors adoption "the certified-fitter and DMEPOS-supplier channel is a defensible moat for a new entrant" → status unverifiable, source_ref null, detail: "Adoption/preference claim ... asserts what clinicians, payers, or patients would do. No free, authoritative, machine-queryable source answers that — it needs primary research (interviews, survey, published preference study) ... Do NOT substitute a model's own estimate of stakeholder behaviour: a synthetic stakeholder opinion is a fabricated claim." The Verifier produced no such estimate. Note the structural point the verified Regulatory section already established: § 880.5780 exempts the generic type from premarket notification, so the exempt route protects incumbents and entrants symmetrically — it is an open door, not a barrier, and cannot be read as moat evidence in either direction. (i) IP half — inherits the block above verbatim: no number named, PATENTSVIEW_API_KEY not set, no discovery connector. Until an FTO/IP search exists, the indicator is an asserted differentiator rather than a demonstrated asset, and this half cannot resolve ahead of the FTO line. (ii) Channel half — connectors adoption "the certified-fitter and DMEPOS-supplier channel is a defensible moat for a new entrant" → status unverifiable, source_ref null, detail: "Adoption/preference claim ... asserts what clinicians, payers, or patients would do. No free, authoritative, machine-queryable source answers that — it needs primary research (interviews, survey, published preference study) ... Do NOT substitute a model's own estimate of stakeholder behaviour: a synthetic stakeholder opinion is a fabricated claim." The Verifier produced no such estimate. Note the structural point the verified Regulatory section already established: § 880.5780 exempts the generic type from premarket notification, so the exempt route protects incumbents and entrants symmetrically — it is an open door, not a barrier, and cannot be read as moat evidence in either direction.
claim 21unconfirmedUS
Mechanism and clinical risk — sustained gradient compression is established maintenance therapy for lymphedema, so mechanism risk is low; the material risk is application risk, principally use over undiagnosed peripheral arterial disease, which makes an arterial-insufficiency contraindication and an ankle-brachial-index screening statement mandatory labeling content rather than optional
jurisdiction: US — confidence: unconfirmed — note: no Stage 3 connector answers a clinical-risk or mechanism claim, and none was forced to. The tempting substitutes are all Stage 0: literature, trials, literature-detail, trial-detail and recalls return a **ScanResult that carries no confidence tag and…the full check cannot acquire one** (connectors/result.py, phase2-spec.md Section 3), so running them would have produced reading material, not verification — and summarising them here would have been the Verifier writing its own clinical opinion, which is the failure mode this gate exists to stop. The claim therefore stays exactly where the Generator left it: clinical reasoning, unverified by primary source. What would settle it is a Tier 3 clinical/regulatory labelling review against the recognised consensus documents on compression in the presence of arterial insufficiency — plus, once a product code is actually confirmed at Factor 1, a recalls sweep read as a signal, not as evidence. One cross-reference the Verifier is recording rather than leaving implicit: the PAD/ABI hazard is worse on this candidate than on the incumbent fitter-applied comparators precisely because the intended_use: is self-application without a fitter, which is the same fact that § 880.9 makes a live premarket-notification question in the Regulatory section above.
claim 22unconfirmedUS
Capital intensity and time-to-revenue — on the exempt route the FDA cost is registration, listing and QMS compliance rather than a submission, so first revenue is gated by textile tooling, fitter training and the PDAC/supplier mechanics above, not by FDA review
jurisdiction: US — confidence: unconfirmed — note: and the load-bearing word is "on the exempt route", which this file has not established. Three points, in order of how much they matter: (i) The antecedent is open, so the whole line is conditional. The Regulatory section verified § 880.5780(b) as Class I and…the full check exempt from subpart E — but it also put on record from the same primary text that both paragraphs identify a device "constructed of elastic material", while this candidate's mechanism: is expressly inelastic short-stretch, and that § 880.9 requires a premarket notification anyway where a device "is intended for lay use where the former intended use was by health care professionals only", which is this candidate's self-application-without-a-fitter indication. Those are FDA judgments no connector resolves. If either goes the other way this row is not slightly worse, it is a different business — a submission, a predicate, and a different calendar. Nothing in this pass may be read as settling the exempt route. (ii) connectors regulation 807.20 --title 21 --expect "registration" (the establishment-registration and device-listing obligations the exemption does not excuse) → status unconfirmed, source_ref null, detail: "eCFR returned HTTP 503 for 21 CFR 807.20" — the endpoint outage described on the benefit-category line, not a finding about § 807.20. (iii) No connector prices tooling, fitter training, PDAC turnaround or CMS-855S enrolment, and the claim is deliberately stated without a dollar or month figure. The Verifier added none: any number here would be invented. Correctly scoped as a Tier 3 human estimate. (i) The antecedent is open, so the whole line is conditional. The Regulatory section verified § 880.5780(b) as Class I and exempt from subpart E — but it also put on record from the same primary text that both paragraphs identify a device "constructed of elastic material", while this candidate's mechanism: is expressly inelastic short-stretch, and that § 880.9 requires a premarket notification anyway where a device "is intended for lay use where the former intended use was by health care professionals only", which is this candidate's self-application-without-a-fitter indication. Those are FDA judgments no connector resolves. If either goes the other way this row is not slightly worse, it is a different business — a submission, a predicate, and a different calendar. Nothing in this pass may be read as settling the exempt route. (ii) connectors regulation 807.20 --title 21 --expect "registration" (the establishment-registration and device-listing obligations the exemption does not excuse) → status unconfirmed, source_ref null, detail: "eCFR returned HTTP 503 for 21 CFR 807.20" — the endpoint outage described on the benefit-category line, not a finding about § 807.20. (iii) No connector prices tooling, fitter training, PDAC turnaround or CMS-855S enrolment, and the claim is deliberately stated without a dollar or month figure. The Verifier added none: any number here would be invented. Correctly scoped as a Tier 3 human estimate.
claim 23unconfirmedUS
Assumption, not a fact: patients who cannot self-don a flat-knit garment — the indicated population — can successfully self-apply a multi-strap wrap and read the tension indicators, including patients with hand arthritis, obesity, or limited hip flexion. There is no connector for patient capability and the Generator has no primary research behind this
jurisdiction: US — confidence: unconfirmed — note: , permanently absent primary research — connectors adoption "patients who cannot self-don a flat-knit garment can successfully self-apply a multi-strap wrap and read the tension indicators, including patients with hand arthritis, obesity or limited hip flexion" →…the full check status unverifiable, source_ref null, detail: "Adoption/preference claim ... needs primary research (interviews, survey, published preference study). Stays unconfirmed permanently unless a human attaches real research and edits the claim by hand. Do NOT substitute a model's own estimate of stakeholder behaviour: a synthetic stakeholder opinion is a fabricated claim." The Verifier offered no opinion on patient capability and no proxy was available that honestly stands in for one — coverage/procedures can count what is billed, never whether a patient could don the device. Recording the structural point plainly, because it is the sharpest thing in this file: the indication is defined by an inability (patients who cannot self-don a flat-knit garment) and the product's premise is a different self-application succeeding in that same population. That is the desirability crux, it is testable cheaply with a handful of supervised donning sessions, and today it has zero evidence on either side. The Verifier offered no opinion on patient capability and no proxy was available that honestly stands in for one — coverage/procedures can count what is billed, never whether a patient could don the device. Recording the structural point plainly, because it is the sharpest thing in this file: the indication is defined by an inability (patients who cannot self-don a flat-knit garment) and the product's premise is a different self-application succeeding in that same population. That is the desirability crux, it is testable cheaply with a handful of supervised donning sessions, and today it has zero evidence on either side.
claim 24unconfirmedUS
Assumption, not a fact: certified lymphedema fitters and DMEPOS suppliers would stock and fit a new brand against four established ones, given that the fitter, not the patient, usually selects the product
jurisdiction: US — confidence: unconfirmed — note: , permanently absent primary research — connectors adoption "certified lymphedema fitters and DMEPOS suppliers would stock and fit a new brand against four established ones" → status unverifiable, source_ref null, same detail as the line above (needs…the full check interviews/survey/published preference study; a model's own estimate of stakeholder behaviour is a fabricated claim). None was produced. Per the agent's own guidance the Verifier attempted the checkable proxies hiding inside this claim rather than settling for one blanket shrug — both are blocked by missing caches, not by absence of the underlying fact: coverage A6552 --jurisdiction US → unconfirmed, detail "No local cache at data/medicare_coverage_policies.csv"; procedures A6552 --jurisdiction US → unconfirmed, detail "No local cache at data/medicare_procedure_volumes.csv". So even the comparator-garment volume that would have told us how big the incumbent channel is could not be read. This assumption is load-bearing for TAM component 3, which is unconfirmable by design — the two failures are the same failure counted twice, and a human commissioning fitter/supplier interviews resolves both at once. Per the agent's own guidance the Verifier attempted the checkable proxies hiding inside this claim rather than settling for one blanket shrug — both are blocked by missing caches, not by absence of the underlying fact: coverage A6552 --jurisdiction US → unconfirmed, detail "No local cache at data/medicare_coverage_policies.csv"; procedures A6552 --jurisdiction US → unconfirmed, detail "No local cache at data/medicare_procedure_volumes.csv". So even the comparator-garment volume that would have told us how big the incumbent channel is could not be read. This assumption is load-bearing for TAM component 3, which is unconfirmable by design — the two failures are the same failure counted twice, and a human commissioning fitter/supplier interviews resolves both at once.
claim 25unconfirmedUS
Assumption, not a fact: clinicians would accept a self-applied wrap as maintenance-phase therapy in patients they would otherwise put in a flat-knit garment or refer for repeat bandaging
jurisdiction: US — confidence: unconfirmed — note: , permanently absent primary research — connectors adoption "clinicians would accept a self-applied wrap as maintenance-phase therapy instead of a flat-knit garment or repeat bandaging" → status unverifiable, source_ref null, same detail (primary research…the full check required; do not substitute a model's estimate of stakeholder behaviour). The Verifier produced no clinician opinion. Note the coupling: the intended_use: requires the device be used "under the direction of a licensed clinician", so clinician acceptance is not a marketing nicety here — it is a precondition written into the indication itself, and it sits unevidenced alongside the § 880.9 lay-use question that the same self-application design raises in the Regulatory section.
claim 26unverifiedUS
Adults prescribed maintenance-phase flat-knit compression garments for below-knee lymphedema frequently abandon or fail them because they cannot self-don them, and that failure is documented in clinical practice rather than assumed
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (desirability deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 27unverifiedUS
Patients in the indicated population will re-apply the wrap to its target strap tension at every donning over months of maintenance use, not only under supervision at the initial fitting
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (desirability deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 28unverifiedUS
Patients prescribed a self-applied gradient compression wrap will have arterial status documented — an ankle-brachial index or equivalent — before first use, as the labelling would require
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (desirability deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 29unverifiedUS
Patients using the wrap in maintenance phase will perceive a limb-volume or symptom change they attribute to the device within the first weeks of use
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (desirability deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 30unverifiedUS
Where the patient cannot apply the wrap unaided, a household caregiver is available and willing to apply it to the indicated tension at each donning
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (desirability deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 31unverifiedUS
The DMEPOS fee-schedule allowable for A6583, after the dispensing supplier's or certified fitter's channel margin, leaves the manufacturer a positive gross margin on one below-knee wrap
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (viability deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 32unverifiedUS
PDAC coding-verification of a new manufacturer's below-knee wrap under A6583 is obtainable without a clinical study and without incumbency in the certified-fitter channel
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (viability deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 33unverifiedUS
The number of firms marketing a below-knee adjustable-strap gradient compression wrap in the US is limited to the four named in this candidate's frontmatter — medi, Essity/BSN, Sigvaris and Solaris
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (viability deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 34unverifiedUS
The four named incumbents would not respond to a strap tension-calibration indicator by adding an equivalent indicator to their existing below-knee wrap lines
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (viability deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 35unverifiedUS
Medicare Advantage, Medicaid and commercial payers reimburse below-knee gradient compression wraps on terms comparable to the Medicare Part B lymphedema compression benefit
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (viability deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 36unverifiedUS
The wrap produces a distal-to-proximal decreasing pressure gradient within the 30-50 mmHg band named in the A6583 descriptor when applied by the patient to indicator-aligned strap tension
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (feasibility deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 37unverifiedUS
An inelastic short-stretch strap assembly retains its applied tension across a full labelled wear period without re-tensioning more often than the labelling states
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (feasibility deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 38unverifiedUS
The self-application-without-a-fitter indication can be supported by human-factors validation testing alone, with no premarket notification and no clinical study
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (feasibility deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 39unverifiedUS
The printed strap elongation window aligns at the design strap tension within a stated tolerance across the whole labelled below-knee circumference range and across production strap lots
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (feasibility deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 40unverifiedUS
The wrap, its hook-and-loop closures and its printed indicators retain gradient performance and indicator calibration over the labelled service life, including repeated home laundering
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (feasibility deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 41unverifiedUS
No unexpired US patent assigned to medi GmbH, Essity/BSN, Sigvaris or Solaris claims a strap tension or elongation indicator on a limb compression wrap
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (feasibility deck, 2026-08-25) — never checked; recorded so the Verifier can see it
claim 42verifiedUS
42 CFR 410.36(a)(4) lists "gradient compression wraps with adjustable straps" as part of the Medicare Part B lymphedema compression treatment items benefit category
jurisdiction: US — confidence: verified — source: eCFR versioner title-42, issue 2026-08-13, section=410.36; verified primary text confirms "Gradient compression wraps with adjustable straps" listed at 410.36(a)(4)(ii)
claim 43verifiedUS
42 CFR 414.1650(a) sets the payment basis for lymphedema compression treatment items, including A6583, at 80 percent of the lesser of the actual charge or a payment amount computed under its own Medicaid/TRICARE/internet-retail-price methodology, for items furnished on or after January 1, 2024
jurisdiction: US — confidence: verified — source: eCFR versioner title-42, issue 2026-08-13, section=414.1650; verified primary text confirms "80 percent of the lesser of" the actual charge or payment amount per paragraph (a), applies "For items furnished on or after January 1, 2024"
claim 44unconfirmedUS
The HCPCS A6583 descriptor published by the DME MAC PDAC coding contractor reads "GRADIENT COMPRESSION WRAP WITH ADJUSTABLE STRAPS, BELOW KNEE, EACH" with no 30-50 mmHg qualifier, unlike adjacent stocking codes A6552 and A6554 which do carry an explicit mmHg range
jurisdiction: US — confidence: unconfirmed — source: none; nothing was searched — detail: No local cache at data/hcpcs_level_ii.csv — code A6583 cannot be checked until it exists. See data/README.md for the CMS source. A missing cache file is a data gap, not a negative result.
claim 45unconfirmedUS
Lymphedema compression treatment items billed under A6583 are limited to three daytime garments/wraps per body area every 6 months and two nighttime garments per body area every 24 months, per DME MAC PDAC coding guidance
jurisdiction: US — confidence: unconfirmed — source: none; nothing was searched — detail: Quantity and frequency limits live in a DME MAC Local Coverage Determination (LCD), not in the HCPCS code itself. connectors coverage A6583 requires data/medicare_coverage_policies.csv, which is missing. Even when present,…the full check coverage connector confirms policy existence, not the specific limits—the LCD and Policy Article must be read directly.
claim 46unconfirmedUS
In a prospective RCT of 24 patients with bilateral lower-leg lymphedema, adjustable compression wraps took significantly less time to apply than inelastic multilayer bandaging (8.4 minutes faster, P<.001) during the intensive complete decongestive therapy phase, and 83.3% of participants indicated they would continue using them
jurisdiction: US — confidence: unconfirmed — source: PMID 40015477 (PubMed PMID efetch); claim text verified against abstract. Stage 0 literature scan returns ScanResult with no confidence tag and cannot verify claims; stays unconfirmed per repo rules. Note: study concerns intensive phase, not maintenance phase of…the full check therapy.
claim 47unconfirmedUS
In a multicentre observational study of 86 chronic-leg-oedema patients completing 6 weeks with an inelastic adjustable compression garment system, 95.3% (82 of 86) could don the garment independently or with a little help from relatives
jurisdiction: US — confidence: unconfirmed — source: PMID 38866131 (PubMed PMID efetch); claim text verified against abstract (Sigvaris Coolflex system). Stage 0 literature scan returns ScanResult with no confidence tag and cannot verify claims; stays unconfirmed per repo rules. Note: product tested is Sigvaris…the full check Coolflex, study population includes lymphoedema, venous oedema, and phlebolymphoedema (lower extremity).
claim 48unconfirmedUS
A bench study of six commercially marketed adjustable compression wraps found inelastic wraps could not exceed approximately 30 mmHg maximum pressure at rest, while higher-stretch wraps including Juxtafit, Juxtalite, and Compreflex could be applied above 60 mmHg
jurisdiction: US — confidence: unconfirmed — source: PMID 36795457 (PubMed PMID efetch); claim text verified against abstract (tested Coolflex inelastic at ~30 mmHg max, Juxtafit/Juxtalite/Compreflex above 60 mmHg). Stage 0 literature scan returns ScanResult with no confidence tag and cannot verify claims; stays…the full check unconfirmed per repo rules. Study tested 6 wraps on healthy subjects.
claim 49unconfirmedUS
In a cross-sectional study of 60 breast-cancer-related (upper-limb) lymphedema patients in Turkey, the most common stated reasons for discontinuing or not wearing a compression garment as recommended were functional difficulties in daily life (33%) and discomfort (28.8%)
jurisdiction: US — confidence: unconfirmed — source: PMID 35245100 (PubMed PMID efetch); JURISDICTION MISMATCH FLAGGED: claim text explicitly states study is "in Turkey" from "Turkish Tertiary Center", but jurisdiction field says "US". This is a non-US study about breast-cancer-related (upper-limb) lymphedema, not…the full check lower-extremity. Claim text accurately discloses the location and condition; the jurisdiction field is incorrect and should be corrected to reflect the actual study location.
claim 50unconfirmedUS
A qualitative interview study of 19 compression-hosiery wearers in the Netherlands found donning and doffing difficulty led to dependency on informal or home care and was a stated reason some participants stopped wearing compression hosiery
jurisdiction: US — confidence: unconfirmed — source: PMID 39724281 (PubMed PMID efetch); JURISDICTION MISMATCH FLAGGED: claim text explicitly states study is "in the Netherlands", but jurisdiction field says "US". This is a non-US study about compression hosiery (garments), not compression wraps. Study addresses…the full check donning/doffing barriers relevant to the candidate's self-application design; however the jurisdiction field is incorrect and should be corrected to reflect the actual study location.
claim 51unverifiedUS
The turnaround from establishment registration and device listing to a first billable Medicare claim under A6583 -- spanning PDAC coding-verification review and DMEPOS supplier (CMS-855S) enrollment -- is short enough to plan a launch calendar against.
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-03) — never checked; recorded so the Verifier can see it
claim 52unverifiedUS
The tooling, fitter-training, PDAC coding-verification and DMEPOS-supplier-onboarding capital required to reach a first billable claim under A6583 is financeable within a launch-stage budget.
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-03) — never checked; recorded so the Verifier can see it
claim 53unverifiedUS
The 20 percent Medicare Part B coinsurance a beneficiary would owe on the A6583 allowable does not, by itself, cause a material share of prescribed patients to decline or abandon the device before first dispensing.
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-03) — never checked; recorded so the Verifier can see it
claim 54unverifiedUS
At least one of the four named incumbents (medi GmbH, Essity/BSN, Sigvaris, Solaris) would pay a royalty or transfer price for a licensed strap tension-calibration indicator sufficient to fund its regulatory-scoping and module-validation cost, rather than developing an equivalent indicator in-house.
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-03) — never checked; recorded so the Verifier can see it
claim 55unverifiedUS
A meaningful share of the indicated population or their caregivers would pay out of pocket for the device at a price above the coinsurance a covered A6583 pathway would leave them owing, sufficient to sustain a cash-pay channel independent of Medicare billing.
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-03) — never checked; recorded so the Verifier can see it
claim 56unverifiedUS
A regulatory pathway to premarket clearance (510(k) or De Novo) exists and is fundable and timeable for this device even though no predicate has been identified for an adjustable-strap inelastic compression wrap under 21 CFR 880.5780 or any other regulation.
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-03) — never checked; recorded so the Verifier can see it