idea-009 · human · US
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.
Finished enough to read, and waiting for you. No department has been asked. 11 of 73 claims verified, 2 refuted. Nobody has yet written down what it rests on.
A below-knee compression wrap for adults 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 strap tension — a purely mechanical gauge, no electronics — so the wearer can put the same tension back on at every donning instead of guessing. It is meant for the long-term self-management phase of lymphedema care, not the intensive phase, and it would be billed to Medicare's lymphedema compression benefit under the existing code for adjustable-strap below-knee wraps, A6583 (a HCPCS code for a supply). That code exists, has a published Medicare allowable and was billed in 2024; it names no pressure range, so it is open to any adjustable-strap below-knee wrap, and the tension window is the only thing this product adds.
In the Wrap's one-paragraph version, written for someone who has not opened the file. Domain: lower-extremity-lymphedema-compression-therapy
The chain has four parties. The file has verified evidence for the payer and the rule, and nothing verified for the two parties who choose the product.
intended_use: itself claim 25unconfirmed. Both are
adoption-class and will never resolve by connector.
What this idea rests on that is not yet known, in the order this idea's own decision queue puts it: worst if false first, cheapest to settle first inside that. The first row is open; open any other for what would settle it.
This idea is unassessed, so nobody has yet named the few things it rests on. Until then, the gaps below are the rubric factors that are unscored or carry an open question. /assess idea-009 replaces this list with the real one.
Why it scored what it did: intended_use: is present and deliberately narrow, so the factor is scoreable. Rests on the load-bearing 880.5780(b) claim (Class I, exempt from premarket notification under subpart E of part 807), the FQL product-code claim, and the…the rest of this reasoning
frontmatter's launch designation. If that exemption claim holds, this is close to the best Factor 1 position available: no submission, no predicate, no clinical study — which is why the file names it as the claim the whole time-to-revenue and capital argument hangs on. Held at 4, not 5, for two reasons the file states itself rather than hides: (a) the Generator's own claim that it did not establish FDA (US Food and Drug Administration) reads a strapped adjustable wrap into a regulation that says "stocking" — no product code for "compression wrap" as a generic type has been confirmed; (b) indication-scope item 4 — a sub-bandage pressure-measurement claim on the product's own differentiating feature would likely break the exempt route entirely, and the mitigation (indicator labelled a strap self-application aid, never a patient measurement) is a labelling intent, not a cleared position. Scored on the launch indication exactly as written.
What would settle it: Settles via a 513(g) Request for Information to FDA (agency fee, several months) or a Tier 3 regulatory-counsel opinion on the draft labelling, for the elastic-material and lay-use membership questions. A free human browse of the FDA…the rest of this gap analysis
product-code classification database by regulation 880.5780 and panel HO would supplement it.
Why it scored what it did: Strongest paper position in the file. Rests on the A6583 descriptor claim ("gradient compression wrap with adjustable straps, below knee, 30-50 mmHg (millimetres of mercury), each") — the product was sized to the code, so the descriptor match is by…the rest of this reasoning
construction, not luck; the adjacent A6552/A6554 garment-competitor claim; and the claim that lymphedema compression items became a distinct Medicare Part B benefit category for items furnished on or after 2024-01-01 under the Lymphedema Treatment Act. A statutory benefit category with a form-factor-specific code is materially better than "a code exists". Held at 4 and not higher because a code is not a pathway: no dollar figure for A6583 is asserted anywhere in this file (correctly — none was found), the coverage-for-any-lymphedema-diagnosis claim comes from a contractor web page rather than a named policy, and the file's own PDAC claim flags that coding verification plus DMEPOS supplier mechanics — not FDA — are the likely rate limiter on first revenue, with no requirement or quantity allowance established.
What would settle it: Stage 4 update (2026-09-29): code, price and benefit are now read from CMS (Centers for Medicare & Medicaid Services)/eCFR. What's left is the DME MAC lymphedema compression policy article, read directly from the Medicare Coverage Database (free, a few hours), plus a PDAC…the rest of this gap analysis
coding-verification enquiry (free, weeks of turnaround).
Why it scored what it did: Not one of the three TAM (total addressable market) components carries a number, so this is a placeholder for "unquantified", not an estimate of a market. Component 1 (annual Medicare claim volume for A6583) — Generator states no figure. Component 2 (net selling…the rest of this reasoning
price) — no price asserted, because the fee-schedule amount it would be bounded by is itself unverified, so it is an assumption resting on an assumption. Component 3 (10-20% obtainable share within five years against four named incumbents) — explicitly the Generator's assumption, embedding a switching assumption, permanently unconfirmable by connector. The 3-5 million US adult lymphedema prevalence figure is aggregator-grade, is flagged in the file as not a TAM input, and was not multiplied by anything here. Scored at the floor because the one genuinely checkable component is unchecked.
What would settle it: Stage 4 update (2026-09-29): component 1 and the price ceiling are now read from CMS files. Components 2 and 3 still need a licensed compression-therapy/lymphedema-DME (durable medical equipment) market report attached by a human (paid), plus fitter/supplier…the rest of this gap analysis
interviews for share.
Why it scored what it did: Rests on a single claim that states outright that no patent search was performed and no patent number is named. Scored as unexamined, not as clear — an absence of found patents is not freedom to operate. Actively concerning rather than…the rest of this reasoning
merely unknown: the four named incumbents (medi GmbH circaid juxtafit/juxta-lite, Essity/BSN JOBST FarrowWrap, Sigvaris Compreflex, Solaris) have sold adjustable-strap inelastic wraps for years, and this candidate's only differentiator — a printed strap elongation window calibrated to a target tension — sits in exactly the narrow art where a blocking claim would live. The file also records that this deployment has no PATENTSVIEW_API_KEY, so even a named number returns unconfirmed; the correct reading of that is still "no search performed".
What would settle it: Stage 4 update (2026-09-29): the incumbent CPC sweep has run. Next is a human search for any US member of Essity family 81386942 and a claim-level read of the leads (free, hours); the definitive answer is a Tier 3 legal FTO (freedom to operate) opinion at…the rest of this gap analysis
Stage 7 (paid).
Why it scored what it did: Rests on the moat claim, whose own candid text says this is a weak moat: the category is textile manufacturing, the A6583 descriptor is open to any product meeting it, and a 510(k) (premarket notification)-exempt route protects incumbents and entrants…the rest of this reasoning
symmetrically — the regulatory advantage in Factor 1 is explicitly not a moat, it is an open door that four incumbents already walked through. The two asserted assets are the tension-indicator calibration and the certified-fitter / DMEPOS channel; the first is unprotected for as long as FTO/IP is unexamined, so this row is capped by the row above, and the second is an assumption about a channel the candidate does not yet occupy.
What would settle it: Resolves as a by-product of the FTO/IP patent search (free) for the IP (intellectual property) half. The channel half needs human-commissioned interviews with certified lymphedema fitters and DMEPOS suppliers on brand-switching (paid primary research), plus a…the rest of this gap analysis
secondary look at the FDA Establishment Registration & Device Listing database to gauge how fast new listings appear.
Why it scored what it did: Rests on the mechanism/clinical-risk claim and the maintenance-phase scope choice. Genuinely favourable: sustained gradient compression is established maintenance therapy in complete decongestive therapy, so there is no novel biological…the rest of this reasoning
mechanism to prove and no efficacy study on the exempt route. Scope discipline helps — excluding the intensive decongestive phase removes the failure mode that is clinical (therapist-applied multilayer bandaging) and leaves one that is ergonomic. Held at 4 rather than 5 for the named material risk: application over undiagnosed peripheral arterial disease, which makes an arterial-insufficiency contraindication and an ankle-brachial-index screening statement mandatory labelling content, and which is a real-world harm pathway a self-applied device makes more likely than a fitter-applied one.
What would settle it: Stage 0 literature, trials, and recalls scans (free) surface reading material but cannot verify a clinical-risk claim by rule. The PAD-contraindication and ABI-screening language settle only via a Tier 3 clinical/regulatory labelling…the rest of this gap analysis
review against recognised consensus documents.
Why it scored what it did: Rests on the capital/time claim, which is deliberately stated without a dollar or month figure — correctly, since both would be invented. The shape is strong: on the exempt route the FDA cost is establishment registration, device…the rest of this reasoning
listing and QMS (quality management system) compliance rather than a submission, and there is no clinical study, so first revenue is gated by textile tooling, fitter training and billing mechanics rather than by FDA review calendar. Held at 4 rather than 5 because the file names its own long pole and does not size it — PDAC coding verification plus DMEPOS supplier enrolment and channel build — and because this entire row is a derivative of Factor 1: if the 880.5780(b) exemption or the wrap-is-a-stocking reading fails, the cost and calendar are a different number entirely, not a slightly worse one.
What would settle it: Depends on Factor 1 resolving first; then eCFR 807.20 (registration/listing) and 21 CFR (Title 21 of the Code of Federal Regulations) 820 (QMSR) confirm what the exemption doesn't excuse (free). The PDAC coding-verification procedure and CMS-855S supplier-enrollment timeline need…the rest of this gap analysis
Scout/human retrieval, and tooling/fitter-training cost is a Tier 3 human estimate.
Why it scored what it did: Low score = high intensity = unfavourable. Four incumbents are named by name in this file — medi circaid juxtafit/juxta-lite, Essity/BSN JOBST FarrowWrap, Sigvaris Compreflex, Solaris — selling into a mature category through a channel…the rest of this reasoning
where, per the file's own adoption assumption, the fitter rather than the patient selects the product. The 2024 benefit category that makes this candidate attractive makes it equally attractive to every one of them and to new entrants, and the exempt route means none of them needs a clearance to respond. Read the structural-null warning claim before scoring this row any higher: because the launch route is 510(k)-exempt, 510k and clearances queries for competing wraps return nothing, and that silence is a property of the exemption, not evidence of an empty field. A clean clearances result here is not an all-clear and must not lift this factor.
What would settle it: The FDA Establishment Registration & Device Listing database, queried by product code (Scout/human retrieval), is what actually counts exempt-route competitors — no 510(k)/clearances result may substitute. A recalls scan by product code…the rest of this gap analysis
and incumbent firm (free, Stage 0) is a supplementary signal, and commissioned fitter/DMEPOS-supplier interviews (paid primary research) settle whether a fifth brand would be stocked.
Why it scored what it did: Left unscored deliberately. No claim in this file addresses portfolio fit, and no portfolio thesis, capital-allocation mandate or target hero-bet/spoke ratio exists anywhere in this repo to score fit against. The candidate's shape is…the rest of this reasoning
legible — a low-capital, fast-to-revenue, weak-moat cash-generative spoke — but shape is not fit, and inventing a number here would be scoring against a portfolio nobody has written down. Not a research gap; a missing referent.
What would settle it: A Tier 3 human portfolio statement at Stage 6 review (recorded in Human Review Notes) — free, but only a human can write it. knowledge-base/calibration-log.md would let this factor score systematically once populated; it's currently…the rest of this gap analysis
empty.
Seven chairs, each answering from its own field. The verdict, and the first condition it set.
Not convened. No department has stated a position on this idea yet — a normal state, not a defect. /round-table idea-009 asks all seven.
Only verified counts toward a score. A low count is usually a statement about the tooling — an absent data file, an unset key — rather than about the idea.
2 claim(s) the Verifier found to be false — a refuted claim is a finding, and the loop owes each one an answer.
Score-mover — a human/Scout retrieval, at no dollar cost, of the DME MAC lymphedema compression policy article / LCD (local coverage determination) from the CMS Medicare Coverage Database and the PDAC coding-verification requirement and A6583 product list, which the Reimbursement row of the Scores table names as still needing "separate human/Scout retrieval — no dollar cost, but real time"; it is the part of that row the CMS files now in data/ cannot answer, and it bears on claims 12, 14, 32, 45 and 61 and on the viability deck's load-bearing condition. This is a selection from that gap analysis, not a new judgement and not a view about the idea. The row's other named step — placing the CMS quarterly files in data/ — has been done. Decision-mover — none can be named: there is no assessment, so no decision queue; /assess idea-009 is what would produce one.
Only verified counts toward a score. A low count is usually a statement about the tooling (an absent data file, an unset key) rather than about the idea.
Evaluated 2026-08-25 against the Verified Composite above, using verified claims only. The Stage 2 draft table was not consulted. Unchecked boxes below mean the condition did not fire — in this file, in every case, because the data the condition reads does not exist yet. A condition that cannot be evaluated is not a condition that passed.
unconfirmed: procedures and payment hit the missing data/
caches (nothing was searched) and market is unverifiable by design. An undefined
operand is not a low one, and the floor was not applied.
PATENTSVIEW_API_KEY. Zero patents were searched. FTO is the rubric's only automatic
kill regardless of other scores, which makes an unexamined field the most consequential
hole here. An absence of found patents is not freedom to operate, and the differentiating
feature sits in exactly the narrow art four long-established incumbents occupy.
All three kill conditions are written over core factors — Regulatory, Reimbursement, TAM, FTO. Of those four, exactly one (Regulatory, 2/5) has a verified claim behind it, and it sits at its floor rather than below. The other three — the three that actually decide this gate — are blank. So the gate is not reporting that this candidate survived scrutiny; it is reporting that the scrutiny the gate performs has nothing to read. That distinction is the whole point of separating queued-research from gated-out: "we don't know yet" is not "the answer is no."
data/ caches: hcpcs (do A6583,
A6552, A6554 exist), payment (what A6583 pays) and coverage (is there a policy). This
leaves the file's strongest-looking asset — the A6583 descriptor the product was
deliberately sized to — entirely unread against primary CMS text. The apparent strength of
this factor at Stage 2 was an artifact of nobody having checked it.
The candidate's desirability crux — that a population defined by inability to self-don a flat-knit garment can nonetheless self-apply a multi-strap wrap to a reproducible tension — has zero evidence on either side, and no connector will ever supply it. adoption is unverifiable by design. The nine rubric factors do not score whether a user wants the thing, so this gate would return the same result whether that premise were true or false.
queued-research, in order: the CMS HCPCS/payment/coverage/
utilization files into data/ (up to 8 claims, no licensing obstacle); re-running the three
eCFR-dependent lines once the endpoint recovers (free — it was down all day 2026-08-25,
established by control); then a human/Scout assignee sweep to find patent numbers, which
must precede setting PATENTSVIEW_API_KEY rather than follow it.
wrapped is not an approval — it means a human can now read this.
No human review is recorded. Shortlisting, legal and clinical sign-off and capital allocation are Tier 3: no agent in this repo makes or simulates one. The packet is wrapped, so it can be read now.
Runs only after a human shortlists the idea.
No loop record: nobody has written down what this idea rests on or convened a department on it. That is a normal state, not a defect. /front-end-loop idea-009 opens one.
Nobody has yet written down what this idea rests on and what it would cost to be wrong. Unassessed is a state, not a low score. /assess idea-009 adds it.
Click any step to see what it holds for this idea. donecurrentloopinghuman only
## Wrap section, as writtenThe one-paragraph version. A below-knee compression wrap for adults 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 strap tension — a purely mechanical gauge, no electronics — so the wearer can put the same tension back on at every donning instead of guessing. It is meant for the long-term self-management phase of lymphedema care, not the intensive phase, and it would be billed to Medicare's lymphedema compression benefit under the existing code for adjustable-strap below-knee wraps, A6583. That code exists, has a published Medicare allowable and was billed in 2024; it names no pressure range, so it is open to any adjustable-strap below-knee wrap, and the tension window is the only thing this product adds.
What would have to be true, quoted verbatim from each deck's load-bearing condition:
No assessment exists for this candidate (wrap_status.py: "assessment: none — unassessed, not a zero"), so there is no decision queue and no top pillars to set beside these three.
Two statements in this file have failed, and both failed on the same fact. claim 8refuted said A6583 is descriptor-defined as "Gradient compression wrap with adjustable straps, below knee, 30-50 mmHg, each"; the current CMS HCPCS file reads "Gradient compression wrap with adjustable straps, below knee, each" — no pressure band claim 8refuted, claim 44verified. The code itself exists; the band does not. claim 36refuted said the wrap produces its gradient "within the 30-50 mmHg band named in the A6583 descriptor"; the descriptor names no band, so the claim as written fails claim 36refuted. What did not fail is the bench question inside claim 36refuted — whether a patient-applied wrap produces a falling distal-to-proximal gradient at any band — which has never been tested; the restated version is claim 70unverified claim 70unverified. The file's own reading of the consequence: the refuted descriptor premise "means the code is not reserved for a product sized to it" (viability deck, Slide 9). No loop record exists for this candidate, so no impact review has been opened on either refutation.
Cheapest next test: Score-mover — a human/Scout retrieval, at no dollar cost, of the DME MAC lymphedema compression policy article / LCD from the CMS Medicare Coverage Database and the PDAC coding-verification requirement and A6583 product list, which the Reimbursement row of the Scores table names as still needing "separate human/Scout retrieval — no dollar cost, but real time"; it is the part of that row the CMS files now in data/ cannot answer, and it bears on claims 12, 14, 32, 45 and 61 and on the viability deck's load-bearing condition. This is a selection from that gap analysis, not a new judgement and not a view about the idea. The row's other named step — placing the CMS quarterly files in data/ — has been done. Decision-mover — none can be named: there is no assessment, so no decision queue; /assess idea-009 is what would produce one.
Where the evidence actually stands. wrap_status.py (2026-09-29): 11 of 73 claims verified — 43 unconfirmed, 17 unverified, 11 verified, 2 refuted; 8 of 9 factors carry a score in the Scores table and 4 of 4 core factors do. Those scores are the Stage 2 triage draft. The Verified Composite (12.0 / 100, 2 / 9 factors verified) and the Gate Check (queued-research) above were computed on 2026-08-29 and 2026-08-25, before the 2026-09-29 Verifier pass that raised claims 9, 11, 15 and 44 to verified and refuted claims 8 and 36. Neither has been re-run, so both describe the file as it stood then, not now.
What the CMS files now settle, each quoted from the claim that carries it: the A6583 Medicare allowable is "non-rural $160.13 across 49 contiguous states/DC" on the July 2026 DMEPOS fee schedule, for one wrap, before the 20% coinsurance claim 11verified; data year 2024 shows "80,433 services across 24,631 beneficiaries" for A6583, which is a Medicare fee-for-service floor in the code's first payable year and never a market size claim 15verified; the adjacent stocking codes A6552 (30-40 mmHg) and A6554 (40 mmHg or greater) exist claim 9verified; and the benefit category names "gradient compression wraps with adjustable straps" claim 42verified, paid at 80 percent of the lesser of actual charge or the payment amount claim 43verified. The regulatory position is verified as far as the generic type goes — § 880.5780(b) is Class I and exempt from premarket notification claim 2verified — but that same text identifies a device "constructed of elastic material", and whether an inelastic wrap belongs to it is still open claim 6unconfirmed; that is an unresolved question in primary text, not a tooling gap.
Blocked on tooling, not on a finding — do not read any of these as a negative:
coverage A6583 now returns refuted, but the cached coverage file holds
Billing & Coding / policy Articles only — no LCD and no NCD (national coverage determination) rows — and its DME MAC policy
articles carry a blank codes column. The file records that this miss "describes this
cache's linkage, not CMS's". Coverage breadth, quantity limits and the PDAC requirement stay
unread claim 12unconfirmed, claim 14unconfirmed, claim 45unconfirmed.
PATENTSVIEW_API_KEY not set" diagnosis records an earlier run and is
historical claim 19unconfirmed; the patent connector now runs on EPO (European Patent Office) OPS, kind-coded
numbers resolve, and a field sweep (patent-scan) exists. That sweep has run over CPC
A61F13/08 against the four named incumbents and surfaced leads, the closest being Essity's
"COMPRESSION GARMENT WITH INDICATOR", seen only as a Canadian application claim 41unconfirmed. What is missing is not a key but an FTO read: nobody has read whether an
in-force US patent claims the indicator. FTO is an unexamined field, not a clear one, on the
rubric's one automatic-kill factor.
One unconfirmed line is a finding about wording rather than a tooling gap: the 2024 benefit category resolves against primary text on three of four elements, but no primary text read names it the "Lymphedema Treatment Act" claim 10unconfirmed.
| Factor | Score | Why | What would settle it |
|---|---|---|---|
| Regulatory pathway | 4 | intended_use: is present and deliberately narrow, so the factor is scoreable. Rests on the load-bearing 880.5780(b) claim (Class I, exempt from premarket notification under subpart E of part 807), the FQL product-code claim, and the…the rest of this reasoningfrontmatter's launch designation. If that exemption claim holds, this is close to the best Factor 1 position available: no submission, no predicate, no clinical study — which is why the file names it as the claim the whole time-to-revenue and capital argument hangs on. Held at 4, not 5, for two reasons the file states itself rather than hides: (a) the Generator's own claim that it did not establish FDA reads a strapped adjustable wrap into a regulation that says "stocking" — no product code for "compression wrap" as a generic type has been confirmed; (b) indication-scope item 4 — a sub-bandage pressure-measurement claim on the product's own differentiating feature would likely break the exempt route entirely, and the mitigation (indicator labelled a strap self-application aid, never a patient measurement) is a labelling intent, not a cleared position. Scored on the launch indication exactly as written. | Settles via a 513(g) Request for Information to FDA (agency fee, several months) or a Tier 3 regulatory-counsel opinion on the draft labelling, for the elastic-material and lay-use membership questions. A free human browse of the FDA…the rest of this gap analysisproduct-code classification database by regulation 880.5780 and panel HO would supplement it. |
| Reimbursement pathway | 4 | Strongest paper position in the file. Rests on the A6583 descriptor claim ("gradient compression wrap with adjustable straps, below knee, 30-50 mmHg, each") — the product was sized to the code, so the descriptor match is by…the rest of this reasoningconstruction, not luck; the adjacent A6552/A6554 garment-competitor claim; and the claim that lymphedema compression items became a distinct Medicare Part B benefit category for items furnished on or after 2024-01-01 under the Lymphedema Treatment Act. A statutory benefit category with a form-factor-specific code is materially better than "a code exists". Held at 4 and not higher because a code is not a pathway: no dollar figure for A6583 is asserted anywhere in this file (correctly — none was found), the coverage-for-any-lymphedema-diagnosis claim comes from a contractor web page rather than a named policy, and the file's own PDAC claim flags that coding verification plus DMEPOS supplier mechanics — not FDA — are the likely rate limiter on first revenue, with no requirement or quantity allowance established. | Stage 4 update (2026-09-29): code, price and benefit are now read from CMS/eCFR. What's left is the DME MAC lymphedema compression policy article, read directly from the Medicare Coverage Database (free, a few hours), plus a PDAC…the rest of this gap analysiscoding-verification enquiry (free, weeks of turnaround). |
| TAM | 2 | Not one of the three TAM components carries a number, so this is a placeholder for "unquantified", not an estimate of a market. Component 1 (annual Medicare claim volume for A6583) — Generator states no figure. Component 2 (net selling…the rest of this reasoningprice) — no price asserted, because the fee-schedule amount it would be bounded by is itself unverified, so it is an assumption resting on an assumption. Component 3 (10-20% obtainable share within five years against four named incumbents) — explicitly the Generator's assumption, embedding a switching assumption, permanently unconfirmable by connector. The 3-5 million US adult lymphedema prevalence figure is aggregator-grade, is flagged in the file as not a TAM input, and was not multiplied by anything here. Scored at the floor because the one genuinely checkable component is unchecked. | Stage 4 update (2026-09-29): component 1 and the price ceiling are now read from CMS files. Components 2 and 3 still need a licensed compression-therapy/lymphedema-DME market report attached by a human (paid), plus fitter/supplier…the rest of this gap analysisinterviews for share. |
| FTO / IP | 1 | Rests on a single claim that states outright that no patent search was performed and no patent number is named. Scored as unexamined, not as clear — an absence of found patents is not freedom to operate. Actively concerning rather than…the rest of this reasoningmerely unknown: the four named incumbents (medi GmbH circaid juxtafit/juxta-lite, Essity/BSN JOBST FarrowWrap, Sigvaris Compreflex, Solaris) have sold adjustable-strap inelastic wraps for years, and this candidate's only differentiator — a printed strap elongation window calibrated to a target tension — sits in exactly the narrow art where a blocking claim would live. The file also records that this deployment has noPATENTSVIEW_API_KEY, so even a named number returns unconfirmed; the correct reading of that is still "no search performed". | Stage 4 update (2026-09-29): the incumbent CPC sweep has run. Next is a human search for any US member of Essity family 81386942 and a claim-level read of the leads (free, hours); the definitive answer is a Tier 3 legal FTO opinion at…the rest of this gap analysisStage 7 (paid). |
| Moat / defensibility | 1 | Rests on the moat claim, whose own candid text says this is a weak moat: the category is textile manufacturing, the A6583 descriptor is open to any product meeting it, and a 510(k)-exempt route protects incumbents and entrants…the rest of this reasoningsymmetrically — the regulatory advantage in Factor 1 is explicitly not a moat, it is an open door that four incumbents already walked through. The two asserted assets are the tension-indicator calibration and the certified-fitter / DMEPOS channel; the first is unprotected for as long as FTO/IP is unexamined, so this row is capped by the row above, and the second is an assumption about a channel the candidate does not yet occupy. | Resolves as a by-product of the FTO/IP patent search (free) for the IP half. The channel half needs human-commissioned interviews with certified lymphedema fitters and DMEPOS suppliers on brand-switching (paid primary research), plus a…the rest of this gap analysissecondary look at the FDA Establishment Registration & Device Listing database to gauge how fast new listings appear. |
| Mechanism & clinical risk | 4 | Rests on the mechanism/clinical-risk claim and the maintenance-phase scope choice. Genuinely favourable: sustained gradient compression is established maintenance therapy in complete decongestive therapy, so there is no novel biological…the rest of this reasoningmechanism to prove and no efficacy study on the exempt route. Scope discipline helps — excluding the intensive decongestive phase removes the failure mode that is clinical (therapist-applied multilayer bandaging) and leaves one that is ergonomic. Held at 4 rather than 5 for the named material risk: application over undiagnosed peripheral arterial disease, which makes an arterial-insufficiency contraindication and an ankle-brachial-index screening statement mandatory labelling content, and which is a real-world harm pathway a self-applied device makes more likely than a fitter-applied one. | Stage 0 literature, trials, and recalls scans (free) surface reading material but cannot verify a clinical-risk claim by rule. The PAD-contraindication and ABI-screening language settle only via a Tier 3 clinical/regulatory labelling…the rest of this gap analysisreview against recognised consensus documents. |
| Capital intensity & time-to-revenue | 4 | Rests on the capital/time claim, which is deliberately stated without a dollar or month figure — correctly, since both would be invented. The shape is strong: on the exempt route the FDA cost is establishment registration, device…the rest of this reasoninglisting and QMS compliance rather than a submission, and there is no clinical study, so first revenue is gated by textile tooling, fitter training and billing mechanics rather than by FDA review calendar. Held at 4 rather than 5 because the file names its own long pole and does not size it — PDAC coding verification plus DMEPOS supplier enrolment and channel build — and because this entire row is a derivative of Factor 1: if the 880.5780(b) exemption or the wrap-is-a-stocking reading fails, the cost and calendar are a different number entirely, not a slightly worse one. | Depends on Factor 1 resolving first; then eCFR 807.20 (registration/listing) and 21 CFR 820 (QMSR) confirm what the exemption doesn't excuse (free). The PDAC coding-verification procedure and CMS-855S supplier-enrollment timeline need…the rest of this gap analysisScout/human retrieval, and tooling/fitter-training cost is a Tier 3 human estimate. |
| Competitive intensity | 1 | Low score = high intensity = unfavourable. Four incumbents are named by name in this file — medi circaid juxtafit/juxta-lite, Essity/BSN JOBST FarrowWrap, Sigvaris Compreflex, Solaris — selling into a mature category through a channel…the rest of this reasoningwhere, per the file's own adoption assumption, the fitter rather than the patient selects the product. The 2024 benefit category that makes this candidate attractive makes it equally attractive to every one of them and to new entrants, and the exempt route means none of them needs a clearance to respond. Read the structural-null warning claim before scoring this row any higher: because the launch route is 510(k)-exempt,510k and clearances queries for competing wraps return nothing, and that silence is a property of the exemption, not evidence of an empty field. A clean clearances result here is not an all-clear and must not lift this factor. | The FDA Establishment Registration & Device Listing database, queried by product code (Scout/human retrieval), is what actually counts exempt-route competitors — no 510(k)/clearances result may substitute. A recalls scan by product code…the rest of this gap analysisand incumbent firm (free, Stage 0) is a supplementary signal, and commissioned fitter/DMEPOS-supplier interviews (paid primary research) settle whether a fifth brand would be stocked. |
| Strategic fit & portfolio balance | *(blank)* | Left unscored deliberately. No claim in this file addresses portfolio fit, and no portfolio thesis, capital-allocation mandate or target hero-bet/spoke ratio exists anywhere in this repo to score fit against. The candidate's shape is…the rest of this reasoninglegible — a low-capital, fast-to-revenue, weak-moat cash-generative spoke — but shape is not fit, and inventing a number here would be scoring against a portfolio nobody has written down. Not a research gap; a missing referent. | A Tier 3 human portfolio statement at Stage 6 review (recorded in Human Review Notes) — free, but only a human can write it. knowledge-base/calibration-log.md would let this factor score systematically once populated; it's currently…the rest of this gap analysisempty. |
All eight wrap criteria are met.
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.
_shared/plain-language.md