idea-009 · human · wrapped
Read this before anything else on the page. A low count here is usually a
statement about this repo's tooling rather than about the idea — a
unconfirmed reimbursement claim most often means the CMS cache file
is absent and nothing was searched, which is not evidence that a code
does not exist.
The one-paragraph version. A below-knee compression wrap for people with leg lymphedema who cannot pull on a conventional compression stocking. It fastens with overlapping hook-and-loop straps rather than being pulled over the foot, and each strap carries a printed window that lines up at a fixed tension — a purely mechanical gauge, no electronics, so the wearer can reproduce roughly the same pressure each time instead of guessing. It is scoped to the maintenance phase of lymphedema therapy, not the intensive phase, and the whole design was worked backwards from one Medicare code, A6583, whose descriptor names an adjustable-strap below-knee gradient wrap.
What would have to be true, quoted from each deck's load-bearing condition:
Cheapest next test: Place the four CMS quarterly files in data/ — the viability deck's own arithmetic is that this "resolves up to eleven claims unattended", including the A6583 descriptor, the payment amount, the coverage policy and the utilisation volume, none of which has ever been searched. Selected from the Reimbursement and TAM rows of the Scores table; this is a selection from that gap analysis, not a new judgement, and not a view about the idea.
Where the evidence actually stands. 7 of 50 claims verified, 8 of 9 factors carrying a score, 4 of 4 core factors scored. Two things a reader should not misread. First, the Reimbursement position looks like the strongest paper argument in the file and rests on a descriptor that was never retrieved — data/ holds only README.md, so every CMS connector returned "no local cache" and nothing was searched; that is an absence of a query, not a favourable finding. Second, the regulatory position is genuinely verified as far as it goes — 21 CFR 880.5780(b) is Class I and exempt — but the same verified text says "constructed of elastic material" while this device is short-stretch by design, which is the feasibility deck's load-bearing condition and is not settled by the regulation being read correctly. FTO is scored 1 as an unexamined field: no patent search has ever run, because PATENTSVIEW_API_KEY is unset, on the rubric's one automatic-kill factor.
| Intended use | For use by adults with a clinician-documented diagnosis of lower-extremity lymphedema, under the direction of a licensed clinician, to apply and maintain gradient compression to the below-knee limb during the maintenance (self-management) phase of complete decongestive therapy, in patients who are unable to self-don a flat-knit compression garment. |
|---|---|
| Mechanism | Inelastic (short-stretch) below-knee wrap applied as overlapping circumferential bands with hook-and-loop straps, each strap carrying a purely mechanical tension-calibration indicator (a printed elongation window that aligns at a fixed strap tension) so the wearer can reproduce a target gradient compression profile at each donning without a fitter, a dynamometer, or any electronics |
| Device class | # Two paragraphs of ONE regulation, which land in two different; Class I — 21 CFR 880.5780(b) ("medical support stocking ... for medical purposes other; than the prevention of pooling of blood in the leg"), product code FQL per the; Generator's web search — 510(k)-exempt under subpart E of part 807, subject to the; limitations in 880.9 — launch designation.; Class II — 21 CFR 880.5780(a) ("to prevent the pooling of blood in the legs"), product; code DWL per the Generator's web search — per the same search, also exempt from; premarket notification, but Class II with special controls. NOT live under the current; intended_use, which deliberately makes no venous / blood-pooling claim. Carried because; a single sentence of marketing copy about "venous circulation" moves the product here.; Regulation NOT identified by the Generator — the route that would apply if the device; carried a venous-leg-ulcer healing claim or a sub-bandage pressure measurement; claim. The Generator could not identify which regulation FDA would use and is not; guessing one. Both claims are excluded by the intended_use for exactly this reason. |
| Predicate or analog | No K-number identified, and none should be expected — the launch route is; 510(k)-exempt, so competing wraps do not appear in openFDA's 510(k); database at all. Market analogs identified by name via web search only:; medi circaid juxtafit / juxta-lite, Essity/BSN JOBST FarrowWrap, Sigvaris; Compreflex, Solaris. The Generator did not confirm which product code any; of these firms lists under. |
| Launch jurisdiction | US |
| Target | human |
| Factor | Score | What would settle it |
|---|---|---|
| Regulatory pathway | 4 | python3 -m connectors regulation 880.5780 --expect "medical support stocking" and read paragraph (b) primary text for the class and the subpart-E exemption phrase; then python3 -m connectors regulation 880.9 for the limitations that…the rest of this gap analysisqualify any Part 880 exemption — the Generator explicitly did not read that language, and it is what converts "exempt" into "exempt unless". Thenpython3 -m connectors classification --product-code FQL and --product-code DWL for the openFDA class / exemption fields (the aggregator page they came from was never read against primary). Then python3 -m connectors classification --device-name "compression wrap" and --device-name "medical support stocking" to test whether a distinct generic type exists for wraps — a hit changes the regulation, not just the confidence. The measurement-claim question in scope item 4 is not connector-answerable: it settles only via a Tier 3 regulatory-counsel opinion on the draft labelling, or a 513(g) Request for Information submitted to FDA. Stage 4 update (2026-08-25): the class/exemption half of this row is now done and does not need re-running — 880.5780(a) and (b) and product codes FQL/DWL are verified off primary text. What remains is entirely the membership question, and it is not a connector gap: (i) whether FDA reads an inelastic short-stretch wrap into an identification paragraph that says "constructed of elastic material", and (ii) whether § 880.9(a) fires on patient self-application "without a fitter" as lay use where the former intended use was by health care professionals only. Neither is answerable by any connector in this repo, now or after the caches land — both are FDA judgments. The two routes are a 513(g) Request for Information or Tier 3 regulatory-counsel review of the draft labelling. One thing that is cheap and still worth doing: browse the FDA product-code classification database by regulation number 880.5780 and by panel HO (human retrieval — the --device-name probe form is known to miss records that exist) to see whether a distinct wrap generic type is listed. |
| Reimbursement pathway | 4 | python3 -m connectors hcpcs A6583 --expect "gradient compression wrap with adjustable straps", plus hcpcs A6552 and hcpcs A6554; these need data/hcpcs_level_ii.csv present — the Generator expects unconfirmed in this deployment,…the rest of this gap analysisand a missing cache file is a data gap, not a negative result.python3 -m connectors payment A6583 against the DMEPOS fee schedule loaded into data/hcpcs_payment_rates.csv (confirm the schedule field says DMEPOS — a PFS or OPPS row for a supply code would be the wrong number), which is the single figure that converts this factor from descriptor-match to economics. python3 -m connectors coverage A6583 plus the actual DME MAC Local Coverage Determination and Policy Article for lymphedema compression treatment items — pull the L-number from the CMS Medicare Coverage Database rather than guessing one, and read the diagnosis and quantity/replacement language directly. The benefit-category effective date settles from the CMS MLN Matters article / transmittal implementing the LTA (Scout download into data/, no connector). The PDAC coding-verification requirement and its product list settle from the PDAC (DME MAC pricing contractor) site — human/Scout retrieval, no connector, and worth doing early since it gates billing. Stage 4 update (2026-08-25): every one of these calls was attempted and every one returned unconfirmed for the same single cause — data/ contains only README.md, so data/hcpcs_level_ii.csv, data/hcpcs_payment_rates.csv and data/medicare_coverage_policies.csv are all absent. Nothing was searched; this factor has zero verified claims behind it, including the A6583 descriptor the product was deliberately sized to, which remains entirely unread against primary CMS text. This is the cheapest fix in the file and it resolves the largest block of claims: one human drops the three CMS quarterly files into data/ per data/README.md and every hcpcs/payment/coverage/procedures line above re-runs unattended. Two cautions for that re-run, unchanged: confirm the schedule field reads DMEPOS, and note the coverage connector confirms policy existence, not a positive stance — the "any diagnosis of lymphedema" breadth still needs the DME MAC LCD and Policy Article read directly. The 2024-01-01 benefit-category date is statutory and no cache fixes it: it needs the CMS transmittal / MLN Matters article downloaded by a human. |
| TAM | 2 | python3 -m connectors procedures A6583 — code-keyed CMS Part B utilisation, the only component with a real primary source. Read the result as a Medicare FFS floor on US volume, never as TAM: it excludes Medicare Advantage,…the rest of this gap analysiscommercial, 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 is a young-code artefact, not a small market.python3 -m connectors payment A6583 supplies the price ceiling for component 2. Component 3 is not connector-checkable (python3 -m connectors market returns unverifiable by design): it needs a licensed compression-therapy / lymphedema-DME market report attached by a human, plus a denominator of enrolled DMEPOS compression suppliers (CMS supplier-enrollment public file) and certified lymphedema fitters (LANA / accrediting-body registry counts). Stage 4 update (2026-08-25): the split between the cheap and the impossible is now sharp. Component 1 (procedures A6583) is blocked only by the missing data/medicare_procedure_volumes.csv — same one-file fix as Reimbursement, and it is the sole component with a real primary source. Components 2 and 3 both returned unverifiable by design and no cache, key or outage fix changes that; they move only when a human attaches a licensed market report and edits the claims by hand. Component 3 additionally embeds an adoption/switching assumption that is unverifiable by a second independent path, so fitter/supplier interviews are part of its price. When the volume file lands, carry both caveats into the line: a Medicare FFS count is a floor on US volume, never a market size, and for a code first payable 2024-01-01 a low number is a young-code artefact, not a small market. |
| FTO / IP | 1 | A search first, then lookups. Assignee sweeps on medi GmbH & Co. KG, BSN Medical / Essity, Sigvaris AG, Solaris (Tactile Medical) in USPTO Patents Public Search and Espacenet, combined with CPC class A61F13/08 (bandages/compression…the rest of this gap analysisfor limbs) and keyword sets on "adjustable compression wrap", "strap tension indicator", "elongation indicator", "sub-bandage pressure" — run by a human or Scout, since no connector performs discovery. Each candidate number then throughpython3 -m connectors patent US<number> for family, legal status and expiry — but supply PATENTSVIEW_API_KEY first, or every lookup returns unconfirmed for an infrastructure reason and would be misread as a clean field. Definitive answer is a Tier 3 legal FTO opinion at Stage 7; nothing an agent produces is one. Stage 4 update (2026-08-25): the pass confirmed two independent blocks, and neither has been lifted — there is still no patent number named anywhere in this file to look up, and PATENTSVIEW_API_KEY is still unset. The ordering matters and is easy to get wrong: setting the key alone buys nothing, because no connector here performs patent discovery; the assignee/CPC sweep has to happen first and produce numbers, and only then does the key make connectors patent US<number> useful. Until both are done this field is unexamined, not clear — the file contains zero evidence about FTO in either direction, and any later reader treating the absence of found patents as an all-clear would be manufacturing a finding. |
| Moat / defensibility | 1 | Resolves as a by-product of the FTO/IP search: a filed or filable claim on the indicator calibration (Patents Public Search → python3 -m connectors patent US<number>) is the only thing that converts the asserted differentiator into an…the rest of this gap analysisasset. The channel half is not connector-checkable —python3 -m connectors adoption returns unverifiable by design — and needs commissioned primary research a human attaches: structured interviews with certified lymphedema fitters and DMEPOS compression suppliers on brand-switching and shelf economics. Secondary read on copyability: the FDA Establishment Registration & Device Listing database under the confirmed product code, to count how fast new listings appear in this generic type. |
| Mechanism & clinical risk | 4 | Stage 0 scans point at the evidence but return no confidence tag and cannot verify a claim: python3 -m connectors literature "compression therapy lymphedema maintenance phase" --since 5y then literature-detail <PMIDs> for…the rest of this gap analysisadherence, sub-bandage pressure reproducibility and adverse events specifically with self-applied adjustable wraps;python3 -m connectors trials --condition "lymphedema" --intervention "compression wrap" then trial-detail <NCT> for the endpoints the field actually uses; python3 -m connectors recalls --product-code FQL --since 5y (once the code is confirmed at Factor 1) for the real-world incumbent-wrap signal, including any PAD-related events. The PAD contraindication and ABI screening language settle only via Tier 3 clinical/regulatory labelling review against the recognised consensus documents, not via any connector. |
| Capital intensity & time-to-revenue | 4 | Depends on Factor 1 resolving first (regulation 880.5780, regulation 880.9, classification --product-code FQL) — the exempt-vs-not fork drives everything in this row. Then the exempt-route obligations from primary text: `python3 -m…the rest of this gap analysisconnectors regulation 807.20 (establishment registration and device listing) to confirm what the exemption does *not* excuse, and the QMSR obligations under 21 CFR 820. The billing-side calendar is not connector-answerable: the PDAC coding-verification process and turnaround from the pricing contractor's own published procedure, and DMEPOS supplier enrolment (CMS-855S) timelines from the CMS enrolment guidance — Scout/human retrieval into data/`. Tooling and fitter-training cost is a Tier 3 human estimate, not a lookup. |
| Competitive intensity | 1 | Not clearances. The database where exempt-route competitors actually appear is the FDA Establishment Registration & Device Listing database, queried by product code once Factor 1 confirms one — no connector covers it, so it is a…the rest of this gap analysisScout/human retrieval intodata/, and it is the specific check that converts the structural null into a real competitor count. Run python3 -m connectors classification --product-code FQL first to get the code right. python3 -m connectors recalls --product-code FQL --firm <incumbent> --since 5y for incumbent trouble (Stage 0 scan, no confidence tag). The decisive half — whether certified fitters and DMEPOS suppliers would stock a fifth brand — is unverifiable by design (python3 -m connectors adoption) and needs commissioned fitter/supplier channel interviews attached by a human. Stage 4 update (2026-08-25): the Verifier demonstrated the failure mode this cell warns about, concretely, and the demonstration should be read before anyone scores this row. 510k "juxtafit" --applicant "medi" returned status refuted — purely from database absence, and it is not a finding that medi has no such product or does not compete; medi circaid juxtafit/juxta-lite is named in this file's own predicate_or_analog: frontmatter as a commercially marketed product. A 510(k)-exempt device is expected to be missing from the 510(k) database, and § 880.5780(a)/(b) exempting the generic type is now verified primary text, so that absence is confirmed structural. A related query also returned verified on K162481, an unrelated powered compression device that merely name-matches — so the null is not even reliable in the direction the claim predicted. No 510(k)/clearances result may lift or lower this factor. The competitor count is unmeasured, not zero: it lives in the FDA Establishment Registration & Device Listing database, which no connector here reaches, and it stays unmeasured until a human queries it by product code. |
| Strategic fit & portfolio balance | *(blank)* | A Tier 3 human portfolio statement at Stage 6 review, recorded in ## Human Review Notes: current portfolio composition, appetite for thin-margin DMEPOS channel businesses, and the hero-bet/spoke balance being targeted.…the rest of this gap analysisknowledge-base/calibration-log.md is the evidence base that would let this factor be scored systematically rather than by taste, and it is currently empty — that emptiness is information, not an obstacle to route around. |
All six wrap criteria are met.
Domain dossier: lower-extremity-lymphedema-compression-therapy
Source file: knowledge-base/candidates/idea-009.md
Nothing on this page is a recommendation. Shortlist review, legal and clinical sign-off and capital allocation are human-only decisions, and no agent in this repo may make or simulate one. This is a compilation of what the candidate file says.