idea-014 · viability deck
Every slide states a condition that would have to be true, then reports where it stands using the candidate file's own claim and its own confidence tag. A deck never upgrades a tag, invents a number, or recommends anything, and there is no ask slide.
The chair: the investor, and the operator who would have to stand up an RPM billing operation and make the CPT-code revenue actually arrive.
How to read this: every slide is a condition, not a conclusion. A bracketed claim reference points into knowledge-base/candidates/idea-014.md — the number is the claim's position in its ## Claims list, the tag is copied from it and never adjusted here. A [no claim] marker means nothing in the file speaks to this. No number appears here that is not in a claim, and there is no ask slide. See docs/deck-spec.md.
First build. At stage: verified, this candidate is cleared at Stage 5 with 6/9 factors verified, including Reimbursement (3/5) — the strongest evidence base of the three lenses, built almost entirely on a direct read of CMS's own CY2026 fee schedule file. This deck's job is to show what that verified evidence does, and does not, establish.
Would have to be true: A specific payer, from a specific budget line, would have to pay for this device and the RPM services around it — and, because this candidate's patients are children ages 5-17, that budget line has to be one children actually have access to.
Where it stands: Every verified reimbursement claim in this file is Medicare-sourced. CMS's own RPM coverage page confirms the general national eligibility criteria — a chronic or acute condition requiring monitoring, a device meeting FDA's medical-device definition, data transmitted at least 2 days per 30 [claim 15: verified]. CMS's CY2026 Physician Fee Schedule National Payment Amount File gives real non-facility payment amounts: 99453 mean $22.53 ($18.42-$30.70 across 109 localities) [claim 16: verified], 99454 mean $54.32 ($44.64-$74.83) [claim 17: verified], 99457 mean $53.31 non-facility / $26.81 facility ($46.88-$66.68 / $25.08-$36.28) [claim 18: verified]. But Medicare is a program for people 65+ or with qualifying disabilities — the file's own TAM analysis notes this candidate's target population is "pediatric (ages 5-17), essentially outside Medicare FFS" [claim 7: unconfirmed]. No claim in the file states that Medicaid (the payer that actually covers most lower-income children) or a commercial health plan (the payer that covers most other children) reimburses these same three codes at comparable rates for a pediatric patient. Formalized in this deck's write-back rather than left silently assumed: a state Medicaid program or commercial health plan reimburses CPT 99453/99454/99457 for pediatric RPM at rates comparable to the verified CY2026 Medicare non-facility amounts [claim 28: unverified]. The family's own out-of-pocket share of whatever rate applies is the desirability deck's Slide 4, referenced rather than restated here.
What would settle it: A state-by-state Medicaid fee-schedule lookup for CPT 99453/99454/99457, and a search for named commercial-payer coverage policies addressing home RPM for pediatric asthma — the Scores table's own "what would settle it" for Reimbursement names exactly this gap.
If it's false: Every dollar figure verified in this file describes a payer that mostly does not cover this candidate's own patient population, and the revenue side of the business has to be re-derived against a payer this file has not yet examined at all.
Would have to be true: Code existence, payment amount, and coverage policy would all have to land favorably, and — distinct from all three, and the subject of Slide 1 — the payer landing on them has to be one that actually serves children.
Where it stands:
coverage connector returns
unconfirmed for lack of a local cache, the same structural gap documented for claims 4 and 6
[claim 5: unconfirmed]. Sustained daily use is itself a coverage precondition for 99454's
16-of-30-day threshold — see the desirability deck's Slide 2 and load-bearing condition,
referenced rather than restated here [claim 14: unconfirmed].
What would settle it: Populating data/hcpcs_payment_rates.csv and data/medicare_coverage_policies.csv from a real CMS release (a named Scout task in the file); a Federal Register policy lookup against the specific PFS final-rule document that states the device-definition/chronic-condition requirement, rather than a CFR text search.
If it's false: A code that exists and a rate that is published are necessary but not sufficient — this candidate could clear both and still have no payer willing to pay them for this specific device and indication.
Would have to be true: Population × persistent-severity rate × price × reachable share would all have to be named, so the total is checkable rather than a single headline figure.
Where it stands:
What would settle it: A primary CDC/NHIS table matching claim 7's 2023 vintage to a persistent-vs-intermittent breakout; the Medicaid/commercial rate lookup from Slide 1, which would also resolve the price leg's payer-applicability question.
If it's false: TAM below floor (2/5) is a hard kill condition in this rubric. It is currently scored at the floor, not below it — but two of four decomposed legs above rest on unconfirmed claims and one has no claim at all, so "at the floor" measures what has been checked, not what the true addressable market is.
Would have to be true: Whichever 510(k) route governs — combined-function (BZG) or bare-hardware-plus-accessory-software (BZH) — plus standing up an RPM billing/compliance operation, would have to reach commercial revenue on capital and a timeline this deck could name.
Where it stands: No cost or calendar-time claim exists anywhere in the file — the Scores table records this factor's own gap analysis rather than a guess, and this deck does not improve on it [no claim]. What is checkable is that the regulatory route itself is unresolved between two real predicates ([claim 1: verified], [claim 2: unconfirmed], [claim 3: verified]), each with different combined-vs-accessory testing implications — see the feasibility deck's Slide 3 for the full read, referenced rather than duplicated here. Two commercial-operations claims speak to the revenue-standup side specifically and remain unresolved: whether this device/indication actually satisfies CMS's general eligibility criteria [claim 11: unconfirmed], and whether prescribers will actually order and bill it — see the desirability deck's Slide 3 [claim 13: unconfirmed].
What would settle it: An FDA pre-submission (Q-sub) to resolve the regulatory pathway question; a cost/timeline benchmark for a comparable Class II connected-respiratory-device 510(k) submission — the Scores table's own named gap for this factor.
If it's false: If the combined-function (BZG) route governs and requires the full symptom/medication-questionnaire software to be validated as part of one submission rather than as separable accessory software, the build and evidence burden — and therefore the capital and timeline — is materially larger than the bare-hardware route implies.
Would have to be true: Something beyond the measurement hardware itself — a patent position, a data or workflow lock-in, a coding requirement a competitor can't meet — would have to keep a fast-follower from copying the prescription-only, RPM-billed positioning once it is public.
Where it stands: The file's own framing names the differentiation as a billing/ indication-scope lever, not a technical one: narrowing intended use to a prescription-only, chronic-disease-management claim, rather than any hardware advantage. That framing cuts against defensibility rather than for it — the underlying hardware space is confirmed crowded: 24 distinct BZG-coded and 14 distinct BZH-coded 510(k) clearances in the 2016-2026 window, spanning roughly 30 distinct applicants [claim 21: verified], any of whom could adopt the same prescription-only, chronic-management framing with comparable hardware. Freedom to operate is the sharper version of the question and belongs to the feasibility deck's Slide 7, referenced rather than duplicated here: no patent or FTO search has been performed for the specific combination of continuous RPM billing plus an action-plan-threshold alerting algorithm [claim 12: unconfirmed].
What would settle it: A search for other prescription-only, RPM-billed pediatric-asthma monitors already marketed or in the FDA pipeline, to see how contested this exact positioning already is — the Scores table's own named gap for Moat/defensibility.
If it's false: A device this file itself frames as differentiated mainly by billing eligibility rather than by technology or IP is exactly the shape a fast-follower among the roughly 30 existing applicants can replicate cheaply.
Would have to be true: The field would have to be open enough, or this candidate's prescription-only RPM-billed positioning distinct enough from existing players and prior attempts, for a new entrant to have room.
Where it stands: The hardware field is confirmed crowded — 24 BZG-coded and 14 BZH-coded 510(k) clearances, roughly 30 distinct applicants, 2016-2026 [claim 21: verified]. The specific RPM-billed pediatric-persistent-asthma positioning, though, has two recent, independent, and unsuccessful attempts on record: a Philips-sponsored pediatric home-asthma RPM study (ALPACA, ages 4-11, moderate-to-severe asthma) was withdrawn before enrolling any participants, sponsor's stated reason "refocus of business" [claim 19: verified]; a Weill Cornell pilot of remote asthma-medication monitoring (ages 3-21, persistent asthma) was terminated after enrolling 12 of its intended participants, reason "Staffing issues with partner site" [claim 20: verified]. Both stopped for operational reasons rather than an efficacy finding against the concept — so the positioning is untested rather than actively contested, but "nobody has done it" is not a claim this file can make either.
What would settle it: A funding-database (Crunchbase/Pitchbook) search for recent raises or launches in this specific niche; a check of whether either terminated study's underlying protocol or data was ever published or licensed.
If it's false: If either abandoned attempt in fact reflected a hard efficacy or adoption finding rather than a staffing/business-refocus reason, this candidate is walking into ground already tested and found wanting rather than genuinely open ground.
Would have to be true: There would have to be one piece of evidence, cheap to obtain, that moves the most claims off unconfirmed at once.
Where it stands: Two candidates, neither attempted. The Medicaid/commercial payer-rate question (Slide 1) is a lookup against public state fee schedules and payer policy documents — cheap, and it resolves the single largest unexamined gap in an otherwise well-evidenced factor. The TAM population leg [claim 7: unconfirmed] needs a primary CDC/NHIS table rather than a web-search summary — the Verified Composite section names this as the most consequential remaining TAM gap.
What would settle it: A state Medicaid fee-schedule lookup for CPT 99453/99454/99457 across several representative states, plus a check for any named commercial-payer RPM coverage policy; a primary CDC/NHIS pediatric-asthma prevalence table for claim 7.
If it's false: Nothing here is false — this slide is a work order, not a finding.
Every condition above with nothing verified behind it — the [no claim] markers, plus the unverified claims this deck itself put on record. Read this slide first.
Structural note: this is the best-evidenced of the three lenses — four verified claims (15-18) rest on a direct read of CMS's own CY2026 fee-schedule file, not a vendor blog. That evidence establishes a code, a rate, and general coverage criteria; it does not establish that the payer it describes serves this candidate's own patient population, which is this deck's load-bearing condition.
If only one thing from this chair could be checked: 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 [claim 28: unverified].
Every verified reimbursement claim in this file (claims 15-18) describes Medicare, a program that generally does not cover children — the file's own TAM note calls the target population "essentially outside Medicare FFS" [claim 7: unconfirmed]. This candidate's Reimbursement factor scored 3/5 verified, the strongest evidence base of any factor in the file, and that evidence answers a question adjacent to, but not identical with, the one that actually decides whether money arrives. Until this resolves, every dollar figure on this deck — the TAM price leg (Slide 3), the family's out-of-pocket share (desirability deck Slide 4) — is priced off a payer that may not be the one paying.
Naming it is not a recommendation, a gate, or a kill.