Cellular devices that patients can actually use, nine CMS programs on one login, and a clinical team that will run the monitoring under your NPI if you have no capacity to spare.
Remote patient monitoring (RPM) is a care-delivery model in which a patient uses connected medical devices at home to collect physiologic data (blood pressure, blood glucose, weight, oxygen saturation, temperature) which transmits automatically to their care team. The team reviews the readings against thresholds the clinician set and intervenes between visits rather than waiting for the next appointment.
Under Medicare it is billable: 99453 for setup and patient education, 99454 for device supply (readings on at least 16 of 30 days), and 99457 plus 99458 for monthly treatment-management time including interactive communication with the patient.
RPM software is the platform underneath that: device management, data ingestion and alerting, care-team dashboards, patient communication and the CPT documentation the billing depends on. HealthArc goes further and runs eight more CMS programs in the same environment, so a patient enrolled in RPM and CCM exists once, in one record, with one time log.
One time log is the whole argument for a single platform. CMS does not let the same minutes count toward two care-management codes, and a practice running RPM in one system and CCM in another has no way to prove it never double-counted when an auditor asks.
Feature lists blur together. These are the five things that decide whether a programme runs or stalls.
| Capability | Why it decides the outcome | What HealthArc does |
|---|---|---|
| Patient-proof devices | The most common reason enrolment stalls is a device the patient cannot get working. | Every device is cellular with 2G fallback and a multicarrier SIM. No app, no pairing, no Wi-Fi, no account. |
| Threshold tracking | 99454 turns on readings in 16 of 30 days. Miss it and the month is unbillable. | The platform counts transmission days live and flags a patient at day 20 while it is still fixable. |
| One time log across programmes | The same minutes cannot be billed twice, and split systems cannot prove they were not. | RPM, CCM, RTM, TCM and the rest share one record with concurrent-billing safeguards. |
| EHR write-back | If notes do not land in the chart, your team documents everything twice. | Two-way HL7 FHIR and HL7 v2 with Epic, Oracle Health, athenahealth, NextGen, eClinicalWorks and 50+ more. See every EHR |
| Clinical staffing, optional | Most practices have no spare care coordinator, which is what actually kills programmes. | A HealthArc clinical pod can run monitoring and outreach under your supervising provider’s name and NPI. |
Alert thresholds are configured per patient by the ordering clinician and adjusted over time. The values above are common starting points, not clinical guidance, and nothing here establishes a standard of care. Reimbursement figures are approximate national non-facility Medicare averages and vary by locality, facility status, payer and calendar year: verify current rates at cms.gov or with your MAC before you bill.
Cellular throughout, shipped activated, and chosen so an older panel can actually use them.
Three cuff sizes with irregular-heartbeat detection.
99454Results reach the care team seconds after the test.
99454Step-on weights with fluid-retention alerting.
99454Clinical-grade SpO2 in under 30 seconds over LTE-M.
99454Time-in-range reporting and nocturnal low alerts.
95249 · 95250FEV1, FVC and peak flow trended against personal best.
98976Per-patient fever thresholds with same-day alerts.
99454Objective dose-event records.
98975The point is not the count. It is that a patient in three programmes still has one record and one time log.
Two or more chronic conditions, coordinated monthly.
99490 · 99439Therapy adherence and symptom data. PTs and OTs bill it directly.
98975–98981The 30 days after discharge.
99495 · 99496One dominant complex condition.
99424–99427Monthly by risk tier, no time tracking.
G0556–G0558Depression and anxiety inside primary care.
99484 · 99492Pharmacist-led regimen review.
99605–99607Navigators and peer support for serious illness.
G0023 · G0024HealthArc connects with 55+ EHRs, including Epic, Oracle Health, athenahealth, NextGen and eClinicalWorks. Patient lists come in from the chart. Readings, notes and time logs go back to it, so your team documents once.
40+ cellular devices plus third-party device APIs, all landing in one reading stream.
A billing-ready export for your RCM system or clearinghouse, every required field filled.
A REST API for your analytics team and population-health reporting.
A BAA is signed before any data moves. Data is encrypted in transit and at rest.
Product names and logos are trademarks of their respective owners. Listing an EHR reflects HealthArc’s integration support and doesn’t imply endorsement by that company. The exact fields exchanged depend on your EHR’s configuration and API, and are confirmed in writing during scoping.
Each page below covers the devices, alert thresholds and billable programs for that population, because a COPD program and a diabetes program are not the same program.
Remote blood pressure monitoring, and the quality measure it closes.
View programCellular meters, CGM data and time-in-range reporting.
View programSpO2, spirometry and the pre-exacerbation window.
View programObesity programmes and heart-failure fluid alerts.
View programDaily weights, TCM and the readmission window.
View programAPCM, CCM and RPM across a whole Medicare panel.
View programHome spirometry trended against personal best.
View programBP and fluid status between lab draws.
View programCGM, time in range and insulin titration support.
View programRTM that physical therapists bill in their own right.
View programMost clients are monitoring patients within 30 days, and no IT team is required on your end.
We screen your panel by diagnosis and payer and model the billable population per programme before you commit.
Provider roster, thresholds, care-plan templates and the bi-directional FHIR connection.
Role-specific sessions for coordinators, billing staff and physicians. Four to eight hours total across the practice.
A 20–50 patient cohort validates the workflow end to end before full rollout.
Enrolment expands to the full eligible panel, and the first billing cycle closes on documentation that built itself.
Remote patient monitoring is a care-delivery model in which a patient collects physiologic data at home using connected medical devices: a blood pressure cuff, glucose meter, weight scale, pulse oximeter or thermometer. That data transmits automatically to their care team.
The team reviews it against clinician-set thresholds and acts between visits. Under Medicare it is a billable service under CPT 99453, 99454, 99457 and 99458.
RPM software is the platform that makes the model operational. It handles device provisioning and connectivity, ingests and stores readings, raises alerts against per-patient thresholds, gives the care team a dashboard and patient-communication tools, tracks time against CPT thresholds, and produces the billing documentation.
The differentiator worth testing in a demo is not the feature list. It is whether the platform can prove, on one time log, that minutes billed to RPM were never also billed to CCM.
The honest answer is that it depends on which failure mode would sink your programme. Five questions separate platforms in practice:
HealthArc answers yes to all five, runs nine CMS programmes on one login, and offers a managed clinical pod under your provider’s NPI.
99453 covers initial setup and patient education, billed once per episode. 99454 covers device supply and data transmission and requires readings on at least 16 of 30 days. 99457 covers the first 20 minutes of monthly treatment-management time including interactive communication, and 99458 each additional 20 minutes.
CMS added codes in 2026 allowing device-supply billing with 2–15 days of data, though 99454 itself still turns on 16 days. See the full RPM code reference.
Yes. CMS permits RPM treatment-management time (99457) and CCM care-management time (99490) for the same patient in the same calendar month, but the same minutes can never count toward both.
This is where split systems fail. Running RPM in one platform and CCM in another leaves you unable to demonstrate the minutes were distinct, which is exactly the question an audit asks.
Not with HealthArc. Every device transmits over its own 4G cellular connection with 2G fallback and a multicarrier SIM, and ships already activated. There is no app to install, no Bluetooth pairing, no home broadband requirement and no account for the patient to create.
This is the single biggest determinant of whether an older, higher-risk panel enrols, because those are exactly the patients least likely to own a smartphone.
HealthArc connects with 55+ EHRs. They include Epic, Oracle Health (Cerner), athenahealth, NextGen Healthcare, eClinicalWorks, Veradigm (Allscripts), AdvancedMD, DrChrono, Elation Health, Greenway Health, Tebra, PointClickCare and PrognoCIS.
The connection runs over HL7 FHIR R4, HL7 v2 messaging or a direct vendor integration, depending on what your system supports, and our team does the interface work so it doesn’t become an IT project on your side. Not listed? Our integration team confirms connectivity during discovery. Setup guides for each live integration are in the EHR integrations directory.
Yes. Reading summaries, flagged readings, signed care-management notes and time logs by CPT code post back to the patient chart, so providers review RPM work where they already chart and your team never documents twice.
What can be written back depends on your EHR’s API. Some systems accept notes and documents but not structured vitals, and a few interfaces are read-only. We confirm the exact fields in writing before go-live.
Both, and you choose. Software-only means your team runs the programme on our platform. Managed services means a dedicated HealthArc clinical pod of RNs, LPNs, medical assistants and enrolment specialists runs monitoring, outreach and documentation under your supervising provider’s name and NPI, with your clinicians keeping every clinical decision.
Many practices run a hybrid: their team keeps the patients it knows, ours absorbs overflow and after-hours contact attempts.
Most clients are actively monitoring patients within 30 days of contract execution, through four phases: discovery and panel analysis, configuration and EHR connection, staff training, then pilot enrolment before full rollout.
Total staff time during onboarding is typically four to eight hours across the practice, and no IT team is required on your end.
Bring your patient count and payer mix. We will model the billable population across RPM, CCM and the rest before you commit to anything.
Practical guidance on remote monitoring, devices and billing. Updated with every new post.
Every FDA-cleared cellular device category on HealthArc compared: conditions, connectivity, the RPM, RTM and CGM codes each supports, and kits by specialty.
Read articleCardiac RPM ROI for provider groups and health plans: 2026 Medicare rates, a 100-patient P&L, break-even enrollment, and the admissions a program must avoid.
Read articleHow to monitor CKD, hypertension and diabetes through one coordinated RPM program: which devices each patient actually needs, how alerts escalate, and why 99454 pays once per patient.
Read articleWant a demo, or just have a question about running RPM in your practice? Send us a few details and a remote care specialist will get back to you shortly.
No commitment required.
No obligation | No spam