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.
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 (US Food and Drug Administration) judgments that no connector answers; they are flagged here, not resolved.
21 CFR 880.5780(a) covers a medical support stocking intended to prevent the pooling of blood in the legs, is Class II (FDA device 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 (quality management system) exemption as well as Class I.
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) (premarket notification) exemption — that comes from the regulation text above, and only if the device is in fact within this generic type.
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.
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.
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 (an FDA 510(k) clearance number) 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.
HCPCS (Healthcare Common Procedure Coding System)A6583 (a HCPCS code for a supply) exists and is descriptor-defined as "Gradient compression wrap with adjustable straps, below knee, 30-50 mmHg (millimetres of mercury), each"
jurisdiction: US — confidence: refuted — note: compound claim, and the halves split. The code exists (verified), but its current CMS (Centers for Medicare & Medicaid Services) descriptor carries no 30-50 mmHg range, so the descriptor definition this claim asserts is false against primary text — and with it the "sized to the descriptor's pressure band"…the full check premise that claim 36refuted and the candidate's positioning lean on. One thing the cache cannot show: the file gives A6583 add_date 20240101 but action_effective_date 20250401 (A6585-A6588 the same; A6584 and A6589 stay 20240101), which is consistent with a descriptor revision on 2025-04-01. Only the current text is carried, so whether the 2024 original read "30-50 mmHg" is not established here — and would not rescue a claim written in the present tense. Reimbursement is not thereby closed: the code exists and prices (claim 16unconfirmed), and the benefit reaches "gradient compression wraps with adjustable straps" (claim 42verified) — source: Earlier record, kept as history (tag then unconfirmed): 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 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." Re-run 2026-09-29: hcpcs A6583 --expect "below knee, 30-50 mmHg" --jurisdiction US → refuted, local cache of CMS HCPCS Level II file, code=A6583 (October 2026 alpha-numeric HCPCS file, retrieved 2026-09-29): "HCPCS A6583 exists but its official description ('Gradient compression wrap with adjustable straps, below knee, each') does not match the claimed description ('below knee, 30-50 mmHg')". The existence half, re-run as originally recorded: hcpcs A6583 --expect "gradient compression wrap with adjustable straps" --jurisdiction US → verified, local cache of CMS HCPCS Level II file, code=A6583: "HCPCS A6583: Gradient compression wrap with adjustable straps, below knee, each" Earlier note (2026-08-25), kept as history — superseded 2026-09-29 by the lookup recorded above, which read the file this note was waiting for: 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.
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: verified — note: both codes exist with descriptors matching the claim's wording (letter case aside), each with add_date 20240101 in the cached row, so "the same 2024 code set" holds. That they describe the garment alternative is a reading of the descriptor word "stocking", which the…the full check text supports; which product a fitter actually substitutes is not something a code file says — source: Earlier record, kept as history (tag then unconfirmed): 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 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. Re-run 2026-09-29: hcpcs A6552 --jurisdiction US → verified, local cache of CMS HCPCS Level II file, code=A6552: "HCPCS A6552: Gradient compression stocking, below knee, 30-40 mmhg, each"; hcpcs A6554 --jurisdiction US → verified, local cache of CMS HCPCS Level II file, code=A6554: "HCPCS A6554: Gradient compression stocking, below knee, 40 mmhg or greater, each" (October 2026 alpha-numeric HCPCS file, retrieved 2026-09-29)
Lymphedema compression treatment items became a distinct Medicare Part B (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. — note: re-check 2026-09-29 (Verifier, cold), tag unchanged (unconfirmed) — three of the claim's four elements now resolve against primary text and one does not, and a half-checkable claim is not verified. Resolved: (a) Part B benefit — regulation 410.36 --title 42 --jurisdiction US → verified, eCFR versioner title-42, issue 2026-08-13, section=410.36: "(a) Medicare Part B pays for the following ... (4) Lymphedema compression treatment items, including ... (ii) Gradient compression wraps with adjustable straps"; (b) effective date — regulation 410.2 --title 42 --jurisdiction US --expect "Furnished on or after January 1, 2024" → verified (the connector's excerpt is truncated before the phrase, so its surrounding definition was not read), and independently 42 CFR 414.1650(a) "For items furnished on or after January 1, 2024"; (c) distinct category and CAA 2023 as the enacting law — policy 2023-24455 --jurisdiction US --expect "section 4133" → verified, 88 FR 77676 (CY (calendar year) 2024 HH PPS final rule, published 2023-11-13): "section 4133 of the CAA, 2023 adds section 1861(s)(2)(JJ) to the Act, adding the Medicare Part B benefit for lymphedema compression treatment items effective January 1, 202[4]", and the same rule refers to "this benefit category". Not resolved: the name "Lymphedema Treatment Act" — policy 2023-24455 --jurisdiction US --expect "Lymphedema Treatment Act" → unconfirmed: "does not contain the phrase 'Lymphedema Treatment Act'", and no CFR section read names it. That is a popular-title label, not a substantive gap: restated as "...following section 4133 of the Consolidated Appropriations Act, 2023", this line would verify on the calls above. Rewording is for the Generator/Scorer, not this pass. 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.
Medicare payment for these items is 80% of the lesser of the supplier's actual charge or the DMEPOS (durable medical equipment, prosthetics, orthotics and supplies) fee schedule amount, with the Part B deductible and coinsurance applying
jurisdiction: US — confidence: verified — 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 until…the full check 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 (physician fee schedule) or OPPS row for a supply code would be the wrong number. — note: re-check 2026-09-29 (Verifier, cold), tag raised unconfirmed → verified. Each element checked against primary text: (i) the 80%-of-lesser rule — regulation 414.1650 --title 42 --jurisdiction US → verified, eCFR versioner title-42, issue 2026-08-13, section=414.1650: "For items furnished on or after January 1, 2024, Medicare pays for lymphedema compression treatment items on the basis of 80 percent of the lesser of— (1) The actual charge for the item; or (2) The payment amount for the item, as determined in accordance with paragraph (b)" (the 20% remainder is the coinsurance); (ii) the deductible — regulation 410.160 --title 42 --jurisdiction US --expect "are subject to, and count toward meeting the annual deductible" → verified, eCFR title-42 issue 2026-08-13, section=410.160; its exceptions list (b)(1)–(13) was read in full and names no lymphedema item (--expect "lymphedema" → unconfirmed, phrase absent); (iii) the operand — payment A6583 --jurisdiction US → verified, local cache of CMS DMEPOS fee schedule, code=A6583, modifier=none, schedule=DMEPOS, release=July 2026: "category LC — lymphedema compression treatment items: non-rural $160.13 across 49 contiguous states/DC" — so the amount is published on CMS's DMEPOS fee schedule, as the claim says. Qualification a reader must not lose: the amount on that schedule is not set by the general DMEPOS fee-schedule method; 42 CFR 414.1650(b) derives it from 120% of average Medicaid state-plan amounts, else the average of internet retail and TRICARE amounts, else internet retail, CPI-U-updated from (c). And $160.13 is Medicare's allowed amount for a single A6583 wrap ("each"), before the 20% coinsurance, not Medicare's payment. (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.
Coverage is available for beneficiaries with any diagnosis of lymphedema, rather than being restricted to a subtype
jurisdiction: US — confidence: unconfirmed — note: tag unchanged; the right instrument now half-answers it and the recorded one does not. (i) The regulatory definition of the benefit carries no subtype restriction: 42 CFR 410.2 defines a lymphedema compression treatment item as one "(1) Furnished on or after…the full check January 1, 2024, to an individual with a diagnosis of lymphedema for treatment of such condition; (2) Primarily and customarily used to serve a medical purpose and for the treatment of lymphedema; and (3) Prescribed by a physician (or a physician assistant, nurse practitioner, or a clinical nurse specialist ...) to the extent authorized under State law." (ii) But "coverage is available" also turns on contractor reasonable-and-necessary policy, which can narrow a benefit the regulation states broadly, and that is still unread. (iii) The code-keyed coverage lookup this line recorded now returns refuted. Not read as a finding about CMS policy: the cache (data/medicare_coverage_policies.csv, provenance: MCD current_article.zip, retrieved 2026-09-29) holds Billing & Coding / policy Articles only — no LCD (local coverage determination) and no NCD (national coverage determination) rows — and the DME MAC (durable medical equipment Medicare administrative contractor) policy articles it does carry have a blank codes column (e.g. A54563 "Surgical Dressings - Policy Article", A52467 "Positive Airway Pressure (PAP) Devices ... - Policy Article"); no article titled for lymphedema compression treatment items appears at all (the only lymphedema-titled row is A55710 "Lymphedema Decongestive Treatment", codes 29581;29584;97140;97535). So a code-keyed miss for a DME MAC-billed A-code describes this cache's linkage, not CMS's — the idea-001 claim 9verified trap the reimbursement reference names; and coverage verifies policy existence, never breadth by diagnosis, so it was the wrong instrument for this claim even when it answers. Settles on the DME MAC lymphedema compression policy article / LCD read directly (L- or A-number from the MCD, not guessed) — source: Earlier record, kept as history (tag then unconfirmed): 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 exists. See data/README.md for the exact CMS source and expected columns. Do not substitute a web search for this file." Re-run 2026-09-29: regulation 410.2 --title 42 --expect "an individual with a diagnosis of lymphedema" --jurisdiction US → verified, eCFR versioner title-42, issue 2026-08-13, section=410.2 (definition quoted in the note); coverage A6583 --expect-stance covered --jurisdiction US → refuted, local cache of CMS Medicare Coverage Database (no policy names this code), code=A6583: "No NCD or LCD in the cached coverage file names A6583. That means Medicare has published no explicit coverage determination for it — claims are left to case-by-case contractor adjudication. This is a real reimbursement risk signal, but it is NOT the same as a denial: many covered services have no dedicated policy." Earlier note (2026-08-25), kept as history — its prediction held: with the cache present, coverage still answers existence, not breadth: 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.
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 (Pricing, Data Analysis and Coding contractor)/supplier-enrolment mechanics below as part of the billing-readiness work that has to be done by a human before first revenue.
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: tag unchanged. Still no connector reaches the PDAC coding-verification process or its product list. The coverage A6583 route this line said was blocked by a missing cache now answers refuted — but Not read as a finding about CMS policy: the cache…the full check (data/medicare_coverage_policies.csv, provenance: MCD current_article.zip, retrieved 2026-09-29) holds Billing & Coding / policy Articles only — no LCD and no NCD rows — and the DME MAC policy articles it does carry have a blank codes column (e.g. A54563 "Surgical Dressings - Policy Article", A52467 "Positive Airway Pressure (PAP) Devices ... - Policy Article"); no article titled for lymphedema compression treatment items appears at all (the only lymphedema-titled row is A55710 "Lymphedema Decongestive Treatment", codes 29581;29584;97140;97535). So a code-keyed miss for a DME MAC-billed A-code describes this cache's linkage, not CMS's — the idea-001 claim 9verified trap the reimbursement reference names. It therefore says nothing about quantity/replacement limits either way, and no number is asserted here — source: Earlier record, kept as history (tag then unconfirmed): 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 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. Re-run 2026-09-29: coverage A6583 --jurisdiction US → refuted, local cache of CMS Medicare Coverage Database (no policy names this code), code=A6583: "No NCD or LCD in the cached coverage file names A6583. That means Medicare has published no explicit coverage determination for it — claims are left to case-by-case contractor adjudication. This is a real reimbursement risk signal, but it is NOT the same as a denial: many covered services have no dedicated policy."
TAM (total addressable market) component 1 — annual Medicare claim volume for A6583
jurisdiction: US — confidence: verified — 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 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." 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 (fee-for-service) count is a floor on US volume and never a market size (it excludes Medicare Advantage (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. — note: re-check 2026-09-29 (Verifier, cold), tag raised unconfirmed → verified. The earlier record above is a missing-file result, now superseded. Source today: procedures A6583 --jurisdiction US → verified, local cache of CMS Medicare DMEPOS utilization file (referring provider geography and service), code=A6583, geography=National; data/provenance.json names the release as mup_dme_ry26_p05_v10_dy24_geor.csv, i.e. data year 2024. Figure read: supplier-billed purchase, 80,433 services across 24,631 beneficiaries. Services are billed units (A6583 is "each", one wrap), so 80,433 counts wraps billed, not patients; the patient count is 24,631. The file's claim count (Tot_Suplr_Clms) is not reported by the connector and was not read. Both caveats set out above still apply: a Medicare FFS count is a floor on US volume, never a market size (it excludes Medicare Advantage, commercial, Medicaid, VA and cash-pay), and 2024 is the code's first payable year, so this is early-uptake volume. Components 2 and 3 are unchanged by this pass.
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: tag unchanged, and the replay's verified does not carry over to this claim. What resolved is the upper-bound operand only: the July 2026 DMEPOS fee schedule prices A6583 (no modifier, category LC) at $160.13 non-rural in all 49 contiguous states/DC —…the full check Medicare's allowed amount per wrap ("each"), out of which the beneficiary's coinsurance comes; it is not a payment and not a manufacturer price. The claim asserts a net selling price, which sits below that allowable by an unmeasured supplier/fitter margin; no connector reads a transfer price or a channel margin, and market stays unverifiable. No price is asserted — source: Earlier record, kept as history (tag then unconfirmed): 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 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. Re-run 2026-09-29: payment A6583 → verified (the invocation as originally recorded, without the flag; same result); payment A6583 --jurisdiction US → verified, local cache of CMS DMEPOS fee schedule, code=A6583, modifier=none, schedule=DMEPOS, release=July 2026: "A6583 — no modifier, category LC — lymphedema compression treatment items: non-rural $160.13 across 49 contiguous states/DC ... A fee schedule amount is Medicare's allowed amount, not the payment"
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.
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.
FTO (freedom to operate) — 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 (intellectual property) 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.
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.
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.
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. — note: re-check 2026-09-29 (Verifier, cold), tag unchanged (unconfirmed). The eCFR outage call in (ii) was re-run: regulation 807.20 --title 21 --jurisdiction US --expect "registration" → verified, eCFR versioner title-21, issue 2026-09-25, section=807.20: "(a) An owner or operator of an establishment ... engaged in the manufacture ... of a device intended for human use shall register and submit listing information". So the registration-and-listing element now resolves. Also read the same day: regulation 880.5780 --title 21 --jurisdiction US --expect "820" → verified, eCFR title-21 issue 2026-09-25: (b)(2) "is also exempt from the current good manufacturing practice requirements of the quality management system regulation in part 820 ..., except for requirements concerning records and complaint files under § 820.35". The line's "QMS compliance" is therefore narrower on the paragraph (b) route than the wording suggests: records and complaint files, not full part 820. Unchanged and still unresolved: (i) whether this inelastic, lay-applied device falls inside § 880.5780(b) or is caught by § 880.9 at all, which is FDA's judgment; and (iii) the cost and calendar of tooling, fitter training, PDAC and CMS-855S, which no connector prices. Neither is a refutation. (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.
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.
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: tag unchanged — permanently, absent primary research. The comparator-garment proxy that was blocked now reads, and it does not bear on the claim's wording: A6552 (below-knee 30-40 mmHg stocking) shows **7,836 supplier-billed purchase services across 1,907…the full check beneficiaries** nationally in Medicare FFS (DMEPOS utilisation file, data year 2024 per provenance). A service is one stocking ("each"), so the patient-level figure is 1,907 beneficiaries. That sizes part of the incumbent channel as a floor (FFS only — excludes Medicare Advantage, commercial, Medicaid, VA, cash-pay); it says nothing about whether fitters or suppliers would stock a new brand. The coverage A6552 proxy now returns refuted, and Not read as a finding about CMS policy: the cache (data/medicare_coverage_policies.csv, provenance: MCD current_article.zip, retrieved 2026-09-29) holds Billing & Coding / policy Articles only — no LCD and no NCD rows — and the DME MAC policy articles it does carry have a blank codes column (e.g. A54563 "Surgical Dressings - Policy Article", A52467 "Positive Airway Pressure (PAP) Devices ... - Policy Article"); no article titled for lymphedema compression treatment items appears at all (the only lymphedema-titled row is A55710 "Lymphedema Decongestive Treatment", codes 29581;29584;97140;97535). So a code-keyed miss for a DME MAC-billed A-code describes this cache's linkage, not CMS's — the idea-001 claim 9verified trap the reimbursement reference names. No stakeholder opinion was produced — source: Earlier record, kept as history (tag then unconfirmed): 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 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. Re-run 2026-09-29: adoption "certified lymphedema fitters and DMEPOS suppliers would stock and fit a new brand against four established ones" → unverifiable (as recorded); procedures A6552 --jurisdiction US → verified, local cache of CMS Medicare DMEPOS utilization file (referring provider geography and service), code=A6552, geography=National: "A6552 (national, supplier-billed (DMEPOS): purchase 7,836 services / 1,907 beneficiaries)"; coverage A6552 --jurisdiction US → refuted, local cache of CMS Medicare Coverage Database (no policy names this code), code=A6552: "No NCD or LCD in the cached coverage file names A6552. That means Medicare has published no explicit coverage determination for it — claims are left to case-by-case contractor adjudication. This is a real reimbursement risk signal, but it is NOT the same as a denial: many covered services have no dedicated policy." Earlier note (2026-08-25), kept as history — both proxies it records as blocked now answer; see today's record on the line above: 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. Re-run 2026-09-29 (supersedes the two blocked results in this note): procedures A6552 --jurisdiction US → verified, 7,836 purchase services / 1,907 beneficiaries, national, supplier-billed; coverage A6552 --jurisdiction US → refuted, no policy in the articles-only cache names A6552 — a linkage artefact, not a CMS finding (see the claim line above).
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.
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: unconfirmed — note: permanently absent primary research. Claims 46-50 carry published abstracts on donning difficulty, but they are unverified literature leads (two non-US, one upper-limb, one hosiery) and a Stage 0 read cannot tag this line. No stakeholder opinion was produced to fill…the full check it — source: deck-surfaced assumption (desirability deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: adoption "Adults prescribed maintenance-phase flat-knit compression garments for below-knee lymphedema frequently abandon or fail them because they cannot self-don them" → unverifiable: "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"
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: unconfirmed — note: permanently absent primary research — a supervised-then-unsupervised donning study is what settles it. No stakeholder opinion was produced to fill it — source: deck-surfaced assumption (desirability deck, 2026-08-25) (never checked before this pass); Verifier…the full check 2026-09-29: adoption "Patients in the indicated population will re-apply the wrap to its target strap tension at every donning over months of maintenance use" → unverifiable: "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"
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: unconfirmed — note: permanently absent primary research. What labelling would require is a separate, unchecked question (claim 21unconfirmed); this line is about what prescribers will actually do. No stakeholder opinion was produced to fill it — source: deck-surfaced assumption (desirability…the full check deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: adoption "Patients prescribed a self-applied gradient compression wrap will have arterial status documented before first use" → unverifiable: "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"
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: unconfirmed — note: permanently absent primary research. No stakeholder opinion was produced to fill it — source: deck-surfaced assumption (desirability deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: `adoption "Patients using the wrap in maintenance phase will…the full check perceive a limb-volume or symptom change they attribute to the device within the first weeks"` → unverifiable: "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"
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: unconfirmed — note: permanently absent primary research. No stakeholder opinion was produced to fill it — source: deck-surfaced assumption (desirability deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: `adoption "A household caregiver is available and willing to…the full check apply the wrap to the indicated tension at each donning"` → unverifiable: "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"
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: unconfirmed — note: decomposed; one operand now reads, the claim does not. The allowable is $160.13 per wrap (DMEPOS fee schedule, July 2026, non-rural, all 49 contiguous states/DC) — Medicare's allowed amount, not its payment. The claim needs two further operands no connector reads —…the full check the supplier/fitter channel margin and the manufacturer's unit cost — and a gross margin computed from a guessed cost would be invented — source: deck-surfaced assumption (viability deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: payment A6583 --jurisdiction US → verified, local cache of CMS DMEPOS fee schedule, code=A6583, modifier=none, schedule=DMEPOS, release=July 2026: "non-rural $160.13 across 49 contiguous states/DC"; market "manufacturer gross margin on one below-knee wrap after supplier or fitter channel margin under the A6583 allowable" → unverifiable: "has no free, authoritative, machine-queryable source"
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: unconfirmed — note: no connector reaches the PDAC coding-verification process, its review criteria or its product list, and none was substituted. The code itself exists (claim 44verified); whether a new manufacturer can get onto it without a study is a contractor-process question for a human to…the full check put to the PDAC — source: deck-surfaced assumption (viability deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: no typed connector for PDAC coding verification; hcpcs A6583 --jurisdiction US → verified, local cache of CMS HCPCS Level II file, code=A6583 (context only — code existence, not PDAC listing)
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: unconfirmed — note: no connector reaches FDA Establishment Registration & Device Listing, which is where firms marketing an exempt FQL/DWL device appear; a 510(k) query is structurally uninformative for an exempt generic type (claim 7unconfirmed). The count of firms is unmeasured, not four —…the full check source: deck-surfaced assumption (viability deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: no typed connector for device listing; nothing run as a stand-in
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: unconfirmed — note: permanently absent primary research. Related record (lead only, no tag): a patent sweep for claim 41unconfirmed found Essity family 81386942, "COMPRESSION GARMENT WITH INDICATOR" (CA3253400A1), so at least one named incumbent has filed in indicator art. No stakeholder opinion…the full check was produced to fill it — source: deck-surfaced assumption (viability deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: adoption "The four named incumbents would not respond to a strap tension-calibration indicator by adding an equivalent indicator" → unverifiable: "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"
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: unconfirmed — note: no connector reads Medicare Advantage, Medicaid or commercial payer policy; the typed reimbursement connectors are Medicare FFS only. No stakeholder opinion was produced to fill it — source: deck-surfaced assumption (viability deck, 2026-08-25) (never checked before…the full check this pass); Verifier 2026-09-29: adoption "Medicare Advantage, Medicaid and commercial payers reimburse below-knee gradient compression wraps on terms comparable to the Medicare Part B lymphedema compression benefit" → unverifiable: "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"
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: refuted — note: compound claim; the half the connector can read is false. The claim locates its target band as "the 30-50 mmHg band named in the A6583 descriptor", and the current CMS descriptor names no pressure band ("Gradient compression wrap with adjustable straps, below knee,…the full check each" — see claim 8refuted). The performance half — whether a patient-applied wrap produces a decreasing distal-to-proximal gradient at any band — is untested bench work no connector answers, and is not what is refuted here. Restated against a design-chosen band with the descriptor reference dropped, the line would return to unconfirmed — source: deck-surfaced assumption (feasibility deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: hcpcs A6583 --expect "below knee, 30-50 mmHg" --jurisdiction US → refuted, local cache of CMS HCPCS Level II file, code=A6583: "HCPCS A6583 exists but its official description ('Gradient compression wrap with adjustable straps, below knee, each') does not match the claimed description ('below knee, 30-50 mmHg')"
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: unconfirmed — note: bench/engineering performance claim; no connector answers device test performance, and no test data exist yet — source: deck-surfaced assumption (feasibility deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: no typed connector for device bench…the full check performance; nothing run
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: unconfirmed — note: the regulation text this turns on was re-read and cuts against it without settling it. 21 CFR 880.9(a) requires a premarket notification for an otherwise-exempt device where "the device is intended for lay use where the former intended use was by health care…the full check professionals only", and 880.9(b) where it "operates using a different fundamental scientific technology"; 880.5780 still identifies the generic type as "constructed of elastic material" against an inelastic mechanism. Whether either trigger fires, and whether human-factors testing alone would then suffice, are FDA judgments no connector reaches (a 513(g) or regulatory counsel). unconfirmed, not refuted: the text states conditions, not FDA's reading of this device — source: deck-surfaced assumption (feasibility deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: regulation 880.9 --title 21 --expect "intended for lay use" --jurisdiction US → verified, eCFR versioner title-21, issue 2026-09-25, section=880.9 (phrase present, quoted in the note); regulation 880.5780 --title 21 --expect "constructed of elastic material" --jurisdiction US → verified, eCFR versioner title-21, issue 2026-09-25, section=880.5780
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: unconfirmed — note: bench/production-tolerance claim; no connector answers it and no lot data exist — source: deck-surfaced assumption (feasibility deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: no typed connector for device bench performance; nothing run
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: unconfirmed — note: durability/laundering performance claim; no connector answers it and no test data exist — source: deck-surfaced assumption (feasibility deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: no typed connector for device bench performance; nothing run
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: unconfirmed — note: a negative FTO claim, and a sweep cannot verify an absence — patent-scan returns leads, never a tag. What was swept (all EPO (European Patent Office) OPS, any publication date): cpc=A61F13/08 × applicant medi GmbH (25 families), Sigvaris (22), BSN medical (8), Essity (6), Solaris (0);…the full check applicant × text "indicator" for each (Essity 9 publications, Sigvaris 3, the rest 0); cpc=A61F13/08 × text "indicator" (9 families). Closest lead: Essity Hygiene & Health AB, "COMPRESSION GARMENT WITH INDICATOR", family 81386942 — only a Canadian application (CA3253400A1, filed 2022-03-28) surfaced; no US member was found in these sweeps, which is not the same as none existing. Sigvaris has 2025 US applications on compression wraps (US20250281332A1/-333A1/-335A1), not indicator-titled and not grants. Unrelated-assignee indicator art also sits in the class (3M WO2014014672A1 "Determining elongation of elastic bandage"; Smith & Nephew CA2215142A1 "Fabric article with extension indicator"). No connector reads patent claims, so whether any in-force US patent claims the indicator is unexamined; an FTO opinion is Tier 3 legal work — source: deck-surfaced assumption (feasibility deck, 2026-08-25) (never checked before this pass); Verifier 2026-09-29: patent-scan --cpc A61F13/08 --text "indicator" --limit 100 --jurisdiction US → found (a ScanResult, no tag), 9 families; patent CA3253400A1 --jurisdiction US → verified, EPO OPS published-data/publication docdb=CA.3253400.A1: "COMPRESSION GARMENT WITH INDICATOR: filed 2022-03-28, naive 20yr term expiration 2042-03-28" (dates only; a Canadian application, not a US patent)
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)
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"
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: verified — note: the descriptor text, the absence of an mmHg qualifier on A6583, and the explicit mmHg ranges on A6552 and A6554 are all confirmed against the CMS HCPCS Level II file. One attribution qualifier: the source read is CMS's national code file, not the PDAC's own publication;…the full check PDAC publishes the same national descriptor, and the claim's substance is the descriptor. This line and claim 8refuted cannot both stand — claim 8refuted is refuted on the same lookup — source: Earlier record, kept as history (tag then unconfirmed): 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. Re-run 2026-09-29: hcpcs A6583 --expect "Gradient compression wrap with adjustable straps, below knee, each" --jurisdiction US → verified, local cache of CMS HCPCS Level II file, code=A6583: "HCPCS A6583: Gradient compression wrap with adjustable straps, below knee, each"; hcpcs A6552 --jurisdiction US → verified, code=A6552: "Gradient compression stocking, below knee, 30-40 mmhg, each"; hcpcs A6554 --jurisdiction US → verified, code=A6554: "Gradient compression stocking, below knee, 40 mmhg or greater, each" (October 2026 alpha-numeric HCPCS file, retrieved 2026-09-29)
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 — note: tag unchanged. The coverage A6583 lookup now answers refuted, but Not read as a finding about CMS policy: the cache (data/medicare_coverage_policies.csv, provenance: MCD current_article.zip, retrieved 2026-09-29) holds **Billing & Coding / policy Articles…the full check only — no LCD and no NCD rows** — and the DME MAC policy articles it does carry have a blank codes column (e.g. A54563 "Surgical Dressings - Policy Article", A52467 "Positive Airway Pressure (PAP) Devices ... - Policy Article"); no article titled for lymphedema compression treatment items appears at all (the only lymphedema-titled row is A55710 "Lymphedema Decongestive Treatment", codes 29581;29584;97140;97535). So a code-keyed miss for a DME MAC-billed A-code describes this cache's linkage, not CMS's — the idea-001 claim 9verified trap the reimbursement reference names. The limits are also not in regulation text: 42 CFR 414.1650 and 414.1660 were read in full and carry payment basis and code-continuity rules, no quantity or frequency limit. The DME MAC policy article must be read directly — source: Earlier record, kept as history (tag then unconfirmed): 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, coverage connector confirms policy existence, not the specific limits—the LCD and Policy Article must be read directly. Re-run 2026-09-29: coverage A6583 --jurisdiction US → refuted, local cache of CMS Medicare Coverage Database (no policy names this code), code=A6583: "No NCD or LCD in the cached coverage file names A6583. That means Medicare has published no explicit coverage determination for it — claims are left to case-by-case contractor adjudication. This is a real reimbursement risk signal, but it is NOT the same as a denial: many covered services have no dedicated policy."; regulation 414.1650 --title 42 --expect "6 months" --jurisdiction US → unconfirmed, eCFR versioner title-42, issue 2026-08-13, section=414.1650 (section exists, phrase absent)
In a prospective RCT (randomised controlled trial) 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 (PubMed identifier) 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.
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).
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.
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.
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.
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: unconfirmed — note: no connector reads PDAC review turnaround or CMS-855S enrolment timing; no month figure was added — source: business-case assumption (2026-09-03) (never checked before this pass); Verifier 2026-09-29: no typed connector for contractor processing times; nothing run
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: unconfirmed — note: no connector prices tooling, fitter training, PDAC review or supplier onboarding, and financeability is a judgement about capital markets; no figure was added — source: business-case assumption (2026-09-03) (never checked before this pass); Verifier 2026-09-29: no…the full check typed connector; nothing run
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: unconfirmed — note: permanently absent primary research. The operand is now known — 20% of the $160.13 allowable is about $32 per wrap (payment A6583, claim 16unconfirmed) — but whether that sum drives abandonment is patient behaviour. No stakeholder opinion was produced to fill it — source:…the full check business-case assumption (2026-09-03) (never checked before this pass); Verifier 2026-09-29: adoption "The 20 percent Medicare Part B coinsurance on the A6583 allowable does not by itself cause a material share of prescribed patients to decline or abandon the device" → unverifiable: "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"
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: unconfirmed — note: permanently absent primary research — incumbent licensing appetite is a stakeholder decision. No stakeholder opinion was produced to fill it — source: business-case assumption (2026-09-03) (never checked before this pass); Verifier 2026-09-29: `adoption "At least one…the full check of the four named incumbents would pay a royalty or transfer price for a licensed strap tension-calibration indicator"` → unverifiable: "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 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: unconfirmed — note: permanently absent primary research. No stakeholder opinion was produced to fill it — source: business-case assumption (2026-09-03) (never checked before this pass); Verifier 2026-09-29: `adoption "A meaningful share of the indicated population or their caregivers…the full check would pay out of pocket above the A6583 coinsurance to sustain a cash-pay channel"` → unverifiable: "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 regulatory pathway to premarket clearance (510(k) or De Novo (De Novo classification request)) 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: unconfirmed — note: the lookup does not answer the claim's wording. The De Novo listing has no grant matching "compression wrap" or even "compression" — that refutes a prior De Novo for this kind of device (so no De Novo-derived predicate exists), not the availability of a De Novo…the full checkrequest, which is a statutory route open to a device without a predicate. Whether that route is fundable and timeable is not something any connector reads. The listing is keyed on trade names, so a description-keyed miss is weaker than it looks — source: business-case assumption (2026-09-03) (never checked before this pass); Verifier 2026-09-29: denovo "compression wrap" --jurisdiction US → refuted, local cache of FDA De Novo listing (no match), device_name='compression wrap': "No granted De Novo request matching 'compression wrap' in the cached FDA De Novo listing (494 records) ... this refutes the De Novo route specifically, not market authorization generally"; denovo "compression" --jurisdiction US → refuted, same listing, no match
In the CMS Medicare DMEPOS utilization file for data year 2024 (national, supplier-billed purchase), the below-knee stocking codes A6552, A6553 and A6554 were billed at 7,836, 7,528 and 290 services respectively, against 80,433 services for the below-knee wrap code A6583
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-29) — never checked; recorded so the Verifier can see it — evidence class 1 (registry fact)
The July 2026 CMS DMEPOS fee schedule (category LC, no modifier) lists non-rural allowables of $57.97 for A6552 and $226.38 for A6553 across the 49 contiguous states/DC, against $160.13 for A6583
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-29) — never checked; recorded so the Verifier can see it — evidence class 1 (registry fact)
HCPCS A6583 carries PFS procedure status X (statutory exclusion) in the 2026 CMS PFS RVU (relative value unit) file, so no physician-fee-schedule practice-expense payment carries the cost of the wrap; it is paid only as a DMEPOS item
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-29) — never checked; recorded so the Verifier can see it — evidence class 1 (registry fact)
In Medicare fee-for-service data year 2024, fewer than 100 DMEPOS suppliers accounted for more than half of national A6583 services
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-29) — never checked; recorded so the Verifier can see it — evidence class 1 (registry fact)
The PDAC DMECS product classification list for HCPCS A6583 names at least one manufacturer other than medi, Essity/BSN, Sigvaris and Solaris, so a new entrant has had a below-knee adjustable-strap wrap coded to A6583 since the benefit began on 2024-01-01
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-29) — never checked; recorded so the Verifier can see it — evidence class 1 (registry fact)
Incumbent manufacturers sell below-knee adjustable-strap wraps billed under A6583 to DMEPOS suppliers at wholesale prices below the $160.13 July 2026 non-rural allowable, so the dispensing supplier retains a positive margin on each wrap
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-29) — never checked; recorded so the Verifier can see it
A below-knee inelastic short-stretch strap wrap carrying printed strap elongation windows can be produced at a landed unit cost below the wholesale price incumbents charge DMEPOS suppliers for a wrap billed under A6583
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-29) — never checked; recorded so the Verifier can see it
Medicare fee-for-service accounts for less than half of all US below-knee adjustable-strap compression wraps dispensed each year, the remainder being Medicare Advantage, Medicaid, commercial, VA and cash-pay
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-29) — never checked; recorded so the Verifier can see it
A device manufacturer enrolled and accredited as a Medicare DMEPOS supplier (CMS-855S) may bill A6583 for its own self-applied wrap shipped to the beneficiary's home, without an in-person fitting by a certified fitter being a condition of payment
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-29) — never checked; recorded so the Verifier can see it
No earlier patent or publication anticipates a printed strap elongation window that aligns at a fixed design strap tension on a below-knee compression wrap, so a US patent application on that indicator is capable of grant
jurisdiction: US — confidence: unverified — source: business-case assumption (2026-09-29) — never checked; recorded so the Verifier can see it — evidence class 2 (published finding)
Adults with below-knee lymphedema in the maintenance phase who cannot self-don a flat-knit compression garment unaided also cannot don it reliably with a commercially available garment donning aid, so a donning aid does not already meet the need an adjustable-strap wrap addresses
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (desirability deck, 2026-09-29) — never checked; recorded so the Verifier can see it — evidence class 3 (stakeholder future)
Patients in the indicated population who self-apply a below-knee adjustable-strap wrap reach the design strap tension more consistently across repeated donnings when each strap carries a printed tension indicator than when it does not
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (desirability deck, 2026-09-29) — never checked; recorded so the Verifier can see it — evidence class 3 (stakeholder future)
In the CMS Medicare DMEPOS utilization file for data year 2025 (national, supplier-billed purchase), A6583 services exceed the 80,433 recorded for data year 2024
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (viability deck, 2026-09-29) — never checked; recorded so the Verifier can see it — evidence class 1 (registry fact)
When applied by the patient to indicator-aligned strap tension, the wrap produces a distal-to-proximal decreasing sub-bandage pressure gradient within a resting pressure band stated in its own labelling, the band being a design choice because the A6583 descriptor names none
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (feasibility deck, 2026-09-29) — never checked; recorded so the Verifier can see it
A single design strap tension, marked by one indicator setting per strap, yields a sub-bandage pressure within the labelled band across the whole labelled below-knee circumference range
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (feasibility deck, 2026-09-29) — never checked; recorded so the Verifier can see it
Labelling the strap tension indicator as a strap self-application aid, with no sub-bandage pressure-measurement claim in mmHg, keeps the device within 21 CFR 880.5780(b) rather than bringing it under a pressure-measurement regulation
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (feasibility deck, 2026-09-29) — never checked; recorded so the Verifier can see it
No unexpired US patent held by any assignee other than 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-09-29) — never checked; recorded so the Verifier can see it
Words on this page28 abbreviation(s) and code(s), with what each stands for — copied from _shared/plain-language.md
21 CFR
Title 21 of the Code of Federal Regulations — the US food-and-drug rulebook; a number after it is one regulation, often the one that classifies a device type
510(k)
premarket notification — the FDA route for a device shown to be as safe and effective as one already on the market; months, no clinical trial as a rule
A####
a HCPCS code for a supply — one billing code for a supply or an accessory; the letter A and four digits
Class II
FDA device class II — moderate-risk devices, usually cleared by 510(k)
CMS
Centers for Medicare & Medicaid Services — the US agency that runs Medicare, and so decides what Medicare pays for
CY
calendar year — the year a Medicare rule or fee schedule applies to
De Novo
De Novo classification request — the FDA route for a new, lower-risk device with no comparable product to point at; longer than a 510(k), usually needs clinical data
DME MAC
durable medical equipment Medicare administrative contractor — one of the four regional contractors that process Medicare's home-equipment claims and write its local coverage rules
DMEPOS
durable medical equipment, prosthetics, orthotics and supplies — the Medicare benefit and fee schedule that home equipment is paid under
EPO
European Patent Office — the European patent office
FDA
US Food and Drug Administration — the US regulator that clears or approves a device before it can be sold
FFS
fee-for-service — the traditional form of Medicare that pays per item or service
FTO
freedom to operate — whether a product can be sold without infringing someone else's live patent
HCPCS
Healthcare Common Procedure Coding System — the US billing codes for equipment, supplies and some services; a code is how a payer recognises what to pay for
IP
intellectual property — patents and the other rights that let a company stop others copying it
K######
an FDA 510(k) clearance number — the public record of one cleared device; the letter K and six digits
LCD
local coverage determination — a Medicare contractor's rule, valid in its region, saying when something is covered
Medicare Advantage
Medicare Advantage — Medicare delivered through a private insurer; must cover at least what Medicare covers
Medicare Part B
Medicare Part B — the part of Medicare that pays for outpatient care and equipment used at home
mmHg
millimetres of mercury — the unit blood pressure, and the suction of a wound pump, are measured in
NCD
national coverage determination — a Medicare rule, valid everywhere in the US, saying whether and when something is covered
PDAC
Pricing, Data Analysis and Coding contractor — the Medicare contractor that decides which billing code a specific product falls under
PFS
physician fee schedule — the Medicare price list for what clinicians do
PMID
PubMed identifier — the public id of one published medical paper
QMS
quality management system — the documented processes a manufacturer must run to be allowed to sell a device
RCT
randomised controlled trial — the kind of clinical study that compares a treatment against an alternative by chance assignment
RVU
relative value unit — the unit Medicare uses to price a clinician's work
TAM
total addressable market — how much money the whole market would be worth if every possible buyer bought