idea-014 · narrative
A synthesis across this candidate's claims, dossier and decks — every statement here traces to something that already exists elsewhere in the knowledge base. A narrative never invents a fact, upgrades a tag, or recommends anything.
How to read this. This is a synthesis, not a new source of truth: every claim it cites carries the tag the candidate file gives it right now, copied not paraphrased, and every line quoted from a deck is quoted verbatim. See docs/narrative-spec.md.
This is a handheld, Bluetooth-connected peak-flow meter and/or spirometer, paired with a smartphone app, meant for children and adolescents ages 5-17 with physician-diagnosed persistent asthma: it logs daily lung-function readings and a symptom/medication-adherence questionnaire and sends the combined record to the prescribing clinician for review between visits [claim 1: verified]. The underlying measurement hardware is not novel — it sits inside a crowded field of at least 24 distinct BZG-coded and 14 distinct BZH-coded Class II 510(k)-cleared connected peak-flow/spirometer devices [claim 21: verified] — and the candidate's own stated differentiator is not the hardware but a narrower, prescription-only indication scope designed to qualify for RPM CPT billing (99453/99454/99457). A research and verification round replaced the file's earlier vendor-blog reimbursement estimates with a direct read of CMS's own CY2026 Physician Fee Schedule and CMS's own RPM coverage page [claim 15: verified] [claim 16: verified] [claim 17: verified] [claim 18: verified], and added a peer-reviewed accuracy study for an adjacent (not this candidate's own) home spirometer [claim 24: verified], bringing the candidate to 6/9 factors verified and wrapped. Since that pass, a business-case pass added nine further claims naming the specific commercial-economics preconditions — device pricing, RPM enrollment share, cost-to-serve margin, and the capital and calendar time to reach FDA clearance and a first commercial sale — that would have to hold for a standalone device business, none of them yet evidenced [claim 33: unverified] [claim 34: unverified] [claim 35: unverified] [claim 36: unverified] [claim 37: unverified] [claim 38: unverified] [claim 39: unverified] [claim 40: unverified]. Which 510(k) route governs the device, whether any payer that actually covers children pays the verified Medicare-level rates, and whether families sustain the daily routine RPM billing requires all remain open.
The problem this candidate targets is chronic, between-visit blindness in pediatric persistent asthma management: a physician writes an asthma action plan at a clinic visit, and nothing tells that physician whether the plan is holding until the next visit or an exacerbation forces one. The mechanism is not new instrumentation — home peak-flow meters and connected spirometers have existed for years, and 24 distinct BZG-coded (diagnostic spirometer) and 14 distinct BZH-coded (peak-flow meter) Class II 510(k)s were cleared 2016-2026 [claim 21: verified] — but a specific combination: prescription-only, tied explicitly to a physician's action plan, in a population (persistent, not intermittent, asthma) sick enough to justify RPM billing. The candidate file states this plainly as a design rationale, not a finding: the lever is indication-scope narrowing to make the device RPM-billable, not new hardware. Why now is not sourced to any seed in this file — seeds: is empty in the frontmatter — so no "why now" macro-trend context applies here.
What has been checked, and changed materially through the research and verification round: the closest functional predicate, the "Asthma Monitor AM3 G+" (K183479), is confirmed a real Class II 510(k), 21 CFR 868.1840, product code BZG, combined lung-function-plus-questionnaire device for home and clinical use, children 5+ [claim 1: verified]; the bare peak-flow-meter classification (21 CFR 868.1860, product code BZH) is also confirmed real and Class II directly from openFDA [claim 3: verified]. Which of the two routes actually governs this device remains unconfirmed — the candidate's own device_class frontmatter field says so explicitly, and the specific bare-hardware predicate, K200832, remains unconfirmed on the details that matter (OTC-vs-Rx status, age claim, its own predicate chain) because FDA's PDF summary returns HTTP 401 [claim 2: unconfirmed]. On reimbursement, a research pass replaced vendor-blog rate guesses with a direct fetch and parse of CMS's own CY2026 Physician Fee Schedule National Payment Amount File, giving real non-facility payment ranges for all three RPM codes across the 109 Medicare payment localities [claim 16: verified] [claim 17: verified] [claim 18: verified], and CMS's own RPM coverage page confirms the general national eligibility criteria (chronic-or- acute condition, a device meeting FDA's medical-device definition, data transmitted at least 2 days per 30) [claim 15: verified]. What that evidence does not establish is that a payer who actually covers children ever pays these rates for this indication [claim 28: unverified], or that this specific device/indication satisfies CMS's general criteria "in a way that a general-wellness OTC peak-flow app would not" [claim 11: unconfirmed]. On clinical mechanism, a peer-reviewed validation study found an app-based home spirometer (VitalFlo, not this candidate's own hardware) had no statistically significant difference in mean FEV1 versus a clinic-grade comparator in 48 adolescents with persistent asthma [claim 24: verified] — favorable analog evidence, not evidence about this candidate's own unbuilt device [claim 29: unverified]. Two independent attempts to run something like this program in practice — a Philips-sponsored trial and a Weill Cornell pilot — both ended before producing outcome data, for stated operational rather than efficacy reasons [claim 19: verified] [claim 20: verified]. What remains almost entirely unchecked at the clinical/behavioral layer: whether families sustain the daily maneuver-plus-questionnaire routine at the 16-of-30-day threshold CPT 99454 requires [claim 14: unconfirmed], whether prescribers actually order and bill it [claim 13: unconfirmed], and whether a live patent blocks the specific RPM-billing-plus-alerting-algorithm combination — genuinely unexamined, not searched and found clear [claim 12: unconfirmed].
A separate, later pass added a business case to the candidate file. It names nine further preconditions, none evidenced by any claim gathered so far, that would have to hold for a standalone device business rather than merely a cleared, billable device: whether the 2023 CDC population figure and the 2006-2010 BRFSS-derived 60.3% persistent-severity share are commensurable enough to multiply into a current addressable-population estimate despite the roughly 15-17-year gap between the two surveys [claim 32: unverified]; whether a prescribing practice would pay a device acquisition or lease price high enough to support a standalone device business [claim 33: unverified]; whether any material share of the addressable population is currently enrolled by any prescriber into RPM billing for any connected home-monitoring device [claim 34: unverified]; whether this candidate's own device would capture a defined, non-trivial share of RPM-enrolled patients by year 3 rather than one of the roughly 38 already-cleared competing devices in product codes BZG and BZH [claim 35: unverified]; whether a practice's fully-loaded per-patient cost to run the program stays below the CY2026 CMS reimbursement, leaving a margin [claim 36: unverified]; whether gross margin on the device itself, at an acquisition price a practice would actually pay, supports a standalone device business [claim 37: unverified]; whether the lag between a patient's enrollment and a practice's first paid RPM claim is short enough to finance without additional working capital [claim 38: unverified]; whether calendar time to FDA clearance, under whichever 510(k) route governs, is on the order of months rather than years [claim 39: unverified]; and whether the capital required to reach clearance plus a first commercial device sale fits a typical Class II device-startup budget [claim 40: unverified]. These nine claims postdate the three pitch decks (each built 2026-09-01, against claims 1 through 31) — none of the decks discusses them directly, though each deck's own capital-to-first-dollar and market-capture questions sit adjacent to several of them.
pypdf nor pdftotext is
installed — leaving the coverage-policy question open on a resolvable, not a structural,
gap [dossier: pediatric-persistent-asthma-home-monitoring].
All three decks are current per engine/scripts/check_decks.py — source_updated on each (2026-09-03) matches the candidate's own updated: field, and every claim reference each deck carries still agrees with the tag the candidate file gives that claim now. Each deck was built 2026-09-01, against claims 1 through 31; the nine business-case claims (32-40, added 2026-09-03) postdate all three decks, so none of them discusses the specific pricing, market-capture, or capital-timeline preconditions those claims name directly — though each deck's own "capital to first dollar" or "who is already there" questions sit adjacent to several of them, referenced below rather than restated.
The desirability deck argues from the family's and prescriber's chair that the whole chain — adherence, prescriber willingness, ability to pay — is unexamined by any connector this repo has, and names the daily-adherence threshold as the condition everything else sits downstream of: if families don't sustain 16 of 30 days, there is no valid RPM data stream regardless of what a prescriber or a payer would otherwise do.
"whether parents/guardians and school-age children with persistent asthma will actually sustain at least 16 days of home peak-flow/spirometry readings and questionnaire responses in a 30-day period" — the load-bearing condition of the desirability deck (built 2026-09-01).
The viability deck argues from the investor's and operator's chair that this file's strongest evidence — the verified CMS reimbursement figures — describes Medicare, a program that generally does not cover the 5-17 population this candidate targets, and that no claim in the file establishes what a payer that actually does cover children would pay for the same codes.
"whether a payer that actually covers children — a state Medicaid program or a commercial health plan — reimburses CPT 99453/99454/99457 for pediatric RPM at rates comparable to the verified CY2026 Medicare non-facility amounts" — the load-bearing condition of the viability deck (built 2026-09-01).
The feasibility deck argues from the engineering chair that the entire build spec — what has to be validated, and under which evidence burden — turns on a regulatory-route question the candidate's own frontmatter says is unresolved: whether the combined-function predicate or the bare-hardware-plus-accessory-software predicate governs.
"which 510(k) route actually governs this device — the combined-function route via 21 CFR 868.1840/BZG (K183479 predicate) or the bare-hardware-plus-accessory-software route via 21 CFR 868.1860/BZH (K200832 or K230423 predicates) / — since the
device_classfield itself states neither has been confirmed by a classification lookup." — the load-bearing condition of the feasibility deck (built 2026-09-01).
Where the three lenses agree: none of them treats the file's strong verified evidence (Regulatory, Reimbursement, Mechanism) as settling the question that chair actually cares about — each identifies a gap between what has been verified in general and what has been verified for this device, this population, or this payer specifically. Where they diverge is in which unresolved condition each names as decisive: desirability points at patient/family behavior, viability at payer identity, feasibility at which regulatory pathway governs the build. The desirability and viability decks also interlock explicitly — the 16-of-30-day adherence question desirability names is the same precondition viability's Slide 2 cites for CPT 99454 billing eligibility — while feasibility's regulatory-route question sits upstream of viability's own admission that it cannot price a capital-to-first-dollar timeline until that route resolves. The business-case claims added since these decks were built sit on the same fault line the viability deck already names: even a resolved payer-identity question (Slide 1) and a priced capital timeline (Slide 4) would still leave open whether a practice would actually pay for the device, whether this candidate captures share from the roughly 30 already-cleared applicants, and whether the unit economics clear a margin — none of which any deck yet addresses directly.
Every piece of primary-source evidence this file has gathered describes something adjacent to this candidate rather than this candidate itself: a payer for adults 65+, not the children this device targets [claim 28: unverified]; two live predicate routes, not a confirmed classification for this device [claim 1: verified] [claim 2: unconfirmed]; a different manufacturer's spirometer, not this candidate's own (unbuilt) hardware [claim 24: verified] [claim 29: unverified]. The business case adds a further layer of the same pattern at the commercial-economics level: a reimbursement rate that exists for Medicare, not a device acquisition price any prescribing practice has actually been asked to pay [claim 33: unverified]; a crowded hardware field of roughly 38 cleared devices, not a demonstrated share this specific device would capture from them [claim 35: unverified]. Does that gap between adjacent evidence and evidence about this candidate specifically close when each is tested directly — a Medicaid or commercial rate that matches Medicare's, a classification lookup that resolves the 510(k) route, a device that performs the way VitalFlo did, a practice that actually agrees to pay for it — or does it stay open at exactly the population, payer, hardware, and business terms this candidate actually depends on?