The 2026 Remote Care Landscape: What Changed and What It Costs You

Two forces, one year

Calendar year 2026 is a genuine inflection point for remote care delivery in the United States. Two structural forces are converging at once, and understanding them together is more important than understanding either one alone.

The first is federal. The CY 2026 Medicare Physician Fee Schedule (PFS) Final Rule, published November 5, 2025, dismantled the 16-day transmission floor and 20-minute management floor that had governed Remote Physiologic Monitoring (RPM) and Remote Therapeutic Monitoring (RTM) billing since the codes were created. In their place: a new short-duration tier that lets practices bill for monitoring episodes as short as two days.¹

The second is mandatory. The Transforming Episode Accountability Model (TEAM), effective January 1, 2026, requires selected acute care hospitals to bear full financial accountability for total cost and quality across 30-day post-surgical episodes in orthopedic and cardiovascular procedures. Readmissions are no longer a revenue event. They are a penalty.²

These two developments were not coincidental. CMS designed the new short-duration RPM codes to fit directly inside the TEAM risk window. Post-discharge monitoring that previously generated no reimbursement now generates both fee-for-service revenue and value-based risk mitigation in the same clinical act.

The alignment is deliberate and meaningful. But it runs headlong into three countervailing pressures: commercial payer retrenchment at scale, severe fragmentation across state Medicaid programs, and the structural fragility of telehealth waivers that nearly evaporated entirely during a 43-day government shutdown in late 2025.

This post examines all of it: the mechanics of the new codes, the TEAM financial model, the legislative turbulence, and the operational infrastructure required to function inside this environment.

What changed in the 2026 Physician Fee Schedule

Why the 16-day threshold failed clinical reality

Before January 1, 2026, the core RPM device-supply code (CPT 99454) required patients to transmit physiologic data on at least 16 of every 30 calendar days to generate a billable claim. The treatment management codes, CPT 99457 for RPM and CPT 98980 for RTM, required a minimum of 20 documented minutes of clinical interaction per month.

The structure was binary. Either a patient crossed both thresholds in a given month, or the practice collected nothing while absorbing the full cost of hardware, software licensing, connectivity, and clinical labor.

Two categories of clinical use were effectively excluded:

Patients with inconsistent adherence. A hypertensive patient who monitored for 14 days and then stopped transmitting triggered a zero-revenue outcome. The practice paid for device provisioning, shipping, cellular data, and nursing time. It billed nothing. At scale, chronic low-adherers were a direct financial drain.

Acute and episodic use cases. Post-discharge surveillance for the first week after an orthopedic procedure, short-duration titration monitoring when starting a new antihypertensive, remote respiratory assessment following a COPD exacerbation, or monitoring a gestational hypertension patient between prenatal visits: none of these generated RPM revenue. The billing structure assumed that remote monitoring was a long-term chronic disease intervention, and only that.

The AMA CPT Editorial Panel and CMS received sustained feedback from health systems, physician groups, and technology companies about this mismatch. The September 2024 AMA panel vote to approve new short-duration codes was the direct result.¹

The new short-duration and low-time codes

CMS finalized the new codes in the November 2025 PFS rule, effective January 1, 2026.

New RPM codes:

Code	Description	Threshold	2026 Rate
CPT 99445	Device supply and data transmission	2 to 15 days in a 30-day period	~$52.11
CPT 99470	Treatment management time	10 to 19 minutes per month	~50% of CPT 99457 rate

The parity pricing on CPT 99445 deserves attention. CMS priced the short-duration device code at the same level as CPT 99454, the existing 16-day code. This reflects a deliberate policy judgment: the fixed costs of provisioning a device, shipping it, onboarding the patient, integrating data feeds, and maintaining the platform do not decrease because the patient transmits for fewer days. CMS is acknowledging that the economics of device deployment are front-loaded, and pricing accordingly.¹

CPT 99470 fills a parallel gap on the management side. When a clinical team spends 12 minutes reviewing vitals, adjusting care plans, and placing a check-in call during the acute post-surgical window, that time has always had clinical value. Before 2026, it had no billing value unless the team could document 20 minutes. The new 10-to-19-minute tier captures that work.

New RTM codes:

Codes	Description	Status
CPT 98979, 98984, 98985, 98986	Short-duration therapeutic data collection and sub-20-minute management across respiratory, musculoskeletal, cognitive, and medication adherence domains	CMS New Technology list; permanent RVU valuation scheduled for 2028

CMS placed the new RTM codes under a three-year new technology review rather than assigning permanent RVU values immediately. The stated rationale is straightforward: CMS wants utilization data and billing pattern visibility before locking in long-term valuations. For RTM programs launching in 2026, the practical implication is that reimbursement rates for these codes may shift materially when the review concludes in 2028.

Across-the-board valuation increases

The 2026 PFS did not just add codes. It raised valuations across the existing remote monitoring and care management family, with increases ranging from 7% to 21%:

CPT 99453 (RPM device setup and patient education): $19.73 in 2025, $21.71 in 2026
CPT 99490 (non-complex Chronic Care Management, first 20 minutes): $60.49 in 2025, $66.13 in 2026

CMS explicitly exempted RPM, RTM, and related care management services from the efficiency adjustments applied to procedural services elsewhere in the 2026 rule. This signals the agency's view that remote monitoring is an investment in reducing downstream costs, not a service category to be squeezed.¹

The agency also reaffirmed two compliance requirements that have not changed: devices used for RPM must meet the FDA definition of a medical device, which rules out consumer wellness trackers, and patient consent must be obtained at the time services are provided.

The TEAM model: how bundled payments create demand for short-duration monitoring

The financial mechanics of TEAM

TEAM is not voluntary. Starting January 1, 2026, CMS requires selected hospitals in designated geographic markets to participate with no opt-out provision. The model defines an episode as the 30-day period following high-volume orthopedic and cardiovascular procedures, including lower extremity joint replacements, spinal fusions, surgical hip fracture repairs, transcatheter aortic valve replacements, and coronary artery bypass grafts.²

Under TEAM, CMS assigns each episode a target price based on historical spending benchmarks. If total spending for that episode, including index hospitalization and all post-discharge care, comes in below the target, the hospital shares in the savings. If spending exceeds the target, the hospital absorbs the difference.

Every 30-day readmission is part of the episode spend. Under fee-for-service, a readmission within 30 days of a joint replacement generates additional facility revenue. Under TEAM, that same readmission is a direct financial loss on top of the existing episode spend. The economic logic of the entire care pathway is inverted.

For hospitals in TEAM markets, the question is no longer whether post-discharge monitoring makes clinical sense. It makes financial sense, and the math is not subtle: a single prevented readmission for a major joint replacement can save between $15,000 and $25,000 in episode costs. A short-duration RPM program that costs $200 to $400 per patient and prevents readmissions at even a modest rate generates substantial returns.

The alignment between 2026 codes and the TEAM risk window

Post-surgical readmission risk is not evenly distributed across the 30-day episode. The majority of preventable readmissions occur in the first two weeks after discharge. Wound complications, infection, fever, deep vein thrombosis, and hemodynamic instability cluster in days 1 through 14. After day 14, risk declines sharply for most patients.

Under the old billing structure, monitoring a patient for 10 days and then discharging them from the program once they stabilized generated zero revenue. The practice paid for the device, the connectivity, and the clinical review time with nothing to show for it on the claim.

Under the 2026 codes, a 10-day monitoring episode is billable under CPT 99445 at approximately $52. If the clinical team spends 12 minutes reviewing data and placing a follow-up call in that period, CPT 99470 covers the management time. The total reimbursement is modest in absolute terms, but it converts a previously uncompensated care activity into a funded one. And the clinical activity being funded is precisely the intervention that prevents the TEAM readmission penalty.¹²

For orthopedic and cardiovascular programs, the operational workflow writes itself: deploy a connected device or FDA-cleared digital therapeutic on discharge day, establish an automated monitoring protocol through the acute risk window, route alerts to clinical staff for review and intervention, document the time, and close the episode when the patient is stable. Bill CPT 99445 for device supply and CPT 99470 for management time. If the patient remains in the program past day 15, transition to CPT 99454 and CPT 99457.

WISeR and RTM as a medical necessity shield

Running parallel to TEAM, CMS is implementing the Wasteful and Inappropriate Service Reduction (WISeR) model in six states: New Jersey, Ohio, Oklahoma, Texas, Arizona, and Washington. WISeR applies algorithmic claim auditing to procedures with historically high variation in utilization, with an emphasis on orthopedic interventions like spinal fusion.³

The model increases audit risk for orthopedic practices in those states, particularly for surgical procedures that lack robust pre-operative documentation of failed conservative treatment.

RTM directly addresses this exposure. A patient enrolled in RTM before surgery generates a longitudinal data record: pain levels, functional deficit scores, adherence rates for home exercise programs, and the clinical decisions made based on that data. When a WISeR audit examines whether surgery was medically necessary, RTM data provides an objective, time-stamped evidence trail that narrative documentation alone cannot match.

For practices operating in WISeR states, RTM should be understood as both a clinical tool and a compliance asset.

Legislative turbulence: the shutdown, waivers, and H.R. 1

The 43-day shutdown and the telehealth cliff

On October 1, 2025, Congress failed to pass continuing appropriations and the federal government shut down. Among the immediate casualties were the geographic and originating-site telehealth waivers that had allowed Medicare patients to receive virtual care at home and in non-rural areas since the public health emergency. For 43 days, the legal basis for a substantial portion of Medicare telehealth billing disappeared.⁴

The shutdown ended November 12, 2025, with the passage of H.R. 5371, a continuing appropriations act that restored the waivers through January 30, 2026. The restored provisions included the waiver of geographic restrictions, audio-only visit allowances, the expanded list of eligible telehealth providers including physical and occupational therapists, and FQHC and RHC distant site permissions.⁴

The episode surfaces a fundamental structural risk that organizations building remote care programs must confront directly. Telehealth waivers are enacted through the congressional appropriations process, subject to political negotiation and expiration dates. They can and do lapse. RPM and RTM billing codes, by contrast, are part of the permanent Medicare Physician Fee Schedule. They were published through notice-and-comment rulemaking and do not require annual renewal. Programs built on permanent fee schedule authority are categorically more stable than programs built on waiver-dependent billing.

This distinction should shape infrastructure investment decisions. Clinical workflows and technology platforms anchored to CPT codes rather than waiver-dependent billing modalities carry less regulatory risk over a three-to-five-year planning horizon.

H.R. 1: the "One Big Beautiful Bill"

Signed July 4, 2025, H.R. 1 is a budget reconciliation package with several provisions that directly affect remote monitoring economics.⁵

Permanent HDHP telehealth and remote care coverage. Effective retroactively to January 1, 2025, High-Deductible Health Plans can provide first-dollar coverage for telehealth and remote care services without disqualifying the patient from HSA contributions. Before this change, patients enrolled in HDHPs with deductibles above $5,000 had to pay out of pocket for virtual visits and RPM enrollment until their deductible was satisfied. This suppressed utilization most severely among the working-age patients most likely to be enrolled in HDHPs. The H.R. 1 change removes that cost barrier and should increase commercial RPM enrollment among patients under 65.

Medicaid physician fee increase. A temporary 2.5% increase to the Medicaid physician fee schedule conversion factor runs from January 1, 2026 through January 1, 2027. For practices with significant Medicaid populations, this modestly improves the margin on care management services including CCM and RTM.

Expanded HSA access. H.R. 1 extends HSA eligibility to Bronze and Catastrophic plan enrollees, and permanently increases the dependent care FSA limit. Neither provision directly affects RPM billing economics, but the overall expansion of HSA-eligible populations increases the pool of patients who can use pre-tax dollars for health services.

Eligibility restrictions with direct impact on patient access. H.R. 1 terminates Medicare eligibility for several immigrant classifications, including individuals with temporary protected status, refugees, and asylum seekers. For practices serving diverse urban populations, this removes a category of patients from federal remote monitoring reimbursement entirely. H.R. 1 also prohibits federal payments to organizations providing certain reproductive health services, with potential downstream effects on Medicaid enrollment for some safety-net providers.⁵

The net effect of H.R. 1 on remote monitoring is directionally positive for commercial market expansion and modestly negative for programs serving populations at the intersection of immigration status and chronic disease management.

The commercial payer problem

UnitedHealthcare's RPM rollback

The single most operationally disruptive development of 2026 may not originate in federal rulemaking at all. UnitedHealthcare, the largest private insurer in the country, announced a sweeping restriction of RPM coverage across its Medicare Advantage, Community Plan, and commercial product lines, limiting reimbursement to two conditions: heart failure and gestational hypertension.⁶

This policy eliminates RPM coverage for chronic hypertension management, type 2 diabetes, COPD, and every other condition outside that narrow list. These are not fringe applications. They represent the majority of active RPM programs in primary care and internal medicine. The evidence base for remote monitoring efficacy is strongest precisely in the conditions UHC chose to exclude.

The operational impact on a mid-size primary care practice is significant. Consider a practice managing 500 patients with type 2 diabetes on RPM. Under the new UHC policy, patients insured through UHC Medicare Advantage or commercial plans cannot be billed for RPM services. The practice faces three choices: absorb the cost of monitoring as an uncompensated service and risk its financial viability, offboard UHC patients from monitoring programs and collect devices, or transition those patients to labor-intensive non-device CCM programs that require more staff time for lower reimbursement.

None of those options is clean. All of them require the practice to split its standard of care by payer, which introduces clinical inconsistency and compliance exposure.

The downstream requirement is clear: payer-specific eligibility verification must happen before a device ships. Verifying that a patient's payer covers RPM for their specific ICD-10 diagnosis codes is no longer a best practice. It is a prerequisite for avoiding unrecoverable revenue loss on deployed hardware.

State Medicaid: a fragmented national picture

A national analysis of priority Medicaid markets shows that 14 of 15 states offer some form of RPM coverage, but "coverage" obscures enormous variation in what each state actually reimburses and under what conditions.⁷

Georgia illustrates the restrictive end of the spectrum. In comparable constrained frameworks, Medicaid RPM reimbursement has been capped at flat rates around $125 per 30-day period regardless of patient acuity, limited to episodes as short as two months per year with a two-episode annual maximum, and gated behind prior authorization, 30-day readmission policies, and strict provider enrollment within the GAMMIS system.⁸ A high-acuity diabetic patient generating daily blood pressure readings, multiple clinical interventions, and significant care coordination costs produces the same revenue as a low-acuity patient who checks in once a week. The economics are structurally unfavorable for complex patients.

New York represents the opposite approach. The state explicitly expanded Medicaid RPM coverage to include maternal health applications, authorizing remote blood pressure monitoring during pregnancy and the postpartum period to address preeclampsia and reduce maternal mortality.⁹ New York Medicaid's expansion recognizes that short-duration, condition-specific monitoring programs can deliver measurable population health outcomes at reimbursable cost.

The Georgia-to-New York spectrum within a single federal payer category illustrates why a national RPM rollout cannot run on a single billing playbook. Each state Medicaid program is effectively a separate payer with its own coverage policies, prior authorization requirements, fee schedules, and provider enrollment processes.

Operational infrastructure for 2026

Automated billing logic is not optional

The coexistence of CPT 99445 (2 to 15 transmission days) and CPT 99454 (16 or more transmission days) makes manual billing workflows indefensible at any meaningful scale. A billing team using spreadsheets and manual day counts will produce errors. At volume, those errors mean either underbilling on compliant episodes or overbilling on non-compliant ones, both of which carry audit and recoupment risk.

The same problem applies on the management time side. CPT 99470 covers 10 to 19 minutes. CPT 99457 covers 20 or more minutes. Getting the right code on the right claim requires precise aggregation of non-face-to-face time across every patient, every month. Clinicians cannot be expected to track their own minutes with the accuracy that audit defense requires.

A billing system adequate for 2026 must handle three functions automatically:

Transmission threshold evaluation. At the close of each 30-day billing period, the system counts transmission days and routes the claim to 99445 or 99454 based on the count. No human decision point. No spreadsheet lookup.

Clinical time aggregation. The system tracks and timestamps all documented non-face-to-face clinical time at the individual patient level. When the billing period closes, it selects the correct management code based on aggregated minutes. CPT 99470 for 10 to 19 minutes, CPT 99457 for 20 or more.

Pre-enrollment eligibility verification. Before a device ships, the system checks the patient's active payer, their ICD-10 diagnoses, and current coverage policies for those diagnoses under that payer. A patient covered by UHC commercial insurance with a diabetes diagnosis should generate an enrollment block, not a shipped device and a denied claim.

Managing alert fatigue at scale

As continuous biometric data volumes increase, the clinical bottleneck shifts from data acquisition to data triage. A monitoring program that sends clinicians every threshold breach generates noise. Staff learn to dismiss alerts. The alerts that matter get missed.

FDA-cleared AI triage systems are producing measurable results in this area. In cardiology, platforms including Octagos and Implicity apply machine learning algorithms to filter remote cardiac device transmissions. In 2025, these systems processed approximately 4 million transmissions, saving an estimated 12 minutes of clinical staff time per transmission, roughly 45 million minutes in aggregate, by filtering clinically irrelevant signals and surfacing only events requiring provider attention. Outcome data from advanced AI-driven remote monitoring platforms has been associated with a 26% reduction in mortality and a 4% reduction in hospitalization length relative to conventional monitoring approaches.¹⁰

The financial logic of AI triage aligns directly with the 2026 billing structure. CPT 99470 reimburses for 10 to 19 minutes of clinical management time. The margin on that code depends on clinical density: how many patients a clinician can meaningfully review in a working hour, and how often their interventions prevent a costly downstream event. AI triage is the mechanism that keeps clinical attention focused on patients who actually need it, rather than diluted across a stream of low-acuity noise.

Supervision rules, concurrent billing, and the documentation requirement

CMS reaffirmed the general supervision standard for RPM and RTM in 2026. Auxiliary staff including medical assistants, licensed practical nurses, and contracted care management companies can perform daily data review and patient outreach under the direction of the billing physician, without requiring the physician to be physically present during those interactions.¹ This standard is essential to the financial viability of large-scale monitoring programs: physician-only review of routine daily data is neither clinically necessary nor economically sustainable.

CMS also introduced optional add-on G-codes for Advanced Primary Care Management (APCM) that integrate Behavioral Health Integration and Collaborative Care Model services into the primary care workflow without requiring separate time-tracking for each service line.¹

Concurrent billing of RPM and CCM in the same month for the same patient remains explicitly permitted, provided the clinical time and documented activities for each service are distinct. A patient with hypertension on a connected blood pressure cuff, enrolled in both RPM (CPT 99454 + 99457) and Chronic Care Management (CPT 99490) for medication reconciliation and care planning, can generate combined monthly reimbursement exceeding $150. At that revenue level per patient per month, a 200-patient panel represents substantial recurring revenue from care that would otherwise be uncompensated.¹

The condition for this to hold is documentation. Stacking billing codes without documented evidence of distinct activities and separately tracked time is an audit vulnerability. CMS and private payer auditors examine concurrent billing patterns as a matter of routine. The documentation infrastructure has to match the billing ambition.

The landscape in summary

CMS has constructed the most clinically flexible and adequately funded remote monitoring framework in Medicare's history. The short-duration codes match how post-acute monitoring actually works. The valuation increases reflect the true cost of device-based care. The TEAM model creates hard financial incentives to deploy remote monitoring exactly where it reduces the most expensive failures.

Against that, commercial payers are moving in the opposite direction. UHC's condition-specific restrictions affect tens of millions of covered lives. State Medicaid programs remain a patchwork of coverage policies, rate caps, and enrollment hurdles that vary enough between states to require fundamentally different operational approaches. And the telehealth waiver infrastructure demonstrated in 2025 that it can collapse for six weeks on a congressional procedural failure, taking an entire category of billing authority with it.

The organizations that succeed in this environment will not be distinguished by the sophistication of their devices or the breadth of their clinical protocols. They will be distinguished by the quality of their operational and compliance infrastructure: billing systems that select the right code automatically at the close of every billing period, eligibility engines that block uncompensated device deployment before it happens, time-tracking that produces audit-ready documentation without burdening clinicians, and clinical workflows that adjust to payer restrictions dynamically rather than requiring manual intervention each time a coverage policy changes.

The clinical case for remote monitoring has never been stronger. The operational requirements to run it profitably and defensibly have never been more demanding.

References

Centers for Medicare & Medicaid Services. "Medicare and Medicaid Programs; CY 2026 Payment Policies Under the Physician Fee Schedule and Other Changes to Part B Payment and Coverage Policies." Federal Register, November 5, 2025. cms.gov/medicare/regulations-guidance/physician-fee-schedule ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸
Centers for Medicare & Medicaid Services. "Transforming Episode Accountability Model (TEAM)." CMS Innovation Center, 2025. innovation.cms.gov/innovation-models/team ↩ ↩² ↩³
Centers for Medicare & Medicaid Services. "Wasteful and Inappropriate Service Reduction (WISeR) Model." CMS Innovation Center, 2025. innovation.cms.gov ↩
U.S. Congress. "Further Continuing Appropriations and Extensions Act, 2026." H.R. 5371, 119th Congress, November 2025. congress.gov ↩ ↩²
U.S. Congress. "One Big Beautiful Bill Act." H.R. 1, 119th Congress, signed July 4, 2025. congress.gov ↩ ↩²
UnitedHealthcare. "Remote Patient Monitoring Coverage Policy Updates, Effective 2026." UHC Provider Bulletin, 2025. uhcprovider.com ↩
Center for Connected Health Policy. "State Telehealth Laws and Reimbursement Policies Report." CCHP, Fall 2025. cchpca.org ↩
Georgia Department of Community Health. "Georgia Medicaid Fee Schedule and Provider Manual Updates." DCH, 2025. medicaid.georgia.gov ↩
New York State Department of Health. "Medicaid Coverage of Remote Patient Monitoring for Maternal Health." NYS Medicaid Update, 2025. health.ny.gov ↩
Octagos Health / Implicity. "Impact of AI-Driven Remote Cardiac Device Monitoring on Clinical Outcomes." Published data, 2025. octagoshealth.com ↩