idea-014 · human · US
For prescription use by children and adolescents ages 5 through 17 with; physician-diagnosed persistent asthma, to record and transmit daily peak expiratory flow; and/or FEV1 measurements together with structured symptom and medication-adherence data from; the home to the prescribing clinician, as an adjunct to guideline-directed asthma; action-plan management and not for use in acute respiratory distress or as a substitute for; emergency care.
Finished enough to read, and waiting for you. No department has been asked. 14 of 40 claims verified. Nobody has yet written down what it rests on.
This is a small handheld device, connected by Bluetooth to a phone app, that a child with persistent asthma (ages 5-17) would use at home once a day: it measures how well their lungs are working (peak flow / FEV1) and asks a few questions about symptoms and whether they took their medication, then sends all of it to their prescribing doctor. It would be sold by prescription only, not over the counter, specifically so the doctor's practice can bill Medicare-style monitoring codes for reviewing that data between office visits — that billing angle, not new hardware, is the whole idea. The underlying measurement technology already exists in several FDA (US Food and Drug Administration)-cleared devices; what doesn't yet exist is a device positioned this way, for this population, tied this explicitly to between-visit billing.
In the Wrap's one-paragraph version, written for someone who has not opened the file. Domain: pediatric-persistent-asthma-home-monitoring
The whole idea's differentiator is a billing angle, not a hardware one — the mechanism description makes the RPM (remote physiological monitoring) CPT (Current Procedural Terminology) code family the point. So the budget-holder chain is where this case has to stand or fall, and it has two cheques written by two different parties.
adoption returns unverifiable on any claim about which entity would
actually stock it (see below).
The chain's weakest link is the second cheque. The device-supply side has a real prescriber and a real CPT code with a verified CMS rate behind it; the RPM-service side has no identified non-Medicare payer at all, for a population that is almost entirely non-Medicare.
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-014 replaces this list with the real one.
Why it scored what it did: Two plausible Class II (FDA device class II) 510(k) (premarket notification) routes, both from real-looking predicates (K183479 (an FDA 510(k) clearance number) combined-function; K200832/K230423 bare peak-flow) — claims 1-3. Neither product code/CFR pairing nor which route applies has been confirmed against a primary…the rest of this reasoning
FDA record; the BZH product code is itself read off a third-party search-tool URL, not FDA.
What would settle it: openFDA classification lookup (BZG, BZH) plus the K183479 510(k) summary PDF — both free, effectively immediate to pull.
Why it scored what it did: CPT 99453/99454/99457 rates quoted from RPM-billing vendor blogs, not the CMS fee schedule itself — claims 4-6. CMS's device-must-meet-FDA-definition-and-chronic-condition-management requirement is stated only as the Generator's own…the rest of this reasoning
reading of vendor-blog content, explicitly flagged as a design assumption — claim 11unconfirmed. No coverage policy or payer precedent identified; codes existing is not the same as a payer paying for this specific device/indication.
What would settle it: CMS Physician Fee Schedule Look-Up Tool (free) for the three CPT rates, plus an LCD (local coverage determination)/NCD/payer-policy search for pediatric RPM coverage — a few hours' work.
Why it scored what it did: Population figure (4.8M children, "current asthma," 2023) is all-severity, not the persistent-asthma subgroup this candidate targets — claim 7unconfirmed. Price ($99/mo) is Generator arithmetic built entirely on the unverified CPT-rate claims above —…the rest of this reasoning
claim 8unconfirmed. Addressable-share (30-40% persistent) is an explicit unsourced Generator guess — claim 9unconfirmed. All three TAM (total addressable market) legs are unverified and the population leg doesn't even match the stated target population yet.
What would settle it: Primary CDC/NHIS prevalence table (free) plus a claims/registry-based RPM-enrollment estimate (likely a licensed report) for population and addressable share.
Why it scored what it did: No patent or FTO (freedom to operate) search was performed at all — stated explicitly as an open gap, not a finding either way (claim 12unconfirmed). Predicate hardware (electronic peak-flow meters, digital spirometers) has existed since the mid-2010s, which is mildly…the rest of this reasoning
reassuring for the base hardware, but the specific combination (continuous RPM billing + action-plan-threshold alerting algorithm) is entirely unexamined.
What would settle it: A PatentsView keyword search on peak-flow/RPM/alerting-logic claims — free API, a few hours' work.
Why it scored what it did: The differentiation is an indication-scope/billing-eligibility lever (prescription-only, chronic-management framing to qualify for RPM CPT codes) rather than a technical one — see "Indication-scope note." Once public, any of the 5+…the rest of this reasoning
existing 510(k) holders for connected peak-flow/spirometer hardware (claim 10verified) could copy the same narrowing move with comparable hardware.
What would settle it: An openFDA/market search for other prescription-only, RPM-billed pediatric-asthma monitors already marketed or pipelined — free, a few hours.
Why it scored what it did: Peak-flow/spirometry measurement is a decades-old, well-characterized mechanism with multiple existing 510(k)-cleared home-use predicates in the same pediatric age range (claims 1, 2, 10). No novel biological or device-accuracy mechanism…the rest of this reasoning
is being proposed — the novelty is in billing/indication scope, not measurement physiology.
What would settle it: Published PubMed literature comparing home vs. clinic-grade spirometry accuracy in the 5-17 age range — a free literature search.
Why it scored what it did: 510(k) (either route) is a moderate, well-trodden pathway relative to De Novo (De Novo classification request)/PMA, with real predicates to cite — claims 1-3, 10. But revenue depends on standing up an RPM billing/compliance operation and clinician adoption, which is…the rest of this reasoning
unverified and could extend time-to-revenue substantially — claims 11, 13.
What would settle it: A device-consulting cost/timeline estimate for a comparable Class II 510(k) (paid), or a public comparable's S-1/10-K R&D disclosures (free).
Why it scored what it did: At least 5 Class II connected/electronic peak-flow-meter or spirometer devices with pediatric home-use indications cleared 2018-2023 (K180487, K183479, K200832, K203196, K230423) — claim 10verified — indicating a moderately crowded hardware space,…the rest of this reasoning
even if the specific RPM-billed persistent-asthma positioning is narrower.
What would settle it: An openFDA 510(k) pull for recently cleared connected peak-flow/spirometer devices, plus a Crunchbase/Pitchbook raise search — Pitchbook is paid.
Why it scored what it did: No claim in the file speaks to portfolio fit — nothing to base even a triage guess on; left blank rather than invented.
What would settle it: An internal portfolio inventory (not a public source) showing where this would sit relative to current hero bets vs. cash-generative spokes.
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-014 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.
No claim on this idea has been refuted.
a PATENTSVIEW-backed patent search for claims covering connected peak-flow/spirometry devices combined with RPM-eligible data transmission and asthma-action-plan-threshold alerting logic (Scores table, FTO/IP row) — FTO is one of only four factors the Stage 5 gate depends on and is currently entirely unexamined (no PATENTSVIEW_API_KEY set in this environment), a keyword landscape search is comparatively cheap next to the CMS-file and CDC-table work already done for other factors, and a single finding here (a live blocking patent) is the one result that could kill this candidate outright regardless of every other score.
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.
Re-run 2026-08-31, second pass — supersedes the first pass's queued-research result (4/9 factors) now that a research + verification round brought the file to 6/9 factors, meeting the rubric's threshold for a genuine gate verdict.
wrapped pending
Stage 6 human shortlist review — clearing the gate is not an approval and does not imply
the idea is good, only that no verified evidence yet says it should be killed.
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-014 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-014 adds it.
Click any step to see what it holds for this idea. donecurrentloopinghuman only
## Wrap section, as writtenThe packet a human reads. See docs/wrap-spec.md. This section says nothing about whether the idea is good — it says the file is finished enough to be read, and names what to do next. Filling it in advances no candidate and approves nothing.
The one-paragraph version. This is a small handheld device, connected by Bluetooth to a phone app, that a child with persistent asthma (ages 5-17) would use at home once a day: it measures how well their lungs are working (peak flow / FEV1) and asks a few questions about symptoms and whether they took their medication, then sends all of it to their prescribing doctor. It would be sold by prescription only, not over the counter, specifically so the doctor's practice can bill Medicare-style monitoring codes for reviewing that data between office visits — that billing angle, not new hardware, is the whole idea. The underlying measurement technology already exists in several FDA-cleared devices; what doesn't yet exist is a device positioned this way, for this population, tied this explicitly to between-visit billing.
What would have to be true. One line per lens, quoted verbatim from that deck's load-bearing condition. Do not summarise or re-rank them.
device_class field
itself states neither has been confirmed by a classification lookup."
Cheapest next test: a PATENTSVIEW-backed patent search for claims covering connected peak-flow/spirometry devices combined with RPM-eligible data transmission and asthma-action-plan-threshold alerting logic (Scores table, FTO/IP row) — FTO is one of only four factors the Stage 5 gate depends on and is currently entirely unexamined (no PATENTSVIEW_API_KEY set in this environment), a keyword landscape search is comparatively cheap next to the CMS-file and CDC-table work already done for other factors, and a single finding here (a live blocking patent) is the one result that could kill this candidate outright regardless of every other score.
Where the evidence actually stands. Per wrap_status.py: 8 of 9 rubric factors carry either a score or a named evidence gap (Strategic fit is the one factor with no claim speaking to it at all, verified or otherwise); all 4 of the 4 gate-relevant core factors (Regulatory, Reimbursement, TAM, FTO/IP) are accounted for, though FTO/IP is accounted for by being explicitly named as unexamined, not resolved. Of 31 claims total: 14 verified, 11 unconfirmed, 6 unverified (the decks' own unbacked-assumption write-backs, claims 26-31). Two things are blocked on tooling, not on a finding, and should not be read as evidence against the idea: (1) FTO/IP — no PATENTSVIEW_API_KEY/EPO OPS credentials are configured in this environment, so "unexamined" means literally that, not "searched and clear"; (2) the hcpcs/payment/coverage connectors still return unconfirmed for the RPM CPT codes because this repo has no local rate-cache file — the actual CMS payment amounts were instead retrieved directly from CMS's own CY2026 PFS National Payment Amount File by the research lane and are verified (claims 16-18), so this is a stale connector gap, not an open question. Set against that: the strongest verified evidence in the file (Regulatory, Reimbursement, Mechanism) all rests on primary sources fetched directly (openFDA, CMS, peer-reviewed literature, ClinicalTrials.gov) rather than vendor-blog or web-search summaries — a materially stronger evidentiary base than the candidate started with at Stage 2.
| Factor | Score | Why | What would settle it |
|---|---|---|---|
| Regulatory pathway | 3 | Two plausible Class II 510(k) routes, both from real-looking predicates (K183479 combined-function; K200832/K230423 bare peak-flow) — claims 1-3. Neither product code/CFR pairing nor which route applies has been confirmed against a primary…the rest of this reasoningFDA record; the BZH product code is itself read off a third-party search-tool URL, not FDA. | openFDA classification lookup (BZG, BZH) plus the K183479 510(k) summary PDF — both free, effectively immediate to pull. |
| Reimbursement pathway | 2 | CPT 99453/99454/99457 rates quoted from RPM-billing vendor blogs, not the CMS fee schedule itself — claims 4-6. CMS's device-must-meet-FDA-definition-and-chronic-condition-management requirement is stated only as the Generator's own…the rest of this reasoningreading of vendor-blog content, explicitly flagged as a design assumption — claim 11unconfirmed. No coverage policy or payer precedent identified; codes existing is not the same as a payer paying for this specific device/indication. | CMS Physician Fee Schedule Look-Up Tool (free) for the three CPT rates, plus an LCD/NCD/payer-policy search for pediatric RPM coverage — a few hours' work. |
| TAM | 2 | Population figure (4.8M children, "current asthma," 2023) is all-severity, not the persistent-asthma subgroup this candidate targets — claim 7unconfirmed. Price ($99/mo) is Generator arithmetic built entirely on the unverified CPT-rate claims above —…the rest of this reasoningclaim 8unconfirmed. Addressable-share (30-40% persistent) is an explicit unsourced Generator guess — claim 9unconfirmed. All three TAM legs are unverified and the population leg doesn't even match the stated target population yet. | Primary CDC/NHIS prevalence table (free) plus a claims/registry-based RPM-enrollment estimate (likely a licensed report) for population and addressable share. |
| FTO / IP | 2 | No patent or FTO search was performed at all — stated explicitly as an open gap, not a finding either way (claim 12unconfirmed). Predicate hardware (electronic peak-flow meters, digital spirometers) has existed since the mid-2010s, which is mildly…the rest of this reasoningreassuring for the base hardware, but the specific combination (continuous RPM billing + action-plan-threshold alerting algorithm) is entirely unexamined. | A PatentsView keyword search on peak-flow/RPM/alerting-logic claims — free API, a few hours' work. |
| Moat / defensibility | 2 | The differentiation is an indication-scope/billing-eligibility lever (prescription-only, chronic-management framing to qualify for RPM CPT codes) rather than a technical one — see "Indication-scope note." Once public, any of the 5+…the rest of this reasoningexisting 510(k) holders for connected peak-flow/spirometer hardware (claim 10verified) could copy the same narrowing move with comparable hardware. | An openFDA/market search for other prescription-only, RPM-billed pediatric-asthma monitors already marketed or pipelined — free, a few hours. |
| Mechanism & clinical risk | 4 | Peak-flow/spirometry measurement is a decades-old, well-characterized mechanism with multiple existing 510(k)-cleared home-use predicates in the same pediatric age range (claims 1, 2, 10). No novel biological or device-accuracy mechanism…the rest of this reasoningis being proposed — the novelty is in billing/indication scope, not measurement physiology. | Published PubMed literature comparing home vs. clinic-grade spirometry accuracy in the 5-17 age range — a free literature search. |
| Capital intensity & time-to-revenue | 3 | 510(k) (either route) is a moderate, well-trodden pathway relative to De Novo/PMA, with real predicates to cite — claims 1-3, 10. But revenue depends on standing up an RPM billing/compliance operation and clinician adoption, which is…the rest of this reasoningunverified and could extend time-to-revenue substantially — claims 11, 13. | A device-consulting cost/timeline estimate for a comparable Class II 510(k) (paid), or a public comparable's S-1/10-K R&D disclosures (free). |
| Competitive intensity | 2 | At least 5 Class II connected/electronic peak-flow-meter or spirometer devices with pediatric home-use indications cleared 2018-2023 (K180487, K183479, K200832, K203196, K230423) — claim 10verified — indicating a moderately crowded hardware space,…the rest of this reasoningeven if the specific RPM-billed persistent-asthma positioning is narrower. | An openFDA 510(k) pull for recently cleared connected peak-flow/spirometer devices, plus a Crunchbase/Pitchbook raise search — Pitchbook is paid. |
| Strategic fit & portfolio balance | — | No claim in the file speaks to portfolio fit — nothing to base even a triage guess on; left blank rather than invented. | An internal portfolio inventory (not a public source) showing where this would sit relative to current hero bets vs. cash-generative spokes. |
All eight wrap criteria are met.
Source file: knowledge-base/candidates/idea-014.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