Remote patient monitoring (RPM) and chronic care management (CCM) programs continue to expand, but the workflows, documentation controls, and oversight needed to support them do not always mature at the same pace.
These services can help healthcare organizations proactively manage chronic disease and keep patients connected to care between visits. However, sustainable growth requires more than simply launching a program and billing for services.
As adoption grows, regulators are paying attention. A September 2024 HHS Office of Inspector General report found that approximately 43% of Medicare enrollees who received RPM did not receive all three components of the service: collection of health data through a connected device, transmission of that data to the provider, and provider review and management of the information to guide treatment.
The finding underscores that RPM and CCM require more than accurate coding. They depend on coordinated clinical, operational, and compliance controls.
For healthcare leaders, a useful framework is straightforward: Clinical need should drive the service. The workflow should deliver it. Documentation should substantiate it. Billing should follow it.
When those elements fall out of alignment, a clinically valuable program can create compliance risk.
Start With the Patient, Not the Code
CCM generally involves patients with two or more chronic conditions requiring ongoing management. Sustainable programs should include structured care planning, patient outreach, prescription management, and care coordination.
RPM uses connected devices to collect and transmit patient health data, such as blood pressure, glucose readings, or weight, so practitioners can evaluate trends and manage care.
In both cases, the starting point should be clinical need, not reimbursement.
For CCM, organizations must determine whether patients meet applicable eligibility requirements, including the nature and expected duration of chronic conditions. The comprehensive care plan should function as a dynamic management tool, not a static enrollment document.
For RPM, transmitting data alone is not enough. Practitioners must be able to review, interpret, and meaningfully incorporate that information into patient management. Technology and workflows should support medically necessary care, not create activity solely to satisfy a billing threshold.
Build Compliance into the Workflow
A strong control environment establishes clear ownership for patient eligibility, consent, service delivery, time capture, billing validation, and auditing.
Medical assistants, nurses, and other ancillary team members may perform permitted activities, but organizations should establish clear guidelines regarding which services may be delegated and which require physician or qualified non-physician practitioner involvement. The use of ancillary staff does not eliminate provider oversight, involvement, or documentation responsibilities.
Documentation presents a similar challenge. Accumulating enough minutes does not establish that a billable service occurred. Documentation should clearly demonstrate what was done, how the activity contributed to patient management, and whether the recorded time is credible.
For example, an entry stating, “faxed information to the pharmacy—five minutes,” may leave a reviewer unable to determine what work was performed, why it was necessary, or whether the documentation supports the reported time.
When documentation and services do not support what is billed, operational weaknesses can become compliance risks.
Remote Patient Monitoring Requires More Than a Connected Device
Effective RPM requires more than deploying technology. The operating model should define device onboarding, data transmission, clinical review processes, and responsibility for responding to meaningful changes in a patient’s condition.
The more important question is, “What value does this data bring to the patient’s care?”
If practitioners cannot meaningfully evaluate the information and use it to guide patient management, the technology is not fulfilling the purpose of RPM.
Make Consent Part of the Workflow
To patients, remote care management may feel like a routine phone call, text message, or follow-up interaction. However, when those interactions are part of a billable service, patients should understand what services they are receiving and any potential cost-sharing obligations.
Consent should be integrated into the workflow rather than treated as a one-time administrative task. Written consent can provide additional evidence that the service, its benefits, and associated financial responsibilities were explained.
The control environment should also include ongoing monitoring as patient eligibility, care plans, workflows, and applicable requirements evolve.
Evaluate Vendor Incentives & Validate the Work
Outsourcing a service does not outsource compliance responsibility. Vendor oversight should include review of documentation, time capture practices, patient communication, staffing models, contractual arrangements, and financial relationships.
Organizations should also implement controls to review vendor-generated documentation and validate that the services performed substantiate what is ultimately billed.
Consider technology that alerts staff when documented time does not meet a required billing threshold. While operationally useful, these prompts can create incentives to focus on achieving billable time rather than ensuring services are driven by clinical need and supported by appropriate documentation.
Due diligence should extend beyond technology capabilities to assess whether a vendor’s workflows promote documentation, service delivery, and billing practices that align with applicable regulatory and compliance requirements.
Build the Foundation Before You Scale
RPM and CCM can strengthen chronic disease management and patient engagement. Before expanding either program, healthcare leaders should be able to answer four fundamental questions:
- Can we demonstrate that patients meet applicable eligibility criteria?
- Can our documentation substantiate the services and time we bill?
- Can we demonstrate appropriate provider involvement and oversight?
- Do we independently validate vendor documentation, time capture, and billing-related workflows?
Together, these questions test whether an organization’s clinical, operational, and compliance controls are keeping pace with program growth. Organizations that prioritize aligned compliance controls are better positioned to expand RPM and CCM programs while supporting sustainable, compliant, and patient-centered care.
Ready to strengthen your RPM or CCM program? Connect with VMG Health to evaluate compliance risks, assess operational controls, and build scalable programs that support patient care, documentation integrity, and compliant billing.
