Key takeaways
- RPM creates a steady stream of non-clinical work: enrollment, consent, device setup, missing-reading outreach, returns.
- Medicare rules shape the workflow: established patients, documented consent, minimum days of data and one billing practitioner per 30 days.
- Front office staff support devices and schedules; readings and alerts always go to clinical staff.
- Decide early who patients call about a device problem: the vendor's support line or your office.
Why RPM lands on the front desk
Remote patient monitoring lets a patient collect health data at home, such as blood pressure, weight or blood sugar, with a connected device that sends the readings automatically to the practice[1]. Clinicians review the data and adjust treatment. That is the clinical picture. The operational picture is different: every enrolled patient generates calls, reminders, device questions and paperwork, and much of it reaches the front office first.
Practices that plan only for the clinical side often find the program stalls at the front desk. Patients call the main line because the cuff will not pair. Readings stop for a week and nobody notices until the billing period closes. A patient who stopped the program still has a device at home. This guide maps that work so you can staff it before you launch.
The rules that shape the workflow
Medicare's requirements are the template most programs follow, and they translate directly into front office tasks. According to CMS, remote physiologic monitoring requires an established patient relationship, must monitor an acute or chronic condition, and requires patient consent at the time RPM services are provided[1]. Data must be collected for 2 to 15 or 16 or more days out of 30, depending on the code billed, and only one practitioner can bill remote monitoring for a patient in a 30-day period[1].
- Established patient: the scheduler confirms the patient has been seen before enrollment.
- Consent: someone documents it, in words the patient understands, before the device ships.
- Days of data: someone watches for patients whose readings stop.
- One billing practitioner: intake asks whether another practice already monitors the patient.
- FDA-defined medical device: the device used to collect and transmit data must meet that definition, so staff do not substitute a consumer gadget[1].
- Auxiliary personnel can provide services under general supervision of the billing practitioner[1], which is why trained staff, not only clinicians, carry much of the day-to-day work.
Medicare matters because it covers a large share of the patients most likely to enroll. Medicare covered 20.1% of the US population in 2025, alongside employment-based insurance at 53.5% and Medicaid at 17.1%[2]. Commercial and Medicaid plans set their own RPM rules, so check each payer before enrolling its members.
The calls RPM generates
| Call or task | Typical trigger | Who handles it | Front office action |
|---|---|---|---|
| Enrollment questions | Provider recommends RPM | Front office or RPM coordinator | Explain the program, cost-sharing and consent; book setup |
| Device setup help | Device arrives at home | Vendor support or coordinator | Warm transfer or scheduled setup call |
| Pairing or connection failure | Readings not arriving | Vendor support | Log the issue; transfer; check readings next day |
| Missing readings outreach | No data for several days | Coordinator | Call patient with reminder script |
| Reading or symptom question | Patient worried about a number | Clinical staff | Transfer to nurse; emergency script if needed |
| Billing question | Statement shows RPM charges | Billing | Explain monthly service; route disputes |
| Stop or pause request | Patient traveling or opting out | Coordinator | Document; arrange device return |
The row that matters most is the reading or symptom question. Front office staff should never interpret a reading. They transfer to clinical staff, and if a caller describes an emergency, they tell the caller to hang up and call 911.
Enrollment, step by step
Provider identifies the patient
A provider orders RPM for an eligible established patient with a documented condition and a reason to monitor.
Coordinator explains the program
What the device does, how often to use it, who reviews readings, what it may cost the patient and how to stop.
Consent is documented
Record the patient's consent in the chart, with the date and who obtained it.
Coverage is checked
Confirm the payer covers RPM and whether another practice already bills monitoring for this patient.
Device is ordered
Order through the vendor with the right shipping address and phone number, and note the device serial number.
Setup is booked
Schedule a short setup call or in-office session within a few days of delivery.
First reading confirmed
Check that the first reading arrived. Until it does, the patient is not really enrolled.
Device setup support
Most patients can manage a device with a little help, but the help must be ready. About 91% of US adults own a smartphone[3], and many RPM devices use cellular connections that need no phone at all, which suits patients without one. Language is a bigger barrier than technology for some patients: about 9.0% of US residents aged 5 and over speak English less than very well[4]. Ask the vendor for setup guides and support in the languages your patients speak.
Example setup call script: 'Hi, this is Maria from Oak Valley Primary Care. Your blood pressure cuff should have arrived. Do you have it with you? Great. Let us put it on together and take one reading while I am on the line, so I can check it reached us. You will use it once a day, at about the same time. If it ever shows an error, call the number on the sticker on the box.'
Missing readings: the quiet failure
The most common operational failure is silence. A patient stops taking readings because the device moved to a different room, the batteries died or they simply forgot. Because billing depends on days of data in each 30-day period, a gap discovered at the end of the month is too late to fix. Build a simple daily list of patients with no reading for three days, and work it every morning.
- Day 3 with no data: automated reminder by text or call, if the patient agreed to it.
- Day 5: a staff call using a short script, checking the device and the routine.
- Day 7: tell the clinical team, who may decide to pause or change the plan.
- Every call: note the reason, so you can see patterns such as one device model that disconnects.
Working with the RPM vendor
RPM vendors range from device suppliers to full-service companies that provide nurses and monitoring. Any vendor that receives readings and patient details for you is a business associate. A covered entity may let a vendor handle that information only with satisfactory assurance, in a business associate agreement, that the vendor will safeguard it[5].
- Who answers patient device calls, at what hours, and in which languages?
- Can patients reach vendor support directly, or does every call come through our main line?
- How do we see which patients have had no readings, and how quickly?
- How are devices shipped, replaced and returned, and who pays for lost devices?
- Where do readings appear in our EHR, and who is alerted for out-of-range values?
Estimating the staff time
Example: a fictional four-provider internal medicine practice planned a program of 60 patients. It estimated about 20 minutes per new enrollment for explanation, consent and ordering, 15 minutes per setup call, and about five outreach calls a day for missing readings once the program was running. In the first month, with all 60 patients enrolling, that came to roughly 35 hours of non-clinical work. After that it settled near 8 hours a week. The practice gave the work to one part-time coordinator rather than spreading it across the front desk.
Your numbers will differ, but the shape is common: a heavy launch, then steady weekly work. Plan the launch in waves of 10 to 15 patients so setup calls do not collide with the normal phone peak.
Pausing, stopping and returns
Patients travel, are admitted to the hospital, change insurance or decide the program is not for them. Each of those needs a documented pause or stop, a note to billing, and a plan for the device. Send a prepaid return label with clear instructions, track returns weekly, and stop billing on the day the patient leaves the program. A monthly reconciliation between enrolled patients, active devices and billed patients catches most errors before they reach a claim.
Launch checklist for the front office
- A named coordinator and backup, with protected time on the schedule.
- A one-page explanation for patients covering what the device does, who reviews readings, possible costs and how to stop.
- A consent template in the EHR, with the date and the staff member who obtained it.
- A daily missing-readings list and the outreach script.
- Clear routing: device problems to vendor support, readings and symptoms to clinical staff, emergencies to 911.
- A monthly reconciliation of enrolled patients, active devices and billed patients.
If any line on this list has no owner, wait before enrolling the first wave. It is far easier to start a program with these habits than to retrofit them after 60 devices are already in patients' homes.
Frequently asked questions
Can front desk staff handle RPM readings?
No. Front office staff can handle enrollment, setup support, reminders and returns. Readings, out-of-range values and symptom questions always go to clinical staff, and emergencies get the call 911 message.
Does Medicare require consent for remote patient monitoring?
Yes. CMS requires patient consent at the time RPM services are provided. Document it in the chart before the device ships.
How many days of readings are needed?
Under CMS rules, data must be collected for 2 to 15 or 16 or more days in a 30-day period, depending on the code. Check each payer's rules for non-Medicare patients.
Who should patients call when a device does not work?
Decide before launch. Many practices give patients the vendor's support number for device problems and the practice number for clinical questions, and print both on the device.
References
Centers for Medicare & Medicaid Services (CMS), Medicare Learning Network (2025). Telehealth & Remote Monitoring (MLN Booklet MLN901705, December 2025) (opens in a new tab) โ
U.S. Census Bureau (2025). Health Insurance Coverage in the United States: 2025 (Current Population Reports P60-291) (opens in a new tab) โ
Pew Research Center (2026). Americans' Use of Mobile Devices in 2026 (Mobile Fact Sheet) (opens in a new tab) โ
U.S. Census Bureau (2024). GCT1603: Percent of People 5 Years and Over Who Speak English Less Than 'Very Well' (2024 ACS 1-year) (opens in a new tab) โ
Legal Information Institute, Cornell Law School (current). 45 CFR ยง 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) โ