How to Start an RPM Program in Primary Care: A Step-by-Step Guide

Setting up remote patient monitoring in a primary care practice can feel overwhelming. Between device logistics, billing codes, consent requirements, and staff workflows, it is easy to stall before you ever enroll your first patient. But for practices with sizeable diabetic populations, RPM is one of the highest-impact programs you can implement, both clinically and financially.

This guide walks you through exactly how to start an RPM program in primary care, from initial patient selection to ongoing compliance tracking. It is written for physicians and practice managers who want a realistic, actionable plan rather than a theoretical overview.

Why Diabetic Patients Are the Ideal Starting Population

Before jumping into logistics, it is worth understanding why diabetes-focused RPM programs have the highest success rate for new implementations.

Diabetic patients already engage in daily self-monitoring (blood glucose readings), which maps directly to the 16-day-per-month transmission requirement for CPT 99454. They are clinically high-risk, making payers more receptive to RPM claims. And the clinical feedback loop, where providers adjust medications based on trend data, is well-established in endocrinology and primary care alike.

Starting with diabetic patients gives your team a cohesive protocol to learn on before expanding to hypertension, CHF, or COPD populations.

Step 1: Define Your Patient Selection Criteria

Not every diabetic patient is a good RPM candidate. You need clear inclusion and exclusion criteria before you begin outreach.

Strong RPM candidates typically have:

• Type 2 diabetes with an A1C above 7.5%
• Active insulin or sulfonylurea therapy requiring glucose monitoring
• A history of hypoglycemic or hyperglycemic episodes
• Medicare or a commercial payer that reimburses RPM codes
• Sufficient cognitive ability to use a connected glucometer (or a caregiver who can assist)

Patients to defer initially:

• Those with unstable housing or no reliable cellular/Wi-Fi connectivity
• Patients who have declined home monitoring in the past
• Individuals already enrolled in another remote monitoring program (e.g., a health plan-sponsored program)

Tip: Start with a target list of 25-50 patients. This is large enough to generate meaningful revenue but small enough for your team to learn the workflows without being overwhelmed.

Step 2: Select Your Devices and Connectivity Model

For diabetic RPM, you need a cellular-connected blood glucose meter that transmits readings automatically to your practice. The key word is “automatically”; devices that require the patient to manually sync via an app create friction and lower adherence.

Device selection criteria:

• FDA-cleared cellular-enabled glucometer
• Automatic daily transmission without patient intervention
• Compatible test strip supply chain (strips are often the bottleneck, not the meter)
• Vendor provides replacement devices and technical support

You will also need to decide on your connectivity model. Cellular-enabled devices that transmit over LTE are strongly preferred over Bluetooth-to-phone setups, because they do not depend on the patient owning or operating a smartphone.

Tip: Negotiate device pricing based on volume commitments. Most device vendors offer tiered per-patient pricing that improves with scale.

Step 3: Build Your Consent and Enrollment Workflow

CMS requires documented patient consent before you can bill for RPM services. This is not optional, and retroactive consent will not hold up to an audit.

Your consent workflow should cover:

1. Verbal or written consent that the patient agrees to receive RPM services
2. Explanation of what data will be collected and how it will be used
3. Notification that the patient may receive cost-sharing (copays or coinsurance)
4. Documentation in the EHR with a date stamp and the name of the staff member who obtained consent

Many practices build a standardized consent template and train their medical assistants to handle enrollment during routine office visits. This is far more effective than cold-calling patients from a list.

Enrollment Visit Workflow

During the enrollment visit (billable under CPT 99453), your staff should:

• Obtain and document consent
• Provide the device and test strips
• Train the patient on device use (even if it is simple, document the education)
• Confirm a successful test reading transmits to your platform
• Set expectations: “We will be reviewing your readings and may call you if we see something concerning”

Step 4: Establish Staff Roles and Train Your Team

RPM programs fail when no one owns the daily workflow. You need clear role assignments before launch.

Typical role structure for a small practice:

Role	Responsibility	Time Commitment
Physician / NP	Order RPM, review escalated alerts, monthly care management	5-10 min per patient per month
RN / Clinical Staff	Daily reading review, patient outreach for missing readings, log clinical time	15-25 min per patient per month
MA / Front Desk	Consent collection, device distribution, enrollment documentation	10-15 min per patient (one-time)
Billing Staff	Claims submission for 99453, 99454, 99457, 99458	5 min per patient per month

Tip: The biggest staffing mistake is assigning RPM as a side task to someone who is already fully utilized. Even a panel of 50 patients requires a dedicated block of time, typically 60 to 90 minutes per day for clinical review and outreach.

Staff Training Checklist

Before go-live, ensure every team member can answer:

• How do I enroll a patient and document consent?
• How do I check if a patient has transmitted readings today?
• What do I do if a reading is critically high or low?
• How do I log my clinical time for billing?
• What are the minimum thresholds for billing each CPT code this month?

Step 5: Configure Your Billing and Documentation Process

RPM billing is where most programs leak revenue. The codes are straightforward, but the documentation requirements are specific and unforgiving.

The four codes you will use:

• 99453: Initial setup and patient education (billed once)
• 99454: Device supply with at least 16 days of readings per 30-day period (billed monthly)
• 99457: First 20 minutes of clinical staff time in a calendar month (billed monthly)
• 99458: Each additional 20 minutes of clinical staff time (billed monthly, add-on)

The most common failure point is 99454: if a patient only transmits readings on 15 days in a month, you cannot bill the code. Your team needs a system to monitor transmission adherence in real time, not at the end of the month when it is too late to intervene.

For 99457 and 99458, clinical staff must log their time accurately. Phone calls, reading reviews, care plan updates, and coordination all count, but the time must be documented with start and end timestamps.

Tip: Build a mid-month checkpoint into your workflow. Around day 15, review which patients are below the 16-day threshold and have your clinical staff reach out to encourage adherence. This single habit can increase your 99454 billing rate by 20-30%.

Step 6: Set Up Compliance Tracking and Audit Readiness

CMS audits of RPM claims are increasing. Your program needs to be audit-ready from day one, not retrofitted after a request for records.

Compliance essentials:

• Consent documentation with dates for every enrolled patient
• Device assignment records (which patient received which device, and when)
• Daily transmission logs showing dates and readings
• Clinical time logs with timestamps, staff name, and activities performed
• Monthly billing reconciliation: did we meet the requirements for every code we billed?

If you are managing this in spreadsheets, it will work for 10 patients. It will not work for 50 or 100. Most practices that scale beyond a pilot phase need dedicated software to track transmission days, aggregate clinical time, and flag billing eligibility automatically.

Step 7: Launch, Monitor, and Iterate

Do not plan a perfect launch. Plan a controlled one. Enroll your first 10 patients in week one, learn from the friction, and expand.

Realistic 4-Week Launch Timeline

Week	Activity	Goal
Week 1	Finalize patient list, complete staff training, configure devices and platform	Ready to enroll
Week 2	Enroll first 10-15 patients during scheduled visits, distribute devices, document consent	First readings flowing
Week 3	Begin daily clinical review workflow, troubleshoot device and connectivity issues, start logging clinical time	Stable daily operations
Week 4	Enroll next batch of 10-15 patients, submit first billing claims (99453 for all, 99454 and 99457 for eligible patients), review denial rates	First revenue cycle complete

After month one, hold a team retrospective. Common issues to address:

• Which patients are not transmitting consistently? Why?
• Is clinical staff time being captured accurately?
• Are there device or connectivity problems recurring with specific patients?
• Did any claims get denied, and what was the reason?

Step 8: Scale With Automation

Once your workflows are stable with 25-50 patients, the manual overhead of tracking transmissions, logging time, and reconciling billing eligibility starts to compound. This is the point where most practices either plateau or invest in automation.

Platforms like Zayd Health are built specifically for this inflection point, automating the compliance tracking, transmission monitoring, and billing reconciliation that consume staff time as panels grow. Rather than hiring additional staff to manage spreadsheets, the right software keeps your per-patient cost flat as you scale from 50 to 500 patients.

Common Mistakes to Avoid

Launching too broadly. Starting with 200 patients on day one guarantees workflow breakdowns. Start small, get the processes right, then expand.

Ignoring the 16-day rule. If you are not actively monitoring transmission adherence mid-month, you are leaving 99454 revenue on the table every billing cycle.

Treating RPM as a set-and-forget program. Patients need periodic re-engagement. Devices need replacement. Clinical protocols need updating. Budget 30 minutes per week for program management beyond direct patient care.

Not documenting clinical time in real time. Reconstructing time logs at the end of the month is inaccurate and audit-risky. Use a timer or time-tracking tool during every patient interaction.

Your First 30 Days

You do not need a six-month implementation plan to start an RPM program. You need a patient list, a device vendor, a consent form, and a staff member who owns the workflow. The technical and billing complexity is real, but it is manageable when you start with a focused diabetic population and expand methodically.

The practices that succeed with RPM are not the ones with the most sophisticated technology. They are the ones that build repeatable daily habits: checking readings, logging time, reaching out to non-adherent patients, and holding themselves accountable to doing it consistently.

Start with 25 patients. Get your first clean billing cycle under your belt. Then scale from a position of confidence.