Avoiding False Claims Act Scrutiny in Remote Patient Monitoring

Remote patient monitoring (RPM) has evolved from a pandemic-era convenience into a core revenue stream for medical practices across multiple specialties. The financial appeal is clear: RPM codes offer recurring reimbursement for chronic condition management that occurs outside the traditional office visit. The compliance risk is equally clear. The Department of Justice (DOJ) and the Office of Inspector General (OIG) have identified RPM as a high-priority enforcement target under the False Claims Act, with investigations focused on practices and vendors that bill for monitoring services that lack clinical substance.

The practices that build RPM programs on solid compliance foundations will retain a valuable revenue stream and improve patient outcomes. Those that prioritize billing volume over clinical integrity will face qui tam lawsuits, OIG audits, and recoupment demands that far exceed the revenue generated.

1. Ensure Clinical Necessity Drives RPM Enrollment

   False Claims Act liability begins with the threshold question of medical necessity. RPM enrollment must be driven by a clinical determination that monitoring will meaningfully contribute to the management of the patient's condition.

   • Establish clinical criteria for RPM eligibility that align with the patient's diagnosis, treatment plan, and risk profile

   • Document the clinical rationale for RPM enrollment in the patient's medical record at the time of initiation

   • Avoid enrolling patients in RPM programs based on financial targets, demographic profiles, or vendor recommendations without clinical justification

   • Conduct periodic clinical reviews of enrolled patients to confirm that RPM continues to serve a medical purpose

   • Remove patients from RPM when monitoring no longer contributes meaningfully to their care plan

2. Verify That Remote Patient Monitoring Data Is Clinically Reviewed and Acted Upon

   Billing for RPM requires that transmitted data is reviewed by a qualified healthcare professional and that clinical decisions are informed by the monitoring results. Passive data collection without clinical engagement does not support RPM billing.

   • Implement workflows that ensure every data transmission is reviewed by a licensed clinician or qualified staff member

   • Document the clinical review of RPM data, including abnormal findings, interventions, and care plan adjustments

   • Establish escalation protocols for data alerts that require immediate clinical intervention

   • Ensure that RPM data reviews are integrated into the patient's clinical record, not siloed in a separate monitoring platform

   • Train staff to distinguish between administrative data processing and clinical data review for billing purposes

3. Meet Time-Based Billing Requirements with Accurate Documentation

   RPM billing codes include time-based requirements that specify the minimum number of minutes of interactive communication and device monitoring per billing period. Time documentation is the most scrutinized element in RPM audits.

   • Implement time-tracking systems that capture the start time, end time, and nature of each RPM activity

   • Ensure that only clinically relevant activities are counted toward time-based billing thresholds

   • Prohibit the aggregation of non-clinical administrative time (data uploads, equipment troubleshooting) toward billing minimums

   • Conduct monthly audits of time documentation to identify patterns that suggest inaccurate or inflated time recording

   • Train all staff involved in RPM on the specific activities that qualify for time-based billing under each CPT code

4. Evaluate Vendor Arrangements for Anti-Kickback Compliance

   Many practices implement RPM through third-party vendors that provide devices, monitoring platforms, and clinical support services. These arrangements must comply with the Anti-Kickback Statute and its safe harbors.

   • Review vendor contracts for provisions that could be interpreted as inducements to refer patients to RPM programs

   • Ensure that device and service pricing reflects fair market value and is not tied to patient enrollment volume

   • Verify that vendor compensation structures do not include per-patient fees that incentivize over-enrollment

   • Confirm that the vendor does not market RPM services directly to patients without the practice's clinical oversight

   • Consult with a healthcare compliance attorney to evaluate the legality of vendor arrangements under applicable safe harbors

5. Address Patient Consent and Engagement Requirements

   RPM programs require patient consent and active patient participation. Billing for patients who are not meaningfully engaged in the monitoring program is a compliance violation.

   • Obtain and document informed consent for RPM enrollment, including an explanation of the monitoring process, data transmission expectations, and any patient costs

   • Establish minimum data transmission thresholds that patients must meet to remain enrolled in the program

   • Implement patient engagement protocols that include reminders, education, and follow-up for patients who are not transmitting data consistently

   • Disenroll patients who are unable or unwilling to participate meaningfully in the monitoring program

   • Document all patient engagement efforts and disenrollment decisions in the medical record

6. Build Audit Readiness into the RPM Program from Day One

   The most effective compliance strategy is designing the RPM program to withstand audit scrutiny from the outset rather than remediating deficiencies after an investigation begins.

   • Develop a written RPM compliance policy that covers enrollment criteria, documentation standards, time tracking, billing procedures, and vendor management

   • Conduct quarterly internal audits of RPM billing, focusing on time documentation, clinical reviews, and medical necessity

   • Maintain a centralized repository of RPM documentation, including consent forms, clinical reviews, data logs, and billing records

   • Include RPM in the practice's annual compliance risk assessment and OIG Work Plan review

   • Engage an independent compliance consultant to conduct an annual RPM program review

Final Takeaway

Remote patient monitoring is a legitimate and valuable clinical tool. It is also one of the most aggressively scrutinized billing categories in healthcare enforcement today. The distinction between a compliant RPM program and a fraudulent one is not the technology or the revenue model. It is the clinical substance behind every enrollment, every data review, and every billed minute. Practices that build their RPM programs around clinical integrity will sustain both the revenue and the trust that the program depends on.

Solstice Group is a healthcare operations consulting firm helping medical and dental practices build sustainable, high-performing businesses. With a background in clinical care and business strategy, we advise practice owners on compliance, revenue optimization, and scalable growth. We can be reached at info@solstice-groups.com or by visiting www.solstice-groups.com.