Prescription-only, Bluetooth-connected home peak-flow/spirometry monitor with symptom-and-medication tracking for pediatric persistent asthma, billed under the RPM CPT code family — business case

Intended use: 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.

Who pays

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.

• Writes the cheque (device): the prescribing practice — pediatrician, pediatric pulmonologist, or allergist — is the entity that orders the device under this prescription-only intended use and the entity CPT 99454 pays for "device supply," which is what makes the practice, not the family, the natural first buyer of the hardware. No claim in the candidate file names who actually sells or leases the unit to the practice (manufacturer direct, a distributor, or a bundled RPM-platform vendor) — that link is unresolved, and adoption returns unverifiable on any claim about which entity would actually stock it (see below).
• Writes the cheque (RPM service): not Medicare — the target population is ages 5-17. Whether 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 Physician Fee Schedule amounts is stated as an explicit, unverified proposition claim 28unverified — no payer of record for this population and indication has been identified anywhere in the file.
• Out of which budget line: on the payer side, the practice's own Physician Fee Schedule billing revenue under CPT 99453/99454/99457, whose CY2026 non-facility amounts are verified directly from CMS (Centers for Medicare & Medicaid Services)'s own published file claim 16verified, claim 17verified, claim 18verified. On the practice side, whether the device is purchased from a capital equipment budget, a per-patient supply budget, or a bundled RPM-platform subscription is not established anywhere in the file.
• Against which comparator: in-office spirometry and periodic asthma action-plan review at scheduled visits — the standard-of-care pathway the intended use frames this device as an "adjunct to," not a replacement for.
• Stops buying instead: nothing named — the intended use explicitly frames the device as additive spend layered onto guideline-directed management, not a substitute for existing office visits, emergency care, or in-office spirometry. Whether the RPM billing revenue itself displaces anything in a practice's existing budget is not addressed in the file.

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.

The money model

Decomposed, not asserted. Every line resolves to a copied claim or a declared assumption.

Read the largest figure first. It is the addressable population (~2.9 million) [assumption A1], and even taking it at face value, no claim or assumption in this case establishes what fraction of it a prescriber would ever enroll [assumption A3], let alone what fraction this specific device would capture against roughly 38 existing competing hardware clearances claim 21verified, [assumption A4].

The two connectors that would ordinarily carry a business case both refuse, and the verdicts go on the page rather than being routed around:

• python3 -m connectors market "US home RPM peak-flow/spirometry monitoring for pediatric persistent asthma represents an addressable market of 4.8M children with current asthma x 60.3% persistent share x CMS RPM payment rates for 99453/99454/99457" → unverifiable — "Market-size claim (...) has no free, authoritative, machine-queryable source. Stays unconfirmed permanently unless a human attaches a licensed report and edits the claim by hand."
• python3 -m connectors adoption "Pediatricians, pediatric pulmonologists, and allergists will prescribe and bill for this RPM peak-flow/spirometry monitor for persistent pediatric asthma patients rather than relying on in-office spirometry and periodic action-plan review" → unverifiable — "Adoption/preference claim (...) asserts what clinicians, payers, or patients would do. No free, authoritative, machine-queryable source answers that — it needs primary research... Do NOT substitute a model's own estimate of stakeholder behaviour: a synthetic stakeholder opinion is a fabricated claim."

The payment/coverage/hcpcs connectors were re-run this pass and return the same missing-cache result the candidate file already records — payment 99454 returns "No local cache at data/hcpcs_payment_rates.csv", coverage 99457 returns "No local cache at data/medicare_coverage_policies.csv", and hcpcs 99454 returns "No local cache at data/hcpcs_level_ii.csv" — all unconfirmed, all a missing local cache, not a wrong number found. The CMS rates used above claim 16verified, claim 17verified, claim 18verified were instead confirmed by a direct fetch of CMS's own CY2026 PFS (physician fee schedule) National Payment Amount File, per the candidate file.

Path to first revenue

• First dollar comes from: the first prescribing practice that acquires the device, enrolls a patient, and completes a billing cycle — starting with a one-time CPT 99453 claim claim 16verified and only reaching CPT 99454 claim 17verified once at least 16 of 30 days of readings exist claim 14unconfirmed. This is a billing event at the practice, not a device sale to a family.
• What must exist first, each attributed:
  • FDA clearance under whichever of the two candidate-identified 510(k) (premarket notification) routes actually governs this device — the combined-function route via 21 CFR (Title 21 of the Code of Federal Regulations) 868.1840/BZG, K183479 (an FDA 510(k) clearance number) predicate claim 1verified, or the bare-hardware-plus-accessory-software route via 21 CFR 868.1860/BZH, K200832 claim 2unconfirmed or K230423 predicates claim 3verified — the candidate's own device_class field states neither route has been confirmed by a classification lookup.
  • A prescriber willing to order it under a prescription-only, chronic-disease-management framing rather than treating in-office spirometry as sufficient claim 13unconfirmed.
  • Enough patient/parent adherence to actually clear 99454's 16-of-30-day threshold claim 14unconfirmed.
  • A non-Medicare payer of record reimbursing at rates comparable to the verified CMS non-facility amounts claim 28unverified — CMS's own general eligibility criteria claim 15verified set a floor but do not establish that any specific Medicaid program or commercial plan applies it to this device or indication.
  • Measurement accuracy in this candidate's own hardware, in its own 5-17 age range, comparable to what a different app-based spirometer (VitalFlo) demonstrated against a clinic-grade comparator in adolescents claim 24verified — that claim is about VitalFlo, not this device; the proposition that this candidate's own hardware performs comparably is a separate, unverified claim claim 29unverified.
  • An alerting algorithm with clinically acceptable sensitivity/specificity for exacerbation risk against a patient-specific action-plan threshold claim 30unverified.
  • A data pathway into the practice's RPM/EHR workflow meeting FDA cybersecurity and software-documentation requirements claim 31unverified.
  • An FTO (freedom to operate) position — entirely unexamined, not merely unconfirmed claim 12unconfirmed.
• Calendar to first dollar: not established anywhere in the file — no cost or timeline estimate for either candidate 510(k) route exists in the claims [assumption A8].
• Capital to first dollar: not established anywhere in the file [assumption A9].
• Lag from first patient enrollment to first paid claim — payer enrollment, prior authorization, and the 30-day data-collection window CPT 99454 itself requires — not established [assumption A7].

Routes

Four, laid out and not ranked. Choosing a commercial strategy is a Tier 3 act — the same class of decision as choosing what to shortlist — so this section presents options and stops.

Route A — Sell or lease the device directly to prescribing practices, who bill the RPM CPT codes themselves

The model the candidate's own mechanism already describes: a device manufacturer selling hardware into pediatric/pulmonology/allergy practices, which order it under prescription, supply it to patients, and bill CPT 99453/99454/99457 against it.

• Requires: FDA clearance under whichever route governs claim 1verified / claim 3verified, pending route confirmation; a prescriber willing to order and bill it claim 13unconfirmed; sufficient patient/parent adherence to clear 99454's threshold claim 14unconfirmed; and a non-Medicare payer actually reimbursing the codes for this population claim 28unverified.
• Costs: calendar to clearance [assumption A8]; capital to clearance and first sale [assumption A9]; a device price the practice will actually pay [assumption A2]; and a practice margin that survives its own billing-compliance overhead [assumption A5].
• Killed by: claim 28unverified resolving false — no Medicaid program or commercial plan pays these codes for pediatric home RPM at rates comparable to the verified CMS non-facility amounts. Without an identified non-Medicare payer, a practice has nothing to bill for the large majority of this population, and this route has no fallback revenue source if that finding holds.

Route B — License the hardware-plus-alerting module into an existing RPM-platform vendor's chronic-care bundle

Ship the differentiator, not the device: an OEM peak-flow/spirometer-plus-action-plan-alerting module licensed into a platform that already runs RPM billing operations for some other pediatric chronic condition, rather than selling a standalone product into a crowded hardware field of roughly 38 existing connected peak-flow/spirometer clearances claim 21verified.

• Requires: the alerting algorithm achieving clinically acceptable sensitivity/specificity claim 30unverified; measurement accuracy in this candidate's own hardware and age range claim 29unverified; an FTO position, entirely unexamined claim 12unconfirmed; and a partner platform willing to carry the module.
• Costs: regulatory scoping for whichever submission route a licensed module needs [assumption A8]; module validation folded into the same capital estimate [assumption A9]. Revenue becomes a royalty or transfer price, so the device-price and margin assumptions in Route A (A2, A6) are replaced rather than resolved.
• Killed by: the candidate's own indication-scope differentiator — a prescription-only, chronic-management framing tied to RPM billing eligibility, as described in the candidate's own "Indication-scope note" — turning out to be trivially replicable by any of the roughly 38 already-cleared connected peak-flow/spirometer manufacturers claim 10verified, claim 21verified, leaving no module differentiated enough for a partner to pay for rather than build in-house.

Route C — Contract with health systems on an exacerbation/ED-avoidance budget line, not per-patient RPM billing revenue

Bypass RPM billing as the primary revenue source: sell into a health system's or integrated delivery network's cost-avoidance budget, where the case is fewer exacerbations, emergency-department visits, or hospitalizations, not a device-supply fee.

• Requires: a finding that enrolling a patient in this program reduces exacerbations, ED visits, or hospitalizations relative to standard in-office spirometry and periodic review claim 27unverified — the premise the whole route stands on; and the $3,362.56/year incremental treated-pediatric-asthma medical-expenditure gap claim 25verified being concentrated enough in avoidable acute events to fund a per-enrolled-patient contract price.
• Costs: a comparative outcomes study scoped to this candidate's own target population [assumption A9], on top of the same clearance calendar as Route A [assumption A8].
• Killed by: claim 27unverified resolving false — a comparative study, or the nearest available revealed-behaviour twin, finding no reduction in exacerbations, ED visits, or hospitalizations attributable to the program. The two closest actual attempts at this kind of pediatric home-RPM-asthma program are an industry-sponsored study withdrawn before enrolling any participants, stated reason "refocus of business" claim 19verified, and an academic pilot terminated after enrolling 12, stated reason "staffing issues with partner site" claim 20verified. Neither reason is a clinical-outcome failure, so neither counts as evidence against this route's premise — but neither is evidence for it either, and a health system underwriting this route would be doing so with no US outcomes data on record either way.

Route D — Launch on the combined-function 510(k) route only, and defer the bare-hardware/accessory-software route

Narrow the regulatory scope at launch rather than pursuing both candidate-identified routes in parallel: commit to the combined spirometer-plus-questionnaire device (K183479 predicate) as the only version sold, and treat the bare-peak-flow-meter-plus-accessory-software route as a later question.

• Requires: confirmation that the combined-function predicate governs this device claim 1verified rather than the bare-peak-flow-meter route claim 2unconfirmed / claim 3verified — the device_class field itself states this is unconfirmed; and acceptance of the narrower device scope as the only version sold at launch.
• Costs: a single regulatory submission calendar and capital estimate rather than two parallel ones [assumption A8], [assumption A9] — narrower by design, at the cost of forgoing the bare-hardware/accessory-software route if it would in fact have been the cheaper path.
• Killed by: an FDA classification lookup, or a direct read of the K183479 510(k) summary, finding that the combined-function route does not actually cover this device's intended use — for example, if FDA reads the RPM-alerting/threshold-flagging function as exceeding what the questionnaire predicate covers. This is the same open finding the candidate's own device_class field names as unresolved.

Assumption register

Every assumption cited above, with what would settle it and who could run it. These are written back to the candidate as unverified claims 32-40 — an assumption that lives only in a business case is invisible to the Verifier.

Where this case outruns the file

Every figure with no claim behind it, gathered as work items.

• The addressable persistent-pediatric-asthma population (~2.9 million) — a product of one unconfirmed web-search figure and one verified but nearly two-decade-old severity split, multiplied across surveys the file never establishes are commensurable (A1).
• The recurring per-patient reimbursement figure (~$107.63/month) — real, verified CMS rates, but with no claim or assumption in the file establishing what fraction of enrolled patients ever bill at the non-facility mean rather than a lower facility rate or a denied claim.
• Any real device price, practice cost, or margin figure (A2, A5, A6) — nothing in the candidate file speaks to the device P&L on either side of the transaction.
• Whether any prescriber enrolls anyone at all into RPM billing for this population today (A3), and whether this device in particular would win any of that enrollment against ~38 cleared competitors (A4) — the file establishes the competitor count and the CMS rate; it establishes nothing about actual enrollment behavior.
• Calendar and capital to first dollar (A7, A8, A9) — unlike some other candidates in this repo, no claim in this file offers even an unconfirmed cost/timeline estimate for either 510(k) route; both are silent, not merely unconfirmed.
• Whether a non-Medicare payer reimburses these codes for this population at all claim 28unverified — the single largest open question in the money model, since the target population is almost entirely outside Medicare FFS (fee-for-service) and no state Medicaid or commercial payer coverage policy for this specific indication has been identified.