Patient Remote Monitoring (RPM): Architecture, FDA Device Rules, CMS CPT Billing, and Clinical Trials

Patient remote monitoring—commonly termed Remote Patient Monitoring (RPM) or, in Centers for Medicare & Medicaid Services (CMS) regulations, Remote Physiologic Monitoring—is a connected healthcare delivery and clinical research methodology that uses non-invasive digital medical devices to collect, transmit, and analyze physiological parameters outside conventional clinical settings. In both chronic disease management and decentralized clinical research under ICH E6(R3) Annex 2 decentralized trial provisions, RPM bridges home telemetry with electronic health record (EHR) and electronic data capture (EDC) systems.

What Is Remote Patient Monitoring in Healthcare?

Which statement best describes remote patient monitoring? In clinical informatics and federal reimbursement policy, remote patient monitoring is the longitudinal acquisition and automated electronic transmission of physiological data—such as blood pressure, pulse oximetry (SpO₂), blood glucose, body weight, spirometry, or ambulatory electrocardiogram (ECG) waveforms—from a patient’s home to a clinical care or study team for acute escalation triage and treatment plan titration.

Unlike synchronous audio-video telehealth visits, RPM operates primarily as an asynchronous physiological surveillance pipeline paired with periodic interactive clinical communication. CMS distinguishes Remote Physiologic Monitoring (RPM) (which tracks physiological parameters via CPT codes 99453, 99454, 99457, and 99458) from Remote Therapeutic Monitoring (RTM) (CPT codes 98975–98981, which captures non-physiologic data such as musculoskeletal therapy adherence, respiratory inhaler actuation, and pain or symptom response).

What Does Remote Patient Monitoring in Healthcare Use? (Technology Stack)

An enterprise or clinical-trial RPM architecture comprises four integrated technical layers when choosing diagnostic and patient monitoring equipment:

1. FDA-Cleared Peripheral Biosensors: Connected medical devices meeting the definition of a device under Section 201(h) of the Federal Food, Drug, and Cosmetic Act (FD&C Act), including oscillometric blood pressure monitors, continuous glucose monitors (CGMs), pulse oximeters, digital weight scales, and patch holter monitors. Under CMS rules, physiological data must be automatically synced and transmitted by the device; manually typed patient self-reports do not qualify for CPT 99454 device supply billing.
2. Edge Connectivity and Telemetry Gateways: Devices transmit readings either via Bluetooth Low Energy (BLE) to a patient’s smartphone application (following IEEE 11073 Personal Health Device [PHD] communication profiles) or directly over cellular LTE-M / NB-IoT base stations that require zero patient Wi-Fi setup.
3. Cloud Ingestion and Alerting Engine: Middleware normalizes device payloads into HL7 FHIR R4 Observation and DeviceMetric resources, evaluates protocol-defined threshold rules (such as a 3-pound weight gain over 48 hours in heart failure), and routes clinical alerts to nursing triage queues.
4. EHR and Trial EDC Integration: Validated vitals and cumulative monthly time logs flow into the EHR flowsheet and chronic care management billing modules, or into clinical trial repositories supporting remote and centralized clinical trial monitoring.

What Is Remote Patient Monitoring Used For?

• Cardiometabolic and Cardiopulmonary Chronic Disease Management: Titrating antihypertensive regimens in uncontrolled hypertension, detecting early fluid overload in congestive heart failure (CHF) to reduce 30-day hospital readmissions, monitoring glycemic variability in Type 1 and Type 2 diabetes, and tracking forced expiratory volume (FEV₁) and SpO₂ in COPD.
• Post-Acute and Hospital-at-Home Transitions: Continuous or intermittent vital signs surveillance following surgical discharge, postpartum hypertension screening, or oncology chemotherapy symptom and neutropenic fever monitoring.
• Decentralized Clinical Trials (DCTs): Collecting high-frequency, objective physiological endpoints in the participant’s home environment without requiring frequent on-site study visits.

Who Can Bill for Remote Patient Monitoring & Can FQHCs Bill for RPM?

Under the CMS Medicare Physician Fee Schedule (PFS), only physicians (MD/DO) and Non-Physician Practitioners (NPPs)—specifically Nurse Practitioners (NPs), Physician Assistants (PAs), Clinical Nurse Specialists (CNSs), and Certified Nurse-Midwives (CNMs)—who are eligible to bill Medicare Evaluation and Management (E/M) services may order and bill for RPM services. Once ordered for an established patient, auxiliary clinical staff (such as registered nurses or medical assistants) may furnish the monthly monitoring and interactive communication under general supervision (42 CFR § 410.26).

CPT Code	Service Description	Key CMS Billing & Frequency Rules
CPT 99453	Initial device setup and patient education on use of equipment	Billed once per episode of care only after at least 16 days of monitoring have occurred within a 30-day period.
CPT 99454	Device(s) supply with daily recording(s) or programmed alert(s) transmission, each 30 days	Requires an FDA-defined medical device transmitting data on at least 16 days out of a 30-day period; billed by only one practitioner per patient per 30 days.
CPT 99457	RPM treatment management services, first 20 minutes in a calendar month	Requires at least 20 minutes of clinical staff/physician/NPP time AND at least one live, real-time interactive communication with the patient/caregiver during the calendar month.
CPT 99458	Each additional 20 minutes of RPM treatment management in a calendar month	Add-on code to 99457 for each additional full 20-minute increment (≥40 minutes total for 1 unit of 99458).

Can FQHCs and RHCs Bill for Remote Patient Monitoring?

Yes. Beginning in the CY 2024 Medicare Physician Fee Schedule Final Rule, CMS authorized Federally Qualified Health Centers (FQHCs) and Rural Health Clinics (RHCs) to receive separate Medicare reimbursement for Remote Physiologic Monitoring outside their all-inclusive Prospective Payment System (PPS) or All-Inclusive Rate (AIR). In CY 2024, FQHCs billed RPM under the bundled general care management HCPCS code G0511. In the CY 2025 PFS Final Rule, CMS unbundled G0511 and transitioned FQHCs and RHCs to billing the individual RPM CPT codes (99453, 99454, 99457, and 99458) directly on institutional claims, reimbursing them at the national non-facility PFS payment rate.

Frequently Asked Questions

What is remote patient monitoring in healthcare?

Remote patient monitoring (RPM) is a digital healthcare workflow that uses FDA-defined non-invasive medical devices—such as connected blood pressure cuffs, pulse oximeters, weight scales, or glucometers—to automatically record and transmit patient physiological data from home to clinicians for chronic disease management, post-discharge surveillance, or clinical trials.

Who can bill for remote patient monitoring and can FQHCs bill for it?

Physicians and qualified Non-Physician Practitioners (NPs, PAs, CNSs, CNMs) who are eligible to bill Medicare E/M services can order and bill RPM CPT codes 99453, 99454, 99457, and 99458, with clinical staff performing treatment management under general supervision. FQHCs and RHCs can also bill Medicare for RPM—initially via HCPCS G0511 in 2024 and directly via individual CPT codes 99453–99458 under the CY 2025 PFS unbundling rules.

Sources

• Centers for Medicare & Medicaid Services (CMS): Medicare Physician Fee Schedule (PFS) Final Rules (CY 2024 & CY 2025) — Remote Physiologic Monitoring and FQHC/RHC Care Management Billing.
• U.S. Food and Drug Administration (FDA): Section 201(h) of the Federal Food, Drug, and Cosmetic Act and Non-Invasive Remote Monitoring Devices Guidance.
• IEEE / HL7 International: IEEE 11073 Personal Health Device (PHD) Standards and HL7 FHIR Personal Health Device Implementation Guide.