Remote patient monitoring (RPM) uses digital devices to collect and transmit health information for clinical review. HHS describes it as asynchronous telehealth: the collection and review do not require the patient and clinician to interact live.
Nursing work may include preparing the patient, reviewing incoming information, contacting the patient about a concern, coordinating escalation, and documenting follow-up. The exact assignment depends on the program, the nurse's role, and approved clinical procedures.
A device is only one part of a service
A useful RPM plan identifies the clinical purpose, eligible patients, appropriate equipment, data-review schedule, and responsible team. It also identifies what will happen when readings are missing or fall outside the program's expected range.
HHS guidance describes patient data collection and transmission alongside provider monitoring, notification, action, and education. Those are connected responsibilities. A device that sends readings successfully cannot ensure that a clinician receives, reviews, or responds to them.
Before enrollment, explain costs through the appropriate benefits or billing process. Do not promise coverage based solely on the fact that a service uses a monitoring device; payer and program details require separate verification.
Make expectations explicit
Patients should receive instructions on using the equipment, when to take readings, how information is sent, and whom to contact. State review hours and the plan for evenings, weekends, and technical failures. Confirm that the patient can demonstrate the necessary steps.
HHS explicitly warns that RPM devices are not emergency tools. Patients should use their emergency plan and emergency services when needed rather than wait for a routine data review. An alert from a device and a message to the clinical team may not have the same meaning or response time.
Illustrative missing-data case
An illustrative program notices that a patient has no new readings. The assigned nurse contacts the patient through the approved workflow and learns that the device displays measurements but is no longer transmitting. The team addresses the technical problem and follows its clinical process for reviewing the gap.
This example shows why a missing upload cannot by itself establish that the patient did not measure or that the patient is clinically stable. It is not a treatment protocol and does not specify a universal response interval.
Evaluate the nursing workload and care process
A local review might examine successful onboarding, missing-data episodes, time to review, unresolved alerts, and patient understanding. Distinguish device-generated notifications from clinically meaningful issues, and distinguish patients enrolled from patients actively transmitting.
Include the work needed for technical support and repeated outreach. Otherwise, the apparent efficiency of remote review can conceal substantial staff time.
Programs should maintain clinical oversight, clear escalation responsibilities, and a way to revise or end monitoring when the service no longer fits the patient's needs.
For the broader question of where an observation came from, see patient-generated health data.
Related
Sources
-
HHS: Getting Started with Remote Patient Monitoring (accessed 2026-09-17).
-
HHS: How Can I Use Remote Patient Monitoring? (accessed 2026-09-17).
-
AHRQ: Health IT Evaluation Toolkit (accessed 2026-09-17).