Loading...

Remote Patient Monitoring IoT in New Jersey: A Billing Guide for Independent Practices

Healthcare IoT

Published by IOT New Jersey Research & Editorial Team

Remote Patient Monitoring IoT in New Jersey: A Billing Guide for Independent Practices

Remote patient monitoring has moved well past its pandemic era novelty and into something closer to a standard chronic care tool, but most of the coverage of healthcare IoT is written for hospital systems building smart hospital infrastructure at a scale few independent practices will ever touch. New Jersey has a large population of small and mid size primary care, cardiology, endocrinology, and internal medicine practices for whom the real question is narrower and more practical: can remote patient monitoring generate sustainable revenue and better outcomes without the administrative overhead swallowing the benefit.

The answer increasingly depends on getting the billing mechanics right as much as the technology, since the 2026 rule changes from the Centers for Medicare and Medicaid Services reshaped both remote patient monitoring, known as RPM, and the newer remote therapeutic monitoring codes, known as RTM, in ways that create real opportunity for practices that document correctly and real risk for those that do not.

Why RPM Makes Sense for Independent Practices in New Jersey

New Jersey has a dense concentration of independent and small group medical practices, particularly in primary care, cardiology, and endocrinology, serving patients across a state where hospital systems compete heavily for the same specialist referrals. For these practices, chronic disease management, hypertension, heart failure, diabetes, and COPD among the most common, represents both the highest clinical need and the clearest financial case for remote monitoring, since these are exactly the conditions where daily vital sign data changes clinical decisions and where CMS has built a reimbursement structure specifically to support continuous, rather than appointment only, monitoring.

Understanding the 2026 RPM and RTM Billing Landscape

Code CategoryWhat It CoversKey 2026 Detail
Device setup (99453)Initial device setup and patient educationBilled once per device, requires at least two days of readings before billing
Device supply, short period (new 99445 for 2026)Two to fifteen days of monthly data transmissionNew for 2026, allows billing for shorter monitoring periods than the previous sixteen day threshold
Device supply, standard period (99454)Sixteen or more days of monthly monitoringCannot be billed in the same month as 99445 for the same patient
Treatment management (99457, 99458)Clinical staff time reviewing data and managing careCan be billed alongside chronic care management time if documented separately
Remote therapeutic monitoring (98975 to 98985)Non physiological data such as medication adherence and musculoskeletal therapy complianceCannot be billed for the same patient in the same month as RPM codes

The Sixteen Day Rule Just Got More Flexible

For years, practices lost RPM revenue whenever a patient failed to transmit at least sixteen days of readings in a calendar month, a common problem with elderly or less tech comfortable patients. The new 99445 code effective in 2026 allows billing for shorter monitoring periods of two to fifteen days, which directly addresses one of the most common reasons independent practices under billed RPM in prior years. A practice that previously wrote off a partial month of data now has a legitimate path to bill for it, provided the documentation supports the actual number of transmission days.

RPM and Chronic Care Management Can Be Billed Together, Carefully

Medicare allows RPM treatment management time to be billed alongside chronic care management and other care management services in the same month, but only if the time spent on each service is documented separately and never double counted. This is where many smaller practices run into trouble, since it requires either disciplined manual documentation or a billing platform built to separate these time logs automatically. Practices new to RPM are often better served starting with a single billing code category cleanly before layering in concurrent chronic care management billing.

RTM as a Complement, Not a Substitute

Remote therapeutic monitoring codes, which track non physiological data such as medication adherence or musculoskeletal therapy compliance rather than vital signs, expanded further in 2026 with new codes for shorter monitoring periods and treatment management time thresholds. RTM cannot be billed for the same patient in the same month as RPM, so a practice treating a patient for both a physiological condition and a therapy adherence issue needs a clear internal policy for which program applies, rather than defaulting to whichever generates more revenue that month, a distinction that also matters for audit defensibility.

Choosing Devices and Vendors as a Small Practice

Independent practices in New Jersey generally do best working with an RPM vendor that handles device provisioning, patient onboarding, and data transmission logistics as a packaged service, rather than assembling the pieces individually, since the administrative burden of managing devices, batteries, connectivity, and patient troubleshooting across a panel of chronic disease patients quickly exceeds what a small practice's existing staff can absorb without dedicated support. The clinical value of RPM depends entirely on patients actually transmitting usable data, and vendor managed onboarding and support materially affects that adherence rate.

A Realistic First Year for a New Jersey Practice

  1. Start with one condition and one device type. Blood pressure monitoring for hypertensive patients is typically the simplest starting point, both clinically and administratively.
  2. Enroll a small, motivated cohort first. Twenty to thirty patients is enough to build internal billing and clinical workflow competence before scaling further.
  3. Assign clear ownership of the billing workflow. Someone on staff needs to own tracking transmission days and treatment management time, whether that is a biller, a clinical staff member, or the vendor's platform.
  4. Audit the practice's own claims after ninety days. Confirm that documentation actually supports every code billed before scaling the program to more patients.
  5. Expand to a second chronic condition once the first is running smoothly. Diabetes and heart failure monitoring are natural next steps for most primary care and cardiology practices.

What This Looks Like in Practice

Consider a two-physician internal medicine practice in Central Jersey with a patient panel that includes a significant share of Medicare-age patients living with hypertension and type 2 diabetes. In its first year of RPM, the practice enrolled thirty patients with a simple cellular-connected blood pressure cuff, working with a vendor that handled device shipping, patient onboarding calls, and monthly data transmission reporting. Billing staff tracked transmission days and treatment management minutes in a shared spreadsheet for the first quarter before moving to the vendor built-in billing report once the workflow was proven out. Two patients whose blood pressure readings trended upward over several weeks were flagged automatically, leading to a medication adjustment during a routine call rather than waiting for the next scheduled office visit, the kind of early intervention RPM is designed to enable. By the end of the first year, the practice had extended the program to a second cohort of diabetic patients using connected glucose meters, having already worked out the documentation habits that kept the original cohort billing clean during an internal audit.

Working With Larger Health Systems in the Region

Independent practices in New Jersey often refer patients to or receive referrals from the larger hospital systems operating across the state, and several of these systems have built their own RPM and telehealth infrastructure at scale. That creates a practical question for a smaller practice: build an independent RPM program or route patients into a hospital system partner platform instead. Both paths are workable, but they carry different tradeoffs. An independent program keeps billing revenue and clinical data inside the practice, while a hospital system partnership can reduce the administrative lift considerably at the cost of losing direct control over device selection and the pace of program changes. Practices considering either route should clarify data sharing and billing attribution terms in writing before enrolling patients, since ambiguity about which party bills which code has been a source of denied claims across the industry.

Challenges Independent New Jersey Practices Run Into

  • Documentation gaps. Under billing and audit risk both stem from the same root cause, insufficient separation of RPM time from other care management services in the medical record.
  • Patient connectivity and tech comfort. Older patients in particular may struggle with device setup or intermittent home internet, which the new shorter monitoring period codes help but do not eliminate.
  • Staff time for data review. Someone clinical still has to look at the data and act on it, and that time has to be built into existing staff workloads rather than treated as free capacity.
  • Multiple specialists monitoring the same patient. Only one clinician can bill RPM or RTM for a given patient in a given month, which requires coordination when a patient sees both a primary care physician and a specialist who might otherwise both want to monitor the same condition.
  • Payer variation. Commercial payers in New Jersey do not always mirror the RPM and RTM rules of Medicare exactly, so a practice with a mixed payer panel needs to verify coverage rules payer by payer rather than assuming the Medicare framework applies universally.

Where Remote Patient Monitoring Is Heading

The 2026 rule changes suggest CMS is actively trying to make RPM more usable for exactly the kind of practice that struggled most under the old sixteen day threshold, smaller operations without dedicated remote monitoring staff. The next phase for practices in New Jersey will likely involve more automated documentation, platforms that separate RPM and chronic care management time automatically and flag potential billing conflicts before a claim goes out, reducing the administrative burden that has kept many independent practices from adopting remote monitoring even when the clinical case was clear.

Frequently asked questions

CMS introduced a new code, 99445, that allows billing for shorter monitoring periods of two to fifteen days in a month, addressing a common problem where practices previously lost revenue whenever a patient failed to transmit the previously required sixteen days of readings.

Yes, but only if the time spent on each service is documented separately and never counted twice. Practices without a reliable way to separate these time logs are better off starting with one program cleanly before adding the other.

Remote patient monitoring tracks physiological data such as blood pressure or heart rate, while remote therapeutic monitoring tracks non physiological data such as medication adherence or musculoskeletal therapy compliance. The two cannot be billed for the same patient in the same month.

Hypertension, heart failure, diabetes, and COPD are the most common starting points, since these conditions benefit clinically from daily data and are well supported by the current CMS billing structure for remote monitoring.

Most independent practices do better working with a vendor that handles device provisioning, patient onboarding, and data transmission logistics as a packaged service, since the administrative burden of managing devices and troubleshooting patient connectivity issues can quickly exceed what existing staff can absorb.

Only one clinician can bill RPM or RTM for a given patient in a given month, so practices sharing a patient with another specialist need a clear agreement about which one owns the monitoring and billing for that period.

Related articles

Top